5:22 a.m.
Hi,
As part of my GSoC project this week, I've done the following:
— Hacked up some -bugs-dist support in debmessenger[1].
— Thought up a preliminary implementation of a replay protocol for
fedmsg in case of dropped messages[2][3].
— Deployed fedmsg on mentors.debian.net (well, most of the work has
been accomplished by Nicolas Dandrimont, kudos for that BTW).
For the curious amongst the readers, you can listen to the chatter
by adding tcp://mentors.debian.net:300[0-4] to the list of
endpoints.
— Implemented service discovery through SRV records in fedmsg
(untested as of today)[4]
For next week, I plan to:
— Rewrite the replay mechanism as the more I think about the current
implementation the less I'm happy with it.
— Deploy a fedmsg gateway that will consume all debian-produced
messages and resend them on a single endpoint, much like [5].
— Work out the last kinks in my packaging (I know, I say that every
week, but try to deal with an overcommitted sponsor ;-) )
— Maybe, deploy an instance of debmessenger somewhere.
Have a nice week-end all!
Cheers,
Simon
[1]
https://github.com/laarmen/debmessenger/commit/dde1454cf362f4f4755d6c9b2a...
[2] https://lists.fedoraproject.org/pipermail/messaging-sig/2013-July/000008....
[3] https://github.com/laarmen/fedmsg/tree/feature/replay
[4] https://github.com/laarmen/fedmsg/tree/feature/srv-records
[5] tcp://hub.fedoraproject.org:9940
11:08 a.m.
New subject: Status report, week 5: FedMsg for Debian
Hi,
Here is my weekly report.
Let's start by see how much I sticked to the plans:
For next week, I plan to:
— Rewrite the replay mechanism as the more I think about the current
implementation the less I'm happy with it.
=> That's done, at least for the server side. I've spent most of my week
on that, to finally come up with this PR[1].
— Deploy a fedmsg gateway that will consume all debian-produced
messages and resend them on a single endpoint, much like [5].
=> Also done, although not by me. Nicolas Dandrimont, my mentor, is to
thank for that.
— Work out the last kinks in my packaging (I know, I say that
every
week, but try to deal with an overcommitted sponsor ;-) )
=> I've done what I could short of bribing the ftpmaster people to make
the packages that are already uploaded go through NEW faster. The
fedmsg package itself is probably not in the best of shapes but it is
functional.
— Maybe, deploy an instance of debmessenger somewhere.
=> Once again, Nicolas is to thank for that.
The gateway is accessible at tcp://fedmsg.olasd.eu:4001
and debmessenger alone can be listen to at tcp://fedmsg.olasd.eu:3000
Nicolas also set up an IRC bot listening to the gateway and
retransmitting everything on #debian-fedmsg on OFTC.
As a result, I've hacked up a fedmsg-meta-debian package[2] in order to
have some pretty-printing for the bot.
My plans for next week are:
- Implement the client side of the fedmsg-replay mechanism
- Write some tests for my SRV-documented endpoint system and get it
merged upstream
- Take a stab at the GPG signing stuff.Take a stab at the GPG signing
stuff.
That's all folks!
Cheers,
Simon
[1] https://github.com/fedora-infra/fedmsg/pull/155
[2]
http://anonscm.debian.org/gitweb/?p=users/laarmen-guest/fedmsg-meta-debia...
12:37 p.m.
New subject: Status report, week 5: FedMsg for Debian
Hi!
Here is my weekly report, sadly thiner that I would have like due to
unfortunate circumstances, namely the destruction of my $HOME along with
two days worth of unpushed commits.
The only thing I've managed to accomplish is the implementation of the
client part of the replay feature for fedmsg, along with tests[1]. I've
briefly looked into the gpgme package for the GPG crypto backend, but
nothing concrete has come out of it yet.
My plans for next week are the followings:
- Do everything I was supposed to this week:
Quoting Simon Chopin (2013-07-19 18:08:42)
- Implement the client side of the fedmsg-replay mechanism
- Write some tests for my SRV-documented endpoint system and get it
merged upstream
- Take a stab at the GPG signing stuff.
- Put a rush on the upload of fedmsg to unstable so that we could have
it backported in time for DebConf
Cheers,
Simon
2:10 a.m.
New subject: Status report, week 7: FedMsg for Debian
Hi!
(since I'm pretty sure it is still Friday somewhere, let's say I'm not
late shall we? :-) )
This is my weekly report, once again.
What has happened since last week:
* The server support for replay has gone into mainline
* I wrote some documentation for it, currently sitting in a PR on
github
* I've reached a state I'm cumfortable with on my client replay code,
I however still have to write the PR, I will probably do it over the
weekend.
* Thanks to algernon, the first round of fedmsg dependencies have
reached unstable. The only blocker before the second wave is a
missing source for a PNG file, I've pinged upstream about it.
* We've sat down and decided on how to address some issues specific to
Debian infrastructure, resulting on a wiki page being created to
document it[1].
* Since we've changed the topic scheme, I've patched debexpo,
debmessenger and fedmsg-meta-debian to take the new scheme into
account.
* Following feedback from the wiser, I've rewritten the part of
debmessenger that were implemented in Hy in Python to reduce the bus
factor, since it appears not many people are cumfortable with Lisp.
Tsk tsk ;-)
* I've spent my whole Friday hunting down a bug somewhere in the gpgme
stack where it sometimes hung forever on some signed emails. While
the bug is only in my mail client so far, since I plan on using the
same software stack for fedmsg I'd like that to be fixed, or at
least identified, neither of which is True :/
For next week, I plan to:
* Finally upstream all of the code that's sitting on my clone
* Hunt down that bug, or look for alternative gpg bindings — there
seems to be a plethora of those.
* Catch up on my schedule and write the GPG backend for the message
signing.
Cheers,
Simon
[1] http://wiki.debian.org/FedMsg
11:25 a.m.
New subject: Status report, week 5: FedMsg for Debian
On Fri, Jul 19, 2013 at 06:08:42PM +0200, Simon Chopin wrote:
As a result, I've hacked up a fedmsg-meta-debian package[2] in
order to
have some pretty-printing for the bot.
Nice! I filed a ticket[1] so we can use it to include debian
endpoints/topics/messages in the fedmsg.com docs at some point in the
future.
Exciting!
[1] https://github.com/fedora-infra/fedmsg/issues/159
3959
days inactive
3981
days old
messaging-sig@lists.fedoraproject.org
4 comments
2 participants
participants (2)
-
Ralph Bean -
Simon Chopin