Re: One ticket per week?

> the biggest problem of opensync is that the project is lacking of
> developers. Currently there are only a few guys (summarized maybe 2.5
> people) which are working on the core to get a new release and no one of
> us has much free time to spend on hacking. I started to work on opensync
> more than one year ago and can't say that I understand all parts.
> Therefore I am not able to fix all kind of tickets (i.e.
> http://www.opensync.org/ticket/1084) and rely on Daniels knowledge.
> Daniel is the only one who (nearly) knows the complete code and has an
> overview of all problems. But recently he started a new job and I guess
> that's the reason (besides the nice weather ;-) ) why the development
> stagnates again.
>
> Many many people are asking why opensync isn't ready and it really
> s***ks to me too that we don't have a stable version yet. But also
> nobody appears who is able to take a look at the code and make some
> patches. THAT would be really helpful. I don't think that money is going
> to speed up the development (except you are able to pay for a developer
> ;-) ) I have a job beside opensync and therefore I have to find some
> rare time to spend on it. Money wouldn't make a difference to me.
>
> So if you are willing to work on opensync maybe you can try to look at
> the code. Start to write some patches for the trivial tickets
> https://www.opensync.org/report/13 or write/improve a plugin to
> understand the behaviour of opensync. This ticket
> https://www.opensync.org/ticket/972 could also be a good starting point.
> Feel free to ask on the mailing list if you have additional questions.
>
> Btw. not all tickets need much work. There are a lot of tickets which
> are invalid already or can be fixed in some mins. But currently we have
> to focus on the blockers for 0.39.