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 |
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.
|
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.
|
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.
|
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.
|
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):
|
2015-07-31 01:24:48.009000 vampire0 |
Hey there. Thanks Dale for noticing me about this issue here.
|
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:
|