You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by Duru Can Celasun <ca...@dcc.im> on 2020/10/03 16:10:11 UTC
Re: Your project's website
Hi Andrew,
Any news on this? How should we proceed?
Cheers,
Can
On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> Hi Andrew,
>
> Sorry for the late response. Last year I started working on a migration
> from Apache CMS to "read the docs" [1] but I never got a chance to
> finish it.
>
> It's mostly complete, but we could definitely use some INFRA help to
> get it over the finish line.
>
> Would it be possible to have a thrift-website repo on Github and have
> it deployed via Travis?
>
> The linked issue has build instructions but I'd be happy to make
> changes if needed.
>
> Please let me how you'd like to proceed.
>
> Cheers,
> Can
>
> [1]
> https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
>
> On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > Hi:
> >
> > I wrote to you two weeks ago about your project website, but have not seen
> > a response. Whom should I contact directly? I am trying to see whether your
> > project still uses the Apache CMS and, if so, what your plans are to
> > migrate off it.
> >
> > Thanks in advance for your help.
> >
> > Andrew
> >
> > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org> wrote:
> >
> > > Hi:
> > >
> > > I am part of the Infrastructure team, and am writing to ask whether your
> > > project is still using the Apache CMS for your project website. As you
> > > know, the CMS is reaching end-of-life, and we need projects to move their
> > > websites onto a different option within the next few weeks.
> > >
> > > There are several alternatives available, including those listed on this
> > > page [1] on managing project websites. Infra is assembling a Wiki page [2]
> > > on migrating a website from the CMS, and is looking forward to helping
> > > projects with this transition.
> > >
> > > Please let me know whether your site is still on the Apache CMS and, if
> > > so, who will be the project point-of-contact with Infra for the migration.
> > >
> > > Thank you!
> > >
> > >
> > >
> > >
> > > [1] https://infra.apache.org/project-site.html
> > >
> > > [2]
> > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andreww@apache.org
> > >
> > >
> > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
> > > www.avast.com
> > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andreww@apache.org
> >
>
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
I think the README covers pretty much everything you're probably looking for.
https://github.com/apache/thrift-website/blob/main/README.md
Specifically, it contains:
1. instructions on how to set up your local environment with all the
prerequisites
2. specific commands to run to test locally
3. explanation about automatic staging of stuff committed to the main
branch (so you never actually *need* to build locally)
4. instructions on how to publish the staged site to production
On Sat, Oct 31, 2020 at 5:41 AM Jens Geyer <je...@apache.org> wrote:
>
> Hi,
>
> Good work!
>
> Removing the sitemap until we don't have an replacement in place seems not
> like a great idea to me. Right, it does look pretty strange now as it is,
> but there are certain pages that are either only linked though it, or the
> links to these pages are so well-hidden it makes one preferring going
> through the sitemap instead to find it quickly.
>
> Question: Is there any "executive summary" available what I have to install
> and do to build the whole thing?
>
> Have fun,
> JensG
>
>
> -----Ursprüngliche Nachricht-----
> From: Christopher
> Sent: Saturday, October 31, 2020 1:33 AM
> To: Duru Can Celasun
> Cc: dev@thrift.apache.org ; Mario Emmenlauer
> Subject: Re: Your project's website
>
> It looks like it's published now. Nice. (probably an INFRA person
> watching this thread. :)
> If so, they might want to fix the default branch in GitBox, so that
> the following works correctly:
> git remote set-head origin -a
> (assuming origin points to
> https://gitbox.apache.org/repos/asf/thrift-website)
>
> On Fri, Oct 30, 2020 at 8:19 PM Christopher <ct...@apache.org> wrote:
> >
> > Everything looks okay to me on the staging site. I see you pushed the
> > asf-staging branch to the asf-site branch, but the main site didn't
> > publish.
> > I think you will have to put in a ticket with INFRA to disable CMS
> > now, and use the asf-site branch from this repo.
> >
> > Once it works, you should be able to tell that the site is drawing
> > from git, and not CMS, because:
> >
> > 1. I added "Accumulo" to the "Other Apache projects using Thrift"
> > section of the about page, and
> > 2. The new .htaccess file should force a redirect from
> > http://thrift.apache.org to https://thrift.apache.org
> >
> > I can see both of these on the staging site, but not yet on the main
> > site. So, INFRA will probably need to switch you over.
> >
> > Follow-on things:
> >
> > 1. You can delete all the CMS website stuff in SVN now
> > (https://svn.apache.org/repos/asf/thrift/), and replace it with a
> > README saying you switched everything to git. The SVN history will
> > still be preserved, but removing it will be less confusing.
> > 2. I do recommend that in future, you find a way to remove the
> > "snippets" copied from the main repo. That part will be hard to
> > maintain in future, and it's probably better to just link to the
> > tutorial stuff in the main repo (or move the tutorials to the website
> > and remove them from the main repo). It also requires a live
> > connection to test the site locally (and might even trigger rate
> > limiting for unauthenticated users), so it's not very reliable.
> > 3. You can probably just remove the sitemap page... it's not very
> > useful, and doesn't look very good right now. If you want a "standard"
> > sitemap.xml, there's Jekyll plugins for automatically generating that,
> > but the HTML one isn't that useful.
> > 4. Some of the documentation on the pages still refers to the
> > lib/paths.pm Perl stuff from CMS. I didn't update those developer
> > docs, but they can probably be removed, since the thrift-website repo
> > now has a good README of its own.
> >
> > Christopher
> >
> > On Fri, Oct 30, 2020 at 6:53 AM Duru Can Celasun <dc...@apache.org>
> > wrote:
> > >
> > > All right, this should be all done now.
> > >
> > > https://thrift.staged.apache.org/
> > > https://thrift.apache.org/
> > >
> > > I've pushed all branches to the new repo [1] and it seems the Github
> > > Action and asf.yml are both working correctly,
> > >
> > > Christopher, thank you once again for working on this. Please take a
> > > look and let me know if anything is wrong or missing.
> > >
> > > Best,
> > > Can
> > >
> > > [1] https://github.com/apache/thrift-website
> > >
> > > On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
> > > >
> > > > Hi guys,
> > > >
> > > > thanks for the great move forward! Can you send a link to the page
> > > > as soon as something can be seen? I'm still pretty new to the project
> > > > and might have missed if you sent it already, sorry for that :-(
> > > >
> > > > All the best, Mario
> > > >
> > > >
> > > > On 30.10.20 11:19, Duru Can Celasun wrote:
> > > > > I've created the repo using self-service
> > > > > https://github.com/apache/thrift-website
> > > > >
> > > > > Once I get write access (I'm assuming it's automated) I'll push all
> > > > > 3 branches and we can take it from there.
> > > > >
> > > > > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> > > > >> I finished the syntax highlighting, but didn't get to the
> > > > >> sitemap...
> > > > >> I'm not sure it's all that important.
> > > > >>
> > > > >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once
> > > > >> you
> > > > >> get the official repo created, all three branches should be moved
> > > > >> over, as-is, in order for everything to work smoothly. You may need
> > > > >> to
> > > > >> ask INFRA to set the "main" branch as the default branch, though.
> > > > >>
> > > > >> If everything is working correctly, you should see the site at
> > > > >> https://thrift.staged.apache.org ; if that is working correctly,
> > > > >> then
> > > > >> you can use the _scripts/publish.sh script to push the staging
> > > > >> branch
> > > > >> to the publish branch (see README for explanation), and then you'll
> > > > >> be
> > > > >> completely off of CMS and can do whatever you want after that. :)
> > > > >>
> > > > >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun
> > > > >> <dc...@apache.org> wrote:
> > > > >>>
> > > > >>> This looks excellent Christopher, thank you for working on this so
> > > > >>> quickly! I'll see if I can create an official repo tomorrow and we
> > > > >>> can take it from there.
> > > > >>>
> > > >
>
Re: Your project's website
Posted by Jens Geyer <je...@apache.org>.
Hi,
Good work!
Removing the sitemap until we don't have an replacement in place seems not
like a great idea to me. Right, it does look pretty strange now as it is,
but there are certain pages that are either only linked though it, or the
links to these pages are so well-hidden it makes one preferring going
through the sitemap instead to find it quickly.
Question: Is there any "executive summary" available what I have to install
and do to build the whole thing?
Have fun,
JensG
-----Ursprüngliche Nachricht-----
From: Christopher
Sent: Saturday, October 31, 2020 1:33 AM
To: Duru Can Celasun
Cc: dev@thrift.apache.org ; Mario Emmenlauer
Subject: Re: Your project's website
It looks like it's published now. Nice. (probably an INFRA person
watching this thread. :)
If so, they might want to fix the default branch in GitBox, so that
the following works correctly:
git remote set-head origin -a
(assuming origin points to
https://gitbox.apache.org/repos/asf/thrift-website)
On Fri, Oct 30, 2020 at 8:19 PM Christopher <ct...@apache.org> wrote:
>
> Everything looks okay to me on the staging site. I see you pushed the
> asf-staging branch to the asf-site branch, but the main site didn't
> publish.
> I think you will have to put in a ticket with INFRA to disable CMS
> now, and use the asf-site branch from this repo.
>
> Once it works, you should be able to tell that the site is drawing
> from git, and not CMS, because:
>
> 1. I added "Accumulo" to the "Other Apache projects using Thrift"
> section of the about page, and
> 2. The new .htaccess file should force a redirect from
> http://thrift.apache.org to https://thrift.apache.org
>
> I can see both of these on the staging site, but not yet on the main
> site. So, INFRA will probably need to switch you over.
>
> Follow-on things:
>
> 1. You can delete all the CMS website stuff in SVN now
> (https://svn.apache.org/repos/asf/thrift/), and replace it with a
> README saying you switched everything to git. The SVN history will
> still be preserved, but removing it will be less confusing.
> 2. I do recommend that in future, you find a way to remove the
> "snippets" copied from the main repo. That part will be hard to
> maintain in future, and it's probably better to just link to the
> tutorial stuff in the main repo (or move the tutorials to the website
> and remove them from the main repo). It also requires a live
> connection to test the site locally (and might even trigger rate
> limiting for unauthenticated users), so it's not very reliable.
> 3. You can probably just remove the sitemap page... it's not very
> useful, and doesn't look very good right now. If you want a "standard"
> sitemap.xml, there's Jekyll plugins for automatically generating that,
> but the HTML one isn't that useful.
> 4. Some of the documentation on the pages still refers to the
> lib/paths.pm Perl stuff from CMS. I didn't update those developer
> docs, but they can probably be removed, since the thrift-website repo
> now has a good README of its own.
>
> Christopher
>
> On Fri, Oct 30, 2020 at 6:53 AM Duru Can Celasun <dc...@apache.org>
> wrote:
> >
> > All right, this should be all done now.
> >
> > https://thrift.staged.apache.org/
> > https://thrift.apache.org/
> >
> > I've pushed all branches to the new repo [1] and it seems the Github
> > Action and asf.yml are both working correctly,
> >
> > Christopher, thank you once again for working on this. Please take a
> > look and let me know if anything is wrong or missing.
> >
> > Best,
> > Can
> >
> > [1] https://github.com/apache/thrift-website
> >
> > On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
> > >
> > > Hi guys,
> > >
> > > thanks for the great move forward! Can you send a link to the page
> > > as soon as something can be seen? I'm still pretty new to the project
> > > and might have missed if you sent it already, sorry for that :-(
> > >
> > > All the best, Mario
> > >
> > >
> > > On 30.10.20 11:19, Duru Can Celasun wrote:
> > > > I've created the repo using self-service
> > > > https://github.com/apache/thrift-website
> > > >
> > > > Once I get write access (I'm assuming it's automated) I'll push all
> > > > 3 branches and we can take it from there.
> > > >
> > > > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> > > >> I finished the syntax highlighting, but didn't get to the
> > > >> sitemap...
> > > >> I'm not sure it's all that important.
> > > >>
> > > >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once
> > > >> you
> > > >> get the official repo created, all three branches should be moved
> > > >> over, as-is, in order for everything to work smoothly. You may need
> > > >> to
> > > >> ask INFRA to set the "main" branch as the default branch, though.
> > > >>
> > > >> If everything is working correctly, you should see the site at
> > > >> https://thrift.staged.apache.org ; if that is working correctly,
> > > >> then
> > > >> you can use the _scripts/publish.sh script to push the staging
> > > >> branch
> > > >> to the publish branch (see README for explanation), and then you'll
> > > >> be
> > > >> completely off of CMS and can do whatever you want after that. :)
> > > >>
> > > >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun
> > > >> <dc...@apache.org> wrote:
> > > >>>
> > > >>> This looks excellent Christopher, thank you for working on this so
> > > >>> quickly! I'll see if I can create an official repo tomorrow and we
> > > >>> can take it from there.
> > > >>>
> > >
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
It looks like it's published now. Nice. (probably an INFRA person
watching this thread. :)
If so, they might want to fix the default branch in GitBox, so that
the following works correctly:
git remote set-head origin -a
(assuming origin points to https://gitbox.apache.org/repos/asf/thrift-website)
On Fri, Oct 30, 2020 at 8:19 PM Christopher <ct...@apache.org> wrote:
>
> Everything looks okay to me on the staging site. I see you pushed the
> asf-staging branch to the asf-site branch, but the main site didn't
> publish.
> I think you will have to put in a ticket with INFRA to disable CMS
> now, and use the asf-site branch from this repo.
>
> Once it works, you should be able to tell that the site is drawing
> from git, and not CMS, because:
>
> 1. I added "Accumulo" to the "Other Apache projects using Thrift"
> section of the about page, and
> 2. The new .htaccess file should force a redirect from
> http://thrift.apache.org to https://thrift.apache.org
>
> I can see both of these on the staging site, but not yet on the main
> site. So, INFRA will probably need to switch you over.
>
> Follow-on things:
>
> 1. You can delete all the CMS website stuff in SVN now
> (https://svn.apache.org/repos/asf/thrift/), and replace it with a
> README saying you switched everything to git. The SVN history will
> still be preserved, but removing it will be less confusing.
> 2. I do recommend that in future, you find a way to remove the
> "snippets" copied from the main repo. That part will be hard to
> maintain in future, and it's probably better to just link to the
> tutorial stuff in the main repo (or move the tutorials to the website
> and remove them from the main repo). It also requires a live
> connection to test the site locally (and might even trigger rate
> limiting for unauthenticated users), so it's not very reliable.
> 3. You can probably just remove the sitemap page... it's not very
> useful, and doesn't look very good right now. If you want a "standard"
> sitemap.xml, there's Jekyll plugins for automatically generating that,
> but the HTML one isn't that useful.
> 4. Some of the documentation on the pages still refers to the
> lib/paths.pm Perl stuff from CMS. I didn't update those developer
> docs, but they can probably be removed, since the thrift-website repo
> now has a good README of its own.
>
> Christopher
>
> On Fri, Oct 30, 2020 at 6:53 AM Duru Can Celasun <dc...@apache.org> wrote:
> >
> > All right, this should be all done now.
> >
> > https://thrift.staged.apache.org/
> > https://thrift.apache.org/
> >
> > I've pushed all branches to the new repo [1] and it seems the Github Action and asf.yml are both working correctly,
> >
> > Christopher, thank you once again for working on this. Please take a look and let me know if anything is wrong or missing.
> >
> > Best,
> > Can
> >
> > [1] https://github.com/apache/thrift-website
> >
> > On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
> > >
> > > Hi guys,
> > >
> > > thanks for the great move forward! Can you send a link to the page
> > > as soon as something can be seen? I'm still pretty new to the project
> > > and might have missed if you sent it already, sorry for that :-(
> > >
> > > All the best, Mario
> > >
> > >
> > > On 30.10.20 11:19, Duru Can Celasun wrote:
> > > > I've created the repo using self-service https://github.com/apache/thrift-website
> > > >
> > > > Once I get write access (I'm assuming it's automated) I'll push all 3 branches and we can take it from there.
> > > >
> > > > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> > > >> I finished the syntax highlighting, but didn't get to the sitemap...
> > > >> I'm not sure it's all that important.
> > > >>
> > > >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
> > > >> get the official repo created, all three branches should be moved
> > > >> over, as-is, in order for everything to work smoothly. You may need to
> > > >> ask INFRA to set the "main" branch as the default branch, though.
> > > >>
> > > >> If everything is working correctly, you should see the site at
> > > >> https://thrift.staged.apache.org ; if that is working correctly, then
> > > >> you can use the _scripts/publish.sh script to push the staging branch
> > > >> to the publish branch (see README for explanation), and then you'll be
> > > >> completely off of CMS and can do whatever you want after that. :)
> > > >>
> > > >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
> > > >>>
> > > >>> This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
> > > >>>
> > >
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
Everything looks okay to me on the staging site. I see you pushed the
asf-staging branch to the asf-site branch, but the main site didn't
publish.
I think you will have to put in a ticket with INFRA to disable CMS
now, and use the asf-site branch from this repo.
Once it works, you should be able to tell that the site is drawing
from git, and not CMS, because:
1. I added "Accumulo" to the "Other Apache projects using Thrift"
section of the about page, and
2. The new .htaccess file should force a redirect from
http://thrift.apache.org to https://thrift.apache.org
I can see both of these on the staging site, but not yet on the main
site. So, INFRA will probably need to switch you over.
Follow-on things:
1. You can delete all the CMS website stuff in SVN now
(https://svn.apache.org/repos/asf/thrift/), and replace it with a
README saying you switched everything to git. The SVN history will
still be preserved, but removing it will be less confusing.
2. I do recommend that in future, you find a way to remove the
"snippets" copied from the main repo. That part will be hard to
maintain in future, and it's probably better to just link to the
tutorial stuff in the main repo (or move the tutorials to the website
and remove them from the main repo). It also requires a live
connection to test the site locally (and might even trigger rate
limiting for unauthenticated users), so it's not very reliable.
3. You can probably just remove the sitemap page... it's not very
useful, and doesn't look very good right now. If you want a "standard"
sitemap.xml, there's Jekyll plugins for automatically generating that,
but the HTML one isn't that useful.
4. Some of the documentation on the pages still refers to the
lib/paths.pm Perl stuff from CMS. I didn't update those developer
docs, but they can probably be removed, since the thrift-website repo
now has a good README of its own.
Christopher
On Fri, Oct 30, 2020 at 6:53 AM Duru Can Celasun <dc...@apache.org> wrote:
>
> All right, this should be all done now.
>
> https://thrift.staged.apache.org/
> https://thrift.apache.org/
>
> I've pushed all branches to the new repo [1] and it seems the Github Action and asf.yml are both working correctly,
>
> Christopher, thank you once again for working on this. Please take a look and let me know if anything is wrong or missing.
>
> Best,
> Can
>
> [1] https://github.com/apache/thrift-website
>
> On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
> >
> > Hi guys,
> >
> > thanks for the great move forward! Can you send a link to the page
> > as soon as something can be seen? I'm still pretty new to the project
> > and might have missed if you sent it already, sorry for that :-(
> >
> > All the best, Mario
> >
> >
> > On 30.10.20 11:19, Duru Can Celasun wrote:
> > > I've created the repo using self-service https://github.com/apache/thrift-website
> > >
> > > Once I get write access (I'm assuming it's automated) I'll push all 3 branches and we can take it from there.
> > >
> > > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> > >> I finished the syntax highlighting, but didn't get to the sitemap...
> > >> I'm not sure it's all that important.
> > >>
> > >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
> > >> get the official repo created, all three branches should be moved
> > >> over, as-is, in order for everything to work smoothly. You may need to
> > >> ask INFRA to set the "main" branch as the default branch, though.
> > >>
> > >> If everything is working correctly, you should see the site at
> > >> https://thrift.staged.apache.org ; if that is working correctly, then
> > >> you can use the _scripts/publish.sh script to push the staging branch
> > >> to the publish branch (see README for explanation), and then you'll be
> > >> completely off of CMS and can do whatever you want after that. :)
> > >>
> > >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
> > >>>
> > >>> This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
> > >>>
> >
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
All right, this should be all done now.
https://thrift.staged.apache.org/
https://thrift.apache.org/
I've pushed all branches to the new repo [1] and it seems the Github Action and asf.yml are both working correctly,
Christopher, thank you once again for working on this. Please take a look and let me know if anything is wrong or missing.
Best,
Can
[1] https://github.com/apache/thrift-website
On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
>
> Hi guys,
>
> thanks for the great move forward! Can you send a link to the page
> as soon as something can be seen? I'm still pretty new to the project
> and might have missed if you sent it already, sorry for that :-(
>
> All the best, Mario
>
>
> On 30.10.20 11:19, Duru Can Celasun wrote:
> > I've created the repo using self-service https://github.com/apache/thrift-website
> >
> > Once I get write access (I'm assuming it's automated) I'll push all 3 branches and we can take it from there.
> >
> > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> >> I finished the syntax highlighting, but didn't get to the sitemap...
> >> I'm not sure it's all that important.
> >>
> >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
> >> get the official repo created, all three branches should be moved
> >> over, as-is, in order for everything to work smoothly. You may need to
> >> ask INFRA to set the "main" branch as the default branch, though.
> >>
> >> If everything is working correctly, you should see the site at
> >> https://thrift.staged.apache.org ; if that is working correctly, then
> >> you can use the _scripts/publish.sh script to push the staging branch
> >> to the publish branch (see README for explanation), and then you'll be
> >> completely off of CMS and can do whatever you want after that. :)
> >>
> >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
> >>>
> >>> This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
> >>>
>
Re: Your project's website
Posted by Mario Emmenlauer <ma...@emmenlauer.de>.
Hi guys,
thanks for the great move forward! Can you send a link to the page
as soon as something can be seen? I'm still pretty new to the project
and might have missed if you sent it already, sorry for that :-(
All the best, Mario
On 30.10.20 11:19, Duru Can Celasun wrote:
> I've created the repo using self-service https://github.com/apache/thrift-website
>
> Once I get write access (I'm assuming it's automated) I'll push all 3 branches and we can take it from there.
>
> On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
>> I finished the syntax highlighting, but didn't get to the sitemap...
>> I'm not sure it's all that important.
>>
>> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
>> get the official repo created, all three branches should be moved
>> over, as-is, in order for everything to work smoothly. You may need to
>> ask INFRA to set the "main" branch as the default branch, though.
>>
>> If everything is working correctly, you should see the site at
>> https://thrift.staged.apache.org ; if that is working correctly, then
>> you can use the _scripts/publish.sh script to push the staging branch
>> to the publish branch (see README for explanation), and then you'll be
>> completely off of CMS and can do whatever you want after that. :)
>>
>> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
>>>
>>> This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
>>>
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
I've created the repo using self-service https://github.com/apache/thrift-website
Once I get write access (I'm assuming it's automated) I'll push all 3 branches and we can take it from there.
On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> I finished the syntax highlighting, but didn't get to the sitemap...
> I'm not sure it's all that important.
>
> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
> get the official repo created, all three branches should be moved
> over, as-is, in order for everything to work smoothly. You may need to
> ask INFRA to set the "main" branch as the default branch, though.
>
> If everything is working correctly, you should see the site at
> https://thrift.staged.apache.org ; if that is working correctly, then
> you can use the _scripts/publish.sh script to push the staging branch
> to the publish branch (see README for explanation), and then you'll be
> completely off of CMS and can do whatever you want after that. :)
>
> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
> >
> > This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
> >
> > On Thu, 29 Oct 2020, at 16:58, Christopher wrote:
> > > While there may be an interest in making quality changes to improve
> > > the layout and content of the site, the immediate need is to migrate
> > > off of CMS, for which INFRA has discontinued (or is discontinuing)
> > > support.
> > >
> > > I spent a few hours today converting all the Markdown over to Jekyll
> > > today... and only have 2 small things left that I'm still working on
> > > are the things that were previously being done in CMS's Perl code:
> > > 1. ensure syntax highlighting for code blocks is working for when code
> > > blocks are pulled in from the main thrift repo, and
> > > 2. fix the sitemap (I have a flattened version in Jekyll, but it
> > > doesn't show the hierarchy).
> > >
> > > The way I have it set up is complete with build instructions for
> > > testing locally, GitHub Actions CI builds for pull requests,
> > > configuration for INFRA's builders to automatically create a staging
> > > website whenever commits are merged to the main branch, and a
> > > convenience script to quickly publish from the asf-staging branch to
> > > the asf-site branch (or you can just merge the commit in git
> > > yourself). The complete lifecycle, from contributor pull request to
> > > publication is taken into consideration.
> > >
> > > The code so far (minus the bits I'm still finishing up) is at
> > > https://github.com/ctubbsii/thrift-website
> > > Of course, the Thrift PMC is not obligated to use what I've done, but
> > > it will get them off of CMS immediately if they want to use it.
> > >
> > > On Thu, Oct 29, 2020 at 5:08 AM Mario Emmenlauer <ma...@emmenlauer.de> wrote:
> > > >
> > > > On 29.10.20 02:33, Christopher wrote:
> > > > > On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
> > > > >
> > > > > [SNIP]
> > > > >>> I'm more than happy to do it your way, especially if you think it'd be
> > > > >>> easier. My one concern is that the current CMS content isn't exactly
> > > > >>> great and my RTD version has improvements, but we can sort that later.
> > > > >>> How should we proceed?
> > > > >
> > > > > Well, ultimately, the decision is up to the Thrift PMC. I can only
> > > > > offer suggestions and opinions, as I'm neither a PMC member nor a
> > > > > committer for Thrift. The CMS content may not be "great" as is, but it
> > > > > is what is there and working now, and its static HTML and/or basic
> > > > > Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
> > > > > convert while preserving the existing site look and feel... just to
> > > > > get off of CMS as quickly as possible. However, since I'm not a
> > > > > committer for Thrift, there's little I can do to actually make it
> > > > > happen. *IF* the PMC wants to go that route to get things done
> > > > > quickly, I can convert over the Markdown this week, and put it in my
> > > > > own repo for them to use directly, but I don't want to do that effort
> > > > > if that's not what they want to do. If they want to go with
> > > > > readthedocs to replace the site look and feel at the same time as
> > > > > getting off of CMS (rather than two steps), then I'd rather spend my
> > > > > effort trying to help you (since you're a PMC member working on this)
> > > > > get the builds automated and an .asf.yaml file in place to trigger the
> > > > > publication.
> > > >
> > > > I have to admit that I'm becoming a bit frustrated with the situation
> > > > of the website. I was ready to invest a few days of work in the content
> > > > when I started with thrift _one_year_ago_. But the content was not
> > > > (easily) editable and was spread out over multiple pages. In my very
> > > > personal opinion it would be essential for the project to get a page
> > > > ASAP. And it would _really_ help new users if the new page replaces all
> > > > spread-out information from current pages like thrift.apache.org,
> > > > github.com/apache/thrift, thrift-tutorial.readthedocs.io etc. And the
> > > > page should be really easy to edit for non-members, like i.e. in a
> > > > public git repository.
> > > >
> > > > I was under the impression that this is where Duru Can Celasun was going,
> > > > and I think that _if_ this requires more discussion then whoever suggests
> > > > something else should also carry this wagon for a bit. Whoever can
> > > > provide that gets my vote.
> > > >
> > > > All the best,
> > > >
> > > > Mario
> > > >
> > >
>
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
I finished the syntax highlighting, but didn't get to the sitemap...
I'm not sure it's all that important.
I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
get the official repo created, all three branches should be moved
over, as-is, in order for everything to work smoothly. You may need to
ask INFRA to set the "main" branch as the default branch, though.
If everything is working correctly, you should see the site at
https://thrift.staged.apache.org ; if that is working correctly, then
you can use the _scripts/publish.sh script to push the staging branch
to the publish branch (see README for explanation), and then you'll be
completely off of CMS and can do whatever you want after that. :)
On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dc...@apache.org> wrote:
>
> This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
>
> On Thu, 29 Oct 2020, at 16:58, Christopher wrote:
> > While there may be an interest in making quality changes to improve
> > the layout and content of the site, the immediate need is to migrate
> > off of CMS, for which INFRA has discontinued (or is discontinuing)
> > support.
> >
> > I spent a few hours today converting all the Markdown over to Jekyll
> > today... and only have 2 small things left that I'm still working on
> > are the things that were previously being done in CMS's Perl code:
> > 1. ensure syntax highlighting for code blocks is working for when code
> > blocks are pulled in from the main thrift repo, and
> > 2. fix the sitemap (I have a flattened version in Jekyll, but it
> > doesn't show the hierarchy).
> >
> > The way I have it set up is complete with build instructions for
> > testing locally, GitHub Actions CI builds for pull requests,
> > configuration for INFRA's builders to automatically create a staging
> > website whenever commits are merged to the main branch, and a
> > convenience script to quickly publish from the asf-staging branch to
> > the asf-site branch (or you can just merge the commit in git
> > yourself). The complete lifecycle, from contributor pull request to
> > publication is taken into consideration.
> >
> > The code so far (minus the bits I'm still finishing up) is at
> > https://github.com/ctubbsii/thrift-website
> > Of course, the Thrift PMC is not obligated to use what I've done, but
> > it will get them off of CMS immediately if they want to use it.
> >
> > On Thu, Oct 29, 2020 at 5:08 AM Mario Emmenlauer <ma...@emmenlauer.de> wrote:
> > >
> > > On 29.10.20 02:33, Christopher wrote:
> > > > On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
> > > >
> > > > [SNIP]
> > > >>> I'm more than happy to do it your way, especially if you think it'd be
> > > >>> easier. My one concern is that the current CMS content isn't exactly
> > > >>> great and my RTD version has improvements, but we can sort that later.
> > > >>> How should we proceed?
> > > >
> > > > Well, ultimately, the decision is up to the Thrift PMC. I can only
> > > > offer suggestions and opinions, as I'm neither a PMC member nor a
> > > > committer for Thrift. The CMS content may not be "great" as is, but it
> > > > is what is there and working now, and its static HTML and/or basic
> > > > Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
> > > > convert while preserving the existing site look and feel... just to
> > > > get off of CMS as quickly as possible. However, since I'm not a
> > > > committer for Thrift, there's little I can do to actually make it
> > > > happen. *IF* the PMC wants to go that route to get things done
> > > > quickly, I can convert over the Markdown this week, and put it in my
> > > > own repo for them to use directly, but I don't want to do that effort
> > > > if that's not what they want to do. If they want to go with
> > > > readthedocs to replace the site look and feel at the same time as
> > > > getting off of CMS (rather than two steps), then I'd rather spend my
> > > > effort trying to help you (since you're a PMC member working on this)
> > > > get the builds automated and an .asf.yaml file in place to trigger the
> > > > publication.
> > >
> > > I have to admit that I'm becoming a bit frustrated with the situation
> > > of the website. I was ready to invest a few days of work in the content
> > > when I started with thrift _one_year_ago_. But the content was not
> > > (easily) editable and was spread out over multiple pages. In my very
> > > personal opinion it would be essential for the project to get a page
> > > ASAP. And it would _really_ help new users if the new page replaces all
> > > spread-out information from current pages like thrift.apache.org,
> > > github.com/apache/thrift, thrift-tutorial.readthedocs.io etc. And the
> > > page should be really easy to edit for non-members, like i.e. in a
> > > public git repository.
> > >
> > > I was under the impression that this is where Duru Can Celasun was going,
> > > and I think that _if_ this requires more discussion then whoever suggests
> > > something else should also carry this wagon for a bit. Whoever can
> > > provide that gets my vote.
> > >
> > > All the best,
> > >
> > > Mario
> > >
> >
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
This looks excellent Christopher, thank you for working on this so quickly! I'll see if I can create an official repo tomorrow and we can take it from there.
On Thu, 29 Oct 2020, at 16:58, Christopher wrote:
> While there may be an interest in making quality changes to improve
> the layout and content of the site, the immediate need is to migrate
> off of CMS, for which INFRA has discontinued (or is discontinuing)
> support.
>
> I spent a few hours today converting all the Markdown over to Jekyll
> today... and only have 2 small things left that I'm still working on
> are the things that were previously being done in CMS's Perl code:
> 1. ensure syntax highlighting for code blocks is working for when code
> blocks are pulled in from the main thrift repo, and
> 2. fix the sitemap (I have a flattened version in Jekyll, but it
> doesn't show the hierarchy).
>
> The way I have it set up is complete with build instructions for
> testing locally, GitHub Actions CI builds for pull requests,
> configuration for INFRA's builders to automatically create a staging
> website whenever commits are merged to the main branch, and a
> convenience script to quickly publish from the asf-staging branch to
> the asf-site branch (or you can just merge the commit in git
> yourself). The complete lifecycle, from contributor pull request to
> publication is taken into consideration.
>
> The code so far (minus the bits I'm still finishing up) is at
> https://github.com/ctubbsii/thrift-website
> Of course, the Thrift PMC is not obligated to use what I've done, but
> it will get them off of CMS immediately if they want to use it.
>
> On Thu, Oct 29, 2020 at 5:08 AM Mario Emmenlauer <ma...@emmenlauer.de> wrote:
> >
> > On 29.10.20 02:33, Christopher wrote:
> > > On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
> > >
> > > [SNIP]
> > >>> I'm more than happy to do it your way, especially if you think it'd be
> > >>> easier. My one concern is that the current CMS content isn't exactly
> > >>> great and my RTD version has improvements, but we can sort that later.
> > >>> How should we proceed?
> > >
> > > Well, ultimately, the decision is up to the Thrift PMC. I can only
> > > offer suggestions and opinions, as I'm neither a PMC member nor a
> > > committer for Thrift. The CMS content may not be "great" as is, but it
> > > is what is there and working now, and its static HTML and/or basic
> > > Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
> > > convert while preserving the existing site look and feel... just to
> > > get off of CMS as quickly as possible. However, since I'm not a
> > > committer for Thrift, there's little I can do to actually make it
> > > happen. *IF* the PMC wants to go that route to get things done
> > > quickly, I can convert over the Markdown this week, and put it in my
> > > own repo for them to use directly, but I don't want to do that effort
> > > if that's not what they want to do. If they want to go with
> > > readthedocs to replace the site look and feel at the same time as
> > > getting off of CMS (rather than two steps), then I'd rather spend my
> > > effort trying to help you (since you're a PMC member working on this)
> > > get the builds automated and an .asf.yaml file in place to trigger the
> > > publication.
> >
> > I have to admit that I'm becoming a bit frustrated with the situation
> > of the website. I was ready to invest a few days of work in the content
> > when I started with thrift _one_year_ago_. But the content was not
> > (easily) editable and was spread out over multiple pages. In my very
> > personal opinion it would be essential for the project to get a page
> > ASAP. And it would _really_ help new users if the new page replaces all
> > spread-out information from current pages like thrift.apache.org,
> > github.com/apache/thrift, thrift-tutorial.readthedocs.io etc. And the
> > page should be really easy to edit for non-members, like i.e. in a
> > public git repository.
> >
> > I was under the impression that this is where Duru Can Celasun was going,
> > and I think that _if_ this requires more discussion then whoever suggests
> > something else should also carry this wagon for a bit. Whoever can
> > provide that gets my vote.
> >
> > All the best,
> >
> > Mario
> >
>
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
While there may be an interest in making quality changes to improve
the layout and content of the site, the immediate need is to migrate
off of CMS, for which INFRA has discontinued (or is discontinuing)
support.
I spent a few hours today converting all the Markdown over to Jekyll
today... and only have 2 small things left that I'm still working on
are the things that were previously being done in CMS's Perl code:
1. ensure syntax highlighting for code blocks is working for when code
blocks are pulled in from the main thrift repo, and
2. fix the sitemap (I have a flattened version in Jekyll, but it
doesn't show the hierarchy).
The way I have it set up is complete with build instructions for
testing locally, GitHub Actions CI builds for pull requests,
configuration for INFRA's builders to automatically create a staging
website whenever commits are merged to the main branch, and a
convenience script to quickly publish from the asf-staging branch to
the asf-site branch (or you can just merge the commit in git
yourself). The complete lifecycle, from contributor pull request to
publication is taken into consideration.
The code so far (minus the bits I'm still finishing up) is at
https://github.com/ctubbsii/thrift-website
Of course, the Thrift PMC is not obligated to use what I've done, but
it will get them off of CMS immediately if they want to use it.
On Thu, Oct 29, 2020 at 5:08 AM Mario Emmenlauer <ma...@emmenlauer.de> wrote:
>
> On 29.10.20 02:33, Christopher wrote:
> > On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
> >
> > [SNIP]
> >>> I'm more than happy to do it your way, especially if you think it'd be
> >>> easier. My one concern is that the current CMS content isn't exactly
> >>> great and my RTD version has improvements, but we can sort that later.
> >>> How should we proceed?
> >
> > Well, ultimately, the decision is up to the Thrift PMC. I can only
> > offer suggestions and opinions, as I'm neither a PMC member nor a
> > committer for Thrift. The CMS content may not be "great" as is, but it
> > is what is there and working now, and its static HTML and/or basic
> > Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
> > convert while preserving the existing site look and feel... just to
> > get off of CMS as quickly as possible. However, since I'm not a
> > committer for Thrift, there's little I can do to actually make it
> > happen. *IF* the PMC wants to go that route to get things done
> > quickly, I can convert over the Markdown this week, and put it in my
> > own repo for them to use directly, but I don't want to do that effort
> > if that's not what they want to do. If they want to go with
> > readthedocs to replace the site look and feel at the same time as
> > getting off of CMS (rather than two steps), then I'd rather spend my
> > effort trying to help you (since you're a PMC member working on this)
> > get the builds automated and an .asf.yaml file in place to trigger the
> > publication.
>
> I have to admit that I'm becoming a bit frustrated with the situation
> of the website. I was ready to invest a few days of work in the content
> when I started with thrift _one_year_ago_. But the content was not
> (easily) editable and was spread out over multiple pages. In my very
> personal opinion it would be essential for the project to get a page
> ASAP. And it would _really_ help new users if the new page replaces all
> spread-out information from current pages like thrift.apache.org,
> github.com/apache/thrift, thrift-tutorial.readthedocs.io etc. And the
> page should be really easy to edit for non-members, like i.e. in a
> public git repository.
>
> I was under the impression that this is where Duru Can Celasun was going,
> and I think that _if_ this requires more discussion then whoever suggests
> something else should also carry this wagon for a bit. Whoever can
> provide that gets my vote.
>
> All the best,
>
> Mario
>
Re: Your project's website
Posted by Mario Emmenlauer <ma...@emmenlauer.de>.
On 29.10.20 02:33, Christopher wrote:
> On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
>
> [SNIP]
>>> I'm more than happy to do it your way, especially if you think it'd be
>>> easier. My one concern is that the current CMS content isn't exactly
>>> great and my RTD version has improvements, but we can sort that later.
>>> How should we proceed?
>
> Well, ultimately, the decision is up to the Thrift PMC. I can only
> offer suggestions and opinions, as I'm neither a PMC member nor a
> committer for Thrift. The CMS content may not be "great" as is, but it
> is what is there and working now, and its static HTML and/or basic
> Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
> convert while preserving the existing site look and feel... just to
> get off of CMS as quickly as possible. However, since I'm not a
> committer for Thrift, there's little I can do to actually make it
> happen. *IF* the PMC wants to go that route to get things done
> quickly, I can convert over the Markdown this week, and put it in my
> own repo for them to use directly, but I don't want to do that effort
> if that's not what they want to do. If they want to go with
> readthedocs to replace the site look and feel at the same time as
> getting off of CMS (rather than two steps), then I'd rather spend my
> effort trying to help you (since you're a PMC member working on this)
> get the builds automated and an .asf.yaml file in place to trigger the
> publication.
I have to admit that I'm becoming a bit frustrated with the situation
of the website. I was ready to invest a few days of work in the content
when I started with thrift _one_year_ago_. But the content was not
(easily) editable and was spread out over multiple pages. In my very
personal opinion it would be essential for the project to get a page
ASAP. And it would _really_ help new users if the new page replaces all
spread-out information from current pages like thrift.apache.org,
github.com/apache/thrift, thrift-tutorial.readthedocs.io etc. And the
page should be really easy to edit for non-members, like i.e. in a
public git repository.
I was under the impression that this is where Duru Can Celasun was going,
and I think that _if_ this requires more discussion then whoever suggests
something else should also carry this wagon for a bit. Whoever can
provide that gets my vote.
All the best,
Mario
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
On Wed, Oct 28, 2020 at 1:50 PM Duru Can Celasun <dc...@apache.org> wrote:
>
> Apologies, I thought I was replying to Andrew and I only just now realize it was Christopher. My point stands though, if there is an easier/preferred way to do this just let me know and we'll do that.
No problem. :)
[SNIP]
> > I'm not a designer and I know nothing about frontend development.
That's totally fine. I'm not a designer either. I was more commenting
to address the "readiness" of the site. If the look/feel are okay to
the Thrift PMC, then that should be enough to be "ready" to replace
the existing site. I don't know where they stand (again, I'm not even
a committer on the project... just offering feedback). :)
[SNIP]
> > That was always the intention, as stated in the original Jira issue
> > [1]. In fact, I've provided build instructions that can be used by
> > INFRA.
As far as I'm aware, INFRA would not be the ones who need those
instructions, but the Thrift committers who will be responsible for
setting up the build and maintaining it. Can you link to those
instructions here? I couldn't find them. Maybe I can suggest a way it
can be automated. At the very least, I want to try to build it locally
to see how it works.
[SNIP]
> > Thanks for the link. I'm not familiar with this but if INFRA could
> > create a thrift-website repo for us on Github I'd be happy to take a
> > look.
A Thrift PMC member can create the repo themselves using the
self-serve tool (http://selfserve.apache.org/). I definitely recommend
having the website in a separate repo from the main code base, just
because it's easier to track pull requests that way, and so people
contributing to one don't have to clone all the commits for the other.
[SNIP]
> > I'm more than happy to do it your way, especially if you think it'd be
> > easier. My one concern is that the current CMS content isn't exactly
> > great and my RTD version has improvements, but we can sort that later.
> > How should we proceed?
Well, ultimately, the decision is up to the Thrift PMC. I can only
offer suggestions and opinions, as I'm neither a PMC member nor a
committer for Thrift. The CMS content may not be "great" as is, but it
is what is there and working now, and its static HTML and/or basic
Markdown is 99% compatible with Jekyll's Markdown, so it's easy to
convert while preserving the existing site look and feel... just to
get off of CMS as quickly as possible. However, since I'm not a
committer for Thrift, there's little I can do to actually make it
happen. *IF* the PMC wants to go that route to get things done
quickly, I can convert over the Markdown this week, and put it in my
own repo for them to use directly, but I don't want to do that effort
if that's not what they want to do. If they want to go with
readthedocs to replace the site look and feel at the same time as
getting off of CMS (rather than two steps), then I'd rather spend my
effort trying to help you (since you're a PMC member working on this)
get the builds automated and an .asf.yaml file in place to trigger the
publication.
Gavin also suggested another option, which would basically be doing
*both* options... a regular site and a readthedocs site with a
docs.thrift.apache.org CNAME. If that's the route that the PMC wants
to do, then it makes sense to just deal with converting over the CMS
content as I suggested first, and then working on getting the
readthedocs site on the CNAME after that.
Whatever the PMC wants to do, the sooner it is decided, the more I can
help make it happen as a mere contributor. :)
Christopher
Re: Your project's website
Posted by Gavin McDonald <gm...@apache.org>.
Hi,
I'd like to cite a couple of example usage of a 'standard' ASF Compliant website + readthedocs usage
Here are two examples:-
libcloud.apache.org
cloudstack.apache.org
Both of those projects have content , built however they want, and the code for the 'website' part can indeed be hosted on Github, with for example a .asf.yaml file in place which would then allow the site to be built and deployed upon commit. (building could trigger a Jenkins build for example, a Github Action, or other methods)
The content of the above websites include the project logo, project description, links to required other areas of the ASF such as The Apache License, Thanks page, how to donate, etc.
They also include project information, such as where to find the mailing lists, how to sign up, where to read the list archives, who the project committers/pmc are, a page describing the latest releases , where to download them from and a cgi pointing folks to their nearest download mirror. Plus more stuff.
What they, and all other project websites have in common is, they are deployed and housed on ASF controlled hardware, that Infra maintains and can therefore control reliability and uptime etc. We can not rely on 3rd party hosting for the 'main' project website.
As for the 'readthedocs' component of the above two sites, they link 'Documentation' to readthedocs and both have also CNAMES in place such as 'docs.libcloud.apache.org' points to 'https://libcloud.readthedocs.io/en/stable/' , whilst 'docs.cloudstack.apache.org' redirects to readthedocs whilst retaining that url. How they generate and upload those docs to readthedocs.org is a question to ask those communities, I know of other ASF projects that use Github and/or Jenkins to build those docs and use a readthedocs token (we'd place on a github repo or jenkins for you) to upload. Github Actions is also a possibility.
I have looked over the thrift.apache.org website, and there is much that can remain, we just need to get you off the CMS and onto another method for you publishing that to thrift.apache.org, various methods are supported and this is what we should thrash out on the Infra ticket. Some of this content on thrift.apache.org could be transferred to generated docs for readthedocs.org. We would also be happy to create a CMAME of docs.thrift.apache.org to point there, and you can use a Documentation page/link on the main website to point users there for the bulk of the Thrift documentation.
Hope that all makes sense. Infra are here to help get you off of the CMS is our main concern at this time.
Gavin (ASF Infra Team)
On 2020/10/28 17:50:24, "Duru Can Celasun" <dc...@apache.org> wrote:
> Apologies, I thought I was replying to Andrew and I only just now realize it was Christopher. My point stands though, if there is an easier/preferred way to do this just let me know and we'll do that.
>
> On Wed, 28 Oct 2020, at 17:46, Duru Can Celasun wrote:
> > Andrew,
> >
> > I think there has been some misunderstanding. Comments below.
> >
> > On Wed, 28 Oct 2020, at 16:31, Christopher wrote:
> > > Can,
> > >
> > > The official site for Apache Thrift is located at thrift.apache.org
> > > It is the sources for that site that needs to move away from CMS. It
> > > is not sufficient to create a new site located elsewhere to address
> > > the CMS issue.
> > >
> > > While this "readthedocs" site looks good, it is missing some key
> > > things required for ASF projects... like the mandatory foundation
> > > links and copyright footer information (see
> > > https://whimsy.apache.org/site/project/thrift).
> >
> > Thanks, I wasn't aware but I'm happy to add all of this.
> >
> > > I also think it
> > > doesn't look quite as good as the current site's layout, but that's
> > > probably personal taste.
> >
> > I'm not a designer and I know nothing about frontend development. The
> > current "look" of the site is simply the default provided by RTD. I
> > have neither the skills nor the interest in a new design and nobody
> > else ever volunteered.
> >
> > It might also be a problem that it has ads on
> > > it at readthedocs.io, though I think that might be possible to address
> > > if it is generated locally and not hosted on readthedocs.io.
> >
> > That was always the intention, as stated in the original Jira issue
> > [1]. In fact, I've provided build instructions that can be used by
> > INFRA.
> >
> > I wasn't aware of any ads, but then again that website is simply a
> > proof of concept on my personal RTD account.
> >
> > >
> > > So, where it is currently hosted at readthedocs.io, it is not a
> > > suitable alternative to the CMS hosted thrift.apache.org site... which
> > > still needs to be addressed.
> >
> > See above.
> >
> > >
> > > In order to replace the CMS site with this new site as the new
> > > thrift.apache.org, the issues I mentioned would need to be fixed, and
> > > then you'd have to generate the site locally and publish it in an ASF
> > > git repository, and configure it to publish to thrift.apache.org using
> > > an '.asf.yaml' configuration file (see
> > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories).
> >
> > Thanks for the link. I'm not familiar with this but if INFRA could
> > create a thrift-website repo for us on Github I'd be happy to take a
> > look.
> >
> > >
> > > However, I think it would be much easier to set up a simple
> > > jekyll-based site using the existing CMS content as a starting point.
> > > It's really not hard to do that at all. I could help with the effort,
> > > but it's harder to explain than it is to do. I've already been helping
> > > maintain both Accumulo and Fluo's websites in this same way, as a
> > > committer on those projects, so I know it's super easy to maintain
> > > once it's set up, and the set up isn't hard at all. I'm not a Thrift
> > > committer, so I can't do most of the steps myself for Thrift, but I
> > > can try to walk a committer through the process.
> >
> >
> > I'm more than happy to do it your way, especially if you think it'd be
> > easier. My one concern is that the current CMS content isn't exactly
> > great and my RTD version has improvements, but we can sort that later.
> > How should we proceed?
> >
> > >
> > > Christopher
> >
> > [1]
> > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> >
> >
> > >
> > > On Wed, Oct 28, 2020 at 8:43 AM Duru Can Celasun <dc...@apache.org> wrote:
> > > >
> > > > Hi Andrew,
> > > >
> > > > The site on ReadTheDocs [1] isn't just documentation, it's the full website including downloads [2] so I'm not sure if any other static landing page is necessary.
> > > >
> > > > If you can clarify that first I'll go ahead and open an INFRA ticket.
> > > >
> > > > Can
> > > >
> > > > [1] https://thrift-fork.readthedocs.io/en/docs/index.html
> > > > [2] https://thrift-fork.readthedocs.io/en/docs/download.html
> > > >
> > > > On Wed, 28 Oct 2020, at 12:35, Andrew Wetmore wrote:
> > > > > Hi, Can:
> > > > >
> > > > > I spoke with Gavin MacDonald on our team, and he said the Thrift project
> > > > > will still need at least a basic static landing page at thrift.a.o. If I
> > > > > understand correctly, you can redirect traffic from there to what you have
> > > > > set up in ReadTheDocs. The landing page should also have information on
> > > > > links for downloading software releases.
> > > > >
> > > > > Gavin requested that you open a Jira ticket directed at Infra to cover the
> > > > > project's migration so we can keep track of what we need to do to provide a
> > > > > smooth transition for the project.
> > > > >
> > > > > Andrew
> > > > >
> > > > > On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> > > > >
> > > > > > Hi Andrew,
> > > > > >
> > > > > > Any news on this? How should we proceed?
> > > > > >
> > > > > > Cheers,
> > > > > > Can
> > > > > >
> > > > > > On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > > > > > > Hi Andrew,
> > > > > > >
> > > > > > > Sorry for the late response. Last year I started working on a migration
> > > > > > > from Apache CMS to "read the docs" [1] but I never got a chance to
> > > > > > > finish it.
> > > > > > >
> > > > > > > It's mostly complete, but we could definitely use some INFRA help to
> > > > > > > get it over the finish line.
> > > > > > >
> > > > > > > Would it be possible to have a thrift-website repo on Github and have
> > > > > > > it deployed via Travis?
> > > > > > >
> > > > > > > The linked issue has build instructions but I'd be happy to make
> > > > > > > changes if needed.
> > > > > > >
> > > > > > > Please let me how you'd like to proceed.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Can
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> > > > > > >
> > > > > > > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > > > > > > Hi:
> > > > > > > >
> > > > > > > > I wrote to you two weeks ago about your project website, but have not
> > > > > > seen
> > > > > > > > a response. Whom should I contact directly? I am trying to see whether
> > > > > > your
> > > > > > > > project still uses the Apache CMS and, if so, what your plans are to
> > > > > > > > migrate off it.
> > > > > > > >
> > > > > > > > Thanks in advance for your help.
> > > > > > > >
> > > > > > > > Andrew
> > > > > > > >
> > > > > > > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi:
> > > > > > > > >
> > > > > > > > > I am part of the Infrastructure team, and am writing to ask whether
> > > > > > your
> > > > > > > > > project is still using the Apache CMS for your project website. As
> > > > > > you
> > > > > > > > > know, the CMS is reaching end-of-life, and we need projects to move
> > > > > > their
> > > > > > > > > websites onto a different option within the next few weeks.
> > > > > > > > >
> > > > > > > > > There are several alternatives available, including those listed on
> > > > > > this
> > > > > > > > > page [1] on managing project websites. Infra is assembling a Wiki
> > > > > > page [2]
> > > > > > > > > on migrating a website from the CMS, and is looking forward to
> > > > > > helping
> > > > > > > > > projects with this transition.
> > > > > > > > >
> > > > > > > > > Please let me know whether your site is still on the Apache CMS and,
> > > > > > if
> > > > > > > > > so, who will be the project point-of-contact with Infra for the
> > > > > > migration.
> > > > > > > > >
> > > > > > > > > Thank you!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1] https://infra.apache.org/project-site.html
> > > > > > > > >
> > > > > > > > > [2]
> > > > > > > > >
> > > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Andrew Wetmore
> > > > > > > > > Technical Writer-Editor
> > > > > > > > > Infra
> > > > > > > > > *Apache Software Foundation*
> > > > > > > > > andreww@apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > <
> > > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > > > > Virus-free.
> > > > > > > > > www.avast.com
> > > > > > > > > <
> > > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > > > > >
> > > > > > > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Andrew Wetmore
> > > > > > > > Technical Writer-Editor
> > > > > > > > Infra
> > > > > > > > *Apache Software Foundation*
> > > > > > > > andreww@apache.org
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Andrew Wetmore
> > > > > Technical Writer-Editor
> > > > > Infra
> > > > > *Apache Software Foundation*
> > > > > andreww@apache.org
> > > > >
> > >
> >
>
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
Apologies, I thought I was replying to Andrew and I only just now realize it was Christopher. My point stands though, if there is an easier/preferred way to do this just let me know and we'll do that.
On Wed, 28 Oct 2020, at 17:46, Duru Can Celasun wrote:
> Andrew,
>
> I think there has been some misunderstanding. Comments below.
>
> On Wed, 28 Oct 2020, at 16:31, Christopher wrote:
> > Can,
> >
> > The official site for Apache Thrift is located at thrift.apache.org
> > It is the sources for that site that needs to move away from CMS. It
> > is not sufficient to create a new site located elsewhere to address
> > the CMS issue.
> >
> > While this "readthedocs" site looks good, it is missing some key
> > things required for ASF projects... like the mandatory foundation
> > links and copyright footer information (see
> > https://whimsy.apache.org/site/project/thrift).
>
> Thanks, I wasn't aware but I'm happy to add all of this.
>
> > I also think it
> > doesn't look quite as good as the current site's layout, but that's
> > probably personal taste.
>
> I'm not a designer and I know nothing about frontend development. The
> current "look" of the site is simply the default provided by RTD. I
> have neither the skills nor the interest in a new design and nobody
> else ever volunteered.
>
> It might also be a problem that it has ads on
> > it at readthedocs.io, though I think that might be possible to address
> > if it is generated locally and not hosted on readthedocs.io.
>
> That was always the intention, as stated in the original Jira issue
> [1]. In fact, I've provided build instructions that can be used by
> INFRA.
>
> I wasn't aware of any ads, but then again that website is simply a
> proof of concept on my personal RTD account.
>
> >
> > So, where it is currently hosted at readthedocs.io, it is not a
> > suitable alternative to the CMS hosted thrift.apache.org site... which
> > still needs to be addressed.
>
> See above.
>
> >
> > In order to replace the CMS site with this new site as the new
> > thrift.apache.org, the issues I mentioned would need to be fixed, and
> > then you'd have to generate the site locally and publish it in an ASF
> > git repository, and configure it to publish to thrift.apache.org using
> > an '.asf.yaml' configuration file (see
> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories).
>
> Thanks for the link. I'm not familiar with this but if INFRA could
> create a thrift-website repo for us on Github I'd be happy to take a
> look.
>
> >
> > However, I think it would be much easier to set up a simple
> > jekyll-based site using the existing CMS content as a starting point.
> > It's really not hard to do that at all. I could help with the effort,
> > but it's harder to explain than it is to do. I've already been helping
> > maintain both Accumulo and Fluo's websites in this same way, as a
> > committer on those projects, so I know it's super easy to maintain
> > once it's set up, and the set up isn't hard at all. I'm not a Thrift
> > committer, so I can't do most of the steps myself for Thrift, but I
> > can try to walk a committer through the process.
>
>
> I'm more than happy to do it your way, especially if you think it'd be
> easier. My one concern is that the current CMS content isn't exactly
> great and my RTD version has improvements, but we can sort that later.
> How should we proceed?
>
> >
> > Christopher
>
> [1]
> https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
>
>
> >
> > On Wed, Oct 28, 2020 at 8:43 AM Duru Can Celasun <dc...@apache.org> wrote:
> > >
> > > Hi Andrew,
> > >
> > > The site on ReadTheDocs [1] isn't just documentation, it's the full website including downloads [2] so I'm not sure if any other static landing page is necessary.
> > >
> > > If you can clarify that first I'll go ahead and open an INFRA ticket.
> > >
> > > Can
> > >
> > > [1] https://thrift-fork.readthedocs.io/en/docs/index.html
> > > [2] https://thrift-fork.readthedocs.io/en/docs/download.html
> > >
> > > On Wed, 28 Oct 2020, at 12:35, Andrew Wetmore wrote:
> > > > Hi, Can:
> > > >
> > > > I spoke with Gavin MacDonald on our team, and he said the Thrift project
> > > > will still need at least a basic static landing page at thrift.a.o. If I
> > > > understand correctly, you can redirect traffic from there to what you have
> > > > set up in ReadTheDocs. The landing page should also have information on
> > > > links for downloading software releases.
> > > >
> > > > Gavin requested that you open a Jira ticket directed at Infra to cover the
> > > > project's migration so we can keep track of what we need to do to provide a
> > > > smooth transition for the project.
> > > >
> > > > Andrew
> > > >
> > > > On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> > > >
> > > > > Hi Andrew,
> > > > >
> > > > > Any news on this? How should we proceed?
> > > > >
> > > > > Cheers,
> > > > > Can
> > > > >
> > > > > On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > > > > > Hi Andrew,
> > > > > >
> > > > > > Sorry for the late response. Last year I started working on a migration
> > > > > > from Apache CMS to "read the docs" [1] but I never got a chance to
> > > > > > finish it.
> > > > > >
> > > > > > It's mostly complete, but we could definitely use some INFRA help to
> > > > > > get it over the finish line.
> > > > > >
> > > > > > Would it be possible to have a thrift-website repo on Github and have
> > > > > > it deployed via Travis?
> > > > > >
> > > > > > The linked issue has build instructions but I'd be happy to make
> > > > > > changes if needed.
> > > > > >
> > > > > > Please let me how you'd like to proceed.
> > > > > >
> > > > > > Cheers,
> > > > > > Can
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> > > > > >
> > > > > > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > > > > > Hi:
> > > > > > >
> > > > > > > I wrote to you two weeks ago about your project website, but have not
> > > > > seen
> > > > > > > a response. Whom should I contact directly? I am trying to see whether
> > > > > your
> > > > > > > project still uses the Apache CMS and, if so, what your plans are to
> > > > > > > migrate off it.
> > > > > > >
> > > > > > > Thanks in advance for your help.
> > > > > > >
> > > > > > > Andrew
> > > > > > >
> > > > > > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi:
> > > > > > > >
> > > > > > > > I am part of the Infrastructure team, and am writing to ask whether
> > > > > your
> > > > > > > > project is still using the Apache CMS for your project website. As
> > > > > you
> > > > > > > > know, the CMS is reaching end-of-life, and we need projects to move
> > > > > their
> > > > > > > > websites onto a different option within the next few weeks.
> > > > > > > >
> > > > > > > > There are several alternatives available, including those listed on
> > > > > this
> > > > > > > > page [1] on managing project websites. Infra is assembling a Wiki
> > > > > page [2]
> > > > > > > > on migrating a website from the CMS, and is looking forward to
> > > > > helping
> > > > > > > > projects with this transition.
> > > > > > > >
> > > > > > > > Please let me know whether your site is still on the Apache CMS and,
> > > > > if
> > > > > > > > so, who will be the project point-of-contact with Infra for the
> > > > > migration.
> > > > > > > >
> > > > > > > > Thank you!
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://infra.apache.org/project-site.html
> > > > > > > >
> > > > > > > > [2]
> > > > > > > >
> > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Andrew Wetmore
> > > > > > > > Technical Writer-Editor
> > > > > > > > Infra
> > > > > > > > *Apache Software Foundation*
> > > > > > > > andreww@apache.org
> > > > > > > >
> > > > > > > >
> > > > > > > > <
> > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > > > Virus-free.
> > > > > > > > www.avast.com
> > > > > > > > <
> > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > > > >
> > > > > > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Andrew Wetmore
> > > > > > > Technical Writer-Editor
> > > > > > > Infra
> > > > > > > *Apache Software Foundation*
> > > > > > > andreww@apache.org
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andreww@apache.org
> > > >
> >
>
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
Andrew,
I think there has been some misunderstanding. Comments below.
On Wed, 28 Oct 2020, at 16:31, Christopher wrote:
> Can,
>
> The official site for Apache Thrift is located at thrift.apache.org
> It is the sources for that site that needs to move away from CMS. It
> is not sufficient to create a new site located elsewhere to address
> the CMS issue.
>
> While this "readthedocs" site looks good, it is missing some key
> things required for ASF projects... like the mandatory foundation
> links and copyright footer information (see
> https://whimsy.apache.org/site/project/thrift).
Thanks, I wasn't aware but I'm happy to add all of this.
> I also think it
> doesn't look quite as good as the current site's layout, but that's
> probably personal taste.
I'm not a designer and I know nothing about frontend development. The current "look" of the site is simply the default provided by RTD. I have neither the skills nor the interest in a new design and nobody else ever volunteered.
It might also be a problem that it has ads on
> it at readthedocs.io, though I think that might be possible to address
> if it is generated locally and not hosted on readthedocs.io.
That was always the intention, as stated in the original Jira issue [1]. In fact, I've provided build instructions that can be used by INFRA.
I wasn't aware of any ads, but then again that website is simply a proof of concept on my personal RTD account.
>
> So, where it is currently hosted at readthedocs.io, it is not a
> suitable alternative to the CMS hosted thrift.apache.org site... which
> still needs to be addressed.
See above.
>
> In order to replace the CMS site with this new site as the new
> thrift.apache.org, the issues I mentioned would need to be fixed, and
> then you'd have to generate the site locally and publish it in an ASF
> git repository, and configure it to publish to thrift.apache.org using
> an '.asf.yaml' configuration file (see
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories).
Thanks for the link. I'm not familiar with this but if INFRA could create a thrift-website repo for us on Github I'd be happy to take a look.
>
> However, I think it would be much easier to set up a simple
> jekyll-based site using the existing CMS content as a starting point.
> It's really not hard to do that at all. I could help with the effort,
> but it's harder to explain than it is to do. I've already been helping
> maintain both Accumulo and Fluo's websites in this same way, as a
> committer on those projects, so I know it's super easy to maintain
> once it's set up, and the set up isn't hard at all. I'm not a Thrift
> committer, so I can't do most of the steps myself for Thrift, but I
> can try to walk a committer through the process.
I'm more than happy to do it your way, especially if you think it'd be easier. My one concern is that the current CMS content isn't exactly great and my RTD version has improvements, but we can sort that later. How should we proceed?
>
> Christopher
[1] https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
>
> On Wed, Oct 28, 2020 at 8:43 AM Duru Can Celasun <dc...@apache.org> wrote:
> >
> > Hi Andrew,
> >
> > The site on ReadTheDocs [1] isn't just documentation, it's the full website including downloads [2] so I'm not sure if any other static landing page is necessary.
> >
> > If you can clarify that first I'll go ahead and open an INFRA ticket.
> >
> > Can
> >
> > [1] https://thrift-fork.readthedocs.io/en/docs/index.html
> > [2] https://thrift-fork.readthedocs.io/en/docs/download.html
> >
> > On Wed, 28 Oct 2020, at 12:35, Andrew Wetmore wrote:
> > > Hi, Can:
> > >
> > > I spoke with Gavin MacDonald on our team, and he said the Thrift project
> > > will still need at least a basic static landing page at thrift.a.o. If I
> > > understand correctly, you can redirect traffic from there to what you have
> > > set up in ReadTheDocs. The landing page should also have information on
> > > links for downloading software releases.
> > >
> > > Gavin requested that you open a Jira ticket directed at Infra to cover the
> > > project's migration so we can keep track of what we need to do to provide a
> > > smooth transition for the project.
> > >
> > > Andrew
> > >
> > > On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> > >
> > > > Hi Andrew,
> > > >
> > > > Any news on this? How should we proceed?
> > > >
> > > > Cheers,
> > > > Can
> > > >
> > > > On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > > > > Hi Andrew,
> > > > >
> > > > > Sorry for the late response. Last year I started working on a migration
> > > > > from Apache CMS to "read the docs" [1] but I never got a chance to
> > > > > finish it.
> > > > >
> > > > > It's mostly complete, but we could definitely use some INFRA help to
> > > > > get it over the finish line.
> > > > >
> > > > > Would it be possible to have a thrift-website repo on Github and have
> > > > > it deployed via Travis?
> > > > >
> > > > > The linked issue has build instructions but I'd be happy to make
> > > > > changes if needed.
> > > > >
> > > > > Please let me how you'd like to proceed.
> > > > >
> > > > > Cheers,
> > > > > Can
> > > > >
> > > > > [1]
> > > > >
> > > > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> > > > >
> > > > > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > > > > Hi:
> > > > > >
> > > > > > I wrote to you two weeks ago about your project website, but have not
> > > > seen
> > > > > > a response. Whom should I contact directly? I am trying to see whether
> > > > your
> > > > > > project still uses the Apache CMS and, if so, what your plans are to
> > > > > > migrate off it.
> > > > > >
> > > > > > Thanks in advance for your help.
> > > > > >
> > > > > > Andrew
> > > > > >
> > > > > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> > > > wrote:
> > > > > >
> > > > > > > Hi:
> > > > > > >
> > > > > > > I am part of the Infrastructure team, and am writing to ask whether
> > > > your
> > > > > > > project is still using the Apache CMS for your project website. As
> > > > you
> > > > > > > know, the CMS is reaching end-of-life, and we need projects to move
> > > > their
> > > > > > > websites onto a different option within the next few weeks.
> > > > > > >
> > > > > > > There are several alternatives available, including those listed on
> > > > this
> > > > > > > page [1] on managing project websites. Infra is assembling a Wiki
> > > > page [2]
> > > > > > > on migrating a website from the CMS, and is looking forward to
> > > > helping
> > > > > > > projects with this transition.
> > > > > > >
> > > > > > > Please let me know whether your site is still on the Apache CMS and,
> > > > if
> > > > > > > so, who will be the project point-of-contact with Infra for the
> > > > migration.
> > > > > > >
> > > > > > > Thank you!
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [1] https://infra.apache.org/project-site.html
> > > > > > >
> > > > > > > [2]
> > > > > > >
> > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Andrew Wetmore
> > > > > > > Technical Writer-Editor
> > > > > > > Infra
> > > > > > > *Apache Software Foundation*
> > > > > > > andreww@apache.org
> > > > > > >
> > > > > > >
> > > > > > > <
> > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > > Virus-free.
> > > > > > > www.avast.com
> > > > > > > <
> > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > > >
> > > > > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrew Wetmore
> > > > > > Technical Writer-Editor
> > > > > > Infra
> > > > > > *Apache Software Foundation*
> > > > > > andreww@apache.org
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andreww@apache.org
> > >
>
Re: Your project's website
Posted by Christopher <ct...@apache.org>.
Can,
The official site for Apache Thrift is located at thrift.apache.org
It is the sources for that site that needs to move away from CMS. It
is not sufficient to create a new site located elsewhere to address
the CMS issue.
While this "readthedocs" site looks good, it is missing some key
things required for ASF projects... like the mandatory foundation
links and copyright footer information (see
https://whimsy.apache.org/site/project/thrift). I also think it
doesn't look quite as good as the current site's layout, but that's
probably personal taste. It might also be a problem that it has ads on
it at readthedocs.io, though I think that might be possible to address
if it is generated locally and not hosted on readthedocs.io.
So, where it is currently hosted at readthedocs.io, it is not a
suitable alternative to the CMS hosted thrift.apache.org site... which
still needs to be addressed.
In order to replace the CMS site with this new site as the new
thrift.apache.org, the issues I mentioned would need to be fixed, and
then you'd have to generate the site locally and publish it in an ASF
git repository, and configure it to publish to thrift.apache.org using
an '.asf.yaml' configuration file (see
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories).
However, I think it would be much easier to set up a simple
jekyll-based site using the existing CMS content as a starting point.
It's really not hard to do that at all. I could help with the effort,
but it's harder to explain than it is to do. I've already been helping
maintain both Accumulo and Fluo's websites in this same way, as a
committer on those projects, so I know it's super easy to maintain
once it's set up, and the set up isn't hard at all. I'm not a Thrift
committer, so I can't do most of the steps myself for Thrift, but I
can try to walk a committer through the process.
Christopher
On Wed, Oct 28, 2020 at 8:43 AM Duru Can Celasun <dc...@apache.org> wrote:
>
> Hi Andrew,
>
> The site on ReadTheDocs [1] isn't just documentation, it's the full website including downloads [2] so I'm not sure if any other static landing page is necessary.
>
> If you can clarify that first I'll go ahead and open an INFRA ticket.
>
> Can
>
> [1] https://thrift-fork.readthedocs.io/en/docs/index.html
> [2] https://thrift-fork.readthedocs.io/en/docs/download.html
>
> On Wed, 28 Oct 2020, at 12:35, Andrew Wetmore wrote:
> > Hi, Can:
> >
> > I spoke with Gavin MacDonald on our team, and he said the Thrift project
> > will still need at least a basic static landing page at thrift.a.o. If I
> > understand correctly, you can redirect traffic from there to what you have
> > set up in ReadTheDocs. The landing page should also have information on
> > links for downloading software releases.
> >
> > Gavin requested that you open a Jira ticket directed at Infra to cover the
> > project's migration so we can keep track of what we need to do to provide a
> > smooth transition for the project.
> >
> > Andrew
> >
> > On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> >
> > > Hi Andrew,
> > >
> > > Any news on this? How should we proceed?
> > >
> > > Cheers,
> > > Can
> > >
> > > On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > > > Hi Andrew,
> > > >
> > > > Sorry for the late response. Last year I started working on a migration
> > > > from Apache CMS to "read the docs" [1] but I never got a chance to
> > > > finish it.
> > > >
> > > > It's mostly complete, but we could definitely use some INFRA help to
> > > > get it over the finish line.
> > > >
> > > > Would it be possible to have a thrift-website repo on Github and have
> > > > it deployed via Travis?
> > > >
> > > > The linked issue has build instructions but I'd be happy to make
> > > > changes if needed.
> > > >
> > > > Please let me how you'd like to proceed.
> > > >
> > > > Cheers,
> > > > Can
> > > >
> > > > [1]
> > > >
> > > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> > > >
> > > > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > > > Hi:
> > > > >
> > > > > I wrote to you two weeks ago about your project website, but have not
> > > seen
> > > > > a response. Whom should I contact directly? I am trying to see whether
> > > your
> > > > > project still uses the Apache CMS and, if so, what your plans are to
> > > > > migrate off it.
> > > > >
> > > > > Thanks in advance for your help.
> > > > >
> > > > > Andrew
> > > > >
> > > > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> > > wrote:
> > > > >
> > > > > > Hi:
> > > > > >
> > > > > > I am part of the Infrastructure team, and am writing to ask whether
> > > your
> > > > > > project is still using the Apache CMS for your project website. As
> > > you
> > > > > > know, the CMS is reaching end-of-life, and we need projects to move
> > > their
> > > > > > websites onto a different option within the next few weeks.
> > > > > >
> > > > > > There are several alternatives available, including those listed on
> > > this
> > > > > > page [1] on managing project websites. Infra is assembling a Wiki
> > > page [2]
> > > > > > on migrating a website from the CMS, and is looking forward to
> > > helping
> > > > > > projects with this transition.
> > > > > >
> > > > > > Please let me know whether your site is still on the Apache CMS and,
> > > if
> > > > > > so, who will be the project point-of-contact with Infra for the
> > > migration.
> > > > > >
> > > > > > Thank you!
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > [1] https://infra.apache.org/project-site.html
> > > > > >
> > > > > > [2]
> > > > > >
> > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrew Wetmore
> > > > > > Technical Writer-Editor
> > > > > > Infra
> > > > > > *Apache Software Foundation*
> > > > > > andreww@apache.org
> > > > > >
> > > > > >
> > > > > > <
> > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > Virus-free.
> > > > > > www.avast.com
> > > > > > <
> > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > > >
> > > > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Andrew Wetmore
> > > > > Technical Writer-Editor
> > > > > Infra
> > > > > *Apache Software Foundation*
> > > > > andreww@apache.org
> > > > >
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andreww@apache.org
> >
Re: Your project's website
Posted by Duru Can Celasun <dc...@apache.org>.
Hi Andrew,
The site on ReadTheDocs [1] isn't just documentation, it's the full website including downloads [2] so I'm not sure if any other static landing page is necessary.
If you can clarify that first I'll go ahead and open an INFRA ticket.
Can
[1] https://thrift-fork.readthedocs.io/en/docs/index.html
[2] https://thrift-fork.readthedocs.io/en/docs/download.html
On Wed, 28 Oct 2020, at 12:35, Andrew Wetmore wrote:
> Hi, Can:
>
> I spoke with Gavin MacDonald on our team, and he said the Thrift project
> will still need at least a basic static landing page at thrift.a.o. If I
> understand correctly, you can redirect traffic from there to what you have
> set up in ReadTheDocs. The landing page should also have information on
> links for downloading software releases.
>
> Gavin requested that you open a Jira ticket directed at Infra to cover the
> project's migration so we can keep track of what we need to do to provide a
> smooth transition for the project.
>
> Andrew
>
> On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
>
> > Hi Andrew,
> >
> > Any news on this? How should we proceed?
> >
> > Cheers,
> > Can
> >
> > On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > > Hi Andrew,
> > >
> > > Sorry for the late response. Last year I started working on a migration
> > > from Apache CMS to "read the docs" [1] but I never got a chance to
> > > finish it.
> > >
> > > It's mostly complete, but we could definitely use some INFRA help to
> > > get it over the finish line.
> > >
> > > Would it be possible to have a thrift-website repo on Github and have
> > > it deployed via Travis?
> > >
> > > The linked issue has build instructions but I'd be happy to make
> > > changes if needed.
> > >
> > > Please let me how you'd like to proceed.
> > >
> > > Cheers,
> > > Can
> > >
> > > [1]
> > >
> > https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> > >
> > > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > > Hi:
> > > >
> > > > I wrote to you two weeks ago about your project website, but have not
> > seen
> > > > a response. Whom should I contact directly? I am trying to see whether
> > your
> > > > project still uses the Apache CMS and, if so, what your plans are to
> > > > migrate off it.
> > > >
> > > > Thanks in advance for your help.
> > > >
> > > > Andrew
> > > >
> > > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> > wrote:
> > > >
> > > > > Hi:
> > > > >
> > > > > I am part of the Infrastructure team, and am writing to ask whether
> > your
> > > > > project is still using the Apache CMS for your project website. As
> > you
> > > > > know, the CMS is reaching end-of-life, and we need projects to move
> > their
> > > > > websites onto a different option within the next few weeks.
> > > > >
> > > > > There are several alternatives available, including those listed on
> > this
> > > > > page [1] on managing project websites. Infra is assembling a Wiki
> > page [2]
> > > > > on migrating a website from the CMS, and is looking forward to
> > helping
> > > > > projects with this transition.
> > > > >
> > > > > Please let me know whether your site is still on the Apache CMS and,
> > if
> > > > > so, who will be the project point-of-contact with Infra for the
> > migration.
> > > > >
> > > > > Thank you!
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [1] https://infra.apache.org/project-site.html
> > > > >
> > > > > [2]
> > > > >
> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > > >
> > > > >
> > > > > --
> > > > > Andrew Wetmore
> > > > > Technical Writer-Editor
> > > > > Infra
> > > > > *Apache Software Foundation*
> > > > > andreww@apache.org
> > > > >
> > > > >
> > > > > <
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > Virus-free.
> > > > > www.avast.com
> > > > > <
> > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> > >
> > > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > >
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andreww@apache.org
> > > >
> > >
> >
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andreww@apache.org
>
Re: Your project's website
Posted by Andrew Wetmore <an...@apache.org>.
Hi, Can:
I spoke with Gavin MacDonald on our team, and he said the Thrift project
will still need at least a basic static landing page at thrift.a.o. If I
understand correctly, you can redirect traffic from there to what you have
set up in ReadTheDocs. The landing page should also have information on
links for downloading software releases.
Gavin requested that you open a Jira ticket directed at Infra to cover the
project's migration so we can keep track of what we need to do to provide a
smooth transition for the project.
Andrew
On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> Hi Andrew,
>
> Any news on this? How should we proceed?
>
> Cheers,
> Can
>
> On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > Hi Andrew,
> >
> > Sorry for the late response. Last year I started working on a migration
> > from Apache CMS to "read the docs" [1] but I never got a chance to
> > finish it.
> >
> > It's mostly complete, but we could definitely use some INFRA help to
> > get it over the finish line.
> >
> > Would it be possible to have a thrift-website repo on Github and have
> > it deployed via Travis?
> >
> > The linked issue has build instructions but I'd be happy to make
> > changes if needed.
> >
> > Please let me how you'd like to proceed.
> >
> > Cheers,
> > Can
> >
> > [1]
> >
> https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> >
> > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > Hi:
> > >
> > > I wrote to you two weeks ago about your project website, but have not
> seen
> > > a response. Whom should I contact directly? I am trying to see whether
> your
> > > project still uses the Apache CMS and, if so, what your plans are to
> > > migrate off it.
> > >
> > > Thanks in advance for your help.
> > >
> > > Andrew
> > >
> > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> wrote:
> > >
> > > > Hi:
> > > >
> > > > I am part of the Infrastructure team, and am writing to ask whether
> your
> > > > project is still using the Apache CMS for your project website. As
> you
> > > > know, the CMS is reaching end-of-life, and we need projects to move
> their
> > > > websites onto a different option within the next few weeks.
> > > >
> > > > There are several alternatives available, including those listed on
> this
> > > > page [1] on managing project websites. Infra is assembling a Wiki
> page [2]
> > > > on migrating a website from the CMS, and is looking forward to
> helping
> > > > projects with this transition.
> > > >
> > > > Please let me know whether your site is still on the Apache CMS and,
> if
> > > > so, who will be the project point-of-contact with Infra for the
> migration.
> > > >
> > > > Thank you!
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://infra.apache.org/project-site.html
> > > >
> > > > [2]
> > > >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andreww@apache.org
> > > >
> > > >
> > > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.
> > > > www.avast.com
> > > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andreww@apache.org
> > >
> >
>
--
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andreww@apache.org
Re: Your project's website
Posted by Andrew Wetmore <an...@apache.org>.
I'm not sure I saw your report before. If you sent it to the list I may
have missed it. Let me look into this and consult the team.
Andrew
On Sat, Oct 3, 2020 at 1:10 PM Duru Can Celasun <ca...@dcc.im> wrote:
> Hi Andrew,
>
> Any news on this? How should we proceed?
>
> Cheers,
> Can
>
> On Wed, 26 Aug 2020, at 16:38, Duru Can Celasun wrote:
> > Hi Andrew,
> >
> > Sorry for the late response. Last year I started working on a migration
> > from Apache CMS to "read the docs" [1] but I never got a chance to
> > finish it.
> >
> > It's mostly complete, but we could definitely use some INFRA help to
> > get it over the finish line.
> >
> > Would it be possible to have a thrift-website repo on Github and have
> > it deployed via Travis?
> >
> > The linked issue has build instructions but I'd be happy to make
> > changes if needed.
> >
> > Please let me how you'd like to proceed.
> >
> > Cheers,
> > Can
> >
> > [1]
> >
> https://issues.apache.org/jira/browse/THRIFT-4710?focusedCommentId=16972218&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16972218
> >
> > On Mon, 24 Aug 2020, at 14:06, Andrew Wetmore wrote:
> > > Hi:
> > >
> > > I wrote to you two weeks ago about your project website, but have not
> seen
> > > a response. Whom should I contact directly? I am trying to see whether
> your
> > > project still uses the Apache CMS and, if so, what your plans are to
> > > migrate off it.
> > >
> > > Thanks in advance for your help.
> > >
> > > Andrew
> > >
> > > On Fri, Aug 7, 2020 at 10:06 AM Andrew Wetmore <an...@apache.org>
> wrote:
> > >
> > > > Hi:
> > > >
> > > > I am part of the Infrastructure team, and am writing to ask whether
> your
> > > > project is still using the Apache CMS for your project website. As
> you
> > > > know, the CMS is reaching end-of-life, and we need projects to move
> their
> > > > websites onto a different option within the next few weeks.
> > > >
> > > > There are several alternatives available, including those listed on
> this
> > > > page [1] on managing project websites. Infra is assembling a Wiki
> page [2]
> > > > on migrating a website from the CMS, and is looking forward to
> helping
> > > > projects with this transition.
> > > >
> > > > Please let me know whether your site is still on the Apache CMS and,
> if
> > > > so, who will be the project point-of-contact with Infra for the
> migration.
> > > >
> > > > Thank you!
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://infra.apache.org/project-site.html
> > > >
> > > > [2]
> > > >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andreww@apache.org
> > > >
> > > >
> > > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.
> > > > www.avast.com
> > > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > > > <#m_3918189248972690169_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > > Technical Writer-Editor
> > > Infra
> > > *Apache Software Foundation*
> > > andreww@apache.org
> > >
> >
>
--
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andreww@apache.org