emacs-async
emacs-async copied to clipboard
jwiegley
Stopping synchronizing to Elpa
Hi @jwiegley , I am stopping updating Elpa as I feel it is really unnecessary, most people are using async from Melpa and use github to report bugs, the Elpa system being more and more obsolete (reporting bugs at emacs-bug is a pain, there is no way on Elpa to know who commit on what etc... the list is long). I will though continue to update the elpa branch here on github, it is the one that is in sync with Elpa.
I know that my vote doesn't count for much, but I am glad that GNU Elpa exists and carries this package; the maintainers of that repository seem to be much more responsible around security than the maintainers of Melpa.
@thierryvolpiatto Not good. Maybe just most people you work with come from the Melpa universe? I wanted to report bugs about this package and see that they have been fixed here long ago. I dunno who the current maintainer of the package is, but if the current situation continues, we will end up with two diverging versions of this package, and this will double the efforts for all of use. @jwiegley do you still care about this stuff?
Michael Heerdegen [email protected] writes:
@thierryvolpiatto Not good.
Agree, no good, but I have not the time to synchronize on Elpa each time
I make a change (I even don't remember how to do it).
I don't want either to maintain this on Elpa directly
as it is a pain to work there for many reasons.
-- Thierry
Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997
Thierry Volpiatto [email protected] writes:
Agree, no good, but I have not the time to synchronize on Elpa each time I make a change (I even don't remember how to do it).
Yeah, it sucks, but also the other way round.
I don't want either to maintain this on Elpa directly as it is a pain to work there for many reasons.
Are you the maintainer now?
Ok, I wonder what we can do to improve the current situation. I think I need to synchronize something else soon, so I'll need to relearn how it worked anyway.
Are you checking that any changes to the code is in accordance with the Gnu standards (committers need to have signed "the papers" etc.)? If not, strictly speaking, we could not even synchronize any more AFAIU.
Michael Heerdegen [email protected] writes:
Thierry Volpiatto [email protected] writes:
Agree, no good, but I have not the time to synchronize on Elpa each time I make a change (I even don't remember how to do it).
Yeah, it sucks, but also the other way round.
Yes, even more on Elpa=>Github.
I don't want either to maintain this on Elpa directly as it is a pain to work there for many reasons.
Are you the maintainer now?
No, Jwiegley is the maintainer.
Ok, I wonder what we can do to improve the current situation. I think I need to synchronize something else soon, so I'll need to relearn how it worked anyway.
Are you checking that any changes to the code is in accordance with the Gnu standards (committers need to have signed "the papers" etc.)?
I think I was checking this (see the Elpa branch which was specific to Elpa requirement e.g. no *pkg.el) but now no, I don't check.
If not, strictly speaking, we could not even synchronize any more AFAIU.
Perhaps.
-- Thierry
Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997
Thierry Volpiatto [email protected] writes:
If not, strictly speaking, we could not even synchronize any more AFAIU.
Perhaps.
Hmm, but then the two versions will diverge, and we'll both have more work again then: you'll get the bug reports about the Elpa version, emacs-bug will get reports about things you have fixed or introduced, emacs-dev will have to fix things you have already fixed, the two versions will start to support different features, people will get confused which versions they should use and where to ask about support, emacs-dev will not care when your version should get broken with a change in Emacs, at least one of us will have to find a new name for the thing sooner or later, etc. I think the gain of time now will soon change into a lasting waste of time.
But I guess you have already discussed your problems and suggestions on emacs-dev and were disappointed. Dunno - is there anything one could do to ease your pain?
Michael.
@jwiegley Thanks. @michael-heerdegen Few people have contributed to this package and when it is the case not big patches that need FSF papers (need to verify though in git log). What diverge between the two branches is only packaging stuff which is different for Elpa than what is needed for Melpa e.g. *-pkg.el file. Also all users and package maintainers (magit) use the Melpa aka github version. We have a Elpa branch, all what is needed is merge it or cherry pick what is needed with master.