Open Stack

Hi Van,

Correct: our Guidelines and our process are ultimately subject to Board approval.  For what it’s worth, TC members I’ve spoken with are well aware of that…in fact, the text of #1 actually calls out that the resolution is partly motivated by an attempt to clearly state TC future direction, which is one of our Criteria.  As you say, we can and do listen to TC input, as the collaborative nature of our work means that the TC and the projects it governs have a stake in the game too.

At Your Service,

Mark T. Voelker



> On May 6, 2016, at 1:25 PM, Van Lindberg <van.lindberg at rackspace.com> wrote:
> 
> Regarding #1, (and I guess even #2 also), it is good to listen to the TC's opinion on these matters, but aren't we governed by the board-approved weighing/inclusion process?
> 
> Hi Folks,
> 
> For those of you who didn’t catch it elsewhere, here are a couple of DefCore-related things that the TC is currently considering that you may want to be aware of:
> 
> "add resolution explaining which tests we think defcore should use"
> https://review.openstack.org/#/c/312718/
> 
> "add resolution asking defcore committee to avoid using proxy APIs in tests"
> https://review.openstack.org/#/c/312719/
> 
> At Your Service,
> 
> Mark T. Voelker
> 
> 
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee