Re: [Vxl-maintainers] Pruning the developer list

[Miguel A. Figueroa-V. <mi...@ie...>]

On Tue, Mar 17, 2009 at 9:35 AM, Matthew Leotta wrote:
>
> On Mar 17, 2009, at 9:22 AM, Wheeler, Frederick W (GE, Research) wrote:
>
>>
>> Amitha wrote:
>>> Given that svn has anonymous http access to the repository,
>>> this is probably a good time to prune down the developer
>>> list.  I propose that we purge the list and re-fill using the
>>> developers that Miguel determined from the commit history.
>>> Unintended drops can be easily re-added by the admins.
>>
>> This is a good idea.  There are many people at GE with write access to
>> the vxl CVS repository, not because they will ever commit, but because
>> our firewall allows us to make ssh but not pserver connections to
>> sourceforge.  And at sourceforge, anonymous CVS access is only
>> available
>> via pserver.  With SVN comes anonymous read-only access via http,
>> which
>> the firewall allows.  So our problem goes away, and pruning makes
>> sense.
>>
> I also agree with this.  We don't have the firewall issue at Brown,
> but some students have graduated and may no longer be involved with
> vxl development.  However, I can think of at least a couple users who
> didn't make the "most recently active" list, but probably will still
> want to make contributions.  We should probably keep a list of old
> users around so that the admins can quickly reactivate those users
> upon request without going through the usual programming background
> check process again.
>
> Matt

This sounds reasonable to me. I was checking the vxl-commit mailing
list and there are people that have committed as close as January (600
commits only go as far as february) that didn't make it. I apologize
for this, but even after going a little farther in time there will
inevitably be people that I miss that should have access.

So, having this list stored in some place for immediate approval is
good, I think.

--Miguel