FWIW: I don't think this requires any input from VP Legal at this point. Thanks, Roman.
On Wed, Jun 23, 2021 at 12:07 AM Rohit Yadav <[email protected]> wrote: > (+ ASF legal) > > ASF Legal and Infra, /cc ACS marketing and PMC > > The Apache CloudStack project is exploring if the project website and blog > can be moved to Wordpress either hosted by ASF infra or hosted by a > 3rd-party managed service such as wordpress.com. We've asked ASF infra > but haven't heard from them in the last three weeks, so asking again both > ASF legal and infra where it is an official ASF/ASF-infra policy on > requiring project websites and blogs to have version control i.e. content > backed by a git repository (most users won't build website and blogs from > source code). > > Alternatively, if indeed it is a policy of the ASF to require project > website and blog tracked by git/source code - could we explore git-based > CMS services such as https://forestry.io, https://www.netlifycms.org/, > https://cloudcannon.com/, https://www.siteleaf.com. Out of which the > netlifycms is opensource and could be hosted either by netlify or ASF infra? > > For reference this thread can be tracked/read here - > https://markmail.org/message/6snytriinby3dgzv > > > Regards. > > > > > > ------------------------------ > *From:* Ivet Petrova <[email protected]> > *Sent:* Friday, June 18, 2021 20:36 > *To:* [email protected] <[email protected]> > *Cc:* Apache CloudStack Marketing <[email protected]>; > [email protected] <[email protected]>; [email protected] <[email protected]>; > [email protected] <[email protected]> > *Subject:* Re: Uploading Blog Post > > Hi everyone, > > I am writing to just check if we can open this discussion again. I have > such a nice interview with Wido den Hollander and materials on why Cloud > and Hosting Providers should choose CloudStack and how they benefit. > It is a pity we cannot share these thing and show that CloudStack is a > turnkey solution for cloud providers. > > Kind regards, > > > > > > > On 15 Jun 2021, at 1:44, Andrija Panic <[email protected]> wrote: > > Gentle ping here. > > I would like to emphasise what Rohit said - "most users won't build > website and blogs from source code" - we need to find a suitable (yet > manageable) solution for the websites, while still complying with Apache > policies. > > Thanks, > Andrija > > On Wed, 9 Jun 2021 at 11:25, Rohit Yadav <[email protected]> > wrote: > > Hi Greg, Mark, infra, > > Ping - any thoughts, advice, opinion on questions I asked in the previous > email esp. if it is an official ASF/ASF-infra policy on requiring project > websites and blogs to have version control and get on a git repository > (most users won't build website and blogs from source code - just saying). > > Regards. > > > > > > ------------------------------ > *From:* Rohit Yadav <[email protected]> > *Sent:* Thursday, June 3, 2021 14:30 > *To:* [email protected] <[email protected]>; Apache > CloudStack Marketing <[email protected]>; [email protected] < > [email protected]>; [email protected] <[email protected]>; [email protected] > <[email protected]> > *Subject:* Re: Uploading Blog Post > > Thanks Greg, Mark for replying. > > > The short answer is "downstream users should have the ability to > access both code and website sources". That implies that the website > source is in a version control system (git or svn) that can be used to > generate the website, just as much as they can fetch sources to build > the [Apache Cloudstack] releases. > > > I understand the requirement for code and docs. May I ask why this is a > requirement for the project website and blog? > Is it any official ASF or ASF infra policy or simply a standard practice? > > Could the availability of posts DB/table synced to Git repo solve that in > case of a CMS such as Wordpress or Drupal? > > We have not found a way to post to Wordpress.com, sourced from version > control, so ... sorry to say: that is not a viable platform for the > primary website. If y'all can find a way to push from version control > over to wp.com, then yay! That would be great. > > > I didn't find anything exactly but the following may be explored: > > https://github.com/deliciousbrains/wp-migrate-db > https://wppusher.com/ > https://wordpress.org/plugins/wp-github-sync/ > > But I hear that TLPs can get a wordpress instance on wordpress.com > (instead of hosting/managing ourselves), if not for the full TLP website > but at least as a separate blog (say on blog.cloudstack.apache.org)? > Thanks. > > > Regards. > > ------------------------------ > *From:* Greg Stein <[email protected]> > *Sent:* Monday, May 31, 2021 18:18 > *To:* [email protected] <[email protected]> > *Cc:* [email protected] <[email protected]> > *Subject:* Re: Uploading Blog Post > > On Mon, May 31, 2021 at 10:55:58AM +0000, Rohit Yadav wrote: > > + users@infra (kindly, reply all so your email is visible to > > participants on other mailing lists copied in this thread) > > users@infra is a private list, so I've removed it from this reply > (mixing public/private lists is problematic) > > Hi Infra, > > The Apache CloudStack (ACS) community is discussing options to > migrate the project website and blog to Wordpress [1] and the > consensus among the people on this thread is they want to go ahead > with this. Some attempts and discussions [2][3] were made in the past. > > > In particular, please note Mark Thomas' point, and my acknowledgement > at [1]. > > The short answer is "downstream users should have the ability to > access both code and website sources". That implies that the website > source is in a version control system (git or svn) that can be used to > generate the website, just as much as they can fetch sources to build > the [Apache Cloudstack] releases. > > We have not found a way to post to Wordpress.com, sourced from version > control, so ... sorry to say: that is not a viable platform for the > primary website. If y'all can find a way to push from version control > over to wp.com, then yay! That would be great. > > Before we go ahead with a PMC vote, I want to ask Infra if this is > technically feasible for the project website to be moved to Wordpress > which (a) may be hosted by ASF infra (preferably as a VM or service > much like other portals/website) > > > Projects may use VMs for their primary websites, but (historically) > Wordpress has had difficulties with self-hosting. As a result, the > Foundation uses wordpress.com to host the Feathercast blog rather than > attempting to self-host. > > Per above, if you can construct a process running on a VM, that pushes > version control over to WP.com, then that problem is solved. > > (and yes, the Foundation would be fine paying the yearly fee to host > at wp.com; that isn't a concern) > > or (b) by an external Wordpress > hosting service which is under the control of ACS PMC. As I understand > this will require the content to be migrated to a Wordpress instance > (either option-a or option-b) and for ASF infra to update the > CNAME/dns record. > > > Per the linked email, the primary concern is the ability for > downstream users to be able to view/construct all the content of an > Apache product's website. > > Out of curiosity - are there any other projects that have their > websites/blogs based on a CMS (a not static website builds), say > Wordpress, Drupal etc. > > > There are many projects currently using Pelican, sourced from a git > repository, to translate Github-Flavored Markdown files to HTML static > content. This is the Infra-recommended process/workflow for website > publishing. Please see https://infra.apache.org/project-site.html > > We recommend this workflow as it allows content-editors to use > github.com to edit/preview pages very simply, and those changes will > quickly appear on the website when saved. > > Best regards, > Greg Stein > Infrastructure Administrator, ASF > > [1] > > https://lists.apache.org/thread.html/6ec3ff74167a7feac0bd5ee6b4361deb0bea9eb8018df5a3a923b10f%40%3Clegal-discuss.apache.org%3E > > > > -- > > Andrija Panić > > >
