I tried uploading them to the wiki, but it only accepts a few file types (not including zip either). I still think we need a safe, accessible place for them with some sort of version control.<br><br><div class="gmail_quote">On Tue Jan 06 2015 at 3:55:52 AM Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 03/12/14 03:58, Anne Gentle wrote:<br>
><br>
><br>
> On Fri, Nov 28, 2014 at 9:15 AM, Christian Berendt<br>
> <<a href="mailto:berendt@b1-systems.de" target="_blank">berendt@b1-systems.de</a> <mailto:<a href="mailto:berendt@b1-systems.de" target="_blank">berendt@b1-systems.de</a>><u></u>> wrote:<br>
><br>
> On 11/28/2014 03:46 PM, Matt Kassawara wrote:<br>
> > rather straightforward. As for .graffle files in the repo, I would like<br>
> > to store them somewhere because a lot of people appear to use<br>
> > OmniGraffle and those files contain metadata that improves efficiency<br>
> > over SVGs.<br>
><br>
> I think that it is not correct to use proprietary software running on a<br>
> proprietary operating system generating proprietary source files to<br>
> create graphics for the OpenStack documentation. There is usable open<br>
> source software to create graphics (like inkscape) and I think such<br>
> software should be used and has to be used.<br>
><br>
><br>
> I know this sentiment runs deep in open source communities. I support<br>
> the spirit but won't enforce in practice other than to ensure open<br>
> formats are in our repo to ensure we're enabling correct licensing of<br>
> the content.<br>
><br>
> For the Ops Guide, we don't use Adobe Illustrator for example, but the<br>
> source from O'Reilly is .ai files. However we don't have those source<br>
> files and have been editing png and svg in the community. I think there<br>
> are similarities here.<br>
><br>
> I think it makes sense to upload CC licensed images to the wiki, as done<br>
> for <a href="https://wiki.openstack.org/wiki/Icons" target="_blank">https://wiki.openstack.org/<u></u>wiki/Icons</a> where there are eps, svg, and<br>
> png.<br>
> I also think that it's not crucial that graffle files or ai files are<br>
> uploaded anywhere.<br>
><br>
> Generally we should document our approach to images, and it should<br>
> include a priority towards open source, but a higher priority towards<br>
> licensing than tooling.<br>
> Just my current thinking, feel free to persuade me for another line.<br>
> Thanks,<br>
> Anne<br>
<br>
Necro-posting here, but what should become of this review, which deletes<br>
all graffle files<br>
<br>
<a href="https://review.openstack.org/#/c/137783/" target="_blank">https://review.openstack.org/#<u></u>/c/137783/</a><br>
<br>
?<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a><br>
</blockquote></div>