+1
I'd also love to see a tag or keyword associated with items that (affects
{project x,y,z}) or (possibly affects {project x,y,z} to highlight areas in
need of collaboration between teams. There is so much going on cross-project
these days, that if the project team thinks the change has side effects or
interaction changes beyond the internal project, they should raise a flag.
--Rocky
From: Boris Pavlovic [mailto:bpavlo...@mirantis.com]
Sent: Tuesday, November 19, 2013 9:33 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] Propose "project story wiki" idea
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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
