Re: Default webpages for new podlings

> On Apr 17, 2018, at 12:27 PM, Matt Sicker wrote: > > On 17 April 2018 at 13:47, Greg Stein wrote: > >> The easiest solution is to place your site source into Git, specifically as >> part of our "gitbox" program. That will allow for direct editing on >>

Re: Default webpages for new podlings

On 17 April 2018 at 13:47, Greg Stein wrote: > The easiest solution is to place your site source into Git, specifically as > part of our "gitbox" program. That will allow for direct editing on > github.com. When the edits are saved, then buildbot or jenkins can pick up > the

Re: Default webpages for new podlings

On Tue, Apr 17, 2018 at 11:51 AM, sebb wrote: > On 17 April 2018 at 19:47, Greg Stein wrote: >> On Mon, Apr 16, 2018 at 8:57 PM, Dave Fisher wrote: >>>... >> >>> Greg - You know which project I’m thinking about - OpenOffice.org. (1) I

Re: Default webpages for new podlings

On 17 April 2018 at 19:47, Greg Stein wrote: > On Mon, Apr 16, 2018 at 8:57 PM, Dave Fisher wrote: >>... > >> Greg - You know which project I’m thinking about - OpenOffice.org. (1) I >> can see a way to make Jekyll or something similar function for site

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 8:57 PM, Dave Fisher wrote: >... > Greg - You know which project I’m thinking about - OpenOffice.org. (1) I > can see a way to make Jekyll or something similar function for site > generation. Since I did the migration in I ought to be able to

Re: Default webpages for new podlings

Hi Matt, It's a little more complex than that. These are users who are often non-English speaking who want to translate plus the full site is about 9GB. No rush on things just need to discuss with PMC and think it over. See what is really happening now. Any change here is large, very large for

Re: Default webpages for new podlings

Can't you still provide patches a pull requests to the asf-site branch for example? Or to the docs source itself if it's generated. On 16 April 2018 at 20:57, Dave Fisher wrote: > Hi - > > Sent from my iPhone > > > On Apr 16, 2018, at 5:13 PM, Greg Stein

Re: Default webpages for new podlings

Hi - Sent from my iPhone > On Apr 16, 2018, at 5:13 PM, Greg Stein wrote: > > On Mon, Apr 16, 2018 at 10:21 AM, Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > >>> On Mon, Apr 16, 2018 at 4:39 PM, Matt Sicker wrote: >>> ...Most places I've

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 10:21 AM, Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Mon, Apr 16, 2018 at 4:39 PM, Matt Sicker wrote: > > ...Most places I've seen the CMS still in use was because of svnpubsub, > not > > necessarily cms.a.o. We use it to commit the

Re: Default webpages for new podlings

On 04/16/2018 07:14 PM, Gian Merlino wrote: Is there any ASF infra that would be usable for automatically running Jekyll on the master branch and pushing the results to the "asf-git" branch, where they can be served? Maybe CI/build infra, if we have that? It would provide an experience that is

Re: Default webpages for new podlings

Is there any ASF infra that would be usable for automatically running Jekyll on the master branch and pushing the results to the "asf-git" branch, where they can be served? Maybe CI/build infra, if we have that? It would provide an experience that is somewhat like GitHub pages. On Mon, Apr 16,

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 6:53 PM, Julian Hyde wrote: > ...The ASF infra just sees HTML, CSS style sheets and images... Yes, to be more precise in the standard gitpubsub setup it's only the asf-site branch of the Git repository that's published, without processing. It can even

Re: Default webpages for new podlings

Just to clarify, in case people are not familiar with Jekyll. It is a code generator that a developer runs in their sandbox, and it generates the site. The developer then checks in the site to git or svn. So, the developer has complete control over the HTML that is checked in. They can

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 4:39 PM, Matt Sicker wrote: > ...Most places I've seen the CMS still in use was because of svnpubsub, not > necessarily cms.a.o. We use it to commit the output from maven-site-plugin, > javadocs, scaladocs, etc. Am I confused here?... AFAIK both

Re: Default webpages for new podlings

Most places I've seen the CMS still in use was because of svnpubsub, not necessarily cms.a.o. We use it to commit the output from maven-site-plugin, javadocs, scaladocs, etc. Am I confused here? On 16 April 2018 at 07:27, John D. Ament wrote: > On Mon, Apr 16, 2018 at

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 7:04 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Mon, Apr 16, 2018 at 12:26 PM, John D. Ament > wrote: > > ...FWIW, Jekyll is pretty heavily used across projects > > Yes, it's good to have a suggested default for this. > >

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 12:26 PM, John D. Ament wrote: > ...FWIW, Jekyll is pretty heavily used across projects Yes, it's good to have a suggested default for this. OTOH the nice thing about the current setup is that people can use whatever tool they want to create

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 5:57 AM sebb wrote: > On 16 April 2018 at 10:39, Bertrand Delacretaz > wrote: > > On Mon, Apr 16, 2018 at 11:20 AM, sebb wrote: > >>... Podlings can create a simple page in Git/SVN, however it won't be > >>

Re: Default webpages for new podlings

