Open Stack

On 05/13/2015 03:13 PM, Stefano Maffulli wrote:
> On 05/13/2015 11:48 AM, Mike Perez wrote:
>> The Cinder team has met today [1] to begin discussions on the deadline
>> for new volume drivers in the Liberty release.
>>
>> The proposed deadline for volume drivers to be merged by is June 19th 2015
> [...]
> 
> Great to read this, thanks Mike.
> 
> On a wider note, I think we should have a more institutional place to
> communicate this sort of important decisions than the mailing list only.
> I'm thinking of proposing a new scope for the OpenStack blog
> https://openstack.org/blog for this.
> 
> We used to use the blog as the main source of communication, from
> Foundation, events, community-related news and the weekly newsletter.
> Recently the Foundation has added two new important publication:
> http://SuperUser.openstack.org and https://openstack.org/news. These end
> up taking lots of the content that was on the blog.
> 
> I think that we might tighten the focus of the blog to contributors and
> operators (and app developers) aspects, use it as the regular platform
> for TC communication, PTLs and community managers to communicate
> relevant news.
> 
> Thoughts?
> 
> /stef
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
Part of the exercise is for folks who wish to be involved in the
community to be involved in the community. This includes staying
informed of discussions on the -dev mailing list as well as
participating in irc channel discussions of the project to which they
wish to contribute a driver and the weekly team meeting (including
reading logs of meetings they don't attend). Attending a third party
meeting is optional but encouraged especially when you happen to do
something you feel is innocuous which has the result of taking out our
gerrit (it has happened and more than once).

The commitment to communicate using accepted developer practices is
turning out to be a rather strong indicator of who is offering a driver
+ ci that actually will be maintained.

I think we need to look at the whole picture here.

Thanks,
Anita.

Also to Mike, nice clarity with expectations and timelines. Well done!