-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Boos skrev 23-06-2008 20:31:
| Scott Bussinger wrote:
(...)
|> 2) A definite show of support from the active developers on the
|> project to actually implement some of the popular features requested
|> (either in the core or as a supported plugin).
|>
|
| That does happen, I should make another report, similar to {32} but for
| what has already been accomplished.
| Here it is: http://trac.edgewall.org/report/33
|
| Now the problem is to find those active developers ... the solution
| being, become an active developer yourself!
|
(...)
| Well, lobbying is one thing, getting effectively involved is another,
| and more effective in the long run. There are many ways to help the
| project, Jani mentioned setting up a documentation team, Jeroen is
| motivating people around the world to contribute translations, etc.
| Before making the more ambitious changes that usually correspond to
| long-standing issues, it is possible for anyone to start getting more
| involved by tackling any problem of intermediate size, from trivial to
| complex. The contribution can be anything, from testing a proposed fix
| (there are /many/ problems nearly fixed, just awaiting feedback),
| investigating strange configuration problems to shed some light on not
| fully understood issues (e.g. #3663 of today), help to tweak the CSS or
| the presentation of templates (e.g. #7075 of today), and so on.
|
| Also, after the 0.11 release I've "reset the counters" on component
| ownership, new tickets are no longer assigned to someone automatically (*).
| That automatic assignment gave a false sense of confidence that the
| ticket would actually be screened or managed by someone. We should
| better face the reality that there are not really that many active core
| developers around...
| So starting from this reset we can either have new people engaging
| themselves to monitor specific components of Trac, or leave the owner
| unset and set the ownership in an ad-hoc way using the "assign to"
| action. I'd even suggest that anyone (i.e. even when not formally part
| of the TracTeam) could take ownership of a ticket, indicating by this
| that he commits himself into resolving the ticket. I think that could
| help stimulate newcomers to get more involved in the project.
| We could even take this reset one step further by clearing that field
| for all the existing opened tickets, not just the newer ones.
(...)
I like the idea of opening up development even more -- especially for bugfixes.
As Noha mentioned, design by chaos isn't a very good approach to software
engineering(**), but to allow all the monkeys (ie us trac users) to help hammer
out minor dents easily, is a good idea.
My limited experience so far has been that the trac team is responsive in this
regard, but I think lowering the bar a bit for developers to become part of the
core team (not by handing out svn commit access, but by making it even easier
to submit patches) would help the project a lot.
I guess I'm just a bit lazy, but something more welcoming on the trac
front-page along the line of "fix a bug now!" with a link to a ticket-report,
might be a good idea.
Writing this mail, i actually did have a look at the relevant link:
~ http://trac.edgewall.org/wiki/HowToContribute
and it appears the "helpwanted" is a bit abused? Eg:
~ http://trac.edgewall.org/ticket/3870
Should one interpret this as "we'd like more input on what to do" ?
Incidentally, I think the idea of using synchonous sending of messages is quite
flawed -- a better solution would probably be to rework the notification system
to use a pipe as standard, supplying a simple smpt/sendmail python-wrapper for
windows (which I think would be the only platform not having a sendmail-binary
by default). Note-to-self -- have a look at this later.
I certainly don't think the devs are hostile to fixes -- and I think a lot of
minor fixes could be contributed by large (larger) parts of the community -- if
only people was aware of where to start.
So far my personal experience have been that I've only fixed (plugin?)bugs I've
run into myself (which is fine, I guess) -- but that it's a bit of a bigger
hurdle to know where to start if I felt like spending a few hours helping the
trac project.
Best regards,
Eirik
(**) I *have* looked at the thunderbird sourcecode, and quickly abandoned all
hope of contributing fixes. Note, I don't think it's completely fair to assume
this is because their metodology is wrong -- I think it mostly just means that
the core mail functionality of Netscape Navigator could've benefited by
borrowing from mutt rather than reinventing the wheel in-house.
- --
~ .---. Eirik Schwenke <[EMAIL PROTECTED]>
( NSD ) Harald Hårfagresgate 29 Rom 150
~ '---' N-5007 Bergen tlf: (555) 889 13
~ GPG-key at pgp.mit.edu Id 0x8AA3392C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIX/Y9xUW7FIqjOSwRAl71AJ9Wmt84HJ/Y6F3J7Jp/7KMvnhwP3ACgs/Bb
OPqhG7EN9pYz2wlETWnSWMs=
=PsUR
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
