Interesting development. Dropping the copyright assignment requirement is surely a good step. On the other hand, from the linked emacs-devel announcement:
> * The package may install other packages in GNU ELPA and NonGNU ELPA, but not any other software.
> We will consider exceptions to that rule, but we will need to consider them carefully, to make sure that the practices are safe for Emacs users, not just in one package but when used in many prackages. Each time we approve such an exception, we will say so in comments in the package, with an explanation of our reasoning.
> * Aside from packages obtained from GNU ELPA and NonGNU ELPA, a package may not run code that it has fetched over the internet.
Not being able to depend on anything from other sources, even MELPA, seems like a fatal flaw for adoption here.
Also, hopefully this doesn't come across as flamebait, but these are somewhat reminiscent of Apple's App Store rules about unbundled code, that we love to complain about with good reason. :/
1 comment
[ 3.4 ms ] story [ 14.7 ms ] thread> * The package may install other packages in GNU ELPA and NonGNU ELPA, but not any other software.
> We will consider exceptions to that rule, but we will need to consider them carefully, to make sure that the practices are safe for Emacs users, not just in one package but when used in many prackages. Each time we approve such an exception, we will say so in comments in the package, with an explanation of our reasoning.
> * Aside from packages obtained from GNU ELPA and NonGNU ELPA, a package may not run code that it has fetched over the internet.
Not being able to depend on anything from other sources, even MELPA, seems like a fatal flaw for adoption here.
Also, hopefully this doesn't come across as flamebait, but these are somewhat reminiscent of Apple's App Store rules about unbundled code, that we love to complain about with good reason. :/