Re: [Plib-devel] Portability - policy suggestion

[Frederic B. <fre...@fr...>]

Steve Baker a =E9crit :

> Alex Perry wrote:
>
>> Steve, maybe we could have a policy that, for every apparently-support=
ed
>> target architecture, at least one of the developers with write access
>> must be able to build and run code on that architecture.
>
>
> I have never yet refused a request for developer privilages.  If someon=
e
> wants to do that, they only have to ask.  I believe I gave one of the B=
SD
> guy's access only a week or two ago.

It could help to use a central patch submission repository like the one=20
provided by sourceforge, so patches are not lost in the bulk of the=20
list. I see the 'Patches' option is not enabled for the Plib project but=20
it is available to project admin. As an example, here is the patch=20
submission form from the fgsd project :
http://sourceforge.net/tracker/?func=3Dadd&group_id=3D45131&atid=3D441962

A list of categories could help too, beginning with the list of=20
currently supported OS, and an assigned maintainer that could refer to=20
the list just *before* a release if he follow the list loosely.

-Fred