There is now a network subteam as well.
https://launchpad.net/~nova-network
http://wiki.openstack.org/Teams
-tr3buchet
On Mon, Oct 17, 2011 at 12:56 AM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> I've been assimilating the plans from the design summit into blueprints.
> In the process i'v
Vishvananda Ishaya wrote:
> I understand the concern. I really want to keep these sub teams focused
> on implementation details as opposed to large theoretical discussions.
> Separate mailing lists may not be the best solution, but lets let it go
> for a couple of months and re-evaluate. Keep in
Hi all -
Working groups are a great idea and I would love to add one for
documentation. Specifically for nova, I think it would be best if we
identify folks like you (Razique) or Kevin Bringard to head up the nova
working group since my attention needs to remain one level up. If you're
willing, I a
Vishvananda Ishaya wrote:
> I've been assimilating the plans from the design summit into blueprints.
> In the process i've noticed that we have a lot planned for the next few
> months. Some of these changes are quite large and involve people from
> many different companies that are working on ope
On Mon, Oct 17, 2011 at 3:14 PM, Trey Morris wrote:
> I notices a gap -> networking
>
Noticed that as well :)
During Essex the Quantum team will be making some non-trivial changes to the
nova network manager code to work better with Quantum (in fact, the first
review should hit tonight, I believ
I notices a gap -> networking
On Mon, Oct 17, 2011 at 12:56 AM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> I've been assimilating the plans from the design summit into blueprints.
> In the process i've noticed that we have a lot planned for the next few
> months. Some of these changes are
Hi Vish,
Sounds good, I'm all for trying out new things. I think updates on the main
openstack list would help.
On Mon, Oct 17, 2011 at 3:08 PM, Vishvananda Ishaya
wrote:
> Hi Nirmal,
>
> I understand the concern. I really want to keep these sub teams focused on
> implementation details as opp
Hi Nirmal,
I understand the concern. I really want to keep these sub teams focused on
implementation details as opposed to large theoretical discussions. Separate
mailing lists may not be the best solution, but lets let it go for a couple of
months and re-evaluate. Keep in mind that it is ju
Separating into subteams seems like a good idea and will allow more focus on
certain areas, but having separate mailing lists for each team might be a
little too overkill, could lead to fragmented development discussions. Even
to have a cursory overview of what's happening in the teams will require
Hi Vish,Jay
> Jay
Thank you for your FYI :)
I would like to lead the Nova Testing Cleanup Team.
As Jay mentioned, we are working on unit test writing and clean-ups.
At first, we draft a blueprint for QA
This is a policy of exception handling policy.
https://blueprints.launchpad.net/openstack-qa/+
On Mon, Oct 17, 2011 at 1:56 AM, Vishvananda Ishaya
wrote:
> Nova Testing Cleanup Team
> https://launchpad.net/~nova-testing
> We have discussed cleaning up the unit tests and separating out integration
> tests for a while, but this needs a specific team to focus on it. We need
> volunteers and a
Hi All,
I thnik it's a great starting point.
What about a Nova Documentation Team also ?
Since more and more content seems to come, and as Anne pointed, more new
contributors.
Best regards,
Razique
Le 17 oct. 2011 à 07:56, Vishvananda Ishaya a écrit :
> Hello Everyone,
>
> I've been assimila
Hello Everyone,
I've been assimilating the plans from the design summit into blueprints. In
the process i've noticed that we have a lot planned for the next few months.
Some of these changes are quite large and involve people from many different
companies that are working on openstack. In or
13 matches
Mail list logo
