From thierry at openstack.org  Mon Mar  2 09:46:10 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Mon, 02 Mar 2015 10:46:10 +0100
Subject: [openstack-tc] TC Meeting tomorrow Tue March 3rd, 20:00 UTC
Message-ID: <54F43162.30301@openstack.org>

Dear TC members,

We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:

* openstack-specs final rubberstamping
  * Add TRACE definition to log guidelines [1]
* Definition of the release:* tags [2]
* Other governance changes
  * Add ironic-lib to Ironic program [3]
  * Add dib-utils as part of TripleO [4]
  * Add mission statement for project 'Heat' [5]
  * Adding Piet Kruithof as Horizon ATC [6]
* Housekeeping
  * Build list of teams from YAML file [7]
  * Update the Infrastructure project homepage URL [8]
* Open discussion
  * Ops Summit in PHL next week

[1] https://review.openstack.org/#/c/145245
[2] https://review.openstack.org/157322
[3] https://review.openstack.org/157757
[4] https://review.openstack.org/158365
[5] https://review.openstack.org/154049
[6] https://review.openstack.org/154271
[7] https://review.openstack.org/125788
[8] https://review.openstack.org/158371

If all goes well, this agenda should leave a bit of time for open
discussion around the next tags and project teams that should be
introduced in the Kilo timeframe.

See you tomorrow,

-- 
Thierry Carrez (ttx)


From mordred at inaugust.com  Mon Mar  2 12:31:36 2015
From: mordred at inaugust.com (Monty Taylor)
Date: Mon, 02 Mar 2015 07:31:36 -0500
Subject: [openstack-tc] TC Meeting tomorrow Tue March 3rd, 20:00 UTC
In-Reply-To: <54F43162.30301@openstack.org>
References: <54F43162.30301@openstack.org>
Message-ID: <54F45828.5080905@inaugust.com>

On 03/02/2015 04:46 AM, Thierry Carrez wrote:
> Dear TC members,
> 
> We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:

FWIW, there is a board meeting tomorrow that overlaps - so some of us
may be absent/distracted. Don't miss on our behalf - just a heads up.

> * openstack-specs final rubberstamping
>   * Add TRACE definition to log guidelines [1]
> * Definition of the release:* tags [2]
> * Other governance changes
>   * Add ironic-lib to Ironic program [3]
>   * Add dib-utils as part of TripleO [4]
>   * Add mission statement for project 'Heat' [5]
>   * Adding Piet Kruithof as Horizon ATC [6]
> * Housekeeping
>   * Build list of teams from YAML file [7]
>   * Update the Infrastructure project homepage URL [8]
> * Open discussion
>   * Ops Summit in PHL next week
> 
> [1] https://review.openstack.org/#/c/145245
> [2] https://review.openstack.org/157322
> [3] https://review.openstack.org/157757
> [4] https://review.openstack.org/158365
> [5] https://review.openstack.org/154049
> [6] https://review.openstack.org/154271
> [7] https://review.openstack.org/125788
> [8] https://review.openstack.org/158371
> 
> If all goes well, this agenda should leave a bit of time for open
> discussion around the next tags and project teams that should be
> introduced in the Kilo timeframe.
> 
> See you tomorrow,
> 



From mikal at stillhq.com  Tue Mar  3 08:18:32 2015
From: mikal at stillhq.com (Michael Still)
Date: Tue, 3 Mar 2015 19:18:32 +1100
Subject: [openstack-tc] TC Meeting tomorrow Tue March 3rd, 20:00 UTC
In-Reply-To: <54F43162.30301@openstack.org>
References: <54F43162.30301@openstack.org>
Message-ID: <CAEd1pt4sBSuYGK+o1OCz6Kp=_7AP=bgB6ysHjwtkUtx535176g@mail.gmail.com>

I write to apologise for the following foolish circumstances:

 - 12 years ago I had a child
 - we decided to school said child, instead of sending him to the salt mines
 - the school we picked (unbeknownst to me) is staffed by raving
communists who believe in "school camps"

Unfortunately, the communist school failed to consult with me about my
meeting schedule before setting the departure time for this
disturbingly uneducational junket to clash with tomorrows TC meeting.
I will thus be unable to attend said meeting, and render my apologies.

