Hi, On Wed, Dec 08, 2010 at 09:27:47AM +0100, Olaf Lenz wrote: > >That being said, the first Savane objective is to get a maintainable > >code base, by reimplementing the currently (centralized) Savane. The > >second Savane objective is decentralizing that new code base. > > Ok, I agree, and I will stick to that agenda. Still, I am building up my > utopia. ;-) > > >We believe that doing the changes in those 2 steps makes it easier > >(or even possible) to migrate existing Savane installations, such as > >Savannah and Gna!. > > That is definitely true. I guess that ESR's forge plucker might help in > that respect?
No, we have a migration script from Savane2 to Savane3. What helps, is running the development in 2 steps. I'm not sure you understood me? > >>Have you ever considered roundup for inclusion into Savane? > >> > >>http://roundup.sourceforge.net/ > > > >Hmmm, in what way is RoundUp decentralized? Models for > >decentralized bug trackers include SD and Fossil. > > Sorry, I should have been clearer on that. > > The main reason why I think roundup would be very useful is that it > unifies forums, trackers and mailing lists into a single interface, that > can be used either via email, command line or via web interface, > whatever the user prefers. > I am really unhappy that if you want to discuss with other people about > topics in the net, you sometimes have forums which may provide RSS > feeds, others Twitter, others mail notifications, others use mailing > lists, which sometimes have archives, sometimes not, etc. > Roundup unifies all that: the user has the freedom to choose what kind > of interface he uses to participate. Certainly, why not. I'm pretty sure that the decentralization work on Savane3 will make is much easy to export/import the data to/from roundup. > >Being able to make a backup copy is good, but decentralizing means > >you don't rely on a client/server architecture at all. > > Roundup is not decentralized out of the box, true. However, I had a look at > the pretty neat architecture, and it looks as though it should not be a > big problem to create a backend for it so that it stores all its data > into a DVCS. Then it would be decentralized. One would, however, have to > think about how merging works. I would be very willing to work on that. > > One could even think about putting all Python code (savane and roundup) > into the repository. Then, the only requirement for a full, useable copy > of your project would be python, maybe apache if you want to run the web > site, and an MTA if you want to allow the mail frontend to be used. I would suggest making a prototype to check how good this works. Though I would steer on completing a maintainable and bug-free Savane3 codebase first. -- Sylvain _______________________________________________ Savane-dev mailing list [email protected] https://mail.gna.org/listinfo/savane-dev
