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

[Juha T. <Juh...@ik...>]

On Monday 19 October 2009 21:37:13 Chris Frey wrote:
> 	- everybody is using the latest code
> 	- any bug that needs to be fixed, or feature that needs to be
> 		implemented, will be felt immediately
> 	- anyone who feels that need, will have the ability to scratch
> 		that itch immediately, and see their work released
> 		within a month, thereby solving both OpenSync's problem
> 		and their own in real time

> People need to be invested in the current code, not 0.22.  Right now,
> 0.22 doesn't solve their needs, 

That's what i suggested a long time ago. We need to officially
announce 0.22 dead, kill it. Fedora upgraded their versions to 0.3x and
then reverted back to 0.22 even i tried to stop that idea there too. :)

If you want to keep everyones eyeballs out of focus (current code), best
way to do is to distract them to look something else. _Opensync is a name
that stands for the concept of pda syncing_. Everyone knows it already.

People stare at the 0.22 and see that's it is not good for anything else 
than filling a package in distro.

That damages both our needs (more eyeballs) and the name. There is no need 
to keep an active placeholder in distros, since everyone knows the name already.

So, i suggest (with quite minimal effort):

- drop 0.22
- leave space empty or...

  Perhaps we should just lift the ban to upgrade distro releases for 0.39?
  That is - announce that it's very close to finished API and everyone should 
  package it now, since once the possible fixes to API happen in next releases,
  those will not be big changes in apps and wont cause lot to work to update.
  Then it would not break the promise of 0.40 with stable api and make people
  stare the current code.

There are not many (or none) using the 0.3x api except our own tools, so people
using those would be able to easily test it via distro packages and we would
be able to do the remaining work until anyone really puts lot of effort to 0.39
api in app - which anyway wont be that much different from 0.40 proper.

btw, Chris you've very valid points in your comments, keep them coming.


Tuju

-- 
Better to have one, and not need it, than to need one and not have it.