Do you have a provisional list of packages you're planning to include? I do, but it's currently not published yet. How will you make money, or is this a labou

Do you have a provisional list of packages you're planning to include? I do, but it's currently not published yet. How will you make money, or is this a labour of love? Red Hat-like subscription model. I will provide support, security advisories, etc. One of the main benefits here is actually that someone has gone through publicly available packages and vetted them for code quality - that might be one of your bigger selling points, even above stability (which is relatively easy to achieve with vendoring). This could potentially be a sort of 'standard stack' for go for corps who want to try out the language. Indeed. Do you have permission from the package authors for this? I realise you don't need it, but it might be nice to involve them in some way, or even make sure it benefits them in some small way if you make money from it? I didn't ask for permission, but I agree with you about involvement. The ultimate goal is to hire/sponsor as many package authors as possible :-) BTW, after doing code reviews of some packages, I already submitted a few pull requests to them, so even thought right now there are no financial contributions to package authors, there are some benefits for being included in StableLib :-) Perhaps you could even act as a broker between corporations who want features/fixes and package writers who want to get paid for their time? This is a great idea, thank you! Are you planning managing patches/bug fixes yourself for packages which fall into disuse? Yes.