On Fri, May 15, 2015 at 06:33:35PM -0700, Joe Gordon wrote:
> On Fri, May 15, 2015 at 2:27 PM, Joe Gordon wrote:
> > On Thu, May 14, 2015 at 3:52 AM, John Garbutt
> > wrote:
> >> Some great points make here.
> >>
> >> Lets try decide something, and move forward here.
> >>
> >> Key requirements se
+1
On Fri, Jun 5, 2015 at 6:38 PM, Vilobh Meshram <
vilobhmeshram.openst...@gmail.com> wrote:
> +1
>
> On Thu, May 14, 2015 at 3:52 AM, John Garbutt
> wrote:
>
>> On 12 May 2015 at 20:33, Sean Dague wrote:
>> > On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
>> >> On 2015-05-12 10:04:11 -0700 (-0
+1
On Thu, May 14, 2015 at 3:52 AM, John Garbutt wrote:
> On 12 May 2015 at 20:33, Sean Dague wrote:
> > On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
> >> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
> >>> It's a nice up side. However, as others have pointed out, it's only
> >>> ca
Markus Zoeller wrote:
Joe Gordon wrote on 05/16/2015 03:33:35 AM:
After further investigation in blockdiag, is useless for moderately
complex diagrams.
Here is my attempt at graphing nova [0], but due to a blockdiag bug
from 2013, [1] it is impossible to clearly read. For example, in the
diagr
Joe Gordon wrote on 05/16/2015 03:33:35 AM:
>
> After further investigation in blockdiag, is useless for moderately
> complex diagrams.
>
> Here is my attempt at graphing nova [0], but due to a blockdiag bug
> from 2013, [1] it is impossible to clearly read. For example, in the
> diagram the
As someone who contributes a significant number of diagrams to OpenStack
documentation [1], I think I can provide some insight from a different
(non-developer?) perspective. Primarily, we should consider the information
that a diagram conveys and the audience that references it. A picture is
worth
On Fri, May 15, 2015 at 2:27 PM, Joe Gordon wrote:
>
>
> On Thu, May 14, 2015 at 3:52 AM, John Garbutt
> wrote:
>
>> On 12 May 2015 at 20:33, Sean Dague wrote:
>> > On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
>> >> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
>> >>> It's a nice up
On Tue, May 12, 2015 at 5:25 AM, Thierry Carrez
wrote:
> Sean Dague wrote:
> > They can be modified if you provide source files, or use a source
> > oriented format like SVG, or ISO standard ODG (used by OpenOffice /
> > LibreOffice). There is a reason the "spider" diagram has ended up in
> > eve
On Thu, May 14, 2015 at 3:52 AM, John Garbutt wrote:
> On 12 May 2015 at 20:33, Sean Dague wrote:
> > On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
> >> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
> >>> It's a nice up side. However, as others have pointed out, it's only
> >>> capabl
On 05/14/2015 06:52 AM, John Garbutt wrote:
> On 12 May 2015 at 20:33, Sean Dague wrote:
>> On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
>>> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
It's a nice up side. However, as others have pointed out, it's only
capable of displaying
On 05/13/2015 04:09 PM, Dolph Mathews wrote:
> Developers can handle ASCII. Developers can't handle steel blue versus
> cornflower blue.
>
> But seriously, graphics collaboratively authored by developers should,
> ideally, be editable via a text file. Otherwise they won't be maintained.
Like how
On 12 May 2015 at 20:33, Sean Dague wrote:
> On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
>> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
>>> It's a nice up side. However, as others have pointed out, it's only
>>> capable of displaying the most basic pieces of the architecture.
>>>
>>
Matthew Treinish wrote:
On Wed, May 13, 2015 at 02:36:48PM -0700, Joshua Harlow wrote:
Dolph Mathews wrote:
Developers can handle ASCII. Developers can't handle steel blue versus
cornflower blue.
But seriously, graphics collaboratively authored by developers should,
ideally, be editable via a
On Tue, May 12, 2015 at 8:22 AM, Steve Baker wrote:
> On 12/05/15 09:57, Joe Gordon wrote:
>
>> When learning about how a project works one of the first things I look
>> for is a brief architecture description along with a diagram. For most
>> OpenStack projects, all I can find is a bunch of rand
On Wed, May 13, 2015 at 02:36:48PM -0700, Joshua Harlow wrote:
> Dolph Mathews wrote:
> >Developers can handle ASCII. Developers can't handle steel blue versus
> >cornflower blue.
> >
> >But seriously, graphics collaboratively authored by developers should,
> >ideally, be editable via a text file.
Dolph Mathews wrote:
Developers can handle ASCII. Developers can't handle steel blue versus
cornflower blue.
But seriously, graphics collaboratively authored by developers should,
ideally, be editable via a text file. Otherwise they won't be maintained.
I'm gonna go out on a limb here and say
Developers can handle ASCII. Developers can't handle steel blue versus
cornflower blue.
But seriously, graphics collaboratively authored by developers should,
ideally, be editable via a text file. Otherwise they won't be maintained.
On Tue, May 12, 2015 at 8:31 PM, Devananda van der Veen <
devana
Woops. I missed most of this thread in my last reply.
I'm all for using open standard formats and versioning them. However. Not
being a graphical artist myself, I have found the learning curve on some of
those tools daunting, eg. inkscape, which means I'm far less likely to
update a graphic in a f
In ironic, we have use asciiflow several times quite successfully in the
spec process.
We also maintain in-tree docs with .PNG graphics, and versioning those has
been a bit of a pain. They were originally taken out of slide decks, and
served their purpose, but really ought to be in a different for
On 05/12/2015 01:12 PM, Jeremy Stanley wrote:
> On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
>> It's a nice up side. However, as others have pointed out, it's only
>> capable of displaying the most basic pieces of the architecture.
>>
>> For higher level views with more components, I do
On 2015-05-12 10:04:11 -0700 (-0700), Clint Byrum wrote:
> It's a nice up side. However, as others have pointed out, it's only
> capable of displaying the most basic pieces of the architecture.
>
> For higher level views with more components, I don't think ASCII art
> can provide enough bandwidth
Excerpts from Jeremy Stanley's message of 2015-05-12 08:35:40 -0700:
> One up side to keeping simple diagrams as ASCII art (and converting
> to something more palatable via a Sphinx plugin) is that people
> browsing the source code can just read it--this is the same reason
> we have a preference fo
One up side to keeping simple diagrams as ASCII art (and converting
to something more palatable via a Sphinx plugin) is that people
browsing the source code can just read it--this is the same reason
we have a preference for reStructuredText over something more
presentation-oriented like SGML or Tex
Sean Dague wrote:
On 05/12/2015 05:22 AM, Thierry Carrez wrote:
John Garbutt wrote:
On 11 May 2015 at 23:46, Boris Pavlovic wrote:
Couldn't we just use real image files to do this. IIRC, gerrit supports
displaying image files which are included in a commit. For example, I've
been
planning to
I'd recommend images if we could figure it out, so much nicer...
I thought we weren't in a time machine anymore, but idk, ha.
Maybe we are all in a hot tub together...
Anyways joking aside,
Stuff like https://wiki.openstack.org/wiki/RunInstanceWorkflows was
generated using https://www.websequ
On Tue, May 12 2015, Sean Dague wrote:
[]
> I mean try doing this workflow in ascii art -
> http://docs.openstack.org/infra/manual/developers.html and see if it's
> as clear.
Hello,
I am a newcomer, and for sure this diagram is not clear. I guess this
is a bad chosen example.
For example ther
On 05/12/2015 08:47 AM, Clint Byrum wrote:
> I agree with all the things above, and I want to add that I think SVG
> is probably the most appropriate candidate as a W3C approved drawing
> format. We can even enforce style rules and use a reformatter so that
> diffs make sense.
+1 for SVG
As alrea
Excerpts from Sean Dague's message of 2015-05-12 03:48:11 -0700:
> On 05/12/2015 05:22 AM, Thierry Carrez wrote:
> > John Garbutt wrote:
> >> On 11 May 2015 at 23:46, Boris Pavlovic wrote:
> Couldn't we just use real image files to do this. IIRC, gerrit supports
> displaying image files
Sean Dague wrote:
> They can be modified if you provide source files, or use a source
> oriented format like SVG, or ISO standard ODG (used by OpenOffice /
> LibreOffice). There is a reason the "spider" diagram has ended up in
> every single OpenStack presentation I've seen for the last 2 years.
A
On 12/05/15 06:48 -0400, Sean Dague wrote:
On 05/12/2015 05:22 AM, Thierry Carrez wrote:
John Garbutt wrote:
On 11 May 2015 at 23:46, Boris Pavlovic wrote:
Couldn't we just use real image files to do this. IIRC, gerrit supports
displaying image files which are included in a commit. For exampl
On 05/12/2015 05:22 AM, Thierry Carrez wrote:
> John Garbutt wrote:
>> On 11 May 2015 at 23:46, Boris Pavlovic wrote:
Couldn't we just use real image files to do this. IIRC, gerrit supports
displaying image files which are included in a commit. For example, I've
been
planning t
On Tue, May 12, 2015 at 5:22 PM, Thierry Carrez
wrote:
> John Garbutt wrote:
> > On 11 May 2015 at 23:46, Boris Pavlovic wrote:
> >>> Couldn't we just use real image files to do this. IIRC, gerrit supports
> >>> displaying image files which are included in a commit. For example,
> I've
> >>> bee
John Garbutt wrote:
> On 11 May 2015 at 23:46, Boris Pavlovic wrote:
>>> Couldn't we just use real image files to do this. IIRC, gerrit supports
>>> displaying image files which are included in a commit. For example, I've
>>> been
>>> planning to copy these images:
>>
>> +1 for real images
>
> On
On 11 May 2015 at 23:46, Boris Pavlovic wrote:
>> Couldn't we just use real image files to do this. IIRC, gerrit supports
>> displaying image files which are included in a commit. For example, I've
>> been
>> planning to copy these images:
>
> +1 for real images
One suggestion I remember around s
lo/websso-portal.html
>
>
> Thanks,
>
> Steve Martinelli
> OpenStack Keystone Core
>
> Joe Gordon wrote on 05/11/2015 05:57:48 PM:
>
> > From: Joe Gordon
> > To: OpenStack Development Mailing List
>
> > Date: 05/11/2015 05:59 PM
> > Subject: [o
.
[1] https://pypi.python.org/pypi/sphinxcontrib-aafig/1.0
Joe Gordon wrote on 05/11/2015 11:57:48 PM:
> From: Joe Gordon
> To: OpenStack Development Mailing List
> Date: 05/12/2015 12:02 AM
> Subject: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?
>
> Wh
Martinelli
OpenStack Keystone Core
Joe Gordon wrote on 05/11/2015 05:57:48 PM:
> From: Joe Gordon
> To: OpenStack Development Mailing List
> Date: 05/11/2015 05:59 PM
> Subject: [openstack-dev] [nova][all] Architecture Diagrams in ascii art?
>
> When learning about how a projec
>
> Couldn't we just use real image files to do this. IIRC, gerrit supports
> displaying image files which are included in a commit. For example, I've
> been
> planning to copy these images:
+1 for real images
Best regards,
Boris Pavlovic
On Tue, May 12, 2015 at 1:36 AM, Matthew Treinish
wrote
On Mon, May 11, 2015 at 02:57:48PM -0700, Joe Gordon wrote:
> When learning about how a project works one of the first things I look for
> is a brief architecture description along with a diagram. For most
> OpenStack projects, all I can find is a bunch of random third party slides
> and diagrams.
On 05/11/15 at 02:57pm, Joe Gordon wrote:
When learning about how a project works one of the first things I look for
is a brief architecture description along with a diagram. For most
OpenStack projects, all I can find is a bunch of random third party slides
and diagrams.
Most Individual OpenSta
Use dia[1] (opensource) or omnigraffle[2] (not free/open) or something
else (preferable the free/opensource ones)?
[1] http://dia-installer.de/
[2] https://www.omnigroup.com/omnigraffle
Joe Gordon wrote:
When learning about how a project works one of the first things I look
for is a brief arch
On 12/05/15 09:57, Joe Gordon wrote:
When learning about how a project works one of the first things I look
for is a brief architecture description along with a diagram. For most
OpenStack projects, all I can find is a bunch of random third party
slides and diagrams.
Most Individual OpenStack
When learning about how a project works one of the first things I look for
is a brief architecture description along with a diagram. For most
OpenStack projects, all I can find is a bunch of random third party slides
and diagrams.
Most Individual OpenStack projects have either no architecture diag
43 matches
Mail list logo
