+2 This topic had come up in Cinder I believe as well. Having a common devref for common content would be good and would make it easier to keep the documentation current.
Jay On Jan 20, 2015 4:05 PM, "Jay Pipes" <jaypi...@gmail.com> wrote: > On 01/20/2015 01:30 PM, Ian Cordasco wrote: > >> On Jan 20, 2015, at 05:23, Thierry Carrez <thie...@openstack.org> >>> wrote: >>> >>> Hi everyone, >>> >>> Given that the agenda docket is pretty slim this week, I'd like to >>> skip this cross-project meeting and have the next one on Jan 27. >>> >>> sigmavirus24 posted the "Cross-project DevRef akin to Nova's" item >>> but I'd prefer if we discussed it on the mailing-list first (not >>> certain it requires everyone's attention just yet, and could just >>> be proposed as a spec). >>> >>> Cheers, >>> >>> -- Thierry Carrez (ttx) >>> >>> ____________________________________________________________ >>> ______________ >>> >>> >>> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> Hey all, >> >> First, let me provide some context. The week before last, an update >> to sqlalchemy-migrate broke glance’s gate. While helping us fix the >> problem, Matt Riedemann noticed that the project doesn’t have a >> Developer Reference document. The document helps new developers >> determine what system packages they need to build a development >> environment for the project. >> >> We discussed the idea of putting one together for glance at the team >> meeting last week. While discussing it, we realized a lot of the >> steps are similar to Nova’s and it might benefit OpenStack as a whole >> to have one common DevRef that links off to individual ones for >> further configuration. The list of common steps could be maintained >> in one place (rather than synchronized between projects) and then >> individual extensions would be maintained with in each project or >> wiki. >> >> Before we started duplicating content in our own document, we wanted >> to present the idea to the cross-project team and the community as a >> whole. >> >> Feedback is greatly appreciated, Ian >> > > I think a common shared developer reference is a great idea, Ian. ++ > > -jay > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev