It isn’t that bad, the steps involved are:
- Create a fork of the GitHub repo.
- Edit the fork and then create a pull request.
- Find someone to manually merge the patch file that is generated by the pull request (the URL of this file is contained in the email sent about the pull request by GitHub, for example
https://patch-diff.githubusercontent.com/raw/cotech/jekyll-website/pull/1.patch).
The main disadvantage is that the dev version of the site only updates when the git.coop repo is updated so the GitHub user doesn’t get to see the results straight after each commit.
I can’t think why not, we have an allow list of domains that can be used to create accounts via email on git.coop so it would simply be a matter of adding all the CoTech member domains to that list, assuming CoTech agrees to abide by the rules, completes an application form and buys one or more membership share (£1 each).