On 19-12-2016 11:08, Lester Caine wrote:
> On 18/12/16 11:19, Mark Rotteveel wrote:
>> Git != GitHub.
>
> But it's the reason most projects use as an excuse to promote git over
> other options :(
> And it's trying to promote itself as yet another social media site
> detracts from the REAL jobs that many years ago SF did so well but
> without actually achieving it.
>
> My point is that github is a distraction most of the time and promoting
> it more does not help develop a better - fully integrated - solution to
> project management. One can have a presence ON github and all the other
> alternatives without 'moving to' github ... and moving a perfectly
> functional repository does not need git messing it up when it does not
> need the compromises git introduces.

So your argument boils down to "I don't like git and GitHub, because 
they 'won' the hearts and minds of the majority of the (open source) 
development community".

That is exactly one of the reasons I propose to move the repository to 
GitHub: that is where the people are, and a lot of people know how to 
use it.

Lets face it: the Firebird documentation project could do with more 
active contributors. Is moving to GitHub going to solve that: of course 
not, but it might make it easier. Moving Jaybird to GitHub last year 
lead to at least 4 (small and large contributions), including the 
support for SRP.

You mention downsides/compromises that git brings to the table: exactly 
what kind of compromises do you think the Firebird documentation project 
specifically would experience with moving to git? As far as I know the 
manual module is pretty straight-forward with a largely linear history, 
and without use of obscure CVS features, so I don't see where those 
compromises would be, and I'd really like to know. However, I can name 
at least one benefit of moving to git: rename/move or copy with history, 
and for moving to GitHub: contributions by pull request.

Also to be clear: I'm talking about moving the repository: the rest can 
stay where it is if that is deemed better (eg you can disable issues if 
you don't want to use the GitHub issue tracker, etc).

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

Reply via email to