It’s the suggestion mode writing that was the problem. A couple groups I trialed this with eventually switch back to gdocs, and the biggest one was when we almost lost ~40h of work we spent on a grant proposal here Try using NextCloud to coordinate project · Issue #239 · hyphacoop/organizing · GitHub
We explored the technical issue a bit and it seems collab parallel writing is just not well supported.
It it’s markdown based I am happy enough, and integration with nextcloud is a plus.
re: Wekan, it was a couple years back when I tried it but it lacked basic features like search, tagging, notifications, email notifications, filtering, teams, permission management, etc. I don’t know how it is today, but at the time the project didn’t have a promising roadmap to these features. If you have better experience I am open to try.
Yes that is what I mean, just to preserve ppl’s attention and not to limit access. One day we may have a privileged directory with customer private information, but I think we can do without for now.
re: GitLab project board I’d like love to try that, esp since Technology Operations is alrdy working in that space. It will require us to have an account on the gitlab instance though. One path is for Meet.coop to join webarchitects and make meet.coop emails for each contributor who needs edit access. idk what @chris thinks about that.
Alternatively we can use Nextcloud Deck, which may be shortest path to get a basic structure set up.
Proposal:
- Nextcloud for content store
- Nextcloud Deck for task tracker
- Nextcloud WYSYWIG markdown for drafting / hackmd as temp pads
- Matrix <> IRC for chat
- GitLab for Technology Operations only