| 1 |
there seems to be a cultural issue here as well, in that core development |
| 2 |
takes place beyond public introspection. without the knowledge transfer and |
| 3 |
insight into core direction that naturally takes place on such core lists, |
| 4 |
'outsiders' will be at a natural communication disjoint when trying to work |
| 5 |
on tasks. at a minimum opening up the archives to public inspection should |
| 6 |
accompany any todo list, and in my opinion should be accessible regardless of |
| 7 |
the outcome of any todo list initiative. |
| 8 |
|
| 9 |
two cents, |
| 10 |
|
| 11 |
-k |
| 12 |
|
| 13 |
|
| 14 |
On Friday 27 September 2002 03:13 pm, Fred Van Andel wrote: |
| 15 |
> Gentoo is a rapidly growing distribution, with that growth comes |
| 16 |
> a number of problems. The workload on the core development team |
| 17 |
> is increasing all the time and if something is not done to address |
| 18 |
> it the development of Gentoo will suffer. |
| 19 |
> |
| 20 |
> It is clear that there are many dedicated individuals involved in |
| 21 |
> Gentoo who are not involved as part of the development team. Its |
| 22 |
> only necessary to monitor one of the mailing lists or browse |
| 23 |
> through the support forums to realize that. A lot of these people |
| 24 |
> may not be qualified to be a full-fledged member of the core |
| 25 |
> development team but they still have skills/time to offer back to |
| 26 |
> the community. |
| 27 |
> |
| 28 |
> Therefore I propose that a public ToDo list be created along with |
| 29 |
> a list coordinator so that the talents of these people can be used. |
| 30 |
> Tasks would be posted on the public list and assigned to specific |
| 31 |
> individuals who volunteer. Tasks should be kept specific rather |
| 32 |
> than open-ended and have a scheduled completion date, if necessary |
| 33 |
> tasks can be broken up into smaller independent tasks to achieve |
| 34 |
> these goals. |
| 35 |
> |
| 36 |
> By the creation of such a list we could help free up the core |
| 37 |
> developers to do other things, and at the same time speed up the |
| 38 |
> completion of many of the necessary but routine tasks that seem to |
| 39 |
> take up so much time. By taking some of the workload off of the |
| 40 |
> developers we can allow them to do what they do best, and that is |
| 41 |
> to develop and refine the features that have attracted us to Gentoo |
| 42 |
> in the first place. |
| 43 |
> |
| 44 |
> Some tasks that might be suitable for inclusion on the list: |
| 45 |
> - Creation and proofreading of new translations of the |
| 46 |
> documentation. |
| 47 |
> - Monitoring of the package list for version changes. |
| 48 |
> - Creation of a troubleshooting guide based on the Q & A from |
| 49 |
> the mailing lists and forums. |
| 50 |
> - Testing of the ebuild scripts/compilation on less common |
| 51 |
> platforms. |
| 52 |
> - Creation of new ebuild scripts base on user requests. |
| 53 |
> - Updating/testing of ebuild scripts when new versions of |
| 54 |
> packages are developed. |
| 55 |
> - The role of ToDo list coordinator(s) |
| 56 |
> |
| 57 |
> The core developers should be in control of the contents of the |
| 58 |
> list to prevent a loss of focus and would have veto powers over the |
| 59 |
> tasks to be assigned and the results of the completed tasks. |
| 60 |
> |
| 61 |
> I now having said my piece I open it up for public discussion. |
| 62 |
> |
| 63 |
> Fred Van Andel |
| 64 |
> |
| 65 |
> _______________________________________________ |
| 66 |
> gentoo-dev mailing list |
| 67 |
> gentoo-dev@g.o |
| 68 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
Archives