Re: Getting involved with conduit


I've got involved in Conduit fairly recently too. I started by writing/fixing the Rhythmbox dataprovider and some parts of the iPod module (this later on as part of Google Summer of Code).
That is a pretty good starting point, make it work for something you care. I'm not sure about the Evolution module status, but there are some recent work on that area, maybe John Carr could explain it better.

But something I missed when I started working on Conduit was the developer page in the homepage:
That is a good way to learn about the Conduit code. Just be careful about the configuration dialog code, it changed recently and the docs wasnt updated.

Btw, how can I edit the Conduit wiki? We should also update our API docs at it's fairly old and outdated. I started to work on some Sphinx based documentation at my github account, although I didnt get far, it would be great if we could migrate to it (we could probably do some automated scripts to migrate).

On Wed, Jun 3, 2009 at 18:01, Mats Taraldsvik <mats taraldsvik bickeringleague net> wrote:
Any interest in new contributors at all? :)

I am not asking for mentoring, just some advice on bugs (or other stuff)
that might be suited for someone who wants to start contributing to

On Wed, 2009-05-27 at 23:43 +0200, Mats Taraldsvik wrote:
> Hi,
> Are there any "favourite" entry points for getting started on conduit
> development? I didn't find many gnome-love bugs in bugzilla ...
> Actually, if there are any (easy/beginner) tasks related to syncing a
> phone (contacts, notes, tasks, calendar) to evolution, I'd love to help!
> Mats Taraldsvik
> _______________________________________________
> Conduit-list mailing list
> Conduit-list gnome org

Conduit-list mailing list
Conduit-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]