> For 4 it's really the community's responsibility, the developers will > code and answer questions but it's the end users that should be helping > to make the wiki work.
One of my pet peeves this, so I'm afraid I've got to comment :). (Oh and I work as a Software Engineer btw). Developers writing code without writing any documentation, or at least a basic explanation isn't really any help to anyone. If you write the worlds most wonderful and helpful code but hide it away and never explain to anyone how to use it, or what it does, what is the point in the code? I realise this is open source, and people are writing the code for fun in their spare time (and writing code is more fun than writing doc for it), but I would really like to see at least basic updates to the wiki as a requirement of adding a feature into Freevo. This would mean that at very least new features came with a skeleton page in the wiki explaining their purpose, simple activation, and one or two config examples. Users can expand on that and provide their real world examples. I don't think that the blame can be placed on the users for not providing documentation for other peoples work. Yes they can help by documenting things as they find them out, but the person who really knows how a feature works is the person that wrote it :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
