On Saturday 07 August 2010 21:46:33 Michael Raskin wrote: > On 08/07/2010 10:06 PM, Evgeny Egorochkin wrote: > > For more complex cases, and especially distributed cases, I'm pretty sure > > > > there will be issues like: > > - people filing bug reports against your branch/fork, which actually > > belong to > > > > the project as whole or your branch-specific bug reports spilling into > > the main project. > > > > - misplaced wiki edits along the same lines > > > > Not that it can't be worked out but at least the gui to resolve this is > > missing(that's what the site says)... > > I guess "use a tool for its job" may give a natural solution: something > like BugsEverywhere (although BE claims to have very work-in-progress > web interface) that stores tickets in the branch itself (support for > Monotone, Darcs, Mercurial, Bazaar, Git, Arch) - bonus points for branch > merge automatically merging tickets.
If there was an UI, it would be a really good idea to move to it as soon as we move to a DVCS. Also it's sad that there doesn't seem to be a distributed wiki although maybe some git-based wiki could be patched to only look into a certain dir in the repo... ikiwiki maybe? After all the easiest thing is to put wiki into wiki dir and consider it done. So missing things are: ui for distributed bugtracker, "distributed" links between projects, bugs, wikis and commits... -- Evgeny _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
