I think there is only one reason to keep tux family. Do we plan on starting
a version archive of previous releases? Reason being they would be good to
have in an archive download repo somewhere to use for regression testing
and comparisons etc.


On Sun, Jul 6, 2014 at 12:35 PM, Tobias Doerffel <tobias.doerf...@gmail.com>
wrote:

> 2014-07-06 12:28 GMT+02:00 Lukas W. <lukas...@gmail.com>:
> > Apart from this, I don't really see a point in moving to tuxfamily. What
> > does tuxfamily provide that SF does not? In what way is it worth the
> effort?
>
> Full ack. Nothing is wrong with Github. Besides the website stuff we
> already host release files at Github so there's no need for an
> external hoster for release files. About the website: if everything is
> possible at Github, why not stick with it? I know we're moving in
> circles with this discussion but I wonder why we're still hunting for
> Tuxfamily & Co.
>
> Toby
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> LMMS-devel mailing list
> LMMS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>



-- 
Jonathan Aquilina
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to