Julien Gilli wrote:
> Currently, the policy is that we don't give write access to anybody. The
reason is not that we don't want people to have write access to Trac
(it's quite the contrary, actually), but it's that we're not ready yet
to handle the workload generated by trying to keep a coherent
documentation while having a lot of writers.
With the past version of Trac, we had a "registration" module that
allowed people to create a Trac account in a few seconds. They could,
when registered, create tickets and comment them. This registration
module has gone with the last Trac upgrade, unfortunately.
Since there are more and more people contributing significantly to the
software, and because they always made insightful comments and
suggestions (like you did), it might be the time to open our Trac
environment more than what it is currently. I'll keep you informed about
the evolution of this policy shortly.
If these are some things you are currently thinking about, there was one other
thing I'll share. Some time ago i saw someone asking about write permission to
the subversion repository as well. Understandably, that is something even more
difficult to just give out to anyone who asks.
I've recently been involved in Drupal development. They use their ticketing
system also to distribute and evaluate patches. So if there is a bug, and Joe
Random Hacker fixes it, he will add it as an attachment to the bug (this is
quite normal also in many oss projects I presume). When the fix has been
evaluated and accepted, a core developer with wite access then applies the patch
and commits it to subversion.
This system is also used to introduce new code, i.e. you issue a feature request
and then the code to implement the feature.
I've found this is a nice way to get more people to contribute code via a
structured process, but still be able to keep the group with write access to
subversion at a controllable size. Same goes for translations, which really
wouldn't need to be distributed on a discussion list (although it doesn't bother
me either.) Therefore, if you'd open up registration to Trac, it would solve
this problem too.
henrik
--
[EMAIL PROTECTED]
+358-40-5697354
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
