librecorps / tasks

Internal ticket tracker related to LibreCorps project planning and management.
https://github.com/orgs/librecorps/projects/1?fullscreen=true
2 stars 0 forks source link

Google Docs vs Github, relations and workflows documented? #27

Closed ghost closed 4 years ago

ghost commented 4 years ago

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:

Nolski commented 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. :(

Nolski commented 4 years ago

With regard to the config, I suspect this is just a bug.

jwflory commented 4 years ago

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: