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

Hey, I feel github much more efficient to navigate and use in git repositories, bugtrackers.
Github is centered on the developper while sourceforge is on the project.
For example if jEdit was on github, then I think we should not commit directly to the project. Just I would do a fork in my user space (that is public), you would do the same, Alan too and any developper who is interested in jEdit's development too. Then I would create a branch for my changes, and when I am satisfied I would submit a pull request from the branch of my personal space to jEdit project.
All those things are very easy to do in github and I found that contributing or forking other projects is very easy to do.

But of course the first thing to do is to migrate from svn to git. Then we can think about moving or not. But I think there is no secret why so many projects are moving to github. Just sourceforge was great in 2000 but it was unable to evolve to the modern standards.


---

**[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:** Thu Aug 31, 2023 06:07 AM 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