hoaproject / contributions-emacs-pp Goto Github PK

There are still some things to do to finish moving this package from my personal repository to this one.

First, the version included in this repository is not up to date. We should take the last version from my repository, which also has auto-indentation.

Then, the readme from the old repo needs to be adapted and inserted in the new one.

We can also talk about the license. I used the GPL license because it seems good for an Emacs package targeted to end-users, but if there is a preferred license for Hoa sub-projects I don't mind changing it.

After the codebase has been updated, we will have to prepare for registration in MELPA. MELPA is an archive for Emacs packages. You can register your package on it by providing the github repository. Each time there is a commit on master, MELPA detects it, and update the package in its archive.

As the master branch of some packages can be unstable, there is another archive, MELPA stable, that looks if new version tags have been created in the package's repository so that the package maintainer can control the releases.

I started to write version tags in my personal repository. Should we keep doing it? If I understand correctly, Hoa projects use a continuous delivery system, So I suppose every push to master must be stable.

In any case, we will have to register the new package's repository in MELPA. It is done by addressing a pull request to the MELPA repository.

And finally, when the PR to MELPA is accepted, I just have to close my personal repo and the migration will be over \o/

Do you have any thoughts about this plan?