Michael

On Mon, Mar 2, 2015 at 8:46 PM, Thierry Carrez <thierry at openstack.org> wrote:
> Dear TC members,
>
> We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:
>
> * openstack-specs final rubberstamping
>   * Add TRACE definition to log guidelines [1]
> * Definition of the release:* tags [2]
> * Other governance changes
>   * Add ironic-lib to Ironic program [3]
>   * Add dib-utils as part of TripleO [4]
>   * Add mission statement for project 'Heat' [5]
>   * Adding Piet Kruithof as Horizon ATC [6]
> * Housekeeping
>   * Build list of teams from YAML file [7]
>   * Update the Infrastructure project homepage URL [8]
> * Open discussion
>   * Ops Summit in PHL next week
>
> [1] https://review.openstack.org/#/c/145245
> [2] https://review.openstack.org/157322
> [3] https://review.openstack.org/157757
> [4] https://review.openstack.org/158365
> [5] https://review.openstack.org/154049
> [6] https://review.openstack.org/154271
> [7] https://review.openstack.org/125788
> [8] https://review.openstack.org/158371
>
> If all goes well, this agenda should leave a bit of time for open
> discussion around the next tags and project teams that should be
> introduced in the Kilo timeframe.
>
> See you tomorrow,
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc



-- 
Rackspace Australia


From adrian.otto at rackspace.com  Wed Mar  4 16:54:25 2015
From: adrian.otto at rackspace.com (Adrian Otto)
Date: Wed, 4 Mar 2015 16:54:25 +0000
Subject: [openstack-tc] Magnum - OpenStack Containers Service
Message-ID: <25FC273D-1DDB-4C11-B8F3-A35F59181B02@rackspace.com>

Dear TC Members,

I have started a thread [1] on openstack-dev to highlight the ?Magnum - OpenStack Containers Service? item on the upcoming TC meeting agenda for 2015-03-10 so that any questions or concerns can be addressed prior to the meeting. Please let me know if there is anything more I can do to help.

Thanks,

Adrian Otto

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-March/058288.html

From thierry at openstack.org  Thu Mar  5 15:57:10 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Thu, 05 Mar 2015 16:57:10 +0100
Subject: [openstack-tc] Meeting next week
Message-ID: <54F87CD6.2030204@openstack.org>

Hi TC members,

Here is the docket of changes proposed with enough advance time to be
included in the next TC meeting agenda:

* Add IRC channel policies [1]
* Magnum - OpenStack Containers Service [2]
* Definition of the release:* tags [3]
* Other governance changes
  * Add the new developer-reference repo to the TC list [4]
  * Remove py26 from PTI [5]
  * Remove reference to Jenkins in PTI [6]
* Housekeeping
  * Add .pyc files to gitignore [7]
  * Update the Infrastructure project homepage URL [8]
  * Publish the extra ATCs for projects [9]
* Open discussion

[1] https://review.openstack.org/159930
[2] https://review.openstack.org/161080
[3] https://review.openstack.org/157322
[4] https://review.openstack.org/161009
[5] https://review.openstack.org/159936
[6] https://review.openstack.org/159935
[7] https://review.openstack.org/161023
[8] https://review.openstack.org/158371
[9] https://review.openstack.org/161465

So there is definitely enough matter to hold a meeting if quorum is
present (7 members).

