cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [Linux-ha-dev] new resource agents repository commit policy
Date: Tue, 29 Mar 2011 16:59:24 +0200	[thread overview]
Message-ID: <4D91F3CC.2070705@redhat.com> (raw)
In-Reply-To: <20110329131504.GA3825@squib>

On 03/29/2011 03:15 PM, Dejan Muhamedagic wrote:
> On Mon, Mar 28, 2011 at 05:41:48PM +0200, Fabio M. Di Nitto wrote:
>> On 3/28/2011 5:28 PM, Dejan Muhamedagic wrote:
>>> On Fri, Mar 18, 2011 at 10:20:48AM +0100, Lars Marowsky-Bree wrote:
>>>> On 2011-03-14T19:49:29, Andrew Beekhof <andrew@beekhof.net> wrote:
>>>>
>>>>> I suspect you want b) with maybe 6 people for redundancy.
>>>>> The pull request workflow should be well suited to a project like this
>>>>> and impose minimal overhead.
>>>>
>>>> I prefer b as well, since it adds another review step. (Should we use
>>>> the github.com code review tools?)
>>>
>>> OK. It seems like nobody's that much interesting in this, so we
>>> can just as well go with option b).
>>
>> WFM of course.
> 
> Woman FIDE Master? :)
> 
>>> Fabio, I'd like to get the commit access rights. Florian Haas and
>>> Lars Ellenberg have also been frequently reviewing user
>>> contributions, so they should get commit rights too. I understand
>>> that Florian already has that. Lars is about to create a
>>> github.com account and he'll send you later his account name.
>>
>> You will need to talk to Andrew for this. I am not the owner of the repo.
> 
> I guess that Andrew's listening.

Yes it appears that I have admin rights on the repo, so just fire up the
requests with your github account and i'll try to add people.

> 
>> For now I did merge bits from Florian and I can do it while Andrew will
>> allow accounts to commit.
>>
>>>
>>>> Oh, and we can use the ha-wg-technical mailing list for cross-project
>>>> coordination ;-)
>>>
>>> Yes, but the list is very new and some people who may be affected
>>> are perhaps not all subscribed.
>>
>> Let?s make sure that the message is sent again to the mailing lists, we
>> can clearly still collect patches on the old lists for two/three months
>> while we transition.
> 
> I actually expected the ha-wg-technical list to be low volume
> and for "project coordination" and similar, not for daily
> business.

As long as we don't start merging the agents into clusterlabs/, I would
assume that patches we get on each mailing lists are targeted to the
specific set.

In the long run, we will have time to decide for a patch-list or
something. I don't think we need to be super strict from day 0 and let's
thing settle down on their own during a transition phase.

fabio



  reply	other threads:[~2011-03-29 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 17:07 [Cluster-devel] new resource agents repository commit policy Dejan Muhamedagic
2011-03-14 18:49 ` [Cluster-devel] [Linux-ha-dev] " Andrew Beekhof
     [not found]   ` <20110318092048.GE23764@suse.de>
2011-03-28 15:28     ` Dejan Muhamedagic
2011-03-28 15:41       ` Fabio M. Di Nitto
2011-03-29 13:15         ` Dejan Muhamedagic
2011-03-29 14:59           ` Fabio M. Di Nitto [this message]
2011-03-31  7:48           ` Fabio M. Di Nitto
2011-03-31 12:56             ` Dejan Muhamedagic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D91F3CC.2070705@redhat.com \
    --to=fdinitto@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).