From: Alyssa Ross <hi@alyssa.is>
To: ville.ilvonen@unikie.com
Cc: discuss@spectrum-os.org
Subject: Re: Documentation and diagrams
Date: Tue, 17 May 2022 12:25:08 +0000 [thread overview]
Message-ID: <20220517122508.ioizqbm6rcpk3waw@eve> (raw)
In-Reply-To: <165276675569.2703.7962474952768136863@atuin.qyliss.net>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi Ville, thanks for looking into this!
On Tue, May 17, 2022 at 05:52:35AM -0000, ville.ilvonen@unikie.com wrote:
> What I'd like to propose that in addition to aiming at
> text-to-diagrams we support diagram drawing tool(s) and agree on
> either png or svg with diagrams. With diagram drawing tools, we
> should store the diagrams in editable format in version control (not
> only png and svg). My 2 cents would go to
> https://github.com/jgraph/drawio but I'm fine with others as well -
> as long as they do not require commercial license.
I've heard very good things about draw.io. I agree with your
assessment that having a graphical diagramming tool would be useful.
draw.io being FOSS is a big plus for it as well — I think it's
desirable that contributing to Spectrum does not depend on proprietary
software.
One question about draw.io: is there a tool we could use in the build
process of our documentation to render the .drawio files to SVG, so we
don't have to check in the SVG files?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-17 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 5:52 Documentation and diagrams ville.ilvonen
2022-05-17 11:42 ` Mark Stosberg
2022-05-17 12:25 ` Alyssa Ross [this message]
2022-05-17 19:00 ` Paco
2022-05-18 12:44 ` Ville Ilvonen
2022-05-18 12:53 ` Alyssa Ross
2022-05-18 13:11 ` Alyssa Ross
2022-05-19 7:25 ` Ville Ilvonen
2022-05-19 7:35 ` Alyssa Ross
2022-05-19 8:33 ` Ville Ilvonen
2022-05-19 8:49 ` Alyssa Ross
2022-05-18 13:09 ` Michael Raskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220517122508.ioizqbm6rcpk3waw@eve \
--to=hi@alyssa.is \
--cc=discuss@spectrum-os.org \
--cc=ville.ilvonen@unikie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).