I was thinking in terms of helping build out a team to work on non-dev related work, as opposed to pulling away time from the devs, who I’m sure are heads down. Fair points though!
Would the same apply to something like creation of a new website? Or a weekly newsletter, or similar? I was assuming that non-dev work would be coordinated outside of GitHub, but could be wrong!
I’m just talking about contributing time to helping develop a platform. Corporations are good at process - so yes, there are definitely lessons to be learned there that should be implemented in any platform that is quickly growing (eg: putting a team of volunteers together to help out)
The issue with that approach (too busy to build structure), is that it’s a never ending battle. There is never a good time. It’s an easy trap to fall into.
The best way to be successful with products like this is to invest time early in building out the team. By doing so, you’re multiplying output and limiting tech debt.
I would even be happy to help with helping build out the team (identifying gaps, key roles, volunteers) as that’s something I’m experienced with.
The GitHub repo will be focused on software-level initiatives, whereas I’m talking more about product-level.
If the team is that small, then they need more people involved in product ownership, which is what I’m interesting in contributing towards (as others are too, I assume)
There is unfortunately not a good tool to help with what you’re looking for.
The best way is to browse to a few servers and see if they feel snappy. You can click through without an account.
https://wirebase.org is ours, which is hosted in the US