On 05/12/2014 06:51 PM, [email protected] wrote:
Anyway, from a packager and developer point of view
I still see significant need to work on our guidance
for new contributors. So, other than packagers and
a few extra methods to increase the quality of packages,
that is, strong rules about checking packages functionality
as well as having people also actually testing them, we
also need good writers to document all procedures, suggest
how to make them easier and/or more standardized, so that
new people would loose less time searching around on how
to get things done, or who to ask for help in irc, mailing
lists, etc.
Yes, this is one of the things we were discussing at LinuxTag, too.
Another thing is that it would be nice to have some TODO lists for
people who would like to contribute but don't know what tasks are of
major priority.
The practice shows that it is not convenient to simply send potential
volunteers to bugzilla or openproject or other complex tools. It would
be nice to have some simple wiki page with TODO items, maybe grouped
according to different criteria (complexity, programming language,
etc.). E.g., even Linux kernel has TODO files in its sources with clear
and explicit tasks.
--
Denis Silakov, ROSA Laboratory.
www.rosalab.ru
