I think Ascii diagrams do make sense if the Blueprint is a major architecture input and will be long lived through many Os cycles, if it's a small short feature and the diagram is useful to describe the architecture then I think its overly painful, speaking from experience!
Alan -----Original Message----- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: April-16-14 1:19 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec On 04/16/2014 12:55 PM, Russell Bryant wrote: > On 04/16/2014 12:42 PM, Kevin Benton wrote: >> The only downside to putting it on the wiki is that it no longer has >> a shared fate with the specification in the repo. If someone deletes >> it or replaces it on the wiki, information for the spec is lost. >> External connectivity is also required just to view a template as well. > > Yeah, that's right. I'd honestly really prefer simple ascii diagrams > in almost all cases anyway. Requiring an external diagram should be a > rare exception, not the rule, IMO. > After some additional discussion on this topic on IRC, I really think we should start by requiring diagrams in ASCII and see if that becomes overly painful. Proposed update to the template regarding this topic here: https://review.openstack.org/88028 -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
