Re: automating process for publishing DLAs on the website
- To: email@example.com
- Cc: firstname.lastname@example.org, email@example.com
- Subject: Re: automating process for publishing DLAs on the website
- From: Antoine Beaupré <firstname.lastname@example.org>
- Date: Fri, 01 Feb 2019 13:58:04 -0500
- Message-id: <[🔎] email@example.com>
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <handler.859123.B.firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
I'm looking at the update process for DLAs on the main website again. In
#859122, I've mentioned that I have, again, updated the MR to include
all DLAs up to DLA-1657-1. The www team folks tell me they will review
that this weekend.
But that mass-import process is kind of clunky: every time I need to
download the entire archive, extract it, parse every email, and add the
diff. It's slow and error prone and not automated, of course.
So I'm bringing back the topic of how we should automate this.
If I remember correctly, the current proposal is to add this as part of
the workflow for LTS developers: when you send the announcement on the
list, you also send a merge request on the website. This would get
reviewed and merged by another LTS developer with access to the webwml
At least me and Holger have those accesses for now, and I would suggest
people who do regular frontdesk work could make sure those MR are
reviewed and merged in a timely manner as well.
Would that work for everyone here?
If so, we can *already* start with that process, which would actually
look like this.
One time setup:
git clone https://salsa.debian.org/webmaster-team/webwml
Each time there's a new DLA:
./bin/gen-DLA --save $CHANGES # correctly claim the DLA
$EDITOR DLA-XXXX-Y # make sure the text is okay, like you normally
# do before the email gets sent
mutt -H DLA-XXXX-Y # send the email
git checkout -b DLA-XXXX-Y
git add 2019/DLA-XXX-Y*
$EDITOR 2019/DLA-XXXX-Y* # make sure everything looks good
git add 2019/DLA-XXX-Y*
git commit -m'DLA-XXXX-Y advisory'
git push -u origin
(Note: that "salsa" command is a new one shipped with devscripts. I only
read the manpage and didn't actually test that. :) Unfortunately, once
the MR is created, there's no magic command to merge it for
reviewers... Seems like this needs to be done through the web
I'd be happy if someone sat down and actually tested that procedure.
The alternative, of course, is to setup "something" that would
automatically parse emails to firstname.lastname@example.org but I suspect
that could be much more brittle than a manual operation like the above,
even if it means slightly more work.
Thank you for your attention.
Hard times are coming when we will be wanting the voices of writers
who can see alternatives to how we live now and can see through our
fear-stricken society and its obsessive technologies to other ways of
being, and even imagine some real grounds for hope. We will need
writers who can remember freedom. Poets, visionaries—the realists of a
larger reality. - Ursula Le Guin