Thank you for your thoughtful post. I hope you don’t mind that I pulled it out of Brandon’s topic on module maintenance conventions. While your post strayed off topic in that thread, I think you make some great points and I wanted to make sure we had space to discuss this.
This doesn’t actually have to do with
/dev stages; rather, it’s a built-in feature of Discourse to ensure visitors to the forum have engaged with the community a bit (built up a level of trust) before they start PM’ing folks.
We need to introduce you to my good friend Docker. The days of installing and managing different versions of software natively are behind us. With Docker installed, a command for installing MySQL 5.6 and running on your machine (regardless of OS) is:
docker run -d -p 3306:3306 -e MYSQL_ROOT_PASSWORD=secret mysql:5.6
Could you take a look at om.rs/gettingstarted and see if there are some ways it could be improved to overcome the challenges you’ve identified? Would a link to om.rs/glossary or specific edits/updates to the om.rs/devmanual help?
This type of detail is important. The uptime for most of our infrastructure is now 99.99%. The demo server is 88.69%, but that is only checking that the web page responds and may not reliably reflect actual uptime. I’ve just modified our uptime check to simulate a login via the REST API, so it should more accurately reflect uptime. Perhaps we could have a virtual hackathon to identify & address specific issues that are reducing the demo server’s reliability.
Also, the Android client could be adapted to alter it’s error message when the server URL contains “demo.openmrs.org” to help the user (e.g., a tip like “Check demo.openmrs.org and/or status.openmrs.org and make sure the demo site is running.”)
It might be time to retire or at least stop advertising Telegram. I think most community chat is happening in IRC or Slack these days. The challenge with chat clients is there’s always the shiny new one and they all have pros & cons. We need matrix.org to take over the world and connect all chat clients so we don’t have to choose.
This sounds like great grist for the documentation teams to take on.
This might be useful for new GSoC students as well. /cc @suthagar23
Bless you for your willingness to share constructively. It’s a beautiful wall you’ve built. I hope @jennifer gets a chance to admire your wall too.