Open Stack

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.




On Wed, Apr 16, 2014 at 8:09 AM, Russell Bryant <rbryant at redhat.com> wrote:

> On 04/16/2014 10:31 AM, Balázs Gibizer wrote:
> > Hi,
> >
> >
> >
> > I’ve just uploaded a new BP proposal to gerrit
> >  https://review.openstack.org/#/c/87978,  but the gate failed as I
> > included an image along with the .rst file in my patch. What is the good
> > place to store the images that are used in the specs?
>
> That just came up in a Neutron thread:
>
> http://lists.openstack.org/pipermail/openstack-dev/2014-April/032885.html
>
> My opinion for now is:
>
> 1) For simple diagrams, try to just use inline ascii.  Try asciiflow.com
> for help making a simple ascii diagram.
>
> 2) If you really need an image, I think we have two options:
>
>    a) host it on the wiki and inline it using the 'image' directive
>       with a link to the image hosted on the wiki.  Then we don't
>       have to deal with managing images in the repo and it's easy
>       to view the image while doing a spec review.
>
>    b) Allow images in nova-specs, perhaps in a subdirectory with
>       the same name as the spec as a new convention.  The benefit
>       is the images are more guaranteed to stay static with the
>       spec, as it was during review.  The downside is it's more of
>       a pain to review, IMO.
>
> Thoughts?
>
> --
> Russell Bryant
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140416/f0261415/attachment.html>