Re: having emacs-matlab in ELPA, finally. FSF paper signed

[Uwe Brauer]

>>> "AC" == Andrea Corallo <acorallo@gnu.org> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>> Hi all
>> 
>> After quite a bit of time I can say the following :
>> 
>> 1) All authors/contributors have either signed the corresponding FSF
>> papers, in the very few cases where they have not, their
>> corresponding code has been completely removed and therefore
>> matlab-emacs could be in ELPA. Eli gave me his ok. (And RMS a
>> while ago, if all legal requirements would be satisfied, of course).

> Hi,

> that's great news!

>> 2) Can someone please provide me with some information or a link how
>> to proceed? I have to say that we, the authors, are now cleaning
>> up a bit the repository, rebase, delete obselete branches etc,
>> before including the package in ELPA.

> The ELPA README is the place to start from
> <https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/README>

Thanks for this pointer. I had a first glance, it reminds me very much
on the xemacs package system (but that used mercurial not git😉). 

I have to read it in more details, but so far, I have two questions.

    1. The name of the branches is fixed, that is the principal branch
       has to be called main (and couldn't be called say default?)

    2. Matlab is right now in MELPA and it seems much simpler to add a
       package to MELPA than to ELPA. Is one of the reasons, the github
       interface MELPA uses, but ELPA is bound to savannah that does not
       provide something similar?

Regards

Uwe 
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine.

smime.p7s
Description: S/MIME cryptographic signature