Re: [Plib-devel] Portability - policy suggestion

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

Frederic Bouvier a =E9crit :

> Steve Baker a =E9crit :
>
>> Alex Perry wrote:
>>
>>> Steve, maybe we could have a policy that, for every=20
>>> apparently-supported
>>> 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 someo=
ne
>> wants to do that, they only have to ask.  I believe I gave one of the=20
>> BSD
>> guy's access only a week or two ago.
>
>
> It could help to use a central patch submission repository like the=20
> one provided by sourceforge, so patches are not lost in the bulk of=20
> the list. I see the 'Patches' option is not enabled for the Plib=20
> project but it is available to project admin. As an example, here is=20
> the patch submission form from the fgsd project :
> http://sourceforge.net/tracker/?func=3Dadd&group_id=3D45131&atid=3D4419=
62
>
> 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.

May I also suggest that any new ( or already registered ) developer be=20
assigned a specific task/category so that it is clear who is doing what=20
and no one wait the other do the job.

I am volunteering to maintain the windows build. My sourceforge account=20
is 'fredb'.

Regards,
-Fred