Gregory Chamberlain <greg@cosine.blue> writes:
> Hi Philip,>> I'd be delighted to see Aircon added to GNU ELPA. How can we do that?
Unless you have already signed the FSF copyright assignment, you should
fill it out and send it to the right address:
Philip Kaludercic <philipk@posteo.net> writes:
> Unless you have already signed the FSF copyright assignment, you should> fill it out and send it to the right address:>> Other than that, I can take care of all the remaining stuff. If you> decide against wanting to sign the CA, I can also add the package to> NonGNU ELPA.
Thanks, I've now sent the CA.
Greg.
Gregory Chamberlain <greg@cosine.blue> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>>> Unless you have already signed the FSF copyright assignment, you should>> fill it out and send it to the right address:>>>> Other than that, I can take care of all the remaining stuff. If you>> decide against wanting to sign the CA, I can also add the package to>> NonGNU ELPA.>> Thanks, I've now sent the CA.
Great, ping me when everything is done, then I can add the package.
> Greg.
Gregory Chamberlain <greg@cosine.blue> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>>> Unless you have already signed the FSF copyright assignment, you should>> fill it out and send it to the right address:>>>> Other than that, I can take care of all the remaining stuff. If you>> decide against wanting to sign the CA, I can also add the package to>> NonGNU ELPA.>> Thanks, I've now sent the CA.
Have you received any update?
> Greg.
Philip Kaludercic <philipk@posteo.net> writes:
>>> Unless you have already signed the FSF copyright assignment, you should>>> fill it out and send it to the right address:>>>>>> Other than that, I can take care of all the remaining stuff. If you>>> decide against wanting to sign the CA, I can also add the package to>>> NonGNU ELPA.>>>> Thanks, I've now sent the CA.>> Have you received any update?
Yes, the copyright assignment was completed yesterday. You can add the
Aircon theme to GNU ELPA now.
I am still improving the theme from time to time, pushing updates to the
repository at the URL below.
https://git.sr.ht/~chambln/aircon-theme.el
Occasionally I tag a commit as a new version, but these "releases" are
somewhat arbitrary. Although changes have been incremental for a while
now, I'm reluctant to call it stable just yet.
What is the process of a new release making its way to GNU ELPA? How
closely do GNU ELPA packages follow upstream releases?
Gregory Chamberlain <greg@cosine.blue> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>>>>> Unless you have already signed the FSF copyright assignment, you should>>>> fill it out and send it to the right address:>>>>>>>> Other than that, I can take care of all the remaining stuff. If you>>>> decide against wanting to sign the CA, I can also add the package to>>>> NonGNU ELPA.>>>>>> Thanks, I've now sent the CA.>>>> Have you received any update?>> Yes, the copyright assignment was completed yesterday. You can add the> Aircon theme to GNU ELPA now.
Great!
> I am still improving the theme from time to time, pushing updates to the> repository at the URL below.>> https://git.sr.ht/~chambln/aircon-theme.el>> Occasionally I tag a commit as a new version, but these "releases" are> somewhat arbitrary. Although changes have been incremental for a while> now, I'm reluctant to call it stable just yet.
I would not worry about that, there is no hard definition of stability
that all ELPA packages hold themselves to. I'd just try my best to not
mark releases with broken or untested code.
> What is the process of a new release making its way to GNU ELPA? How> closely do GNU ELPA packages follow upstream releases?
The package specification can be configured to synchronise the Git
repository daily, but new versions are released only when the version
tag is bumped. ELPA does not use Git tags at all. Between releases you
can check http://elpa.gnu.org/devel/ to see how a package would appear
if published. You should watch out not to force-push to your default
branch, because otherwise the upstream mirror will diverge and that will
have to be fixed manually.
Gregory Chamberlain <greg@cosine.blue> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>>>>> Unless you have already signed the FSF copyright assignment, you should>>>> fill it out and send it to the right address:>>>>>>>> Other than that, I can take care of all the remaining stuff. If you>>>> decide against wanting to sign the CA, I can also add the package to>>>> NonGNU ELPA.>>>>>> Thanks, I've now sent the CA.>>>> Have you received any update?>> Yes, the copyright assignment was completed yesterday. You can add the> Aircon theme to GNU ELPA now.>> I am still improving the theme from time to time, pushing updates to the> repository at the URL below.>> https://git.sr.ht/~chambln/aircon-theme.el>> Occasionally I tag a commit as a new version, but these "releases" are> somewhat arbitrary. Although changes have been incremental for a while> now, I'm reluctant to call it stable just yet.>> What is the process of a new release making its way to GNU ELPA? How> closely do GNU ELPA packages follow upstream releases?
Also could you apply these changes:
Philip Kaludercic <philipk@posteo.net> writes:
> Also could you apply these changes:>> The first and third change are the most important, since ELPA packages> are officially part of Emacs.>> The other ones are just recommendations.
Yep, done. Thanks!
To git.sr.ht:~chambln/aircon-theme.el
9aea676..4741bd1 master -> master
Gregory Chamberlain <greg@cosine.blue> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>>> Also could you apply these changes:>>>> The first and third change are the most important, since ELPA packages>> are officially part of Emacs.>>>> The other ones are just recommendations.>> Yep, done. Thanks!
Great, I have added the specification to the repository, so the package
should appear on the archive and the website soon.
> To git.sr.ht:~chambln/aircon-theme.el> 9aea676..4741bd1 master -> master
Before I forget, all contributors to GNU ELPA packages have to have
signed the CA, for any "significant" contribution making up roughly 15
lines of code or more. If someone hasn't done so, you can always direct
them to emacs-devel@gnu.org to request the assignment form.
> Before I forget, all contributors to GNU ELPA packages have to have> signed the CA, for any "significant" contribution making up roughly 15> lines of code or more. If someone hasn't done so, you can always direct> them to emacs-devel@gnu.org to request the assignment form.
OK, I'll keep that in mind.