[jedit:feature-requests] #553 jEdit should move to github

whydo pplstillusesf via jEdit-devel <[email protected]>
Newsgroups gmane.editors.jedit.devel
Message-ID </p/jedit/feature-requests/553/828d2f54cf2faab061f20c422b214e9a22bd4387.feature-requests@jedit.p.sourceforge.net>
I just realized my comments maybe didn't end up here even though i replied to the email i got (something that works on github pretty well).

in reponse to so list them out, i posted on Mon, Jun 12, 5:37 AM (edt)

Sure:
pros:
1. discoverability - github is the library of congress for code - people expect to find it there - would argue that it is safer there than here as msft has a lot in the bank and they are invested in getting everybody's code and preserving it in there supposedly to train ai etc
2. deduplication of effort - several developers have already exported the project and uploaded it to their personal github accounts
3. up and coming developers from this generation can find it and keep the project alive
4. git - git is the lingua franca of version control systems.
5. github actions - you can prove to the world that your code works because you can put a green checkmark at the top which links to a successful unit test run (i mean this is not unique, but it is built into github and free)
6. myriad of other github features (codespaces, labelled issues, PRs, etc)
7. up and coming developers from this generation can find it and keep the project alive
cons:
1. requires some amount of work
2. might lose some info in the process (like old issues) - i am personally not above writing a puppeteer script or something to scrape these off of SF and manually add them to a github issue tracker
3. you lose that retro feel

Alan, to your point i responded shortly after you posted:

> I am more than happy to help with that.
> 
> You can see a cvs export for jEdit-Syntax that i did from SF to GH here -> https://github.com/alexanderankin/jEdit-Syntax (granted, its only a couple of commits, from here - https://sourceforge.net/projects/jedit-syntax/).
> 
> Am curious to receive any feedback on that output - particularly with any flaws anyone can find or something that anyone wants to change, so it can be the best solution. I am also working (haven't touched it since hearing back that there are already plans for jEdit) on an issues copier tool from SF to GH.


---

**[feature-requests:#553] jEdit should move to github**

**Status:** open
**Group:** none
**Labels:** github 
**Created:** Wed Jun 02, 2021 12:07 AM UTC by sigzero
**Last Updated:** Mon Jun 19, 2023 05:15 PM UTC
**Owner:** nobody


There was a ticket (#3922) back in 2016 that brought up the idea that jEdit should be moved to github. I think the developers should revisit the idea.  I believe the pros vastly outweigh the cons now.

Thanks.


---

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/jedit/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/jedit/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

-- 
-----------------------------------------------
jEdit Developers' List
[email protected]
https://lists.sourceforge.net/lists/listinfo/jedit-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.