Will do by Friday this week
Nothing has changed. With Overleaf, you can have access either if I add you as collaborators (requires account, possibly even pro version), or if you use the edit link, which I shared before. My mistake was to include a vanilla link copied from my browser bar, which of course does not work for you because you don’t have the right cookie.
2 Likes
Still recovering from COVID and am behind on a lot of work – I’ll be catching up on this but likely won’t be able to do it until December.
Just an FYI; I am working on my section on Google docs until I remember how LaTeX works - it’s been years since I had to touch that syntax. Once I have a draft I will try to TeX-ify it as best I can.
Yes, sure. Just beware the Markdown syntax of # Header, because it breaks the compiler.
1 Like
Hello all, I have resumed work on the White Paper lately (read only link, co-authors also have the read-write one). Here is an update.
The White Paper turns out to be quite a large endeavor. The current version stands at over 8,000 words, and is far from finished. Plus, it is only a draft; even the parts that are already written need at least one substantial pass. I am not clear how close to finished it should be before we put online a first version.
On the other hand, it is a really valuable comprehensive document. I imagine it will not be read back-to-back, but rather consulted.
- I have now full drafts of sections 1, 3, 4, 5, 11 and 13. Section 5, on network reduction, does not yet contain a discussion on hierarchies as network reduction.
- I have copied the text from @hugi’s Google Doc into section 12, in practice it contains an intro and section 12.1, with a few more subsections to finish.
- I have added data repositories to section 14.2.
To complete a first draft, this leaves:
- Section 2 on epistemology. This is perhaps the most dense. @markomanka and I organized a discussion about it for next week.
- Section 6 on saturation, care of Marco.
- Section 7 and 8 on coding, care of @amelia.
- Sections 9 and 10, on outreach and community management. But here I have mixed feelings. Perhaps, given the more general approach we are giving to SSNA lately, we could also remove these sections, and introduce a simple reference to them into section 13. Any thoughts, anyone?
- Section 12 needs to be finished (by Hugi)
- Section 14.1 (code repos) needs also to be finished.
When that is done, we will need to attack a second draft; re-read, edit, address the comments (I have already left many, I don’t doubt many more will come).
Are you guys still up for this, or should I stop investing time?
I am. The reason I stopped is that the tech stack looked like it was going to change, with a new Graphryder arriving earlier than I’d first expected. That might bring about changes that should be included in the white paper, so I’m waiting for that to settle.
This is the work I’m currently doing to define the next version of Graphryder.
Once we have finalized the features and technical choices and start the development of the new version, I will come back to the whitepaper and write my section based on that.