[ jEdit-devel ] Moved from #3922: Discussion of moving to github

[Dale A. <da...@da...>]

Moving the discussion about moving jedit source code from bug #3922 to the
mailing list.

Here is the last message from #3922 from Björn regarding this issue, plus
my comments following:

--------

Hey there. Thanks Dale for noticing me about this issue here.
I think this is a topic that should be discussed on the devel mailing list
and not in a ticket though.

I'm against moving to GitHub.

I don't see any added value.
We have less control over the Git repositories (no own hook scirpts for
sending changes to the mailing list, no own hook scripts for access control
like we have them currently, ...)
At SF everything is there already.

Yes, SF has an outage currently, but ever hosting provider can run into a
disk crash and SF is working 24x7 on restoring everything back while the
most stuff is up and running already.

At SF we have great service and great services.
Website Hosting with custom VHOST, various VCSs, as many different Ticket
Tools as you like to logically separate the tickets etc.

In my opinion if we would move to GitHub, we would give up much power and
good service we have and just because some people thing it is more "hip".

That the community page is a bit outdated is true, but that has nothing to
do whether you work on SourceForge or on GitHub.

On SourceForge you have the same "Web 2.0" if it comes to the serivces
provided by SF themselves, like the Tickettools etc.

I have nothing against mirroring the jEdit Sources on GitHub after the move
to Git, but in my opinion we should stay at SourceForge which served us
great the last 2 decades and still provides a great service.

About the jEdit account at GitHub, I'm already trying to reach the owner of
that account to ask for transferral of the name, unfortunately despite the
public idleness, the account is not dormant, otherwise GitHub would have
given it to me already. In case we do not get that account, I also already
reserved jedit-editor for use as the GitHub organisation.

About the Git transition of jEdit core, it is almost done, I found the
errors I made during prior try and fixed them, so there is little that
speaks against a new try of the Git transition. I just wanted to restore
the Wiki pages of the Mediawiki where the Git-commands were listed first.

I'm currently working on upgrading our Community-Wiki and then integrate
the backup of the old Mediawiki into that new version of the Foswiki. After
that I would have done the Git-switch again.

And about the dated community page, yes, it is also on my to-do list to
update that.
But that the news are 10 years old is just bullshit, the newest news is
from 16 April, 2015.

------

I tend to agree with Björn, there is a lot of structure built up around the
project using the SF tools that would be difficult/tedious to reimplement
at github. Further, the intent of the sites seems to be different to me --
SF is more about distributing software to end users where github is more
about source code management and developer collaboration. SF provides git,
to which Björn is already working on migrating the code from svn.

Björn, would you expand on this: "I have nothing against mirroring the
jEdit Sources on GitHub after the move to Git," How difficult is that to
set up and keep in sync, both ways? Having a second repository available in
case of an outage at the other would be nice.

I have also contacted github about the jEdit project there, they have
forwarded a message to the current owner of that project asking if they'd
give up the name to us. I have not heard back yet.

Björn, another question for you -- when do you think you'll have the core
code for jEdit moved to git? I also wonder if that is really necessary,
doesn't git-svn give git users the ability to use git with an svn
repository?


Dale