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

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

On Mon, Oct 19, 2009 at 06:29:24PM +0200, Daniel Gollub wrote:
> I want to suggest now that we _all_ should try something new:
> 
> We look for volunteers who are interested in becoming OpenSync core 
> contributors and assign special components of the core to them. There is no 
> deep knowledge in OpenSync core development required today ... just the 
> willing to help the OpenSync development and maybe some very basic C 
> programming is required (i leanred C also while programming on OpenSync ... so 
> don't hesistate to start here as well).

Continuing from my previous email in the other thread....

There are two pools of developers:

	A) developers who have lots of free time and are looking for
		a project to significantly contribute to

	B) developers who are solving their own problems and willing to
		help another project only so far as it helps them

Pool B is a whole lot bigger than pool A.

The above strategy only targets pool A.  We're publishing a list of bugs,
and asking who wants to step up and fix them.

Going with my suggestion (see other email on losing API stability)
targets both pools, since:

	- 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

One of those needs is documentation.  I think releasing 0.5x and dropping
API stability will help fix that too.

People need to be invested in the current code, not 0.22.  Right now,
0.22 doesn't solve their needs, and 0.4x is held up by artificial constraints,
so people are developing their own non-API-stable platforms.

- Chris


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