Re: Module Proposal: Zeitgeist



Hi Mikkel,

On Thu 22 Apr 2010 21:40, Mikkel Kamstrup Erlandsen <mikkel kamstrup gmail com> writes:

> Here's what we do. We set a series of milestones and target bugs and
> blueprints to these milestones. We also attach branches (not patches)
> to bugs and blueprints. When a linked branch is ready to merge into
> another branch (trunk or other) we add a merge request, which enables
> the review system.

It's not as slick as launchpad, but have you tried bgo's splinter? One
can push git branches to bugzilla, and review the patches on the web,
with a quite acceptable interface.

Just a data point :)

> We create sub teams and sub projects that all have
> different rights and responsibilities. So basically we use pretty much
> all aspects of a modern project hosting solution. Bugzilla is just a
> bug tracker.

Obviously you have to do what's best for you, but I have found it best
to rely on a more flat technical rights division -- for example, either
you're in the project or you're out, and most people that want to should
be in. Rights and responsibilities can in many cases be managed better
on the social level, with trust. This also allows people to migrate to
different areas of resposibility over time. YMMV, of course.

Happy hacking,

Andy
-- 
http://wingolog.org/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]