On 22-03-30 09:19, Antonio Rojas via arch-dev-public wrote:
> El lunes, 21 de marzo de 2022 19:33:32 (CET), Brett Cornwall via
> arch-dev-public escribió:
> >
> > I'd be interested in:
> >
> > * spice-protocol
> > * libmusicbrainz5
> > * libdiscid
> > * libdvdcss (Not sure if that one should go to
On 22-03-16 16:23, David Runge via arch-dev-public wrote:
> On 2022-03-16 17:09:59 (+0200), Felix Yan via arch-dev-public wrote:
> > certbot
> > certbot-dns-rfc2136
>
> I can look into co-maintaining those with Jelle (who is at least
> maintaining cerbot) when I'm back. I'm using (some of) those my
On 22-02-02 21:03, Felix Yan via arch-dev-public wrote:
> There is a regex plugin and a htmlparser plugin for this.
>
> The htmlparser plugin accepts XPath, but if you want to process it further
> the regex plugin may just work better.
>
> Examples for your packages:
>
> [html-xml-utils]
> source =
On 22-02-01 08:21, Morten Linderud via arch-dev-public wrote:
> These require running arbitrary scripts on archweb so they should probably
> remain
> unsupported. Is there no better options?
At this stage, the following [community] packages that I maintain
require massaging of HTML sources:
* ht
On 22-01-31 21:25, Jelle van der Waa via arch-dev-public wrote:
> We’ve wanted automatic flagging packages out of date for a while and
> currently every packager has to come up with it’s own solution. Let’s solve
> this centralized by integrating nvchecker into archweb.
>
> nvchecker is a program w
On 21-07-16 10:10, Allan McRae via arch-dev-public wrote:
> And you can see my draft of a much more simple Code of Conduct here:
>
> https://gitlab.archlinux.org/allan/service-agreements/-/blob/coc/code-of-conduct.md
>
> I believe it still covers everything in the previous version while being
> onl
On 21-05-22 00:51, Morten Linderud via arch-dev-public wrote:
> Yo Andrzej :)
>
> I hope you are doing fine despite the circumstances!
>
> I adopted a few of your packages when you announced this in October. I'm just
> going to paste the current list of your packages missing a co-maintainer so
>