On 16 April 2018 at 10:39, Bertrand Delacretaz wrote: > On Mon, Apr 16, 2018 at 11:20 AM, sebb wrote: >>... Podlings can create a simple page in Git/SVN, however it won't be >> displayed without some Infra setup to copy the html from the SCM to >>

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 11:20 AM, sebb wrote: >... Podlings can create a simple page in Git/SVN, however it won't be > displayed without some Infra setup to copy the html from the SCM to > the host... Granted but that's quite easy to do from the podling's side: just push the

Re: Default webpages for new podlings

On 16 April 2018 at 09:34, Bertrand Delacretaz wrote: > On Mon, Apr 16, 2018 at 8:50 AM, Greg Stein wrote: >> ...placeholder page. It should explain the situation. Provide links to >> the incubator and the podling status page, to the

Re: Default webpages for new podlings

On Mon, Apr 16, 2018 at 8:50 AM, Greg Stein wrote: > ...placeholder page. It should explain the situation. Provide links to > the incubator and the podling status page, to the original/external site, > disclaimer, etc. Just one page. Fast set up. Done... Yes, BIG +1 to this.

Re: Default webpages for new podlings

Sent from my iPhone >> On Apr 15, 2018, at 11:50 PM, Greg Stein wrote: >> >> On Sun, Apr 15, 2018 at 9:30 PM, Ted Dunning wrote: >> >> On Sun, Apr 15, 2018 at 12:37 PM, Dave Fisher >> wrote: >>> Hi - >>> >>> I think that a

Re: Default webpages for new podlings

On Sun, Apr 15, 2018 at 9:30 PM, Ted Dunning wrote: > On Sun, Apr 15, 2018 at 12:37 PM, Dave Fisher > wrote: > > Hi - > > > > I think that a brand compliant initial podling page would not be hard to > > create using the Apache CMS. > The CMS is

Re: Default webpages for new podlings

griffin is using the same tech for site generator. check the repo if you would like to https://github.com/apache/incubator-griffin-site Thanks, William On Mon, Apr 16, 2018 at 1:38 PM, Ted Dunning wrote: > Dave, > > You probably already know enough to use Jekyll. > >

Re: Default webpages for new podlings

Dave, You probably already know enough to use Jekyll. It is just a markdown to HTML translator. It is what github uses, as I remember. On Sun, Apr 15, 2018 at 8:31 PM, Dave Fisher wrote: > I’m always willing to learn new tools. > > Regards, > Dave > > Sent from my

Re: Default webpages for new podlings

On Sun, Apr 15, 2018 at 8:15 PM, Julian Hyde wrote: > Luciano created a Jekyll prototype a year or so ago. Let’s dust that off. > > Julian > > Here is the link: https://github.com/apache/apache-website-template -- Luciano Resende http://twitter.com/lresende1975

Re: Default webpages for new podlings

I’m always willing to learn new tools. Regards, Dave Sent from my iPhone > On Apr 15, 2018, at 8:15 PM, Julian Hyde wrote: > > Luciano created a Jekyll prototype a year or so ago. Let’s dust that off. > > Julian > >>> On Apr 15, 2018, at 19:30, Ted Dunning

Re: Default webpages for new podlings

Luciano created a Jekyll prototype a year or so ago. Let’s dust that off. Julian > On Apr 15, 2018, at 19:30, Ted Dunning wrote: > >> On Sun, Apr 15, 2018 at 12:37 PM, Dave Fisher wrote: >> >> Hi - >> >> I think that a brand compliant initial

Re: Default webpages for new podlings

On Sun, Apr 15, 2018 at 12:37 PM, Dave Fisher wrote: > Hi - > > I think that a brand compliant initial podling page would not be hard to > create using the Apache CMS. > The problem I have with that is that it encourages further use of CMS and also that CMS is hard for

Re: Default webpages for new podlings

A template paragraph of simple HTML seems ideal, and it’s reasonable to expect podlings to create it by the time of their first board report. A full branding-compliant web site is a more complex undertaking, and we the IPMC should not try to hurry that process. The podling's interests are

Re: Default webpages for new podlings

> This avoid unnecessary 404's for the project, and gives them some time to > move their infrastructure over. Once they have their website up and > running (either migrated or created from scratch) then they can switch the > redirect to point to their actual content. I have a (not necessarily

Re: Default webpages for new podlings

Hi - I think that a brand compliant initial podling page would not be hard to create using the Apache CMS. This could have two simple pages that would show a compliant examples: (1) Index page with all of the appropriate links to both podling Mailing lists, Download placeholder, Apache

Re: Default webpages for new podlings

I don't believe that linking to the status page would satisfy the website requirement, but solves the 404 issue. At least in my mind it wouldn't get them out of needing a website. I put out three months because that's that's the longest I've seen the bootstrapping to take. To make sure I'm

Re: Default webpages for new podlings

I think this is a great day one idea but by 3 months,.the project should be having a website to start that ball rolling. This might be too much of a crutch. On Sun, Apr 15, 2018, 11:10 John D. Ament wrote: > Based on some of the on going discussions, wanted to get

Default webpages for new podlings

Based on some of the on going discussions, wanted to get opinions on how to get podling websites bootstrapped a bit easier. When I review https://incubator.apache.org/guides/sites.html it seems pretty clear what we expect on a podling website. I'm wondering if during the bootstrapping phase