On Thu, 24 Aug 2017 00:32:20 +0200, Alex Muntada wrote: > > Will try to attend, without any garantee as I'll be doing the > > Alioth Sprint thing. > Thanks for your work on the Alioth sprint last weekend. Even > though the sprint is over, I'll follow up with some details > regarding the questions you raised below. Thanks for this summary! I'll just add some details. > AFAIK pkg-perl most used service in alioth is git, plus remote > hooks that send notificacions to IRC and lists, and another hook > that builds the HTML web pages from POD files in website repo. And PET. > KGB instances run on dmn's, gregoa's and Tincho's servers. Right, and the client is an Alioth, triggered by our hook script. > PET seems to run on petrova.debian.org, so it's not an alioth > service though it may depend on some alioth magic like repos > traversal, running local scripts, etc. that send changes to PET. Right, it's also triggered by our hook script (and a cronjob with "update-all" just to make sure). Additionally, our fancy .mrconfig piggy-backs on PET's cache file (to `git pull' only from repos where the local last commit differs). And .mrconfig itself is updated by dpt-alioth-repo (locally) and by a bunch of scripts on alioth for adding/archiving/removing git repos. Tagging bugs pending also happens from the hook. /home/groups/pkg-perl/meta/pkg-perl-post-receive > Both pkg-perl lists (pkg-perl-maintainers and pkg-cvs-commits) > are used mostly for notifications (VCS, bts, etc.) so they don't > match the criteria for migrating them to l.d.o, AFAICT. In the > case of pkg-perl-maintainers, we'll need to come up with some > solution since it's the contact in Maintainer field in d/control > for all 3400+ packages maintained by pkg-perl team. Not sure if we can create a list on l.d.o for pkg-perl-maintainers, but since (as Christoph found out) this affects 58% of all packages (having @lists.alioth.d.o in Maintainer) I hope for some solution. > The LHF reminder is run by a Dom's cron job somewhere. Ack. > The pkg-perl calendar file in website repo is built manually by > dmn, AFAIK. Ack, that's a static file, manually curated in git and exposed via the webspace. > perl.debian.net server runs on Dom's hardware. Right. > The annual ping reminder for pkg-perl members is run in alioth > via pkg-ruby-extras' find-inactive-contributors, plus some > additional steps for pkg-perl. We'll need to figure out how to > do the same for git.d.o replacement. And I guess we have some time for it, as the new pkg-perl team on salsa.d.n will start out with 0 members, if I understand the plans correctly. > There's a proof of concept pkg-perl manual in the website repo > that is build from POD files via Sphinx and then rsync-ed to > alioth manually. Since Sphinx is getting traction in other > Debian teams too, I expect that some kind of service will be > setup eventually that we could use too. Right. > That's all I can remember so far. There are also scripts/cronjobs to produce the 2 files in https://pkg-perl.alioth.debian.org/qa/ but I guess we can live without them :) > I guess we'll need to draft > some plans for things that are going to break when alioth is > put in read-only mode and finally shut down. I think it's good to collect things that we need (as we do right now :)); for most issues I hope there will be general solutions or howtos etc. as many projects are affected. Maybe we should start a gobby doc or wiki page to list our tasks? Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Peg Leg Sam: Joshua Fit The Battle Of Jericho
Attachment:
signature.asc
Description: Digital Signature