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

2016-12-19 Thread 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

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

2016-12-17 Thread 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

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

2016-12-17 Thread 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

[Firebird-docs] Consider migrating to GitHub?

2016-12-16 Thread Mark Rotteveel
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. Mark -- Mark Rotteveel