Personally I can't commit to be there, it depends on how the Ops Summit
will go (as I'd like to give it priority). Jim offered to chair if the
meeting is not skipped. It will probably make little sense to discuss
the next round of release:* tags without me around to defend it, and I
would obviously prefer to be around when we discuss our first addition
of the project structure reform era (Magnum)... but I also appreciate
that we have no time to lose, so if there is a quorum and a chair to
drive it, the meeting should certainly happen.

Thoughts, comments ?

-- 
Thierry Carrez (ttx)


From doug at doughellmann.com  Thu Mar  5 16:50:17 2015
From: doug at doughellmann.com (Doug Hellmann)
Date: Thu, 5 Mar 2015 11:50:17 -0500
Subject: [openstack-tc] Meeting next week
In-Reply-To: <54F87CD6.2030204@openstack.org>
References: <54F87CD6.2030204@openstack.org>
Message-ID: <65F97589-F25C-4A07-B9DB-A2C42656D663@doughellmann.com>


> On Mar 5, 2015, at 10:57 AM, Thierry Carrez <thierry at openstack.org> wrote:
> 
> Hi TC members,
> 
> Here is the docket of changes proposed with enough advance time to be
> included in the next TC meeting agenda:
> 
> * Add IRC channel policies [1]
> * Magnum - OpenStack Containers Service [2]
> * Definition of the release:* tags [3]
> * Other governance changes
>  * Add the new developer-reference repo to the TC list [4]
>  * Remove py26 from PTI [5]
>  * Remove reference to Jenkins in PTI [6]
> * Housekeeping
>  * Add .pyc files to gitignore [7]
>  * Update the Infrastructure project homepage URL [8]
>  * Publish the extra ATCs for projects [9]
> * Open discussion
> 
> [1] https://review.openstack.org/159930
> [2] https://review.openstack.org/161080
> [3] https://review.openstack.org/157322
> [4] https://review.openstack.org/161009
> [5] https://review.openstack.org/159936
> [6] https://review.openstack.org/159935
> [7] https://review.openstack.org/161023
> [8] https://review.openstack.org/158371
> [9] https://review.openstack.org/161465
> 
> So there is definitely enough matter to hold a meeting if quorum is
> present (7 members).
> 
> Personally I can't commit to be there, it depends on how the Ops Summit
> will go (as I'd like to give it priority). Jim offered to chair if the
> meeting is not skipped. It will probably make little sense to discuss
> the next round of release:* tags without me around to defend it, and I
> would obviously prefer to be around when we discuss our first addition
> of the project structure reform era (Magnum)... but I also appreciate
> that we have no time to lose, so if there is a quorum and a chair to
> drive it, the meeting should certainly happen.
> 
> Thoughts, comments ?

I don?t think there?s any particular rush on the release tags, so we could talk about those but defer questions to the review so you could answer them.

We?ve warned projects that we?re going to take it slow bringing on more official projects, so we could start the Magnum discussion without committing to making a decision this week as well.

The IRC issue seems like something we might be able to resolve this week, unless it proves more controversial than I expect.

All of those items are up for review, so anyone with objections can log them in gerrit before the meeting. We can defer final votes if there is strong opposition to anything, since we know we will have a number of members absent.

Anyway, if we have quorum, it seems like we should go ahead and meet and discuss the items in the order you have them listed in the proposed agenda.

Doug

> 
> -- 
> Thierry Carrez (ttx)
> 
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc



From jaypipes at gmail.com  Thu Mar  5 19:03:06 2015
From: jaypipes at gmail.com (Jay Pipes)
Date: Thu, 05 Mar 2015 11:03:06 -0800
Subject: [openstack-tc] Meeting next week
In-Reply-To: <65F97589-F25C-4A07-B9DB-A2C42656D663@doughellmann.com>
References: <54F87CD6.2030204@openstack.org>
 <65F97589-F25C-4A07-B9DB-A2C42656D663@doughellmann.com>
Message-ID: <54F8A86A.3050108@gmail.com>

Agree with everything Doug says below. Let's hold the meeting and get 
stuff done where we can.

Best,
-jay

On 03/05/2015 08:50 AM, Doug Hellmann wrote:
>
>> On Mar 5, 2015, at 10:57 AM, Thierry Carrez <thierry at openstack.org> wrote:
>>
>> Hi TC members,
>>
>> Here is the docket of changes proposed with enough advance time to be
>> included in the next TC meeting agenda:
>>
>> * Add IRC channel policies [1]
>> * Magnum - OpenStack Containers Service [2]
>> * Definition of the release:* tags [3]
>> * Other governance changes
>>   * Add the new developer-reference repo to the TC list [4]
>>   * Remove py26 from PTI [5]
>>   * Remove reference to Jenkins in PTI [6]
>> * Housekeeping
>>   * Add .pyc files to gitignore [7]
>>   * Update the Infrastructure project homepage URL [8]
>>   * Publish the extra ATCs for projects [9]
>> * Open discussion
>>
>> [1] https://review.openstack.org/159930
>> [2] https://review.openstack.org/161080
>> [3] https://review.openstack.org/157322
>> [4] https://review.openstack.org/161009
>> [5] https://review.openstack.org/159936
>> [6] https://review.openstack.org/159935
>> [7] https://review.openstack.org/161023
>> [8] https://review.openstack.org/158371
>> [9] https://review.openstack.org/161465
>>
>> So there is definitely enough matter to hold a meeting if quorum is
>> present (7 members).
>>
>> Personally I can't commit to be there, it depends on how the Ops Summit
>> will go (as I'd like to give it priority). Jim offered to chair if the
>> meeting is not skipped. It will probably make little sense to discuss
>> the next round of release:* tags without me around to defend it, and I
>> would obviously prefer to be around when we discuss our first addition
>> of the project structure reform era (Magnum)... but I also appreciate
>> that we have no time to lose, so if there is a quorum and a chair to
>> drive it, the meeting should certainly happen.
>>
>> Thoughts, comments ?
>
> I don?t think there?s any particular rush on the release tags, so we could talk about those but defer questions to the review so you could answer them.
>
> We?ve warned projects that we?re going to take it slow bringing on more official projects, so we could start the Magnum discussion without committing to making a decision this week as well.
>
> The IRC issue seems like something we might be able to resolve this week, unless it proves more controversial than I expect.
>
> All of those items are up for review, so anyone with objections can log them in gerrit before the meeting. We can defer final votes if there is strong opposition to anything, since we know we will have a number of members absent.
>
> Anyway, if we have quorum, it seems like we should go ahead and meet and discuss the items in the order you have them listed in the proposed agenda.
>
> Doug
>
>>
>> --
>> Thierry Carrez (ttx)
>>
>> _______________________________________________
>> OpenStack-TC mailing list
>> OpenStack-TC at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>


From mikal at stillhq.com  Thu Mar  5 23:27:36 2015
From: mikal at stillhq.com (Michael Still)
Date: Fri, 6 Mar 2015 10:27:36 +1100
Subject: [openstack-tc] Meeting next week
In-Reply-To: <54F87CD6.2030204@openstack.org>
References: <54F87CD6.2030204@openstack.org>
Message-ID: <CAEd1pt6s5KUakKsMB4S4WmvcNaFc_Mfu9tyNM507CxXFcqGK7w@mail.gmail.com>

I also can't make next week as I am at a conference as well. Feel free
to hold one without me though.

Michael

On Fri, Mar 6, 2015 at 2:57 AM, Thierry Carrez <thierry at openstack.org> wrote:
> Hi TC members,
>
> Here is the docket of changes proposed with enough advance time to be
> included in the next TC meeting agenda:
>
> * Add IRC channel policies [1]
> * Magnum - OpenStack Containers Service [2]
> * Definition of the release:* tags [3]
> * Other governance changes
>   * Add the new developer-reference repo to the TC list [4]
>   * Remove py26 from PTI [5]
>   * Remove reference to Jenkins in PTI [6]
> * Housekeeping
>   * Add .pyc files to gitignore [7]
>   * Update the Infrastructure project homepage URL [8]
>   * Publish the extra ATCs for projects [9]
> * Open discussion
>
> [1] https://review.openstack.org/159930
> [2] https://review.openstack.org/161080
> [3] https://review.openstack.org/157322
> [4] https://review.openstack.org/161009
> [5] https://review.openstack.org/159936
> [6] https://review.openstack.org/159935
> [7] https://review.openstack.org/161023
> [8] https://review.openstack.org/158371
> [9] https://review.openstack.org/161465
>
> So there is definitely enough matter to hold a meeting if quorum is
> present (7 members).
>
> Personally I can't commit to be there, it depends on how the Ops Summit
> will go (as I'd like to give it priority). Jim offered to chair if the
> meeting is not skipped. It will probably make little sense to discuss
> the next round of release:* tags without me around to defend it, and I
> would obviously prefer to be around when we discuss our first addition
> of the project structure reform era (Magnum)... but I also appreciate
> that we have no time to lose, so if there is a quorum and a chair to
> drive it, the meeting should certainly happen.
>
> Thoughts, comments ?
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc



-- 
Rackspace Australia


From annegentle at justwriteclick.com  Thu Mar  5 23:56:50 2015
From: annegentle at justwriteclick.com (Anne Gentle)
Date: Thu, 5 Mar 2015 17:56:50 -0600
Subject: [openstack-tc] Meeting next week
In-Reply-To: <54F87CD6.2030204@openstack.org>
References: <54F87CD6.2030204@openstack.org>
Message-ID: <CAD0KtVG8=0+r8wWNT4vg3W8satQpB4tyXEgRf8fZ=M1fnEOR0A@mail.gmail.com>

On Thu, Mar 5, 2015 at 9:57 AM, Thierry Carrez <thierry at openstack.org>
wrote:

> Hi TC members,
>
> Here is the docket of changes proposed with enough advance time to be
> included in the next TC meeting agenda:
>
> * Add IRC channel policies [1]
> * Magnum - OpenStack Containers Service [2]
> * Definition of the release:* tags [3]
> * Other governance changes
>   * Add the new developer-reference repo to the TC list [4]
>   * Remove py26 from PTI [5]
>   * Remove reference to Jenkins in PTI [6]
> * Housekeeping
>   * Add .pyc files to gitignore [7]
>   * Update the Infrastructure project homepage URL [8]
>   * Publish the extra ATCs for projects [9]
> * Open discussion
>
> [1] https://review.openstack.org/159930
> [2] https://review.openstack.org/161080
> [3] https://review.openstack.org/157322
> [4] https://review.openstack.org/161009
> [5] https://review.openstack.org/159936
> [6] https://review.openstack.org/159935
> [7] https://review.openstack.org/161023
> [8] https://review.openstack.org/158371
> [9] https://review.openstack.org/161465
>
> So there is definitely enough matter to hold a meeting if quorum is
> present (7 members).
>
> Personally I can't commit to be there, it depends on how the Ops Summit
> will go (as I'd like to give it priority). Jim offered to chair if the
> meeting is not skipped. It will probably make little sense to discuss
> the next round of release:* tags without me around to defend it, and I
> would obviously prefer to be around when we discuss our first addition
> of the project structure reform era (Magnum)... but I also appreciate
> that we have no time to lose, so if there is a quorum and a chair to
> drive it, the meeting should certainly happen.
>
>
Thanks for the advanced review time with a large docket.

I'd be fine with meeting to get through admin items if we have quorum and
waiting to discuss application and tags when we have more members available.

Anne


> Thoughts, comments ?
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
>



-- 
Anne Gentle
annegentle at justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20150305/8e8807cc/attachment.html>

From rbryant at redhat.com  Tue Mar 10 16:30:34 2015
From: rbryant at redhat.com (Russell Bryant)
Date: Tue, 10 Mar 2015 12:30:34 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
Message-ID: <54FF1C2A.304@redhat.com>

I just started a thread proposing we hold off on new project proposals
for now.  Here's the thread start:

http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html

-- 
Russell Bryant


From thierry at openstack.org  Tue Mar 10 18:10:51 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Tue, 10 Mar 2015 14:10:51 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
In-Reply-To: <54FF1C2A.304@redhat.com>
References: <54FF1C2A.304@redhat.com>
Message-ID: <54FF33AB.4030000@openstack.org>

Russell Bryant wrote:
> I just started a thread proposing we hold off on new project proposals
> for now.  Here's the thread start:
> 
> http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html

FWIW I fear this thread will turn into a pile-up of (1) incumbent
project people afraid of change that may dilute/downgrade them, (2)
people historically opposed to the big-tent concept and (3) people
personally opposed to specific project additions, all +1ing the idea of
a freeze as a practical way to prevent stuff from happening.

Basically those people oppose the big-tent concept, not the timing of
the tags addition ?

-- 
Thierry Carrez (ttx)


From jaypipes at gmail.com  Tue Mar 10 18:15:39 2015
From: jaypipes at gmail.com (Jay Pipes)
Date: Tue, 10 Mar 2015 14:15:39 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
In-Reply-To: <54FF33AB.4030000@openstack.org>
References: <54FF1C2A.304@redhat.com> <54FF33AB.4030000@openstack.org>
Message-ID: <54FF34CB.8070803@gmail.com>

On 03/10/2015 02:10 PM, Thierry Carrez wrote:
> Russell Bryant wrote:
>> I just started a thread proposing we hold off on new project proposals
>> for now.  Here's the thread start:
>>
>> http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html
>
> FWIW I fear this thread will turn into a pile-up of (1) incumbent
> project people afraid of change that may dilute/downgrade them, (2)
> people historically opposed to the big-tent concept and (3) people
> personally opposed to specific project additions, all +1ing the idea of
> a freeze as a practical way to prevent stuff from happening.

Yep, that's exactly what it will be.

> Basically those people oppose the big-tent concept, not the timing of
> the tags addition ?

Again, agreed.

-jay


From rbryant at redhat.com  Tue Mar 10 18:19:30 2015
From: rbryant at redhat.com (Russell Bryant)
Date: Tue, 10 Mar 2015 14:19:30 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
In-Reply-To: <54FF34CB.8070803@gmail.com>
References: <54FF1C2A.304@redhat.com> <54FF33AB.4030000@openstack.org>
 <54FF34CB.8070803@gmail.com>
Message-ID: <54FF35B2.6070200@redhat.com>

On 03/10/2015 02:15 PM, Jay Pipes wrote:
> On 03/10/2015 02:10 PM, Thierry Carrez wrote:
>> Russell Bryant wrote:
>>> I just started a thread proposing we hold off on new project proposals
>>> for now.  Here's the thread start:
>>>
>>> http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html
>>>
>>
>> FWIW I fear this thread will turn into a pile-up of (1) incumbent
>> project people afraid of change that may dilute/downgrade them, (2)
>> people historically opposed to the big-tent concept and (3) people
>> personally opposed to specific project additions, all +1ing the idea of
>> a freeze as a practical way to prevent stuff from happening.
> 
> Yep, that's exactly what it will be.
> 
>> Basically those people oppose the big-tent concept, not the timing of
>> the tags addition ?
> 
> Again, agreed.

Part of selling the big-tent concept was that we'd have an even *better*
way of communicating all of the important information consumers need
about projects.  We haven't done that yet.  We've gotten rid of what we
did have but haven't finished building that new system.  I'm opposed to
approving projects until we finish putting that system in place.

Please don't just dismiss the discussion out-right ...

-- 
Russell Bryant


From thierry at openstack.org  Tue Mar 10 18:28:03 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Tue, 10 Mar 2015 14:28:03 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
In-Reply-To: <54FF35B2.6070200@redhat.com>
References: <54FF1C2A.304@redhat.com> <54FF33AB.4030000@openstack.org>
 <54FF34CB.8070803@gmail.com> <54FF35B2.6070200@redhat.com>
Message-ID: <54FF37B3.4010705@openstack.org>

Russell Bryant wrote:
> Part of selling the big-tent concept was that we'd have an even *better*
> way of communicating all of the important information consumers need
> about projects.  We haven't done that yet.  We've gotten rid of what we
> did have but haven't finished building that new system.  I'm opposed to
> approving projects until we finish putting that system in place.

The "system" will never be "finished", though. Tags will always be added
and refined. So when will it be finished enough ? I actually asked that
question on the other thread, we should argue there instead of here.

> Please don't just dismiss the discussion out-right ...

I'm not dismissing it, just worried it will end up as yet another
gigantic thread which only represents a vocal minority...

But let's see where it goes.

-- 
Thierry Carrez (ttx)


From rbryant at redhat.com  Tue Mar 10 19:05:07 2015
From: rbryant at redhat.com (Russell Bryant)
Date: Tue, 10 Mar 2015 15:05:07 -0400
Subject: [openstack-tc] Thread on deferring new project proposals
In-Reply-To: <54FF37B3.4010705@openstack.org>
References: <54FF1C2A.304@redhat.com> <54FF33AB.4030000@openstack.org>
 <54FF34CB.8070803@gmail.com> <54FF35B2.6070200@redhat.com>
 <54FF37B3.4010705@openstack.org>
Message-ID: <54FF4063.2070009@redhat.com>

On 03/10/2015 02:28 PM, Thierry Carrez wrote:
> Russell Bryant wrote:
>> Part of selling the big-tent concept was that we'd have an even *better*
>> way of communicating all of the important information consumers need
>> about projects.  We haven't done that yet.  We've gotten rid of what we
>> did have but haven't finished building that new system.  I'm opposed to
>> approving projects until we finish putting that system in place.
> 
> The "system" will never be "finished", though. Tags will always be added
> and refined. So when will it be finished enough ? I actually asked that
> question on the other thread, we should argue there instead of here.

Yep, it's hard to define "finished".  I tried to make a case for it
being at least more than 0 tags.  If there's no support for that, so be it.

>> Please don't just dismiss the discussion out-right ...
> 
> I'm not dismissing it, just worried it will end up as yet another
> gigantic thread which only represents a vocal minority...
> 
> But let's see where it goes.
> 


-- 
Russell Bryant


From thierry at openstack.org  Mon Mar 16 09:43:50 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Mon, 16 Mar 2015 10:43:50 +0100
Subject: [openstack-tc] TC Meeting tomorrow Tue March 17th, 20:00 UTC
Message-ID: <5506A5D6.1030608@openstack.org>

Dear TC members,

We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:

* Final rubberstamping of spec to eliminate SQL Schema Downgrades [1]
* Tags
  * Definition of the release:* tags [2]
  * Next WIP tags [3] [4] [5]
  * Moving tags to a separate project-catalog repository (to make it
clear it's more documentation than governance)
* New project teams additions
  * Freezing or slowly considering [6]
  * Add OpenStackClient project [7]
* Other governance changes
  * Add the new developer-reference repo to the TC list [8]
  * Add reference to running an election to new projects requirements [9]
  * Add proposal to rename core teams as maintainer teams [10]
* Housekeeping
  * Publish the extra ATCs for projects [11]
  * Add the bindep repo to Infrastructure Project [12]
  * Add devstack-plugin-cookiecutter to QA [13]
  * Add Gnocchi repository to Ceilometer [14]
  * Add new project puppet-openstackci to infra [15]
* Open discussion

[1] https://review.openstack.org/#/c/152337/
[2] https://review.openstack.org/157322
[3] http://ttx.re/facets-of-the-integrated-release.html
[4] https://review.openstack.org/163851
[5] https://review.openstack.org/163236
[6]
http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html
[7] https://review.openstack.org/161885
[8] https://review.openstack.org/161451
[9] https://review.openstack.org/162789
[10] https://review.openstack.org/163660
[11] https://review.openstack.org/161465
[12] https://review.openstack.org/161771
[13] https://review.openstack.org/161886
[14] https://review.openstack.org/162145
[15] https://review.openstack.org/163246

See you tomorrow,

-- 
Thierry Carrez (ttx)


From thierry at openstack.org  Mon Mar 23 09:35:32 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Mon, 23 Mar 2015 10:35:32 +0100
Subject: [openstack-tc] TC Meeting tomorrow Tue March 24th, 20:00 UTC
Message-ID: <550FDE64.4030909@openstack.org>

Dear TC members,

We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:

* openstack-specs final rubberstamping
  * Add library stable release procedures/policy [1] ?
* New project teams additions
  * Magnum - OpenStack Containers Service [2]
* Tags
  * Add a tag for affiliation diversity [3]
* Other governance changes
  * Add proposal to rename core teams as maintainer teams [4]
* Housekeeping
  * Adds puppet-bandersnatch to Infrastructure [5]
  * Add oslo.cache to reference/projects.yaml [6]
  * Add coreos-image-builder to Ironic [7]
  * Add puppet-puppet project [8]
* Open discussion

[1] https://review.openstack.org/#/c/155072/
[2] https://review.openstack.org/161080
[3] https://review.openstack.org/163851
[4] https://review.openstack.org/163660
[5] https://review.openstack.org/163734
[6] https://review.openstack.org/164342
[7] https://review.openstack.org/164370
[8] https://review.openstack.org/165438

See you tomorrow,

-- 
Thierry Carrez (ttx)


From jaypipes at gmail.com  Mon Mar 23 11:58:05 2015
From: jaypipes at gmail.com (Jay Pipes)
Date: Mon, 23 Mar 2015 07:58:05 -0400
Subject: [openstack-tc] TC Meeting tomorrow Tue March 24th, 20:00 UTC
In-Reply-To: <550FDE64.4030909@openstack.org>
References: <550FDE64.4030909@openstack.org>
Message-ID: <550FFFCD.3080705@gmail.com>

Can we get Murano's application on the agenda as well?

https://review.openstack.org/#/c/162745/

-jay

On 03/23/2015 05:35 AM, Thierry Carrez wrote:
> Dear TC members,
>
> We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:
>
> * openstack-specs final rubberstamping
>    * Add library stable release procedures/policy [1] ?
> * New project teams additions
>    * Magnum - OpenStack Containers Service [2]
> * Tags
>    * Add a tag for affiliation diversity [3]
> * Other governance changes
>    * Add proposal to rename core teams as maintainer teams [4]
> * Housekeeping
>    * Adds puppet-bandersnatch to Infrastructure [5]
>    * Add oslo.cache to reference/projects.yaml [6]
>    * Add coreos-image-builder to Ironic [7]
>    * Add puppet-puppet project [8]
> * Open discussion
>
> [1] https://review.openstack.org/#/c/155072/
> [2] https://review.openstack.org/161080
> [3] https://review.openstack.org/163851
> [4] https://review.openstack.org/163660
> [5] https://review.openstack.org/163734
> [6] https://review.openstack.org/164342
> [7] https://review.openstack.org/164370
> [8] https://review.openstack.org/165438
>
> See you tomorrow,
>


From thierry at openstack.org  Mon Mar 23 14:41:56 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Mon, 23 Mar 2015 15:41:56 +0100
Subject: [openstack-tc] TC Meeting tomorrow Tue March 24th, 20:00 UTC
In-Reply-To: <550FFFCD.3080705@gmail.com>
References: <550FDE64.4030909@openstack.org> <550FFFCD.3080705@gmail.com>
Message-ID: <55102634.1010202@openstack.org>

Jay Pipes wrote:
> Can we get Murano's application on the agenda as well?
> 
> https://review.openstack.org/#/c/162745/

Added at the end of the main agenda (before housekeeping / open
discussion items, will be covered if we have enough time left).

Cheers,

-- 
Thierry Carrez (ttx)


From thierry at openstack.org  Mon Mar 30 09:52:24 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Mon, 30 Mar 2015 11:52:24 +0200
Subject: [openstack-tc] TC Meeting tomorrow Tue March 31st, 20:00 UTC
Message-ID: <55191CD8.1010203@openstack.org>

Dear TC members,

We'll have a TC meeting tomorrow at 20:00 UTC, with the following agenda:

* Add the Congress project [1]
* Apply release:* tags to current projects [2]
  * Should we tag git repositories or "deliverables" (collections of
OpenStack software code repositories released together) ?
* Add Group Based Policy Project [3]
* Projects list housekeeping
  * Adds the openstack/os-cloud-management to TripleO... [4]
  * Add os-testr repo to QA [5]
  * Add ansible-puppet repo to infra [6]
  * Add ansible-build-image to infra [7]
  * Add bashate to the QA program [8]
  * Add puppet-diskimage-builder to Infra [9]
  * Move os-client-config to openstack namepsace [10]
* Open discussion
  * Neutron renaming "core reviewers" to "maintainers" [11]

[1] https://review.openstack.org/165204
[2] https://review.openstack.org/167682
[3] https://review.openstack.org/161902
[4] https://review.openstack.org/166723
[5] https://review.openstack.org/167244
[6] https://review.openstack.org/166820
[7] https://review.openstack.org/166821
[8] https://review.openstack.org/168012
[9] https://review.openstack.org/167612
[10] https://review.openstack.org/167730
[11] https://review.openstack.org/164208

See you tomorrow,

-- 
Thierry Carrez (ttx)


From thierry at openstack.org  Tue Mar 31 07:01:00 2015
From: thierry at openstack.org (Thierry Carrez)
Date: Tue, 31 Mar 2015 09:01:00 +0200
Subject: [openstack-tc] TC Meeting tomorrow Tue March 31st, 20:00 UTC
In-Reply-To: <55191CD8.1010203@openstack.org>
References: <55191CD8.1010203@openstack.org>
Message-ID: <551A462C.1010600@openstack.org>

FYI

The Group-Based Policy folks have put their proposal back to WIP, which
defers our voting on this. I guess we can still discuss it in Open
discussion if there is any time left.

I adjusted the agenda to match.

-- 
Thierry Carrez (ttx)