As I've mentioned before in the newsgroups, I'd like to run a Bug Week 
to help get new contributors to Mozilla making their first patches. I've 
already written some software to help with that - 
http://www.mozilla.org/hacking/patch-maker/ - and we now need people.

To make this work, we need people who know, understand and have hacked 
on Mozilla, and are familiar with the process. I expect the emphasis to 
be on polish, XPFE and themes bugs, so experience in that area is 
particularly desired, but anyone who's been around the block can help.

The dates I've tentatively picked are Saturday 27th October until Sunday 
the 4th of November. This encompasses two weekends - one to kick start 
people, and one for people to finish off what they are doing.

Ideally, we'd have one person officially on duty in the channel at all 
times. This may not be possible if everyone wants to be asleep. :-) 
Hopefully other people would also hang out there and help whenever they 
were on IRC. Being on duty would involve:

- Helping people get build environments, or Patch Maker, set up
- Teaching about Bugzilla and how to search for suitable bugs to fix
- Pointing people at the documentation for various technologies
- Answering questions about patches
- Guiding people through the review and super-review process
- Perhaps doing some reviewing, if you are qualified

We need to start ramping this up quite soon, so I'd appreciate hearing 
back from anyone who can spare some time. You can either give me times 
you can do, or times you can't. I'd also need some indication of what 
sort of length of shift you can do - "I can do Wednesday afternoon" or 
"I can do any morning from 9, but not for longer than three hours". All 
times are Pacific :-) If you are in other time zones, this is 
particularly good, as you can be around when the US West Coast is asleep.

Hopefully people who come through this should be able to go on and make 
more significant patches on their own time without help. This is where 
the win for the project is.

Gerv


Reply via email to