News for hackers. Stuff that matters.
Re:Emacs and Magit by tarsius on Friday July 21, 2017 @08:54AM (#14820048)
Most of the packages that are distributed using GNU Elpa (i.e. the non-built-in packages under FSF control) are developed on Github.
Re:Emacs and Magit by ivanbakel on Friday July 21, 2017 @09:03AM (#14820126)
Can you show me an example of such a package? All the Elpa packages are hosted on a Savannah instance.

https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/packag...

Re:Emacs and Magit by tarsius on Friday July 21, 2017 @09:17AM (#14820230)
> Can you show me an example of such a package?

https://github.com/magnars/dash.el

> All the Elpa packages are hosted on a Savannah instance.

That's the "publishing repository". You have to push there for a new version of your package to be published on GNU Elpa. But for most packages development happens elsewhere, and in most cases "elsewhere" is Github. Emacs maintainers sometimes commit directly in the Elpa repository (and package maintainers are expected to deal with the consequences, such as "two diverging mainlines"), but development happens elsewhere.

Re:Emacs and Magit by mnarayan01 on Friday July 21, 2017 @11:31AM (#14821311)
> Emacs maintainers sometimes commit directly in the Elpa repository (and package maintainers are expected to deal with the consequences, such as "two diverging mainlines")

Is a model like this what you mean when you say "No, we would continue to use Github for the foreseeable future"? I guess if you're doing all the legwork, it won't be overly visible to other people who want to contribute. Still though...

Re:Emacs and Magit by __david__ on Friday July 21, 2017 @12:19PM (#14821699)
That doesn't seem that onerous. It's just a pull and and a merge—it's what git is designed for.
Re:Emacs and Magit by BeetleB on Friday July 21, 2017 @10:22AM (#14820741)
Orgmode is another example.