On Tue, Nov 08, 2016 at 10:09:10AM +0000, Stephen Finucane wrote: > - We deploy to a subdomain like 'docs.openvswitch.org' and actually host on > ReadTheDocs [3] or similar > > We would start with a stock theme and possibly look at creating one that > matches the visual identity of the main site at a later date (see the > OpenStack Docs [4] vs. OpenStack main site [5]). ReadTheDocs would provide > automatic uploading, versioning, etc., preventing the need to manually > update the site each time we get a doc-related patch. There is, however, an > optional cost associated with this (*). I noticed that the mailing list > archives seem to have been moved to 'mail.openvswitch.org' over the weekend, > for example. > > I prefer the second option, but I'm used to this workflow and therefore > biased.
I'm willing to try the readthedocs option. We've had great success using other SaaS (github, travis, appveyor) for Open vSwitch, and although I don't have experience with readthedocs I'm willing to give it a shot. > (*) I have less than zero say in this, but if we end up using ReadTheDocs > then I would request that the project look at the corporate options offered > (https://readthedocs.com/services/#open-source-support). ReadTheDocs do a > fantastic job for the open source community and, as Heartbleed and the > subsequent Core Infrastructure Initiative showed us, open source tools and > sites always need the cash to keep doing what they do. I'm not actually sure whether I understand the options there. The URL you mention talks about "Open Source Support" as if it is different from their other pricing options, but I do not see anything special for open source when I click on "Pricing". I'm sure I can get VMware to kick in $50/month for the "Basic" plan, but I don't know whether I'm actually looking at the right thing there. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
