Re: [Firebird-docs] Consider migrating to GitHub?

[Mark Rotteveel]

On 19-12-2016 11:39, Andre van Zuydam wrote:
> So bouncing in here on a tangent,  I've done this with a couple of
> Source forge projects, simply set Source forge to clone the Github
> project or visa versa.  The only reason I would suggest having things on
> Github is for more visibility.  Anyway my five cents.  You can still
> continue to commit as always, just have things cloned on both.   Each
> versioning system has its pros and cons, those of us who started with
> CVS may have moved on to use other systems but hey, its such a mission
> to switch things that work.

That works (barely) if you already have a git project on SourceForge, 
but as far as I know not if you have CVS project on SourceForge.

If a conversion is going to happen (but the strong resistance seems to 
indicate no), then I'd prefer going GitHub the way the core project did 
as well, instead of having a hybrid solution where you try to balance 
between GitHub and SourceForge and having to keep both repositories in-sync.

Mark
-- 
Mark Rotteveel

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
___
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Re: [Firebird-docs] Consider migrating to GitHub?

[Helen Borrie]

On 18/12/2016 11:48:34 AM, Paul Vinkenoog  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
--
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

Re: [Firebird-docs] Consider migrating to GitHub?

[Paul Vinkenoog]

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.

No objections here, but does anybody have any experience with this kind
of migration? (Preferably including history.)

Myself, I'm a basic GIT user and I only use it locally.


Paul Vinkenoog

--
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