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: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

I like the idea of generating a placeholder for a podling on incubation. It can serve many purposes. See the other thread. I don’t think time limits like three months works as some podlings wait more than six months for all of their SGAs. Regards, Dave > On Apr 15, 2018, at 10:26 AM, Greg

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: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

Exactly. Nobody ever mentioned "redirect". Gian's original email said "placeholder" five times. On Sun, Apr 15, 2018, 10:15 Gian Merlino wrote: > Hi John, > > What we were thinking in Druid is that we want to have _something_ up on > http://druid.incubator.apache.org/, but it

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

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

Hi Gian, Knowing that you're waiting on SGAs explains this a bit better. I have an inquiry out to press to confirm what's expected (since I know that's why everyone's reacting to websites right now). I would recommend podlings review the Branding guide, there's important tidbits

Re: Are MySQL driver and MySQL protocol allowed in distribution?

Yes, MySQL will be an optional feature. And only required by a few people. So, asking them to download is good enough. I will share this solution to the community. Sheng Wu ---Original--- From: "sebb" Date: Fri, Apr 13, 2018 21:36 PM To:

RE: Are MySQL driver and MySQL protocol allowed in distribution?

The simple rule, in standards or in open source, is: Incorporate by Reference not by Inclusion. All else is details. -Original Message- From: William Guo [mailto:gu...@apache.org] Sent: Sunday, April 15, 2018 8:44 AM To: general@incubator.apache.org Subject: Re: Are MySQL driver and

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

Hi John, What we were thinking in Druid is that we want to have _something_ up on http://druid.incubator.apache.org/, but it didn't seem appropriate to move over the full site before the SGA & CLAs have all been finalized (those are in progress). So we put up a temporary placeholder. IMO, a

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

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

On Sun, Apr 15, 2018 at 10:08 AM sebb wrote: > On 15 April 2018 at 14:48, Greg Stein wrote: > > It is unreasonable to assume a podling can do everything on Day One. > > > > Incubation is a *process*, not an instantaneous production of effort. > > > > While

Re: [VOTE] Release of Apache Griffin-0.2.0-incubating [RC3]

On Sun, Apr 15, 2018 at 07:39, William Guo wrote: > that means if we cannot have category X dependencies in our source release, > but for category B, since we don't bundled in our source release, so it is > fine. That’s correct. > > Correct me if I am wrong. > > Thanks, >

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

On Sun, Apr 15, 2018 at 9:48 AM Greg Stein wrote: > It is unreasonable to assume a podling can do everything on Day One. > > There's nothing about my email that says this needs to be done on day one. > Incubation is a *process*, not an instantaneous production of effort. > >

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

On 15 April 2018 at 14:48, Greg Stein wrote: > It is unreasonable to assume a podling can do everything on Day One. > > Incubation is a *process*, not an instantaneous production of effort. > > While the website work is being performed, having > podling.incubator.apache.org NOT

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

It is unreasonable to assume a podling can do everything on Day One. Incubation is a *process*, not an instantaneous production of effort. While the website work is being performed, having podling.incubator.apache.org NOT produce a 404 is useful. Having that page describe the podling is in the

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

My input is a point for pagespeed to consider. Personally, I'm not comfortable with what's proposed by Druid but it's not worth muddying up pagespeed's inquiry. My preference is for a podling to get their website moved over quickly (and we need to figure out how to help them make that move

Re: Are MySQL driver and MySQL protocol allowed in distribution?

Thanks for the explanation. William On Fri, Apr 13, 2018 at 9:36 PM, sebb wrote: > On 13 April 2018 at 11:26, Karl Wright wrote: > > You can't distribute the MySQL driver, but as long as you don't > distribute > > the driver, you are free to solve the

Re: [VOTE] Release of Apache Griffin-0.2.0-incubating [RC3]

that means if we cannot have category X dependencies in our source release, but for category B, since we don't bundled in our source release, so it is fine. Correct me if I am wrong. Thanks, William On Fri, Apr 13, 2018 at 11:58 PM, Matt Sicker wrote: > On 13 April 2018 at