[Swift-devel] Swift dev.globus chair

[Michael Wilde]

was: Re: [Swift-devel] [Fwd: Re: [incubator-committers] Re: swift 
project in hibernation]

--

The Globus process defines Chair as:

"Each Globus project is required to name a project Chair via some 
process defined by the project’s Committers. A project Chair has no 
enhanced authority, but has certain responsibilities relative to the 
function of the Globus Alliance. Specifically:

     * The Chair should generate, on or before March 31st, June 30th, 
September 30th, and December 31st of each year, reports concerning the 
activities of the project during the past quarter, its current status, 
and future plans.
     * The Chair is responsible for forwarding to the Globus 
Infrastructure group requests to add or delete Committers for the project."

(from http://dev.globus.org/wiki/Guidelines)

I.e the chair needs to report on the activity status and plans quarterly.

Gigi suggested to me that Ben as Project Coordinator should serve this 
role. That would be OK with me.

This is also a good time to step back and look at our process, and see 
what of anything we want to change. But if all else is ready to roll on 
incubator environment, lets just agree on a chair while we sort it out.

For now, I suggest this: Ben, if you want to be chair, I support that. 
If you dont, I feel the same about you, Mihael. If neither of you want 
to be chair, I propose to remain chair.

All: After we hear from Ben (or Mihael if Ben declines) please indicate 
your support with a response to this thread.

- Mike



On 6/5/08 11:16 AM, Mihael Hategan wrote:
> Actually, from a dev.globus perspective, there is no "manager" in the
> sense of somebody having more decision power than other committers.
> 
> Such management decisions are made through voting.
> 
> So you should probably think a bit about this. The control structure
> imposed by our job hierarchy or by the flow of money have no say in the
> decision making process of the project. That doesn't mean that you can't
> exercise authority as long as you have the means to, but globdev isn't
> going to give you such means.
> 
> In regard to the task at hand, there are no problems really. You  will
> probably have the honors of making the official request. That wasn't my
> point though. I was simply asking whether there was a rule in place, and
> all I got was an opinion. I didn't want an opinion. It was a simple
> question and I wanted a "yes" or a "no".
> 
> On Thu, 2008-06-05 at 10:35 -0500, Michael Wilde wrote:
>> If "chair" is someone who maintains the infrastructure it should be a 
>> developer.
>>
>> If its someone that makes management decisions and speaks for the 
>> project, it should be me.
>>
>> I should be the one who requests the project to be un-hibernated, but at 
>> least designated developer should be able to interact with dev.globus 
>> regarding infrastructure setup, imho.
>>
>> Mihael, Ben - do you have a recommendation on this? Seems like once 
>> infrastructure setup is done, I should be able to be chair.
>>
>> - Mike
>>
>>
>> -------- Original Message --------
>> Subject: Re: [incubator-committers] Re: swift project in hibernation
>> Date: Thu, 05 Jun 2008 09:14:17 -0500
>> From: Mihael Hategan <hategan at mcs.anl.gov>
>> To: Jennifer M. Schopf <jms at mcs.anl.gov>
>> CC: Jennifer M. Schopf <jms at eol.org>,	incubator-committers at globus.org, 
>> wilde at mcs.anl.gov,	Ben Clifford <benc at hawaga.org.uk>
>> References: <20080604223759.9D756B00006C at sumac.eol.org>	 
>> <1212621397.17056.11.camel at localhost>	 
>> <20080605020236.B489EB00006C at sumac.eol.org>	 
>> <1212640861.22960.25.camel at localhost>	 
>> <20080605130731.515E4ABC001 at zimbra.anl.gov>
>>
>> Short ones inline.
>>
>> On Thu, 2008-06-05 at 09:05 -0400, Jennifer M. Schopf wrote:
>> ...
>>>> I will also reformulate the question:
>>>> If I (or any other committer for that matter) ask for the project to be
>>>> un-hibernated, while meeting all the requirements, will the project be
>>>> un-hibernated or not?
>>> Mike's gotten in touch with us - so if one of you 
>>> gets a document or shows effort towards this end 
>>> that should suffice, but you've got to include 
>>> him as chair in my opinion. If he's not being the 
>>> chair that's something for you as a project to 
>>> sort out - we really only interface to the chair 
>>> of a project , that's what the chair is in our 
>>> view, the person making this project happen from 
>>> an incubator point of view. If your chair isn't 
>>> doing that then likely something need to change 
>>> inthe project. It is not uncommon for a project 
>>> to have a PI that isn't the chair, for example. 
>>> But generally, yes, we work with the chair not 
>>> other group members or else this process simply 
>>> wouldn't scale. I can't give you an authoritative 
>>> answer without a meeting of the IMP which takes 
>>> place in roughly 2 weeks, all i can give you is 
>>> my best interpretation of the process as it exists.
>> Ok. Please let me know what the answer is when you can.
>>
>> ...
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>