Bugzilla skin software#

Let me go through them as I want you to be thinking about them when you look at the ActiveState version: I’ve circled a couple of the key features to zero in on. So let’s start with the Mozilla instance of Bugzilla – as this was the one I was used to.

Bugzilla skin software#

Here we have two identical pieces of software (so the “usefulness” is the same) but what makes ActiveState’s version of Bugzilla so nice are a few simple things they’ve done to make it more user friendly (doubly pleased to see them implement some ideas I’d blogged earlier as well – great minds think alike!).

Bugzilla is the software many open source projects use to identify, track and resolve bugs. Hence why I enjoyed recently discovering ActiveState’s implementation of Bugzilla (re-themed by Tara Gibbs). Especially when you are running an open source community and want to encourage participation and ease people up the learning curve faster. But it’s no excuse for not making things easier to use. (This may or may not have influenced some fashion choices earlier in life as well – I’d like to think things have improved – but not everyone may agree it has improved sufficiently).īeing useful may be sufficient (although take a look at the government website at the bottom of this post – it’s a very useful website). To my credit, it was a long time ago… but I used to think, if the tool was good enough, the design won’t matter, people will use it cause it is helpful. There was a time when I thought design didn’t matter. Design Matters: Looking at a Re-themed Bugzilla This entry was posted in negotiation, open source and tagged bugzilla, community management, drupal, mozilla, opensource on Novemby David Eaves. This is exactly the type of skill and community norms I think we need to build tino more of bug tracking environments/communities, which can sometimes be pretty hostile and aggressive, something that I think turns off many potentially good contributors. Seems like someone was listening during the workshop since I just sent this link to a conversation about a tricky drupal bug (Screen shot below) asking questions are critical moments to try to open up the dialogue and uncover interests. Obviously, understanding the difference is key, but so is acting on it, e.g. Positions are challenging to work with as they tend to lock people into what they are asking and makes outcomes either binary or fosters compromises that may make little sense, where as interests (which you get by being curious and asking lots of whys) can create the conditions for make creative, value generative outcomes that also strengthen the relationship. As part of my talk I ran them through some basic negotiation skills – particularly around separating positions (a demand) from interests (the reasons/concerns that created that demand).

I gave a hour long version of my OSCON keynote on the Science of Community Management and had a great time engaging what was clearly a room of smart, caring people who want to do good things, ship great code, and work well with one anther. The other week I was invited down to the Bay Area Drupal Camp (#BadCamp) to give a talk on community management to a side meeting of the 100 or so core Drupal developers.