PreviousNextTracker indexSee it online !

(223/239) 3922 - Move jEdit source code to GitHub

The jEdit community website is falling to disrepair. The chatbox has critical bugs (Today just by signing on I think I crashed the server). The news posts are more than 10 years old.

The whole website is undermaintained. That's a shame, since the community is very important for any open source project. The website is critical to keeping a good community. Maybe thats one reason the community is quite weak in Jedit.

Personally Jedit is a good project. Maybe it's not the most "trendy" of text editors, without all the features of Eclipse, but this is also its strength. It's fast, lightweight and portable.

It's time to upgrade the community of JEdit to the new web2.0 paradigm.

Github brings features like bug tracking, commit logs, easy integration with a large community and download server. It pulls everything into 1 place. Let's also not forget the recent Sourceforge problems this month (July 2015).

It should be quite simple to bring some aspects of the community over to GitHub. Even if it's not possible to move the main CVS repo, we can at least start a mirror repo on GitHub and make it the official location for bug tracking. And update the JEdit website with a post that we are moving to GitHub. That will help to move things in the right direction.

It's also time to remove the old Jedit "community" website.

Submitted chrosmull91 - 2015-07-25 23:19:48.588000 Assigned
Priority 6 Labels
Status open Group normal bug
Resolution None

Comments

2015-07-25 23:20:51.986000
chrosmull91

It would also help to spur on new plugins and editor modes (for example, the 'Go' mode for Go integration).

2015-07-26 19:38:46.127000
ezust

I am a novice at github so I would need an expert there to help me get things right.
Are you volunteering? For example, I just tried creating a repo but it appears under my own name. I don't yet know how to create one that is just called "jEdit" without being "ezust/jEdit".

2015-07-26 19:41:57.763000
ezust

Also, each plugin needs to have its own git "project". Some still need to be converted from SVN. Including jEdit core. vampire was working on that for a while and running into troubles.

2015-07-26 21:57:27.104000
vanza

If you want to go this route the best way is probably to create a "jEdit" organization and host all repos (jEdit and plugins) under it.

I've never done that (create a new org) but it seems easy, and you can add people to it easily too.

2015-07-26 22:15:08.706000
ezust

looks like someone else picked the user "jEdit" already.

2015-07-27 05:20:44.158000
elberry

You might check with Vampire regarding this. I vaguely remember someone saying they set up a jedit account, and it might have been him.

There's nothing associated with that user (no repos, or commits, they haven't contributed to anything), so looks like someone could have reserved it?

I also checked bitbucket - which I personally think is a better choice than github, but looks like the username was taken there as well. It was taken last year, but they also don't seem to have anything associated with them. I could try and reach out and see if we're interested in going that route.
https://bitbucket.org/JEDIT/

2015-07-29 17:28:57.144000
ezust

Someone else needs to set up the jEdit account and repo in github, give me admin privs, and do the migration.
After that, I volunteer to fix up the links to various repos in the documentation sources.

2015-07-30 02:38:01.331000
daleanson

I have time to work on this. I'm in contact with github to find out if the existing jEdit user will give up the name to us. I've also messaged Vampire to see if he's the one that set it up, but no word back on either yet.

2015-07-30 05:57:52.028000
elberry

I went-a-lookin' and found this conversation back in 2013 (almost exactly 2 yrs ago):
http://jedit.9.x6.nabble.com/jEdit-devel-jEdit-core-and-Git-td5000109i20.html

There's a response in there from Vampire about setting up a cron-job to push changes to a github repo.
http://jedit.9.x6.nabble.com/jEdit-devel-jEdit-core-and-Git-td5000109i20.html#a5000261

I think this is where I got the idea he may have set it up.

If he didn't and we can't get the username, (option?) would it be terrible if we got something like "jedit-org", or "jedit_org"?

2015-07-31 01:24:48.009000
vampire0

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.

2015-08-22 07:25:21.132000
ahlearn

I would like to forward a comment from a stackoverflow user. The comment is not related to GitHub vs. SF, but it is related to the community page, and I partially agree with it:

http://stackoverflow.com/questions/71336/whatever-happened-to-jedit
Very very long time jEdit user here (since 2005). Cons: terrible community, open bugs galore, new versions introduce new (and quite visible) bugs, pretty much useless on OSX, requires a jre. Pros: the most flexible editor ever, can be scripted with beanshell or even javascript, clean api, lightweight (compared to Eclipse and other monstrosities). – Szabolcs Kurdi Apr 14 at 5:21