I would also like to be involved. I, along with @chexxor, maintain the Discourse instance, and I’d rather that and other *.purescript.org resources be held by a PureScript organization instead of a private server.
I don’t have any answers around funding except that:
- I think it’s worth revisiting the idea of an Open Collective account if we are going to accept funding
- I’m happy to pitch in the equivalent cost of running the Discourse each year as my contribution, or more
- I think we should be open to corporate backing, as many of us work at organizations which are deeply invested in PureScript
- This funding could go explicitly to our community resources, meaning hosting, bandwidth, etc, to keep the scope small
I see the costs to run *.purescript.org are small. We’re talking about $240/yr at the moment. But a PureScript organization with some funds can ensure that an uptick in usage doesn’t run anybody in particular dry.
I’ve seen a number of reports in Slack about intermittent Pursuit outages; I think that warrants a deeper look into whether the Linode box is sufficient. I don’t know if there is any monitoring on that server that would reveal the issue. This may end up increasing the cost.
I agree with @hdgarrood that it makes sense for a small group of maintainers to have SSH (and repository access) to manage these resources, and ideally changes to the repositories automatically deploy. That group of maintainers could have a Discourse area as a communication channel to discuss issues, as well.
Unrelated to the infrastructure maintenance of the *.purescript.org organization, I also care deeply about PureScript documentation and resources and things like try.purescript.org being up to date and usable and would like to broaden access for folks to help out and get updates made to them.
@paf31 As these resources are currently yours, how did you envision handing things over to the relevant people?