{"action":"created","issue":{"url":"https://api.github.com/repos/milkypostman/melpa/issues/3383","labels_url":"https://api.github.com/repos/milkypostman/melpa/issues/3383/labels{/name}","comments_url":"https://api.github.com/repos/milkypostman/melpa/issues/3383/comments","events_url":"https://api.github.com/repos/milkypostman/melpa/issues/3383/events","html_url":"https://github.com/milkypostman/melpa/issues/3383","id":121927123,"number":3383,"title":"Packages that are also available from GNU Elpa","user":{"login":"tarsius","id":25046,"avatar_url":"https://avatars.githubusercontent.com/u/25046?v=3","gravatar_id":"","url":"https://api.github.com/users/tarsius","html_url":"https://github.com/tarsius","followers_url":"https://api.github.com/users/tarsius/followers","following_url":"https://api.github.com/users/tarsius/following{/other_user}","gists_url":"https://api.github.com/users/tarsius/gists{/gist_id}","starred_url":"https://api.github.com/users/tarsius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tarsius/subscriptions","organizations_url":"https://api.github.com/users/tarsius/orgs","repos_url":"https://api.github.com/users/tarsius/repos","events_url":"https://api.github.com/users/tarsius/events{/privacy}","received_events_url":"https://api.github.com/users/tarsius/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":17,"created_at":"2015-12-13T16:01:37Z","updated_at":"2015-12-15T20:13:20Z","closed_at":null,"body":"The following packages are available from Melpa as well as from GNU Melpa.  In some cases this is probably the right thing to do, in others not so much.\r\n\r\n### Packages that I think *should* probably be remove from Melpa\r\n\r\n- [x] [vlf](https://github.com/m00natic/vlfi)\r\n- [ ] [web-server](https://github.com/eschulte/emacs-web-server)\r\n\r\nThese repositories have not been updated in quite some time (more than half a year) that probably means that development now happens in the GNU Elpa repository.  Or if these packages are \"done\" then bugfixes probably only happen in GNU Elpa and do not get merged back to the repositories on Github.\r\n\r\n@m00natic and @eschulte please let us know which is the case.\r\n\r\n- [x] [seq](https://github.com/NicolasPetton/seq.el)\r\n\r\nIn addition to being available from both GNU Elpa and Melpa, it also will be part of Emacs v25.1.  That seems like a bit much.\r\n\r\n@NicolasPetton where does development happen?  Elpa, Melpa, or Emacs?  Are all three versions identical (though possibly out of sync at times), or is one of these versions a backport?\r\n\r\n### Packages that I think should probably *not* be remove from Melpa\r\n\r\n- [ ] [ergoemacs-mode](https://github.com/ergoemacs/ergoemacs-mode)\r\n- [x] [pabbrev](https://github.com/phillord/pabbrev)\r\n- [x] [ahungry-theme](https://github.com/ahungry/color-theme-ahungry)\r\n- [x] [easy-kill](https://github.com/leoliu/easy-kill)\r\n- [x] [names](https://github.com/Malabarba/names)\r\n- [x] [ztree](https://github.com/fourier/ztree)\r\n\r\nThese repositories have seen updates during the last six months, so it appears they are still being actively worked on.  Never-the-less I would like to know from @ergoemacs, @phillord, @ahungry, @leoliu, @Malabarba, and @fourier\r\n\r\n1. Should your package remain on Melpa? Why?\r\n2. Where does development happen primarily?\r\n3. How are the repositories synced?\r\n4. How often do you sync?\r\n5. Do commits flow in both directions?\r\n\r\nIf the answer to (1) is \"yes\", then I'll probably also mirror your Github repository on the Emacsmirror.\r\n\r\nI expcet that for `ergoemacs-mode` and `paabbrev` (3) should be trivial because they use dedicated branches in the Elpa repository.  But for the others this is less clear.  Do you use `git subtree` or do you do you just dump a version into the Elpa repository and create a commit \"update to version X\"?\r\n\r\n### Lets talk about subtrees\r\n\r\nIf you do use `git subtree`, then please also describe your workflow.  While I much preferred it if the Elpa repository used a separate branch for each package (or even a separate repository) the current approach forces the use of `git subtree` (or giving up on proper merges).\r\n\r\nI hope that eventually the Elpa repository will use one branch per package and one `master` branch which tracks all the package branches as submodules.  But that's not the issue here - for now we are stuck with `git subtree` (which some of you might actually prefer) or doing it by hand.\r\n\r\nI am considering adding support for `git subtree` to Magit - sharing your workflow will make it easier to get this right."},"comment":{"url":"https://api.github.com/repos/milkypostman/melpa/issues/comments/164883566","html_url":"https://github.com/milkypostman/melpa/issues/3383#issuecomment-164883566","issue_url":"https://api.github.com/repos/milkypostman/melpa/issues/3383","id":164883566,"user":{"login":"tarsius","id":25046,"avatar_url":"https://avatars.githubusercontent.com/u/25046?v=3","gravatar_id":"","url":"https://api.github.com/users/tarsius","html_url":"https://github.com/tarsius","followers_url":"https://api.github.com/users/tarsius/followers","following_url":"https://api.github.com/users/tarsius/following{/other_user}","gists_url":"https://api.github.com/users/tarsius/gists{/gist_id}","starred_url":"https://api.github.com/users/tarsius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tarsius/subscriptions","organizations_url":"https://api.github.com/users/tarsius/orgs","repos_url":"https://api.github.com/users/tarsius/repos","events_url":"https://api.github.com/users/tarsius/events{/privacy}","received_events_url":"https://api.github.com/users/tarsius/received_events","type":"User","site_admin":false},"created_at":"2015-12-15T20:13:20Z","updated_at":"2015-12-15T20:13:20Z","body":"Lol. I was just right now looking at this package in more depth."}}