Closed ghost closed 4 years ago
This is a great question. So, we originally started developing all of our documents using Google Docs due to its ability to support real-time collaboration. As an initial attempt to publish these in a way that's a bit more friendly to consume online (and separate from Google docs) we made an initial attempt at throwing most (but not all) of our resources through pandoc and publish them on a static website in markdown.
We don't yet have a good workflow yet for keeping these documents in sync. In general, when we have shared our resources, we have linked to the google docs. In terms of fostering further collaboration among them, that's been a significant problem that we haven't yet solved. :(
With regard to the config, I suspect this is just a bug.
Included in 2020-03-24 issue triage and cleanup.
This is something I want to address, but @Nolski has an issue open for a similar topic in #12. I'm going to use that issue as a central place to discuss how our content on closed platforms makes its way into more open content.
Closing as duplicate. :clapper:
While skimming the opensource.com article today, I drilled down two levels deep from the provided links into the Google Docs reading list, and noticed a typo.
I've since done the usual: Forked and cloned the librecorps/resources repo, corrected it in my clone, pushed to my fork, and from my fork issued a pull request to upstream. Assuming that goes through well enough, that will correct the typo in the repo. (Maybe I should have saved it as an easy bug for HFOSS but alas sometimes I have to just do the thing.) So far so good.
Along the way of doing that though I noticed a few things that aren't clear to me but that might be documented somewhere if only I can get some pointers and which might help other potential contributors less familiar with LibreCorps day-to-day:
[ ] What is the relationship between the resources repo and the Google docs?
[ ] How does content flow from one to the other, and in which direction?
[ ] Since the Google docs versions are the published ones but are not generally editable (I cannot, for instance, edit them from my non-RIT Google account), how might someone who is less familiar than me with our idiosyncratic use of
tasks
repos meant to channel their contributions? Any chance we can eventually replace each of the Google docs with some short text redirecting to their counterparts on the web site?[ ] I noticed that the config.toml file makes reference to https://librecorps.github.io/resources which is fine. but the base URL (https://librecorps.github.io/) is 404, which I found disorienting.