Ned and I maintain the StarBrowser package.


On Thursday, Aug 7, 2003, at 00:58 Europe/Zurich, 
goran.krampe at bluefish.se wrote:

> Hi all!
>
> Colin Putney <cputney at wiresong.ca> wrote:
>> Göran wrote:
>>
>>> Now, that said - as a few of you may be aware SM1.1 will include the
>>> concept of "accounts" which will enable tons of nice things to come.
>>>
>>> Today we have per package:
>>> 	- Author
>>> 	- Maintainer
>>> 	- Registrant
>>>
>>> I am keeping author as before but I am simplifying by dropping the
>>> distinction between registrant and maintainer. I am using the field
>>> maintainer (ignoring registrant) when migrating to SM1.1 which means
>>> that I am producing accounts for the current maintainers.
>>
>> One thing I'd like to see is allowing multiple maintainers for a given
>> package. Or even better, the reverse: the authorization for each
>> account including "maintainer" capabilities for a collection of
>> packages.
>>
>> Colin
>
> Right... How about this:
>
> 1. Packages are always owned by ONE account. That person is the
> maintainer.
> 2. The maintainer can mark the package as "orphaned" meaning that it is
> free to "pick up" by another account. This would solve the issue Doug
> mentioned.
> 3. The maintainer can add other accounts as "co-maintainers". I am
> actually not sure though why this would be useful. Colin? Concrete use
> cases?
>
> regards, Göran
>
>
Roel Wuyts                                                   Software 
Composition Group
roel.wuyts at iam.unibe.ch                       University of Bern, 
Switzerland
http://www.iam.unibe.ch/~wuyts/
Board Member of the European Smalltalk User Group: www.esug.org