Re: [Opensync-devel] Fixing the OpenSync core development BUS factor

[Chris F. <cd...@fo...>]

On Mon, Oct 19, 2009 at 09:14:27PM +0200, Daniel Gollub wrote:
> Actually i planned to target also pool B - at least some of them.
> Do you see any chance that i get any of those?

I liked your topical list.  That kind of project breakdown is good for
anyone to get a mental handle on things.

But I can only talk from my own experience here, which is as part of
the team for the barry-sync plugin.

I don't really have time to read all the code in opensync, so I end up
focusing on the parts that pertain to me.  This ends up being the plugin
API, learning as I go, and the opensync_time.c functions, which I
started looking at back when I was trying to do timezone stuff correctly.
(Still haven't finished that in the barry-sync plugin.)

Also, I've been working a bit on the application side of the opensync API,
and I find little things there too.  If I can read the code and submit
a fix, I just go ahead and commit it.

So that's 3 areas that I'm interested in: plugin API, time functions, and
application side API.  But I don't have the time to volunteer to take
charge of any of them, only to contribute where I bump into issues.

So, while I consider myself in pool B, unfortunately I'm passing by
your list completely, since I'm not in pool A, and don't have the time
to take on any more responsibility.

Not sure if that answers your question...

- Chris


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.