On 18-12-2016 03:24, Helen Borrie wrote: > >> On 18/12/2016 11:48:34 AM, Paul Vinkenoog <p...@vinkenoog.nl> 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. For visibility: the documentation project will be in the same group on GitHub as the Firebird project itself. This makes discovery of the project a lot easier. Also these days GitHub is the go-to place for hosting open-source projects. More people know git and GitHub than CVS. GitHub provides a lot of features that simplify contributing to a project even if you don't have commit rights (eg pull requests). > 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. The main advantage I see are that one-off contributions become simpler, and those might lead to more. > 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. As a sidenote: SourceForge considers CVS type projects to be deprecated these days, don't be surprised if we get a notice in the future that we need to migrate anyway. From https://sourceforge.net/p/forge/documentation/CVS/ : "CVS is no longer available for new projects, we only offer limited support for CVS for projects previously using it on the Classic SourceForge system. We recommend that projects upgrade to a more modern SCM, like Subversion, rather than using CVS. CVS has limitations which newer SCM solutions have been designed to overcome. We continue to support CVS for those projects who decide that CVS adequately supports their needs." -- Mark Rotteveel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
