Communication within project and further

[petermr]

We've now got several high-quality volunteers, and I expect more. How do we keep in touch? And how do we allow newcomers (who may not have Git logins and not know what it is) to leave and read messages.

Here are some ideas:

• Googledocs. Annotable, supports asynchorism, not easy to expose publicly.
• Etherpad or Cryptpad. Very simple to start, deliberately ephemeral. Security through obscurity

I don't want to run a server as I can't guarantee I'll be able to keep running it. But is there any sort of unattended lightweight server? Does Github have servers?

The messages are likely to be:

• what does this site do?
• I can offer help
• X doesn't work|
• spam

[petermr]

Record EVERYTHING on the site IMMEDIATELY. Here's what I wrote to Clyde:

• Create a new directory on the site. Call it textIndexing/
• create a subdirectory SOLR
• Open a new MD doc
• run each command and paste the command and result IMMEDIATELY. Does NOT have to be pretty!
• we may get someone else to clean it later.

The point is that we all need to know what the others are doing. This is not an academic publication, it's an emergency.

[petermr]

MEETING at 1200 UTC 2020 03 27

I'm talking with Dan Hagon at 1200. I sugest as many as possible join . We'll all try to give an overview.

[axiomsofchoice]

We've set up a Slack: https://openvirus.slack.com