Hi! On Fri, 2025-08-22 at 10:16:39 +0200, Andreas Tille wrote: > Am Thu, Aug 21, 2025 at 03:19:31PM +0200 schrieb Guillem Jover: > > I see there are already some in: > > > > https://salsa.debian.org/debian-dpl/dpl-helpers > > Good catch! I noticed those texts differ somewhat from the final > delegation mails, and I'm not entirely sure what their intended role > was. I've left them unchanged but moved them into the appropriate > subdirectories in > > > https://salsa.debian.org/debian-dpl/dpl-helpers/-/tree/master/delegations?ref_type=heads > > In addition, I've started adding the actual delegation mail texts, using > the naming scheme YYYYMMDD. This makes it easy to find the corresponding > message in the mailing list archive. I'm in favour of keeping every > single delegation in one file since you can easier follow the history of > this specific delegation text. For sure we can also rely on Git to have > the history but for the moment I think we can stick to this.
I think it's more important to have the history available, than what shape it takes. One advantage of using different files (at least for now until things settle), is that they can be modified easily (such as adding URLs to the mailing list archive, or additional metadata). They could always be imported as a single file later on if needed. > Before going further (and I'd very much welcome help here!), we should > clarify the following: Should we > > * simply store the delegation text itself (perhaps including the mail > subject), or > > * keep the full mail with all metadata (To, Subject, From, Date, > Message-Id, signature)? For reuse purposes as templates for the next one, probably storing at least anything that you'd use with say «mutt -H delegation-file» seems helpful (Subject, To, Cc, etc). But I guess the other metadata could be added immediately after sending the delegation with no need for the mail to reach the archive, even with an URL with the msgid link Judit pointed out or a URL in the form used in the organization web page (see below). I guess this could even be scripted, like in: ,--- bin/delegate-refresh $delegation --- mutt -H $delegation/delegation -e "set record=$delegation/$date_now" inject msgid URL into $delegation/$date_now (with formail f.ex.) update $delegation/delegation symlink to $delegation/$date_now `--- > The second option is more complete for historical purposes, though > redundant with the list archive. The first option is easier to edit and > comment on - which I encourage and usually also invite future delegates > to do. See above. > > (Ideally importing all of the existing and obsolete delegations with > > their history? :) > > Definitely and I'd appreciate help in restoring the history there. ;-) I think <https://www.debian.org/intro/organization> has most (if not all?) of the delegated mails linked. (The webwml source for that might also have pointers, but probably not all (?), to old delegations.) Thanks, Guillem
