Re: [gentoo-dev] A proposal for discussion

[Mike Frysinger <vapier@gentoo.org>]

i would have to disagree on this ...
running a todo list is kind of out of scope of opening public access to the
-core list.  plus, turning -core into the center of todo operations is outside
the scode of the -core list.
discussions that happen on -core are meant for the 'core' of Gentoo.
also, as we've seen in the past, some topics that are discussed on -core
can lead to an explosion of misguided discussions.
-mike

On Monday 30 September 2002 12:12 am, k wrote:
> there seems to be a cultural issue here as well, in that core development
> takes place beyond public introspection. without the knowledge transfer and
> insight into core direction that naturally takes place on such core lists,
> 'outsiders' will be at a natural communication disjoint when trying to work
> on tasks. at a minimum opening up the archives to public inspection should
> accompany any todo list, and in my opinion should be accessible regardless
> of the outcome of any todo list initiative.
>
> two cents,
>
> -k
>
> On Friday 27 September 2002 03:13 pm, Fred Van Andel wrote:
> > Gentoo is a rapidly growing distribution, with that growth comes
> > a number of problems. The workload on the core development team
> > is increasing all the time and if something is not done to address
> > it the development of Gentoo will suffer.
> >
> > It is clear that there are many dedicated individuals involved in
> > Gentoo who are not involved as part of the development team. Its
> > only necessary to monitor one of the mailing lists or browse
> > through the support forums to realize that. A lot of these people
> > may not be qualified to be a full-fledged member of the core
> > development team but they still have skills/time to offer back to
> > the community.
> >
> > Therefore I propose that a public ToDo list be created along with
> > a list coordinator so that the talents of these people can be used.
> > Tasks would be posted on the public list and assigned to specific
> > individuals who volunteer. Tasks should be kept specific rather
> > than open-ended and have a scheduled completion date, if necessary
> > tasks can be broken up into smaller independent tasks to achieve
> > these goals.
> >
> > By the creation of such a list we could help free up the core
> > developers to do other things, and at the same time speed up the
> > completion of many of the necessary but routine tasks that seem to
> > take up so much time.  By taking some of the workload off of the
> > developers we can allow them to do what they do best, and that is
> > to develop and refine the features that have attracted us to Gentoo
> > in the first place.
> >
> > Some tasks that might be suitable for inclusion on the list:
> >    - Creation and proofreading of new translations of the
> >      documentation.
> >    - Monitoring of the package list for version changes.
> >    - Creation of a troubleshooting guide based on the Q & A from
> >      the mailing lists and forums.
> >    - Testing of the ebuild scripts/compilation on less common
> >      platforms.
> >    - Creation of new ebuild scripts base on user requests.
> >    - Updating/testing of ebuild scripts when new versions of
> >      packages are developed.
> >   - The role of ToDo list coordinator(s)
> >
> > The core developers should be in control of the contents of the
> > list to prevent a loss of focus and would have veto powers over the
> > tasks to be assigned and the results of the completed tasks.
> >
> > I now having said my piece I open it up for public discussion.
> >
> > Fred Van Andel
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev