« Return to Thread: One ticket per week?
Re: One ticket per week?
by Bjšoern Ricks-2
::
Rate this Message:
Hi Dotan,
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.
> I have been following OpenSync development for about two years, hoping
> to have sync between my Nokia 6288 and KDE-PIM (specifically,
> Kaddressbook and Korganizer, the contacts and calendar components).
> However, it seems that the rate of progress stands at about one issue
> closed per week (http://www.opensync.org/roadmap?show=all), and at
> that rate 0.41 ("Completing this milestone will lift the distribution
> packaging ban.") will be ready in around August 2010. So in the most
> troll-free and understanding manner, I ask the community what I, as a
> user, can do to get my contacts on the phone in a stable, non-hacky
> manner. Should I switch to Windows / Outlook / Nokia's sync suite?
> Should I donate $20 to the Opensync project? Should I learn to program
> and fix it myself?
>
> I appreciate the dev's work and I am _not_ complaining. I am only
> asking because I have been waiting for a long time and it does not
> look like the wait is going to end anytime soon. There is no need to
> be defensive, I understand the dimensions of the problems being solved
> by the devs and I am very grateful for their work.
>
>
--
/Bjoern Ricks
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Opensync-users mailing list
Opensync-users@...
https://lists.sourceforge.net/lists/listinfo/opensync-users
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.
> I have been following OpenSync development for about two years, hoping
> to have sync between my Nokia 6288 and KDE-PIM (specifically,
> Kaddressbook and Korganizer, the contacts and calendar components).
> However, it seems that the rate of progress stands at about one issue
> closed per week (http://www.opensync.org/roadmap?show=all), and at
> that rate 0.41 ("Completing this milestone will lift the distribution
> packaging ban.") will be ready in around August 2010. So in the most
> troll-free and understanding manner, I ask the community what I, as a
> user, can do to get my contacts on the phone in a stable, non-hacky
> manner. Should I switch to Windows / Outlook / Nokia's sync suite?
> Should I donate $20 to the Opensync project? Should I learn to program
> and fix it myself?
>
> I appreciate the dev's work and I am _not_ complaining. I am only
> asking because I have been waiting for a long time and it does not
> look like the wait is going to end anytime soon. There is no need to
> be defensive, I understand the dimensions of the problems being solved
> by the devs and I am very grateful for their work.
>
>
--
/Bjoern Ricks
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Opensync-users mailing list
Opensync-users@...
https://lists.sourceforge.net/lists/listinfo/opensync-users
« Return to Thread: One ticket per week?
| Free embeddable forum powered by Nabble | Forum Help |
