/me stuck in a conference for the next 48hrs
it's good stuck though https://plutojl.org/plutocon2021/
it's open to anyone
going to be a little late
phone call running long
planning doc: https://cryptpad.fr/code/#/2/code/edit/1FhyaBOOANgdSTKA8xbYIt8t/
gonna cancel this one because it seems like people are busy, if anyone has anything they want to talk about lmk and I can start the video call again
@Charles Ellis O'Riley Jr. has been making steady progress on the diagram
beyond that I don't think there's been much work in the last few weeks
Was late to the meeting
did you have anything else you wanted to talk about charles?
I still need to get back to you on your most recent version of the chart
I figured we could keep that async since everyone else is busy
no. I'm good.
we could start defining tasks asynchronously and discuss at the general meeting
the big one is still document structure which includes a data dump of all users experience of error handling
if we could have better structure around content broken up into smaller tasks idk where to start tho
starting is the hard part :grimacing:
I need to take an afternoon and parse through all the notes we've taken in the planning doc and organize + summarize it
I'll aim to do that before the next meeting and come up with a plan
and ill run it by you before then
or we can work on it together if you'd like
we should collab on it yeah
Sorry I didn't attend the book meeting. I did end up writing up a blog post based on some stuff Jane helped me out with as far as extending the minigrep project from the Book: https://github.com/seanchen1991/blog/blob/main/posts/extending-minigrep/index.md
a lot of people are caught up in the async vision process
The content can easily be repurposed for the book in the future
that's definitely a start :heart:
I was also afk yesterday :smile: glad you managed to do meet
Meeting in 30 minutes
today I was hoping we could review the diagram that @Charles Ellis O'Riley Jr. has been working on and plan how to piece it together
Here's the current version of the diagram
discussed pausing future BoFs until progress on book catches up with more contributors
also waiting to hear back on some style questions related to diagram tools and other guidelines for 'rust-doc' books
i.e. which diagram format [i.e. tool] is recommended? also anything about including custom graphical contents?
Oliver, just informed Jane that I spent yesterday getting Graphviz set up on my machine. That was a tool that was used in the part of the Book that I looked at.
never used gv actually, I do that in R
I have r studio. Can that go to git? I never used gv either
which package would you use?
Don’t know. I don’t know if it can be saved to git.
rules eh :rolling_eyes:
Found this: http://r4stats.com/examples/graphics-traditional/
look at ggdag
this is actually pretty hilarious:
tidy_dag <- tidy_dagitty(dag)
I’ll have to do further research. Found this also: https://rkabacoff.github.io/datavis/SavingGraphs.html
.png that's nice
.svg is used in the Book with gv
.svg for gv nice
to know that
existing Rust documentation seems _really_ sparse on diagrams now that I look at it
solving logic problems, [i.e. what Rust presents to 'the user'(sic)], may benefit from being visualized for the reader
This link shows a diagram: https://doc.rust-lang.org/book/ch04-02-references-and-borrowing.html
maybe we should start in the existing docs and add a diagram there
what could be done to show the memory model in a dag package?
ofc. rust _needs_ a memory model :laughing:
so hopefully we're not waiting on that
trying to think about this from a libs project perspective :thinking:
did we ever get feedback on which diagramming format is recommended/approved for Rust documents?
Graphviz is what’s been used. Just did a pull request so you can check out the code.
cool, on the GH?
I understand you can call on this app now. How’s that done?
not yet, it's still wip
Just hijacking this topic. I opened a PR for some general feedback on a high level structure for the book: https://github.com/rust-lang/project-error-handling/pull/45
I'll refine the structure as feedback comes in.
@Jane Lusby @Sean Chen (he/him)
Last updated: Jan 29 2022 at 09:28 UTC