Hi Sam,
what about Fossil (http://fossil-scm.org) as an alternative to Savannah?
It also integrates a wiki and one could base the gnewsense website/wiki
on Fossil instead of having one distributed version control system and
one separate wiki/website.
Cheers,
mark
Am 04.02.2016 22:34, schrieb Sam Geeraerts:
Op Thu, 4 Feb 2016 10:49:57 +0100
schreef "lorde...@riseup.net" <lorde...@riseup.net>:
what might be of interest to us, is the way they setup their system.
i don't know all the ins 'n outs, but on their website [1] they
have a small drawing of their continuous integration setup.
I definitely want to give Jenkins a try. Vagrant might also be useful
to get people started with gNewSense development.
Personal branches are also on my wishlist. That means moving the code
away from Savannah. Most code hosting tools seem to be geared towards
Git. I prefer Bazaar, but I'm not married to it. In any case, Gitlab's
open core model is not very appealing. Ideas welcome.
_______________________________________________
gNewSense-dev mailing list
gNewSense-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
_______________________________________________
gNewSense-dev mailing list
gNewSense-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
