bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0

[Protesilaos Stavrou <info@protesilaos.com>]

[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]

On 2020-10-16, 10:13 -0700, Stefan Kangas <stefankangas@gmail.com> wrote:

> Protesilaos Stavrou <info@protesilaos.com> writes:
>
>> + The two themes are also available in GNU ELPA.  What is the best way
>>   to ensure that we sync between emacs.git and elpa.git?  GNU ELPA has
>>   hitherto pulled from dedicated branches on my upstream git repository.
>>   Maybe it would be better/easier to start building directly from the
>>   Emacs source?  This would reduce the overall workload.
>
> What does "start building directly from the Emacs source" mean here?

"Build" is the wrong term here.  Sorry about that!  My intent is to find
an easy way/workflow to get the files from Emacs into GNU ELPA.

And by "easy" I mean not to duplicate the work we do here.  So I would
not have to contact the GNU ELPA maintainers separately and have them
pull from my git source.

> FWIW, I don't think we should feel too bound to any particular process;
> this seems like a practical matter where we should try to do whatever
> is most practical.

Good to know.  I have no particular preference on the matter and shall
adapt to whatever you and others may recommend.

>> + Sending attachments with large diffs has the downside of losing the
>>   commit history.  Do Emacs maintainers wish to keep track of it?  If
>>   so, what would be the best way to preserve it, seeing as I am
>>   developing them on my own upstream?
>
> I don't think we generally worry about preserving history for packages
> managed externally.  We just sync the latest version.
>
> (If one really would like to preserve it, it could perhaps be done with
> some git magic.  I'm not sure it's worth the extra effort.)

Syncing the latest version works fine for me.

I have thus far published tagged releases on a monthly cadence.  Expect
the next one in mid to late November.

>> + Should the texinfo file be mentioned in the NEWS entry about the two
>>   themes?  The attached patch does not include such a change.
>
> We could of course add a NEWS entry for it.  Would you like to propose
> one?

I attach a possible rewording that also corrects "colour" and adds an
explicit reference to the WCAG AAA accessibility spec.  Please note that
I do not know how to properly reference an Info node: I used 'C-u 0 x',
which calls 'Info-copy-current-node-name'.

-- 
Protesilaos Stavrou
protesilaos.com

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Update-Modus-themes-NEWS-entry.patch --]
[-- Type: text/x-patch, Size: 1252 bytes --]

From 4b235a54973570aeb9330c15315f47682b7f121f Mon Sep 17 00:00:00 2001
From: Protesilaos Stavrou <info@protesilaos.com>
Date: Sat, 17 Oct 2020 09:50:48 +0300
Subject: [PATCH] Update Modus themes' NEWS entry

* etc/NEWS: Reword entry about new 'modus-operandi' and
'modus-vivendi' themes.  Include reference to their manual.
---
 etc/NEWS | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/etc/NEWS b/etc/NEWS
index 1838b6b38a..d782e6c12c 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -1403,9 +1403,11 @@ mode, as are other data files produced by Emacs.
 It's a library to create, query, navigate and display hierarchy structures.
 
 ** New themes 'modus-vivendi' and 'modus-operandi'.
-These themes are designed for colour-contrast accessibility.  You can
-load the new themes using 'M-x customize-themes' or 'load-theme' from
-your init file.
+These themes are designed to conform with the highest standard for
+color-contrast accessibility (WCAG AAA).  You can load either of them
+using 'M-x customize-themes' or 'load-theme' from your init file.
+Their on-line documentation describes the customization options they
+provide.  Consult '(info "(modus-themes) Top")'.
 
 \f
 * Incompatible Editing Changes in Emacs 28.1
-- 
2.28.0