Guys,
I think that I sent out an email about getting BIRT involved in the Eclipse Bug Days. I was
hoping we could spend some time discussing the logistics of making this
happen in our next PMC. I think that if we are going to do this, there
may need to be a bit of change on the process side for the dev team.
For example, I had a look at some relatively simple code that could be
cleaned up and made more efficient. I submitted a bugzilla entry
for it and asked if this is a good help wanted item. One of the
reasons that I thought it would be a good bug day item is that it is so
trivial. Believe me, it would have been far easier for me to just
re-write the code myself and check it in. My thought is that this is
just the type of bug that is ideal as a help wanted item.
So instead of just fixing it, we would provide information on the tests
that the fix needs to pass, and mark it as a help wanted / bug day
item. Then someone from the community has a chance to get involved and
give something back. I think the key here is to give people the
opportunity to give something back in bite size chunks.
The hard thing for the dev team will be to change the style from just
fix it and get it done. To figure out how to build bite size pieces and
be able to manage these pieces. I think initially, supporting this
structure will be more work, but my hope is that over the long run we
will get more participation and ownership of the BIRT code, which I
think would be good for everyone.
Thoughts? Or is this better to discuss on the phone?
Scott
|