new maintainer Re: [PEAR-DEV] Re: [ANNOUNCEMENT] System_SharedMemory-0.0.4 (beta) Released.

Stefano F. Rausch wrote:

However, having said this, I would expect that at least the first official release does fully comply with the PCS! Let's see it from a

I dont think this necessarily needs to be the case for the first set of alpha releases at the beginning. Then again its very important that the directory stucture and file naming is done right at the beginning, since this can hardly be changed in CVS.

Futhermore, I find it really boring that most of the new proposals have comments like "please be so kind to conform with the PCS" ... do we have guidelines to follow or not? Do we want to achieve consistency within the PEAR project or not? Otherwise we could just postpone the whole PCS topic 'til the first official package has been released and only then start insisting on it - i.e. it would not matter how the proposal is presented, for only the added value and the desing of the package would be of importance.

Well the learning curve in PEAR development is not exactly steep imho, but it is there. I think as long as the package is in early alpha the developer can one by one work through things. We might also add an entry to the new maintainer guide "your first release: a checklist". Some of the regulations are also missing from the manual. I just opend a bug report on this. Finally we might consider sending an email to all new developers which points them at the "new maintainer" guidelines and welcomes them to the team. regards, Lukas