Open Stack

Agreed I like the idea.

It reminds me of the blog the solum team is setting up. I think I asked then when they announced that blog if there was plans to make it easy for other projects to also have there own supported blog.

http://lists.openstack.org/pipermail/openstack-dev/2013-October/017977.html

Maybe we should see how that could be done since the update page is pretty similar to a blog (and a blog can include other things as well, like "tips and tricks" for using rally for example).

Thoughts?

Sent from my really tiny device...

On Nov 19, 2013, at 9:36 PM, "Boris Pavlovic" <bpavlovic at mirantis.com<mailto:bpavlovic at mirantis.com>> wrote:

Hi stackers,


Currently what I see is growing amount of interesting projects, that at least I would like to track. But reading all mailing lists, and reviewing all patches in all interesting projects to get high level understanding of what is happing in project now, is quite hard or even impossible task (at least for me). Especially after 2 weeks vacation =)


The idea of this proposal is that every OpenStack project should have "story" wiki page. It means to publish every week one short message that contains most interesting updates for the last week, and high level road map for future week. So reading this for 10-15 minutes you can see what changed in project, and get better understanding of high level road map of the project.

E.g. we start doing this in Rally: https://wiki.openstack.org/wiki/Rally/Updates


I think that the best way to organize this, is to have person (or few persons) that will track all changes in project and prepare such updates each week.



Best regards,
Boris Pavlovic
--
Mirantis Inc.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto: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/20131120/bdc02a82/attachment.html>