Hello, In addition to the list of actions that bill-auger mentioned, I can think of the following tasks:
- send a note to [email protected] announcing the new release - ensure that all code contributors have the necessary copyright assignments granted - set up distribution through the extension stores of other browsers that support the WebExtension APIs (such as Google Chrome) I have gone through the steps to be listed as the "official" maintainer of LibreJS, but I agree that if Nathan is so inclined, he would make a better candidate for that role than myself (and I'm happy to share the maintainership role too). I will communicate with Reuben, Loic, and Nick about getting access to the Mozilla Addons page/account and will get the git repo in the required state. -zach On Sun, Dec 17, 2017 at 1:27 AM, bill-auger <[email protected]> wrote: > > > off-hand i can think of a few things that would need to be done - ping > me in the #librejs channel if you need my help with any of them > > * copy some important files from the master git branch such as > 'ChangeLog' and the 'dcos' dir to the 'webext' git branch > * append to the ChangeLog and write up a press release noting any > improvements and added or removed features > * update the documentation[1] and commit to git > * add a git tag of the form MAJOR.MINOR.REV (e.g. the latest is 6.0.13) > the the HEAD of the 'webext' branch > * rename the 'master' git branch to 'old-stable' then rename the > 'webext' git branch to 'master' > * upload signed tarball and installer (.xpi) to the GNU FTP server[2] > (this could/should have been done already for the alpha versions[3]) > * upload the new version to the official mozilla addons page[4] > * update the librejs website[5] (again this could/should have been done > already to mention the alpha versions) > * update the FSD page[6] > > i realize that many of these things you will not be able to do yourself > (and there are surely some things i have missed) - the original > maintainers will need to attend to some of these tasks - Loic, Nik, and > Ruben are noted as maintainers for the mozilla repo - i dont know who to > ask about the GNU website and FTP server > > i must add though, that some discussion regarding the future maintenance > plans for this project are imperative - and yes, i mean BEFORE it is > released - there has been little discussion (either public or private) > regarding this new version and nathan has been the only person doing any > significant work on it - i think it is safe to say that he did 99.9% of > the work on this version and is probably the only person who has read > more than 5% of the the source code for it - so without nathan's > continuing involvement, this future of project is highly dubious - > indeed, if nathan had not done this work, there would be no librejs at > all; because the existing version has been obsoleted - unfortunately > that work appears to have ceased 6 weeks ago while the project is still > in the alpha phase; and this is clearly reason for concern - so there > are some critical points to address such as: > > * whether nathan (or anyone) plans to write more code and actively > maintain this project or is this essentially releasing abandon-ware from > day 1 - this must be asked because the answer is not at all apparent > > * whether nathan should (and wants to) become an official maintainer as > noted prominently in the "Maintainer" section of the website front page > and given write access to the official mozilla add-ons page - this must > be asked bacause zach is the only person from the original dev team that > has paid any attention to this project since i have been involved; and > zach is not one of the people with write access to the mozilla page > > > [1]: https://git.savannah.gnu.org/cgit/librejs.git/tree/doc > [2]: ftp://ftp.gnu.org/gnu/librejs/ > [3]: ftp://alpha.gnu.org/gnu/librejs/ > [4]: https://addons.mozilla.org/en-US/firefox/addon/librejs/ > [5]: https://www.gnu.org/software/librejs/ > [6]: https://directory.fsf.org/wiki/IceCat/GNU_LibreJS >
