|
From: Helen B. <he...@ii...> - 2016-12-18 02:24:17
|
On 18/12/2016 11:48:34 AM, Paul Vinkenoog <pa...@vi...> wrote: Mark Rotteveel wrote: > Isn't it time to consider migrating the documentation repository from > SourceForge CVS to GitHub? > > SourceForge itself considers CVS deprecated, and having the repository > on GitHub might increase visibility and will likely lower the barrier > for contribution. Helen Borrie: I don't see how moving the source from one obscure repository to a different obscure repository would heighten visibility or lower any barrier. If there's a good reason to change, I'd go with it, albeit it currently aint broke so there be nothing to fix. PaulV has it nicely set up for use by the translators and it is all well documented, enough so that those of us who actually DO stuff regularly, rather than just talk about doing it, have our local setups that are more or less automated. One of us can always step in to assist people who don't want to work with a repository for whatever reason. I don't see how changing the repository would (or should) alter that. My personal experience so far with GitHub is that it is a dog to work with, actually, given that I don't upload or download any programming code, only documentation. I guess if I had to, I'd find a way to make it useful for me to use. I just can't think of a good reason right now to spend time and energy on creating a solution to a non-existent problem. Helen |