[Soc-coordination] SoC report for the fedmsg project, week 3
chopin.simon at gmail.com
Mon Jul 8 09:34:41 UTC 2013
My most humble apologies, it seems I forgot to send out the draft
For the past week, I've done the following:
— Experimented with the PAIR-type sockets in ZeroMQ as a possible way
to allow clients to ask for replay in case of message loss.
— Think about ways for the client to actually notice message loss —
still WIP at the moment
— Hack up a small tool in Python/Hy, Debmessenger, to dump the
content of a Changes file delivered via mailing lists into a fedmsg
I am ashamed to say I haven't harassed my sponsors to get them to upload
all my packages to NEW, and the fedmsg code still hasn't been deployed
to the mentors.debian.net Debexpo instance.
For the next week, I plan to:
— start implementing the replay mechanism as soon as I have figured
out the detection angle, assuming upstream support on the proposal.
— harass olasd until he has deployed fedmsg on mentors.d.n.
— implement a -bugs-dist <-> fedmsg gateway in debmessenger
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
More information about the Soc-coordination