Closed Ainali closed 4 years ago
we should consider buying maillist hosting services
Yes. Buying the service relieves us from having to do sys admin and backup of it ourselves. Perhaps we should do a quick session for a set of requirements that we would have on such a service and then look around to see what is available?
So after a short meeting we came up with the following short list of requirements:
So based on the requirements above, I looked at the list on the mailman site and found some alternatives that all seem to be good enough:
I suggest we start out with the first one, setting up a list for the standard and see how it works out.
I agree, @Ainali could you see which one fits our procurement principles the best? Then let's go for that one.
@gmarpons This is my previous research. I misremembered that there were any totally free mailman hosts. I cannot find any here or in my browser history that does it free of charge.
Just a note that I am actively having this on hold until I can explore how the mailing lists in Odoo works. If it fulfill our requirements above we should consider using it.
It turned out that what I thought could be mailing lists in Odoo only was email campaigns in the Email marketing app. With that settled I will go ahead with Power Netz that seems closest to our procurement principles.
I updated the requirements after good input from @bvhme. Search continues.
Based on @Ainali, @demkodo and me reviewing the list of early incubation product assets, we'll need vetted tools we can recommend (and deploy promptly) for: codebase repository hosting, marketing website hosting (we're currently missing MVP templates for static sites), community fora, documentation hosting (if the codebase is extensive enough), issue tracking and roadmap.
A related need is to have examples we like of how other open source codebases have set up their tooling, so a codebase considering adopting a new tool can see a range of perfectly reasonable options. @Ainali also mentions having a mechanism for getting a codebase a domain name.
Made an overview of the community tool needs and possibilities. Let's mule it over and plan a moment to see what the next best step can be. Information on the quote, setup and possibilities, including other options can be found here: https://drive.google.com/drive/u/0/folders/1U1n60VSpnLhKneYaZfIGjf7Te2-WzKVj
There are no other hosting companies that I know of that can provide these services, so Greenhost is our best shot. Greenhost has not offered Discourse and Phabricator before so we can discuss a custom setup for this with them. An alternative is doing the 'basic' services such as provisioning (sub) domain names, Mailman mailing lists, VPS'es for GitLab and Bitbucket at Greenhost, and have Discourse and Phabricator hosted and serviced on premises at these companies themselves.
Very nice, thanks @demkodo!
So we really only need Discourse for our own purposes immediately. The other ones can be put on hold for now until we see more of a concrete need in codebases that are incubating. (Me and @ElenaFdR were quite convinced by Matt Broberg's talk at FOSDEM that it is superior to mailing lists and therefore that we should start with just that.) Perhaps setting this up deserves to be broken out to its own issue?
Continuing on this issue, we should probably start taking notes on our experiences with different tools and hosting alternatives so that we can point codebases that have not made a commitment towards stewardship yet to good solutions. Open questions around that is: where to store such a list and what does it need to include to be useful?
@demkodo I guess we can close this one now?
We now have a functional mailing list, checked with @demkodo - this can be closed :tada:
From the session about the top 20 in publiccodenet/jekyll-theme#30 it was discovered that we should look into maybe hosting some sort of mailing lists for codebases that are under stewardship. @ericherman and I will look into that.