Open Stack

+1

Especially googledocs that are "final" or implemented should be moved to an OpenStack repository and pointed to in the design and/or developer documents.  It's easy to lose history, reference and/or context if the document(s) are hard or impossible to find.

--Rocky

> -----Original Message-----
> From: Collins, Sean [mailto:Sean_Collins2 at cable.comcast.com]
> Sent: Friday, March 14, 2014 1:09 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Neutron] Developer Documentation -
> Architecture design docs in Google docs
> 
> Hi,
> 
> I just read through some of the design docs that were linked to the DVR
> blueprints - and realized we probably have a ton of Neutron developer
> documentation and architecture stuff in Google docs.
> 
> Should we try and gather them all up and place links to them in
> the Developer Documentation - or perhaps even bring them into the
> developer documentation tree (if they are not currently undergoing
> discussion and development)?
> 
> --
> Sean M. Collins
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev