You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Ivet Petrova <iv...@shapeblue.com> on 2021/05/13 12:19:59 UTC
Re: Uploading Blog Post
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<https://www.linkedin.com/company/ewerk-group> | Xing<https://www.xing.com/company/ewerk> | Twitter<https://twitter.com/EWERK_Group> | Facebook<https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com>. They referred me to a legal discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Cc: users@cloudstack.apache.org
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
Re: Uploading Blog Post
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Jun 25, 2021 at 12:32 AM Rohit Yadav <ro...@apache.org> wrote:
>
> Thanks for replying Roman. So as I understand, there is no official ASF Legal or Infra policy, correct?
Not all foundation policies are driven by Legal or Infra. Some, for
example, are driven by VP Brand.
In this particular case -- I'd day it is a branding/PR issue.
> TLP PMC can decide how they want to host, manage, publish the project website and blogs?
Anyone can host a website or blog anywhere. The real question is
what's the only website/blog that can speak on behalf of the entire
PMC. I believe this to be a branding/PR issue and I would expect the
requirement for it to include a domain name in the .apache.org domain.
I don't think hosting technology should be part of the consideration.
Thanks,
Roman.
Re: Uploading Blog Post
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Jun 25, 2021 at 12:32 AM Rohit Yadav <ro...@apache.org> wrote:
>
> Thanks for replying Roman. So as I understand, there is no official ASF Legal or Infra policy, correct?
Not all foundation policies are driven by Legal or Infra. Some, for
example, are driven by VP Brand.
In this particular case -- I'd day it is a branding/PR issue.
> TLP PMC can decide how they want to host, manage, publish the project website and blogs?
Anyone can host a website or blog anywhere. The real question is
what's the only website/blog that can speak on behalf of the entire
PMC. I believe this to be a branding/PR issue and I would expect the
requirement for it to include a domain name in the .apache.org domain.
I don't think hosting technology should be part of the consideration.
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@apache.org>.
Thanks for replying Roman. So as I understand, there is no official ASF
Legal or Infra policy, correct?
TLP PMC can decide how they want to host, manage, publish the project
website and blogs?
Regards.
On Wed, Jun 23, 2021 at 9:41 PM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> 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 <ro...@shapeblue.com>
> 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 <iv...@shapeblue.com>
>> *Sent:* Friday, June 18, 2021 20:36
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> *Cc:* Apache CloudStack Marketing <ma...@cloudstack.apache.org>;
>> gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>;
>> users@infra.apache.org <us...@infra.apache.org>
>> *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 <an...@gmail.com> 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 <ro...@shapeblue.com>
>> 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 <ro...@shapeblue.com>
>> *Sent:* Thursday, June 3, 2021 14:30
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
>> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com
>> <
>> gstein@gmail.com>; ged@apache.org <ge...@apache.org>;
>> users@infra.apache.org
>> <us...@infra.apache.org>
>> *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 <gs...@gmail.com>
>> *Sent:* Monday, May 31, 2021 18:18
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
>> *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ć
>>
>>
>>
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@apache.org>.
Thanks for replying Roman. So as I understand, there is no official ASF
Legal or Infra policy, correct?
TLP PMC can decide how they want to host, manage, publish the project
website and blogs?
Regards.
On Wed, Jun 23, 2021 at 9:41 PM Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> 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 <ro...@shapeblue.com>
> 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 <iv...@shapeblue.com>
>> *Sent:* Friday, June 18, 2021 20:36
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> *Cc:* Apache CloudStack Marketing <ma...@cloudstack.apache.org>;
>> gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>;
>> users@infra.apache.org <us...@infra.apache.org>
>> *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 <an...@gmail.com> 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 <ro...@shapeblue.com>
>> 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 <ro...@shapeblue.com>
>> *Sent:* Thursday, June 3, 2021 14:30
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
>> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com
>> <
>> gstein@gmail.com>; ged@apache.org <ge...@apache.org>;
>> users@infra.apache.org
>> <us...@infra.apache.org>
>> *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 <gs...@gmail.com>
>> *Sent:* Monday, May 31, 2021 18:18
>> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
>> *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ć
>>
>>
>>
Re: Uploading Blog Post
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
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 <ro...@shapeblue.com>
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 <iv...@shapeblue.com>
> *Sent:* Friday, June 18, 2021 20:36
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* Apache CloudStack Marketing <ma...@cloudstack.apache.org>;
> gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>;
> users@infra.apache.org <us...@infra.apache.org>
> *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 <an...@gmail.com> 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 <ro...@shapeblue.com>
> 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 <ro...@shapeblue.com>
> *Sent:* Thursday, June 3, 2021 14:30
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <
> gstein@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org
> <us...@infra.apache.org>
> *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 <gs...@gmail.com>
> *Sent:* Monday, May 31, 2021 18:18
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> *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ć
>
>
>
Re: Uploading Blog Post
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Rohit,
(moving legal-discuss to Bcc, this is really a technical discussion now)
On Wed, Jun 23, 2021 at 11:24 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...I'll test and PoC and share results here if we can do something like this;
>
> Fork www repo of a apache project
> Integrate with netlify for non-technical person who uses UI-editor to work/with save/create stuff
> Have a Github action that raises PR to the source repo when a commit is made
> ACS bot or authorised committer/PMC merge/publish the website ..
This sounds like a good plan to me. I think it's good for the PMC to
be in the loop for final publishing, and your setup might allow using
the "non-technical persons UI" for some parts of the website only
which is nice.
-Bertrand
Re: Uploading Blog Post
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Rohit,
(moving legal-discuss to Bcc, this is really a technical discussion now)
On Wed, Jun 23, 2021 at 11:24 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...I'll test and PoC and share results here if we can do something like this;
>
> Fork www repo of a apache project
> Integrate with netlify for non-technical person who uses UI-editor to work/with save/create stuff
> Have a Github action that raises PR to the source repo when a commit is made
> ACS bot or authorised committer/PMC merge/publish the website ..
This sounds like a good plan to me. I think it's good for the PMC to
be in the loop for final publishing, and your setup might allow using
the "non-technical persons UI" for some parts of the website only
which is nice.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi,
Thanks for the feedback Bertrand. Our first choice is still to explore WordPress, the use-case is that non-technical persons who don't have Github accounts or git-know-how should still be able to contribute to CloudStack website and blogs (mostly marketing activities hence discussed on the marketing@c.a.o list). The current practice and requirements make it less inclusive for non-technical people involved.
+1 yes of course, we want the problem fixed and I think if we're not getting support on WordPress or similar CMSs then I would certainly try git-based/backed CMS + document this on our project cwiki for other projects to benefit.
As an experiment, I just finished playing with netlify and looks like it may work as long as Ivet and others are happy with it. Netlify CMS requires certain access to Github repo and commit access as a Github account to allow for commits when pages are edited/saved. One thing I really liked so far is the netlify import/setup took me less than half-hour so far 🙂
The current CloudStack website is based on middleman which is slow, I tested it with github+netflify and found each commit/change took about 5mins to publish (which is in-line what we got here):
Repo: https://github.com/cloudstack/netlify-cloudstack-www
Test preview/publishing: https://happy-brattain-4bd9a5.netlify.app/
I also tested Hugo based on your suggestion which was super quick
Repo: https://github.com/rhtyd/test-hugo-netlify
Test: https://sleepy-wilson-181ad1.netlify.app/
Due to this limitation, I'll test and PoC and share results here if we can do something like this;
* Fork www repo of a apache project
* Integrate with netlify for non-technical person who uses UI-editor to work/with save/create stuff
* Have a Github action that raises PR to the source repo when a commit is made
* ACS bot or authorised committer/PMC merge/publish the website
Regards.
________________________________
From: Bertrand Delacretaz <bd...@apache.org>
Sent: Wednesday, June 23, 2021 13:51
To: Rohit Yadav <ro...@shapeblue.com>; users@infra.apache.org <us...@infra.apache.org>
Cc: legal-discuss@apache.org <le...@apache.org>; private@cloudstack.apache.org <pr...@cloudstack.apache.org>; marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hi,
On Wed, Jun 23, 2021 at 9:07 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...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...
I'm not from infra, but if you find a solution that can update an
ASF-hosted repository, using a client-side or a pass-through CMS
service I suppose that would work.
I see for example that Netlify CMS supports Hugo (
https://www.netlifycms.org/docs/hugo/ ) which several ASF projects use
for their websites, at least those:
https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
I haven't checked if that requires specific settings on the GitHub
side, which is where our infra might need to get involved.
If you pursue such an option I would suggest creating a place (wiki
page or such) where people from other projects can collaborate, as I
suppose others might be interested.
Note also the poor man's variant of that which is to edit Markdown
using the built-in GitHub editor - but I suppose you're looking for
something less "technical" for content authors. And also
https://blogs.apache.org/ which I think I already mentioned.
-Bertrand
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi,
Thanks for the feedback Bertrand. Our first choice is still to explore WordPress, the use-case is that non-technical persons who don't have Github accounts or git-know-how should still be able to contribute to CloudStack website and blogs (mostly marketing activities hence discussed on the marketing@c.a.o list). The current practice and requirements make it less inclusive for non-technical people involved.
+1 yes of course, we want the problem fixed and I think if we're not getting support on WordPress or similar CMSs then I would certainly try git-based/backed CMS + document this on our project cwiki for other projects to benefit.
As an experiment, I just finished playing with netlify and looks like it may work as long as Ivet and others are happy with it. Netlify CMS requires certain access to Github repo and commit access as a Github account to allow for commits when pages are edited/saved. One thing I really liked so far is the netlify import/setup took me less than half-hour so far 🙂
The current CloudStack website is based on middleman which is slow, I tested it with github+netflify and found each commit/change took about 5mins to publish (which is in-line what we got here):
Repo: https://github.com/cloudstack/netlify-cloudstack-www
Test preview/publishing: https://happy-brattain-4bd9a5.netlify.app/
I also tested Hugo based on your suggestion which was super quick
Repo: https://github.com/rhtyd/test-hugo-netlify
Test: https://sleepy-wilson-181ad1.netlify.app/
Due to this limitation, I'll test and PoC and share results here if we can do something like this;
* Fork www repo of a apache project
* Integrate with netlify for non-technical person who uses UI-editor to work/with save/create stuff
* Have a Github action that raises PR to the source repo when a commit is made
* ACS bot or authorised committer/PMC merge/publish the website
Regards.
________________________________
From: Bertrand Delacretaz <bd...@apache.org>
Sent: Wednesday, June 23, 2021 13:51
To: Rohit Yadav <ro...@shapeblue.com>; users@infra.apache.org <us...@infra.apache.org>
Cc: legal-discuss@apache.org <le...@apache.org>; private@cloudstack.apache.org <pr...@cloudstack.apache.org>; marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hi,
On Wed, Jun 23, 2021 at 9:07 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...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...
I'm not from infra, but if you find a solution that can update an
ASF-hosted repository, using a client-side or a pass-through CMS
service I suppose that would work.
I see for example that Netlify CMS supports Hugo (
https://www.netlifycms.org/docs/hugo/ ) which several ASF projects use
for their websites, at least those:
https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
I haven't checked if that requires specific settings on the GitHub
side, which is where our infra might need to get involved.
If you pursue such an option I would suggest creating a place (wiki
page or such) where people from other projects can collaborate, as I
suppose others might be interested.
Note also the poor man's variant of that which is to edit Markdown
using the built-in GitHub editor - but I suppose you're looking for
something less "technical" for content authors. And also
https://blogs.apache.org/ which I think I already mentioned.
-Bertrand
Re: Uploading Blog Post
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Wed, Jun 23, 2021 at 9:07 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...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...
I'm not from infra, but if you find a solution that can update an
ASF-hosted repository, using a client-side or a pass-through CMS
service I suppose that would work.
I see for example that Netlify CMS supports Hugo (
https://www.netlifycms.org/docs/hugo/ ) which several ASF projects use
for their websites, at least those:
https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
I haven't checked if that requires specific settings on the GitHub
side, which is where our infra might need to get involved.
If you pursue such an option I would suggest creating a place (wiki
page or such) where people from other projects can collaborate, as I
suppose others might be interested.
Note also the poor man's variant of that which is to edit Markdown
using the built-in GitHub editor - but I suppose you're looking for
something less "technical" for content authors. And also
https://blogs.apache.org/ which I think I already mentioned.
-Bertrand
Re: Uploading Blog Post
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
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 <ro...@shapeblue.com>
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 <iv...@shapeblue.com>
> *Sent:* Friday, June 18, 2021 20:36
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* Apache CloudStack Marketing <ma...@cloudstack.apache.org>;
> gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>;
> users@infra.apache.org <us...@infra.apache.org>
> *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 <an...@gmail.com> 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 <ro...@shapeblue.com>
> 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 <ro...@shapeblue.com>
> *Sent:* Thursday, June 3, 2021 14:30
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <
> gstein@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org
> <us...@infra.apache.org>
> *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 <gs...@gmail.com>
> *Sent:* Monday, May 31, 2021 18:18
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> *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ć
>
>
>
Re: Uploading Blog Post
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Wed, Jun 23, 2021 at 9:07 AM Rohit Yadav <ro...@shapeblue.com> wrote:
> ...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...
I'm not from infra, but if you find a solution that can update an
ASF-hosted repository, using a client-side or a pass-through CMS
service I suppose that would work.
I see for example that Netlify CMS supports Hugo (
https://www.netlifycms.org/docs/hugo/ ) which several ASF projects use
for their websites, at least those:
https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
I haven't checked if that requires specific settings on the GitHub
side, which is where our infra might need to get involved.
If you pursue such an option I would suggest creating a place (wiki
page or such) where people from other projects can collaborate, as I
suppose others might be interested.
Note also the poor man's variant of that which is to edit Markdown
using the built-in GitHub editor - but I suppose you're looking for
something less "technical" for content authors. And also
https://blogs.apache.org/ which I think I already mentioned.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
(+ 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<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 <iv...@shapeblue.com>
Sent: Friday, June 18, 2021 20:36
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org <us...@infra.apache.org>
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 <an...@gmail.com>> 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 <ro...@shapeblue.com>> 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 <ro...@shapeblue.com>>
*Sent:* Thursday, June 3, 2021 14:30
*To:* users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; Apache
CloudStack Marketing <ma...@cloudstack.apache.org>>; gstein@gmail.com<ma...@gmail.com> <
gstein@gmail.com<ma...@gmail.com>>; ged@apache.org<ma...@apache.org> <ge...@apache.org>>; users@infra.apache.org<ma...@infra.apache.org>
<us...@infra.apache.org>>
*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<http://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<http://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 <gs...@gmail.com>
*Sent:* Monday, May 31, 2021 18:18
*To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
*Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
*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ć
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
(+ 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<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 <iv...@shapeblue.com>
Sent: Friday, June 18, 2021 20:36
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org <us...@infra.apache.org>
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 <an...@gmail.com>> 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 <ro...@shapeblue.com>> 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 <ro...@shapeblue.com>>
*Sent:* Thursday, June 3, 2021 14:30
*To:* users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; Apache
CloudStack Marketing <ma...@cloudstack.apache.org>>; gstein@gmail.com<ma...@gmail.com> <
gstein@gmail.com<ma...@gmail.com>>; ged@apache.org<ma...@apache.org> <ge...@apache.org>>; users@infra.apache.org<ma...@infra.apache.org>
<us...@infra.apache.org>>
*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<http://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<http://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 <gs...@gmail.com>
*Sent:* Monday, May 31, 2021 18:18
*To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
*Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
*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ć
Re: Uploading Blog Post
Posted by Ivet Petrova <iv...@shapeblue.com>.
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 <an...@gmail.com>> 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 <ro...@shapeblue.com>> 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 <ro...@shapeblue.com>>
*Sent:* Thursday, June 3, 2021 14:30
*To:* users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; Apache
CloudStack Marketing <ma...@cloudstack.apache.org>>; gstein@gmail.com<ma...@gmail.com> <
gstein@gmail.com<ma...@gmail.com>>; ged@apache.org<ma...@apache.org> <ge...@apache.org>>; users@infra.apache.org<ma...@infra.apache.org>
<us...@infra.apache.org>>
*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<http://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<http://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 <gs...@gmail.com>
*Sent:* Monday, May 31, 2021 18:18
*To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
*Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
*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ć
Re: Uploading Blog Post
Posted by Ivet Petrova <iv...@shapeblue.com>.
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 <an...@gmail.com>> 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 <ro...@shapeblue.com>> 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 <ro...@shapeblue.com>>
*Sent:* Thursday, June 3, 2021 14:30
*To:* users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; Apache
CloudStack Marketing <ma...@cloudstack.apache.org>>; gstein@gmail.com<ma...@gmail.com> <
gstein@gmail.com<ma...@gmail.com>>; ged@apache.org<ma...@apache.org> <ge...@apache.org>>; users@infra.apache.org<ma...@infra.apache.org>
<us...@infra.apache.org>>
*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<http://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<http://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 <gs...@gmail.com>
*Sent:* Monday, May 31, 2021 18:18
*To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
*Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
*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ć
Re: Uploading Blog Post
Posted by Andrija Panic <an...@gmail.com>.
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 <ro...@shapeblue.com> 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 <ro...@shapeblue.com>
> *Sent:* Thursday, June 3, 2021 14:30
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <
> gstein@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org
> <us...@infra.apache.org>
> *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 <gs...@gmail.com>
> *Sent:* Monday, May 31, 2021 18:18
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> *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ć
Re: Uploading Blog Post
Posted by Andrija Panic <an...@gmail.com>.
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 <ro...@shapeblue.com> 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 <ro...@shapeblue.com>
> *Sent:* Thursday, June 3, 2021 14:30
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache
> CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <
> gstein@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org
> <us...@infra.apache.org>
> *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 <gs...@gmail.com>
> *Sent:* Monday, May 31, 2021 18:18
> *To:* users@cloudstack.apache.org <us...@cloudstack.apache.org>
> *Cc:* marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> *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ć
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <ro...@shapeblue.com>
Sent: Thursday, June 3, 2021 14:30
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org <us...@infra.apache.org>
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 <gs...@gmail.com>
Sent: Monday, May 31, 2021 18:18
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
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
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <ro...@shapeblue.com>
Sent: Thursday, June 3, 2021 14:30
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Apache CloudStack Marketing <ma...@cloudstack.apache.org>; gstein@gmail.com <gs...@gmail.com>; ged@apache.org <ge...@apache.org>; users@infra.apache.org <us...@infra.apache.org>
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 <gs...@gmail.com>
Sent: Monday, May 31, 2021 18:18
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
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
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <gs...@gmail.com>
Sent: Monday, May 31, 2021 18:18
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
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
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <gs...@gmail.com>
Sent: Monday, May 31, 2021 18:18
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
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
Re: Uploading Blog Post
Posted by Greg Stein <gs...@gmail.com>.
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
Re: Uploading Blog Post
Posted by Greg Stein <gs...@gmail.com>.
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
Re: Uploading Blog Post
Posted by "G.W. Haywood" <ge...@apache.org>.
Hi there,
On Mon, 31 May 2021, Rohit Yadav wrote:
> The Apache CloudStack (ACS) community is discussing options to migrate the project website and blog to Wordpress ...
> ...
> Thoughts, feedback ... ?
Just an observation, and this is by no means exhaustive:
$ grep -i 'http.*wordpress' ~/.../SECURITY_TRAINING/programme
https://arstechnica.com/information-technology/2020/09/hackers-are-exploiting-a-critical-flaw-affecting-350000-wordpress-sites/
https://arstechnica.com/information-technology/2020/02/hackers-exploit-critical-vulnerability-found-in-100000-wordpress-sites/
https://arstechnica.com/information-technology/2019/05/hackers-actively-exploit-wordpress-plugin-flaw-to-send-visitors-to-bad-sites/
https://arstechnica.com/information-technology/2019/03/two-serious-wordpress-plugin-vulnerabilities-are-being-exploited-in-the-wild/
https://www.theregister.co.uk/2018/11/07/woocommerce_hole_wordpress/
https://www.theregister.co.uk/2018/09/21/wordpress_flaws_attacked/
https://www.theregister.co.uk/2018/07/30/malvertising_wordpress/
https://arstechnica.com/information-technology/2015/09/active-malware-campaign-uses-thousands-of-wordpress-sites-to-infect-visitors/
If security has been discussed and people are OK with it I'll head back to my cave.
--
73,
Ged.
Re: Uploading Blog Post
Posted by "G.W. Haywood" <ge...@apache.org>.
Hi there,
On Mon, 31 May 2021, Rohit Yadav wrote:
> The Apache CloudStack (ACS) community is discussing options to migrate the project website and blog to Wordpress ...
> ...
> Thoughts, feedback ... ?
Just an observation, and this is by no means exhaustive:
$ grep -i 'http.*wordpress' ~/.../SECURITY_TRAINING/programme
https://arstechnica.com/information-technology/2020/09/hackers-are-exploiting-a-critical-flaw-affecting-350000-wordpress-sites/
https://arstechnica.com/information-technology/2020/02/hackers-exploit-critical-vulnerability-found-in-100000-wordpress-sites/
https://arstechnica.com/information-technology/2019/05/hackers-actively-exploit-wordpress-plugin-flaw-to-send-visitors-to-bad-sites/
https://arstechnica.com/information-technology/2019/03/two-serious-wordpress-plugin-vulnerabilities-are-being-exploited-in-the-wild/
https://www.theregister.co.uk/2018/11/07/woocommerce_hole_wordpress/
https://www.theregister.co.uk/2018/09/21/wordpress_flaws_attacked/
https://www.theregister.co.uk/2018/07/30/malvertising_wordpress/
https://arstechnica.com/information-technology/2015/09/active-malware-campaign-uses-thousands-of-wordpress-sites-to-infect-visitors/
If security has been discussed and people are OK with it I'll head back to my cave.
--
73,
Ged.
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
+ users@infra (kindly, reply all so your email is visible to participants on other mailing lists copied in this thread)
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. 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) 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.
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.
Thoughts, feedback, options? Thanks.
[1] https://markmail.org/message/6snytriinby3dgzv
[2] https://lists.apache.org/thread.html/d20daf9889e442bfe44e0908d303c3288e31f437101ca610f1f49eed@%3Clegal-discuss.apache.org%3E
[3] https://markmail.org/message/gqzrihyek4jjo4df
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Monday, May 31, 2021 15:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
All,
I've asked ASF infra again for the possibility and I got reply from Daniel/Humbedooh that:
"we can't move the main web site, primarily due to DNS restrictions
you could have something like blog.cloudstack.a.o"
So there is light at the end of the tunnel, I think most of the discussion was around blogs so we can get a Wordpress instance either hosted by ASF or donated/maintained that is under PMC control. I'm still exploring the possibility of ASF infra to repoint the cloudstack.a.o record with a CNAME/A record for an external service that runs Wordpress (or a VM hosted by ASF) - I'll keep everyone posted if that's feasible for them. If not, at least we can get our blog hosted as a Wordpress instance.
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Tuesday, May 18, 2021 17:41
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Giles Sirett <gi...@shapeblue.com>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
+ users@infra (kindly, reply all so your email is visible to participants on other mailing lists copied in this thread)
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. 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) 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.
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.
Thoughts, feedback, options? Thanks.
[1] https://markmail.org/message/6snytriinby3dgzv
[2] https://lists.apache.org/thread.html/d20daf9889e442bfe44e0908d303c3288e31f437101ca610f1f49eed@%3Clegal-discuss.apache.org%3E
[3] https://markmail.org/message/gqzrihyek4jjo4df
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Monday, May 31, 2021 15:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
All,
I've asked ASF infra again for the possibility and I got reply from Daniel/Humbedooh that:
"we can't move the main web site, primarily due to DNS restrictions
you could have something like blog.cloudstack.a.o"
So there is light at the end of the tunnel, I think most of the discussion was around blogs so we can get a Wordpress instance either hosted by ASF or donated/maintained that is under PMC control. I'm still exploring the possibility of ASF infra to repoint the cloudstack.a.o record with a CNAME/A record for an external service that runs Wordpress (or a VM hosted by ASF) - I'll keep everyone posted if that's feasible for them. If not, at least we can get our blog hosted as a Wordpress instance.
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Tuesday, May 18, 2021 17:41
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Giles Sirett <gi...@shapeblue.com>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
All,
I've asked ASF infra again for the possibility and I got reply from Daniel/Humbedooh that:
"we can't move the main web site, primarily due to DNS restrictions
you could have something like blog.cloudstack.a.o"
So there is light at the end of the tunnel, I think most of the discussion was around blogs so we can get a Wordpress instance either hosted by ASF or donated/maintained that is under PMC control. I'm still exploring the possibility of ASF infra to repoint the cloudstack.a.o record with a CNAME/A record for an external service that runs Wordpress (or a VM hosted by ASF) - I'll keep everyone posted if that's feasible for them. If not, at least we can get our blog hosted as a Wordpress instance.
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Tuesday, May 18, 2021 17:41
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Giles Sirett <gi...@shapeblue.com>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
All,
I've asked ASF infra again for the possibility and I got reply from Daniel/Humbedooh that:
"we can't move the main web site, primarily due to DNS restrictions
you could have something like blog.cloudstack.a.o"
So there is light at the end of the tunnel, I think most of the discussion was around blogs so we can get a Wordpress instance either hosted by ASF or donated/maintained that is under PMC control. I'm still exploring the possibility of ASF infra to repoint the cloudstack.a.o record with a CNAME/A record for an external service that runs Wordpress (or a VM hosted by ASF) - I'll keep everyone posted if that's feasible for them. If not, at least we can get our blog hosted as a Wordpress instance.
Regards.
________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Tuesday, May 18, 2021 17:41
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; Giles Sirett <gi...@shapeblue.com>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Rohit Yadav <ro...@shapeblue.com>.
The ASF infra prefers to have websites where changes are tracked by source code which is why most TLP websites use Git repos as source of truth. I don't know if there are other TLPs using non-Git based websites. I think Giles was leading that conversation @Giles Sirett<ma...@shapeblue.com> can you update if we made any progress? Thanks.
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Friday, May 14, 2021 11:45
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Ivet Petrova <iv...@shapeblue.com>.
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Ivet Petrova <iv...@shapeblue.com>.
Andrija,
You have a point for sure.
I can research for a good WP theme and suggest some wireframes for a new blog.
Then if the community is OK and approves it, we can implement it.
Something simple, clean and showing the identity of Apache CloudStack. Also with improved UX and option to show our news and achievements to the world.
Kind regards,
On 14 May 2021, at 1:11, Andrija Panic <an...@gmail.com>> wrote:
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Hey all,
Do we have any progress on this? Can I help somehow?
I have a new interview with Sven Vogel to upload and will need to torture
Rohit again to help to upload on the existing blog :)
Sorry Rohit!
Kind regards,
On 29 Apr 2021, at 11:31, Sven Vogel <S....@ewerk.com><mailto:
S.Vogel@ewerk.com<ma...@ewerk.com>>> wrote:
+1
__
Sven Vogel
Senior Manager Research and Development - Cloud and Infrastructure
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com<ma...@ewerk.com>
www.ewerk.com<http://www.ewerk.com><http://www.ewerk.com/>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Support:
+49 341 42649 555
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2018
ISAE 3402 Typ II Assessed
EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
https://www.linkedin.com/company/ewerk-group> | Xing<
https://www.xing.com/company/ewerk> | Twitter<
https://twitter.com/EWERK_Group> | Facebook<
https://de-de.facebook.com/EWERK.Group/>
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
Vielen Dank.
The contents of this e-mail (including any attachments) are confidential
and may be legally privileged. If you are not the intended recipient of
this e-mail, any disclosure, copying, distribution or use of its contents
is strictly prohibited, and you should please notify the sender immediately
and then delete it (including any attachments) from your system. Thank you.
Von: Nicolas Vazquez <Ni...@shapeblue.com><mailto:
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>>
Datum: Montag, 26. April 2021 um 22:22
An: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>, users@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>> <us...@cloudstack.apache.org><mailto:
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Betreff: Re: Uploading Blog Post
+1
Regards,
Nicolas Vazquez
________________________________
From: Andrija Panic <an...@gmail.com><mailto:
andrija.panic@gmail.com<ma...@gmail.com>>>
Sent: Monday, April 26, 2021 5:06 PM
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
Subject: Re: Uploading Blog Post
+1
On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <ga...@apache.org>
<ma...@apache.org>>
wrote:
+1
Investing in marketing, documentation, and usability is as important as
stability and code quality.
This looks like a good step in making it easier to share content for users
and devs while also improving the project marketability.
Best regards,
Gabriel
Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
+1
Kind regards
Giles
*From:* Sunando Bhattacharya <su...@indiqus.com><mailto:
sunando@indiqus.com<ma...@indiqus.com>>>
*Sent:* 26 April 2021 10:26
*To:* marketing@cloudstack.apache.org<ma...@cloudstack.apache.org><mailto:
marketing@cloudstack.apache.org<ma...@cloudstack.apache.org>>
*Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
*Subject:* Re: Uploading Blog Post
my 2 cents... we really need to have a more "content friendly" platform
for cloudstack where we can easily populate content that is current and
relevant. Hosting on WordPress or Webflow really would make life easy for
content managers. This will also enable us to attract more users to the
community and grow it.
Best,
Sunando
www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com><http://www.indiqus.com>
On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <gi...@shapeblue.com>
<ma...@shapeblue.com>>
wrote:
[discuss]
I would be fully supportive of this - as Andrija says: we should have
done this years ago. In fact, we have had this discussion a number of
times over the years. For example [1]
Every time its raised, most people seem to be +1 on having a site that
can be easily maintained/ managed with tools that are familiar with the
more marketing focussed people in our community (i.e. some sort of CMS) .
However, every time, the initiative has fizzled out because of the "belief"
that top level project websites HAVE to be hosted on Apache infra and have
to be static HTML. We then get into long discussions about everybody's
favourite types of HTML generator tools - most of which immediately
switch off folks like Ivet - who (without putting words into their mouths)
just want a wordpress/jupal/etc site that is easy to manage & update
I spoke to some of the infra guys at Apachecon NA 2019. They seemed
informally open to the idea of a project hosting their website on something
like wordpress.com<http://wordpress.com><http://wordpress.com>. They referred me to a legal
discussion that theyd
had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
site and it doesn’t have to be static HTML.
AFAIK, I don’t think that ever became policy, but the key message is, as
long as certain requirements are met there seems (or rather seemed at the
time) to be no problem with doing this
So, the question needs to be: as long as the details can be figured, and
infra/policy allows it, is there any remaining objection to rebuilding our
website on something like wordpress ?
If there is no strong objection here, I'd be happy to reach out to infra
to check that their thoughts from 2 years ago remain the same and what
is/is not OK
I think that they'd want to see a vote from this community - but lets
see the art of the possible first.
Thoughts ?
Kind regards
Giles
giles.sirett@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com><http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>>
Sent: 25 April 2021 22:04
To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>>
Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
+1, but..
If that would be that easily doable, we should surely migrate ages ago -
there are certain limits from the ASF itself, I don't know all the details
- but it's the same story for the main web site - old, ugly, unfriendly -
make's you want to avoid it... but, there you go... it's always good to try
to move forward.
On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>>
wrote:
Perhaps one good idea is migrating the blog to WordPress.
It is easy to use and operate and supports different levels of access.
PMC members can be administrators, and there can be just Authors and
Editors in addition.
Kind regards,
On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>>
wrote:
FYI - published on behalf of Ivet here:
https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
rascher as only committers are allowed access to publish on the Apache
CloudStack blog (something that could be discussed and fixed in
future).
Regards.
________________________________
From: Ivet Petrova <iv...@shapeblue.com>
Sent: Monday, April 19, 2021 12:09
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
Subject: Re: Uploading Blog Post
Hello again and Happy Monday Everyone,
Once again - can somebody give me some guidance on this?
Kind regards,
ivet.petrova@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
<mailto:
ivet.petrova@shapeblue.com>> wrote:
Hi,
Can somebody help me on how a new blog posts can be uploaded on the
CloudStack blog?
Is there any backend which is used, or only code?
Thanks a lot on advance!
Kind regards,
ivet.petrova@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair (CloudStack VP)
The Apache Software Foundation
https://www.apache.org/
https://cloudstack.apache.org/
--
Andrija Panić
Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
http://www.shapeblue.com/>>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
--
Andrija Panić
Re: Uploading Blog Post
Posted by Andrija Panic <an...@gmail.com>.
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>
wrote:
> Hey all,
>
> Do we have any progress on this? Can I help somehow?
>
> I have a new interview with Sven Vogel to upload and will need to torture
> Rohit again to help to upload on the existing blog :)
> Sorry Rohit!
>
> Kind regards,
>
>
>
>
> On 29 Apr 2021, at 11:31, Sven Vogel <S.Vogel@ewerk.com<mailto:
> S.Vogel@ewerk.com>> wrote:
>
> +1
>
>
> __
>
> Sven Vogel
> Senior Manager Research and Development - Cloud and Infrastructure
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com<ma...@ewerk.com>
> www.ewerk.com<http://www.ewerk.com/>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Support:
> +49 341 42649 555
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2018
>
> ISAE 3402 Typ II Assessed
>
> EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> https://www.linkedin.com/company/ewerk-group> | Xing<
> https://www.xing.com/company/ewerk> | Twitter<
> https://twitter.com/EWERK_Group> | Facebook<
> https://de-de.facebook.com/EWERK.Group/>
>
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> Von: Nicolas Vazquez <Nicolas.Vazquez@shapeblue.com<mailto:
> Nicolas.Vazquez@shapeblue.com>>
> Datum: Montag, 26. April 2021 um 22:22
> An: Apache CloudStack Marketing <marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>>, users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org> <users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>
> Betreff: Re: Uploading Blog Post
> +1
>
> Regards,
> Nicolas Vazquez
> ________________________________
> From: Andrija Panic <andrija.panic@gmail.com<mailto:
> andrija.panic@gmail.com>>
> Sent: Monday, April 26, 2021 5:06 PM
> To: Apache CloudStack Marketing <marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>>
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: Re: Uploading Blog Post
>
> +1
>
> On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <gabriel@apache.org
> <ma...@apache.org>>
> wrote:
>
> +1
>
> Investing in marketing, documentation, and usability is as important as
> stability and code quality.
> This looks like a good step in making it easier to share content for users
> and devs while also improving the project marketability.
>
> Best regards,
> Gabriel
>
> Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
> giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
>
> +1
>
>
>
> Kind regards
>
> Giles
>
>
>
>
>
>
>
>
> *From:* Sunando Bhattacharya <sunando@indiqus.com<mailto:
> sunando@indiqus.com>>
> *Sent:* 26 April 2021 10:26
> *To:* marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>
> *Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> *Subject:* Re: Uploading Blog Post
>
>
>
> my 2 cents... we really need to have a more "content friendly" platform
> for cloudstack where we can easily populate content that is current and
> relevant. Hosting on WordPress or Webflow really would make life easy for
> content managers. This will also enable us to attract more users to the
> community and grow it.
>
>
> Best,
>
>
>
> Sunando
>
> www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com>
>
>
>
>
>
>
>
> On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <giles.sirett@shapeblue.com
> <ma...@shapeblue.com>>
> wrote:
>
> [discuss]
> I would be fully supportive of this - as Andrija says: we should have
> done this years ago. In fact, we have had this discussion a number of
> times over the years. For example [1]
>
> Every time its raised, most people seem to be +1 on having a site that
> can be easily maintained/ managed with tools that are familiar with the
> more marketing focussed people in our community (i.e. some sort of CMS) .
> However, every time, the initiative has fizzled out because of the "belief"
> that top level project websites HAVE to be hosted on Apache infra and have
> to be static HTML. We then get into long discussions about everybody's
> favourite types of HTML generator tools - most of which immediately
> switch off folks like Ivet - who (without putting words into their mouths)
> just want a wordpress/jupal/etc site that is easy to manage & update
>
> I spoke to some of the infra guys at Apachecon NA 2019. They seemed
> informally open to the idea of a project hosting their website on something
> like wordpress.com<http://wordpress.com>. They referred me to a legal
> discussion that theyd
> had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
> site and it doesn’t have to be static HTML.
>
> AFAIK, I don’t think that ever became policy, but the key message is, as
> long as certain requirements are met there seems (or rather seemed at the
> time) to be no problem with doing this
>
> So, the question needs to be: as long as the details can be figured, and
> infra/policy allows it, is there any remaining objection to rebuilding our
> website on something like wordpress ?
>
> If there is no strong objection here, I'd be happy to reach out to infra
> to check that their thoughts from 2 years ago remain the same and what
> is/is not OK
>
> I think that they'd want to see a vote from this community - but lets
> see the art of the possible first.
>
>
> Thoughts ?
>
>
>
> Kind regards
> Giles
>
> giles.sirett@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 25 April 2021 22:04
> To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
> Cc: users@cloudstack.apache.org
> Subject: Re: Uploading Blog Post
>
> +1, but..
>
> If that would be that easily doable, we should surely migrate ages ago -
> there are certain limits from the ASF itself, I don't know all the details
> - but it's the same story for the main web site - old, ugly, unfriendly -
> make's you want to avoid it... but, there you go... it's always good to try
> to move forward.
>
>
> On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>
> wrote:
>
> Perhaps one good idea is migrating the blog to WordPress.
> It is easy to use and operate and supports different levels of access.
> PMC members can be administrators, and there can be just Authors and
> Editors in addition.
>
> Kind regards,
>
>
>
>
>
>
> On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>
> wrote:
>
> FYI - published on behalf of Ivet here:
> https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
> rascher as only committers are allowed access to publish on the Apache
> CloudStack blog (something that could be discussed and fixed in
> future).
>
> Regards.
>
>
> ________________________________
> From: Ivet Petrova <iv...@shapeblue.com>
> Sent: Monday, April 19, 2021 12:09
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> Subject: Re: Uploading Blog Post
>
> Hello again and Happy Monday Everyone,
>
> Once again - can somebody give me some guidance on this?
>
> Kind regards,
>
>
> ivet.petrova@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
> On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
> <mailto:
> ivet.petrova@shapeblue.com>> wrote:
>
> Hi,
>
> Can somebody help me on how a new blog posts can be uploaded on the
> CloudStack blog?
> Is there any backend which is used, or only code?
>
> Thanks a lot on advance!
>
> Kind regards,
>
>
> ivet.petrova@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
>
>
>
> --
>
> Andrija Panić
>
>
>
> --
> Gabriel Beims Bräscher
> Apache CloudStack PMC Chair (CloudStack VP)
> The Apache Software Foundation
> https://www.apache.org/
> https://cloudstack.apache.org/
>
>
>
> --
>
> Andrija Panić
>
> Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
> http://www.shapeblue.com/>>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
--
Andrija Panić
Re: Uploading Blog Post
Posted by Andrija Panic <an...@gmail.com>.
Ivet,
I will be harsh probably if I say that nobody reads that blog page anyways,
so your effort is in vain, atm. Up to you. Every new ACS release asks for
updating the same blog page, and that is complete pain in the neck, almost
a suicide action.
Let's better push forward the ACS website/blog to a
manageable-by-normal-people CMS platform.
Just muy 2 cents.
Best,
On Thu, 13 May 2021 at 14:20, Ivet Petrova <iv...@shapeblue.com>
wrote:
> Hey all,
>
> Do we have any progress on this? Can I help somehow?
>
> I have a new interview with Sven Vogel to upload and will need to torture
> Rohit again to help to upload on the existing blog :)
> Sorry Rohit!
>
> Kind regards,
>
>
>
>
> On 29 Apr 2021, at 11:31, Sven Vogel <S.Vogel@ewerk.com<mailto:
> S.Vogel@ewerk.com>> wrote:
>
> +1
>
>
> __
>
> Sven Vogel
> Senior Manager Research and Development - Cloud and Infrastructure
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com<ma...@ewerk.com>
> www.ewerk.com<http://www.ewerk.com/>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Support:
> +49 341 42649 555
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2018
>
> ISAE 3402 Typ II Assessed
>
> EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> https://www.linkedin.com/company/ewerk-group> | Xing<
> https://www.xing.com/company/ewerk> | Twitter<
> https://twitter.com/EWERK_Group> | Facebook<
> https://de-de.facebook.com/EWERK.Group/>
>
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> Von: Nicolas Vazquez <Nicolas.Vazquez@shapeblue.com<mailto:
> Nicolas.Vazquez@shapeblue.com>>
> Datum: Montag, 26. April 2021 um 22:22
> An: Apache CloudStack Marketing <marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>>, users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org> <users@cloudstack.apache.org<mailto:
> users@cloudstack.apache.org>>
> Betreff: Re: Uploading Blog Post
> +1
>
> Regards,
> Nicolas Vazquez
> ________________________________
> From: Andrija Panic <andrija.panic@gmail.com<mailto:
> andrija.panic@gmail.com>>
> Sent: Monday, April 26, 2021 5:06 PM
> To: Apache CloudStack Marketing <marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>>
> Cc: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: Re: Uploading Blog Post
>
> +1
>
> On Mon, 26 Apr 2021 at 17:02, Gabriel Beims Bräscher <gabriel@apache.org
> <ma...@apache.org>>
> wrote:
>
> +1
>
> Investing in marketing, documentation, and usability is as important as
> stability and code quality.
> This looks like a good step in making it easier to share content for users
> and devs while also improving the project marketability.
>
> Best regards,
> Gabriel
>
> Em seg., 26 de abr. de 2021 às 11:11, Giles Sirett <
> giles.sirett@shapeblue.com<ma...@shapeblue.com>> escreveu:
>
> +1
>
>
>
> Kind regards
>
> Giles
>
>
>
>
>
>
>
>
> *From:* Sunando Bhattacharya <sunando@indiqus.com<mailto:
> sunando@indiqus.com>>
> *Sent:* 26 April 2021 10:26
> *To:* marketing@cloudstack.apache.org<mailto:
> marketing@cloudstack.apache.org>
> *Cc:* users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> *Subject:* Re: Uploading Blog Post
>
>
>
> my 2 cents... we really need to have a more "content friendly" platform
> for cloudstack where we can easily populate content that is current and
> relevant. Hosting on WordPress or Webflow really would make life easy for
> content managers. This will also enable us to attract more users to the
> community and grow it.
>
>
> Best,
>
>
>
> Sunando
>
> www.indiqus.com<http://www.indiqus.com><http://www.indiqus.com>
>
>
>
>
>
>
>
> On Mon, Apr 26, 2021 at 2:22 PM Giles Sirett <giles.sirett@shapeblue.com
> <ma...@shapeblue.com>>
> wrote:
>
> [discuss]
> I would be fully supportive of this - as Andrija says: we should have
> done this years ago. In fact, we have had this discussion a number of
> times over the years. For example [1]
>
> Every time its raised, most people seem to be +1 on having a site that
> can be easily maintained/ managed with tools that are familiar with the
> more marketing focussed people in our community (i.e. some sort of CMS) .
> However, every time, the initiative has fizzled out because of the "belief"
> that top level project websites HAVE to be hosted on Apache infra and have
> to be static HTML. We then get into long discussions about everybody's
> favourite types of HTML generator tools - most of which immediately
> switch off folks like Ivet - who (without putting words into their mouths)
> just want a wordpress/jupal/etc site that is easy to manage & update
>
> I spoke to some of the infra guys at Apachecon NA 2019. They seemed
> informally open to the idea of a project hosting their website on something
> like wordpress.com<http://wordpress.com>. They referred me to a legal
> discussion that theyd
> had [2]. Which, in summary, says - yes, you can use a 3rd party to host a
> site and it doesn’t have to be static HTML.
>
> AFAIK, I don’t think that ever became policy, but the key message is, as
> long as certain requirements are met there seems (or rather seemed at the
> time) to be no problem with doing this
>
> So, the question needs to be: as long as the details can be figured, and
> infra/policy allows it, is there any remaining objection to rebuilding our
> website on something like wordpress ?
>
> If there is no strong objection here, I'd be happy to reach out to infra
> to check that their thoughts from 2 years ago remain the same and what
> is/is not OK
>
> I think that they'd want to see a vote from this community - but lets
> see the art of the possible first.
>
>
> Thoughts ?
>
>
>
> Kind regards
> Giles
>
> giles.sirett@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 25 April 2021 22:04
> To: Apache CloudStack Marketing <ma...@cloudstack.apache.org>
> Cc: users@cloudstack.apache.org
> Subject: Re: Uploading Blog Post
>
> +1, but..
>
> If that would be that easily doable, we should surely migrate ages ago -
> there are certain limits from the ASF itself, I don't know all the details
> - but it's the same story for the main web site - old, ugly, unfriendly -
> make's you want to avoid it... but, there you go... it's always good to try
> to move forward.
>
>
> On Fri, 23 Apr 2021 at 12:12, Ivet Petrova <iv...@shapeblue.com>
> wrote:
>
> Perhaps one good idea is migrating the blog to WordPress.
> It is easy to use and operate and supports different levels of access.
> PMC members can be administrators, and there can be just Authors and
> Editors in addition.
>
> Kind regards,
>
>
>
>
>
>
> On 23 Apr 2021, at 12:57, Rohit Yadav <ro...@shapeblue.com>
> wrote:
>
> FYI - published on behalf of Ivet here:
> https://blogs.apache.org/cloudstack/entry/meet-the-community-gabriel-b
> rascher as only committers are allowed access to publish on the Apache
> CloudStack blog (something that could be discussed and fixed in
> future).
>
> Regards.
>
>
> ________________________________
> From: Ivet Petrova <iv...@shapeblue.com>
> Sent: Monday, April 19, 2021 12:09
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Cc: marketing@cloudstack.apache.org <ma...@cloudstack.apache.org>
> Subject: Re: Uploading Blog Post
>
> Hello again and Happy Monday Everyone,
>
> Once again - can somebody give me some guidance on this?
>
> Kind regards,
>
>
> ivet.petrova@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
> On 9 Apr 2021, at 12:48, Ivet Petrova <ivet.petrova@shapeblue.com
> <mailto:
> ivet.petrova@shapeblue.com>> wrote:
>
> Hi,
>
> Can somebody help me on how a new blog posts can be uploaded on the
> CloudStack blog?
> Is there any backend which is used, or only code?
>
> Thanks a lot on advance!
>
> Kind regards,
>
>
> ivet.petrova@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
>
>
>
> --
>
> Andrija Panić
>
>
>
> --
> Gabriel Beims Bräscher
> Apache CloudStack PMC Chair (CloudStack VP)
> The Apache Software Foundation
> https://www.apache.org/
> https://cloudstack.apache.org/
>
>
>
> --
>
> Andrija Panić
>
> Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<
> http://www.shapeblue.com/>>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
--
Andrija Panić