Open Stack

Hey Clint, thanks for your question. I think it's been fully answered by this time. You and other people are very welcome to collaborate :)

Joshua, as far as renaming the original document I would suggest we keep it as it is for now just to preserve the explicit history of how it's been going so far. We now have a link from launchpad name to Convection proposal so one shouldn't be confused about what is what.

Thanks!

Renat Akhmerov
Mirantis Inc.

On 15.10.2013, at 0:32, Joshua Harlow <harlowja at yahoo-inc.com> wrote:

> +2 More collaboration the better :)
> 
> From: Stan Lagun <slagun at mirantis.com>
> Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
> Date: Monday, October 14, 2013 1:20 PM
> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] [Mistral] Announcing a new task scheduling and orchestration service for OpenStack
> 
> 
> > Why exactly aren't you just calling this Convection and/or collaborating
> > with the developers who came up with it?
> 
> We do actively collaborate with TaskFlow/StateManagement team who are also the authors of Convection proposal. This is a joint project and we invite you and other developers to join and contribute.
> Convection is a Microsoft trademark. That's why Mistral
> 
> 
> On Tue, Oct 15, 2013 at 12:04 AM, Clint Byrum <clint at fewbar.com> wrote:
>> Excerpts from Renat Akhmerov's message of 2013-10-14 12:40:28 -0700:
>> > Hi OpenStackers,
>> >
>> > I am proud to announce the official launch of the Mistral project. At Mirantis we have a team to start contributing to the project right away. We invite anybody interested in task service & state management to join the initiative.
>> >
>> > Mistral is a new OpenStack service designed for task flow control, scheduling, and execution. The project will implement Convection proposal (https://wiki.openstack.org/wiki/Convection) and provide an API and domain-specific language that enables users to manage tasks and their dependencies, and to define workflows, triggers, and events. The service will provide the ability to schedule tasks, as well as to define and manage external sources of events to act as task execution triggers.
>> 
>> Why exactly aren't you just calling this Convection and/or collaborating
>> with the developers who came up with it?
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> -- 
> Sincerely yours
> Stanislav (Stan) Lagun
> Senior Developer
> Mirantis
> 35b/3, Vorontsovskaya St.
> Moscow, Russia
> Skype: stanlagun
> www.mirantis.com
> slagun at mirantis.com
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131015/dd48235a/attachment.html>