Open Stack

Apologies for following-up my own message, but I wanted to share the
link to a TC resolution[2].  This came up in relation to a *very*
active thread[1] around retiring the Community App Catalog.  If you
have not been following that thread on the dev list, I urge you all to
read through it.  There are some really interesting views being
expressed there and it directly relates to application development and
PaaS support on OpenStack.

[1]: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113362.html
[2]: https://review.openstack.org/#/c/447031/

-Christopher


On Mon, Mar 13, 2017 at 1:28 PM, Christopher Aedo <doc at aedo.net> wrote:
> On Sun, Mar 12, 2017 at 4:08 PM, Yih Leong, Sun. <yihleong at gmail.com> wrote:
>> It is sad to hear this decision.
>>
>> Instead of wrapping up this group, would you consider merge this under
>> Enterprise WG?
>> There are work in Enterprise WG (such as ISV) that could have overlap with
>> SaaS/PaaS and App Development?
>
> At this point there's no "group" to merge.  We've satisfied the
> majority of the efforts we had started, and any new efforts around
> engaging PaaS groups would really be a chance in direction from where
> we started.  (Not to mention this working group does not have many
> "workers" left).
>
> Going forward there's nothing stopping the Enterprise WG from deciding
> you would want to take on managing relationships with PaaS vendors to
> facilitate better cooperation between those folks and the OpenStack
> community, if something like that is what makes the most sense.
>
> This would be a good time for the User Committee to get involved here
> and talk about the strategic implications around OpenStack
> applications.  My understanding (partly based on this thread on the
> dev list [1]) is that the foundation wants to foster better
> relationships with ecosystems that already have lots of developers,
> rather than appearing to compete with them by trying to build our own
> niche ecosystem.
>
> Having said all that, one of the reasons we chose to shut down our
> specific working group is due to lack of participation.  Any ongoing
> efforts are going to require wrangling some volunteers; this seems
> like a good opportunity to re-brand the efforts and hopefully capture
> the interest of some new folks.
>
> [1]: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113362.html
>
> -Christopher
>
>>
>> On Thu, Mar 9, 2017 at 7:25 PM, Christopher Aedo <doc at aedo.net> wrote:
>>>
>>> Those of us still involved with the App Dev Enabling Working Group
>>> have agreed it’s time to wrap up our efforts.  Last year we
>>> experienced great participation from several different organizations
>>> and were able to coordinate the Cloud Benchmark, First App guides,
>>> along with the Guadalajara Hackathon. In Barcelona we came up with
>>> some priority efforts[1] to pursue before the next summit in Boston
>>> and we have delivered improvements in developer.openstack.org.
>>>
>>> This year however we have been talking about taking a more pragmatic
>>> approach around finding application developers building things on top
>>> of OpenStack clouds.  The hope is that if we work more closely with
>>> the various platforms as a service that run beautifully on top of
>>> OpenStack clouds, we can reach a wider audience and focus on enabling
>>> them (and their respective PaaS’s).
>>>
>>> We feel this mission represents a significant departure from where
>>> this began (as the AppDev Ecosystem WG).  We think it makes sense to
>>> retire this working group and suggest a new one that can focus closely
>>> on cooperating with the PaaS options and their already existing
>>> ecosystem of application developers.
>>>
>>> [1]: https://etherpad.openstack.org/p/app-eco-objectives
>>>
>>>
>>> -Christopher
>>>
>>> _______________________________________________
>>> User-committee mailing list
>>> User-committee at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>>
>>