|Subject:||Re: [fluid-dev] Move upstream to github|
|Date:||Fri, 2 Jun 2017 16:34:59 +0200|
On 06/01/2017 09:27 PM, Element Green wrote:
Sounds good to me. I have had very little time for FluidSynth or my other free software projects and I haven't heard much from other maintainers as of late, so it seems to make sense to make things easier for collaboration and contribution.
Unfortunately I don't currently have a lot of time to even move things over from SourceForge. I'd be happy to create a FluidSynth repo on my github account, but wont have much time to approve contributors or maintain things. If someone else wants to take on this role, that would be great! Someone else could do the migration, though I can provide admin only accessible data if needed. It's then just a matter of updating the website to point to the new github locations.an
I'd suggest to create a github organisation. Then you can have one repo for the code and maybe in the future other repos (website, sound-fonts, ...)
I'm currently hosting the fluidsynth.org website which is basically just wordpress. Would be happy to provide other admin accounts on there or turn over hosting to someone else.
On Thu, Jun 1, 2017 at 11:48 AM, Tom M. <address@hidden> wrote:
Any comments?Sadly, fluidsynth's upstream is basically dead. There are so many custom fluidsynth forks floating around (esp. on github) that it's really hard to find and choose an update-to-date one. Personally I'm currently very demotivated to look through any recent patches, because I know they wont make it into upstream anyway. Not even talking about doing any further development.Hence I insistently ask the fluidsynth owners: Please, do the step and move to github. github has been a very popular and modern platform for a couple of years now, while sourceforge is pretty much the opposite IMO. There are tutorials and scripts online to migrate code and tickets easily (https://github.com/ttencate/s
f2github). Create a github organization and invite a few people who have been actively developing patch recently, to allow them to merge patches. That way we would at least revive upstream development.
fluid-dev mailing list
_________________ fluid-dev mailing list address@hidden https://lists.nongnu.org/ mailman/listinfo/fluid-dev
fluid-dev mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|