I would suggest that place to start for recruiting trainers+curriculum is the original AppDev Training authors: http://www.openstack.org/blog/2015/07/writing-your-first-openstack-application/ Also, I've started to have a conversation around a "Training Repository" where any AppDev trainer could contribute their "learning challenges" as we iterate and build the trainer (and train-the-trainer) communities. https://github.com/DFFlanders/AppDev-Training-Challenges-OpenStack My apologies for not being able to attend in person. I'm attending the infra-cloud midcycle currently. I'll attempt to lurk on the etherpad during this discussion which I would wholeheartedly support. Thanks for any updates on this mailing list as trainers are wrangled :) Kind Regards, Flanders On Tue, Feb 23, 2016 at 12:13 PM, Sterrett, Craig <craig.sterrett at intel.com> wrote: > Hello Everyone > > For those of you who were unable to attend the Application Ecosystem > Working Group meeting today, we are looking for possible volunteers and > interested parties. > > We have been asked by the foundation to have a session at the summit about > architecting apps for the cloud. We are trying to gather people who are > interested in brainstorming how we can pull of a training session with the > short time remaining. We will be setting up a meeting (Thursday 02/25 at > 2:00PM PST) to start the brainstorming session. We currently have an > etherpad with a few thoughts, feel free to add to the etherpad > https://etherpad.openstack.org/p/TranningSession_HowToArchitectCloudApps > Or if you would like to join us > +1 (888) 875-9370, (916) 356-2663; Bridge:5; Passcode: 4954262 > > Craig Sterrett > phone: 503.264.0706 > cell:503.720.8165 > craig.sterrett at intel.com > > > > _______________________________________________ > User-committee mailing list > User-committee at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160224/28367d55/attachment.html>