>> Thursday, April 08, 2010
When I first starting working on eclipse, I quickly realized that I have to say no a lot. I only have a couple hundred bugs in my bucket. Not many compared to some of my committer friends.
I have a friend. Let's call him Paul. He has about 1300 bugs assigned to him in the Eclipse 3.x stream. He can solve 20-30 bugs a milestone. Each milestone is six weeks. That's excellent fix rate. So thousands of bugs. Can't fix them all. We'll never have a zero bug count.
In the beginning, I would close bugs with something like "Sorry, I'll never have time to fix this". This isn't a way to win new friends in the community. I've learned that the way you say no makes a difference. You need to say no in a way that will make others say yes. How do you do that?
For instance, say I'm spending a lot of time working on a plan item for 3.6M7. I really don't have time to fix a new bug that a member of the community has just opened in my bucket. But, I can be helpful and give them pointers to where the code needs to be changed.
Here's the repository location of the code. Here are the JUnit tests. I can offer to provide guidance, but you need to take ownership of this problem if you want to get it fixed. Taking ownership means transparency. People will be watching you. This community grows by letting others to step up to the plate.
Previous Eclipse Top Ten posts