| 1 |
On 20/03/06, Ciaran McCreesh <ciaranm@g.o> wrote: |
| 2 |
> |
| 3 |
> On Mon, 20 Mar 2006 23:07:37 +0000 Daniel Drake <dsd@g.o> wrote: |
| 4 |
> | One of the bigger problems is that we have a huge user community who |
| 5 |
> | are keen on contributing, but we have such a high barrier for entry |
| 6 |
> | to the developer community. Quite rightly so - we're dealing with a |
| 7 |
> | live tree, so we can't give out commit access on the street. |
| 8 |
> |
| 9 |
> A relatively easy way of lowering that barrier would be to provide |
| 10 |
> good, up to date, example-oriented ebuild writing documentation. |
| 11 |
> There's too much stuff that people need to know to write ebuilds that's |
| 12 |
> not written down anywhere -- this not only makes it harder for users to |
| 13 |
> write good ebuilds, but also leads to some of them being dissuaded when |
| 14 |
> they're told that the only way to know what's policy is by having paid |
| 15 |
> attention on the mailing lists for the past five years. |
| 16 |
> |
| 17 |
> Bridge the gap between the developers and the users and you have a user |
| 18 |
community that has a better knowlege of the distro and it's working and you |
| 19 |
have a developeer community more in touch with it's users. Most people would |
| 20 |
love to help but knowing where to start is the greatest challenge, make it |
| 21 |
easy for them to know how to be a developer and then they can decide if they |
| 22 |
have something to contribute. As Ciaran said, up-to-date ebuild |
| 23 |
documentation is a must but it needs a bit of "the idiots guide to ebuilds" |
| 24 |
style to it. Also a big assumption is made that people know how to use CVS |
| 25 |
and other systems. |
| 26 |
|
| 27 |
"Book them and they will come..." |
| 28 |
|
| 29 |
George |
Archives