None currently, Aaron helped wean me from my psychological dependence on kdesrc-build
Aaron generally organizes then polishes, Some users may be offended by misspellings or hanging links to pages that do not exist, and making placeholders for content that he thinks should go there.
He likes using categories whenever possible.
I find that wiki's especially, mediawiki, get misused when in techbase role. It is important to use Categories, and NOT subdirectories so that wiki linking becomes easy. Filing something under Getting Started is a horrible way to do it, because the item will also be related to the [[Topic]] In general, sub pages should be used only if the topic page is too large, and the additional content is exclusive to the topic. I hope to re-arrange the wiki to make it easier to navigate.
Aaron will move content about and adjust sentence structure to get right to the point. He rarely deletes content, rather, prefers to move it to new pages.
I talk a lot, I am learning about projects that i interact with, and hope that I am actually contributing. I want to give a high signal to noise, and I have a lot of time right now (July 2010) and am running with high enthusiasm.
Aaron generally cares a great deal about the projects he works on and would very much enjoy talking with what they are working on, and requests help learning this stuff.
Telephone: 206 334 5925
Part of my creativity comes from experimentation. I try a lot of things, and I believe i have a talent for testing software, and creating user interfaces.
I file a lot of bugs and wishlist items. Often the fix is not trivial, and does not fit exactly in the category I put the item... because I have no idea where it should go. For example, I don't think we should program based on click, double click, drag, I think we need more abstract concepts .
I have filed bugs for bugzilla at mozilla regarding micropayment integration, and I tend to prefer Mantis as a bug/feature tracker. I also very much think that searching for existing bugs should go thru closed bugs and not just open bugs.
Aaron has enjoyed using applications made in KDE and QT for quite some time, and has posted bugs. He would like to be considered a usability contributer and is attempting to set up a build environment to actually fix some of the behavior he cares deeply about.
an example would be a slide-lock on an iphone, a double click, or similar
a confirmation dialog/interuption of user is required.
a confirmation dialog may be requried.
-- The active user interface field is IN the plasmoid, so one less click. (first seen with IE4beta but then removed.. also seen in KDE3)
(wishlist/bug filed: https://bugs.kde.org/show_bug.cgi?id=245124 ) Spent many many hours reading api / source code etc trying to figure this out ;) still
<notmart> MrDarkUser: you reimplement void Applet::createConfigurationInterface(KConfigDialog *parent)
. Need to have a filter on incoming messages, and present a log view. Would like to implement a time and check condition capability, conditions to check would be file is filesize, window has gotten focus, other things to help knotify if it should pop up that annyoing dialog. Also the application can send information like how many it expects to send.
Would like all kinds of things to get logged. Deletion of files, trash cleared..... tons of stuff would be great to keep track of. sorting it would be a pain tho.
kreactor overheard a conversation and started thinking about using it to make a social networking portal alternative -- standards based websites that people put up themselves (already a project) (facebook afterall, is just a glorified, centralized log analyzer that can trigger alarms) We could eventually string all of our instant messages thru our log analyzer, have it show us what we want, and retransmit based on rules if certain conditions are met.
While it is great that you are editing this wiki, I really do not feel the edits you have made to this article aid new contributors.
Looking at the after/before edits (respectively): http://techbase.kde.org/Getting_Started http://techbase.kde.org/index.php?title=Getting_Started&oldid=43418
The latter definitely seems more cleanly organized and easier for a beginning contributor to disect. Keep in mind that the people we are attempting to target, will almost *definitely* be unsure of their abilities, unsure of whether working on KDE is easy, or even possible. It is best to not throw a ton of information their way all at once. It needs to be easy for them to digest...Not only that, there are a ton of dead links everywhere..so the visitor really gets the impression that we are..lacking, I suppose.
Personally, I like the old-style one that I listed, more. While it wasn't perfect, it was simple and somewhat concise. And the banner-like objects helped break it down, and looked attractive while doing so. Then from there, the user was led to a series of more technical articles(although I think it was pretty much one big one after that..the separation is still very important. although, even in the older versions, there is of course still room for improvement).
I am planning on reverting your changes, either by a full revert, or by a manual bit-by-bit one...depending on how much information was gained/lost between the versions. This is if I don't hear a response from you in some random amount of time...
I really do not want new-comers to see the page like this, which is why I am being semi-expedient with this. contact me at email@example.com so we can discuss this. Or just reply to this. (I couldn't find your e-mail, so I just posted this thing here).
Fulldecent 01:26, 16 December 2010 (UTC) I agree that this is less appealing. I currently maintain kde.org/getinvolved and hear about people that are having trouble getting KDE set up. I will attempt to edit this page in the following way: I will add a graphic up front that describes the different choices a user has. Then, I will attempt to move some of the detailed links on this page (eg setting up with git) down into another related page (eg setting up with svn) so that this is focused on getting a user to quickly make a decision on the path they want and get started. Will Entriken 484-843-1313, firstname.lastname@example.org