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 quickly). What I do believe though is that our branding requirements would propagate over to that website as well (which it sounds like Druid has a bit wrong, at least in my take).
- Redirecting to another website that's hosting your docs doesn't remove the need for proper naming, so it should be Apache Druid (incubating) or Apache PageSpeed (incubating) upon first entry. - Even if the website is hosted elsewhere, I still expect to see the disclaimer. - The downloads page should indicate these are not Apache releases. Perhaps Mark T has some more input on the branding and naming aspects. John On Sat, Apr 14, 2018 at 12:02 AM Julian Hyde <jhyde.apa...@gmail.com> wrote: > I (as a Druid mentor) suggested the placeholder page, for the exact > reasons Greg describes. Short term, I promise, and better than a 404. > > Julian > > > On Apr 13, 2018, at 20:15, Greg Stein <gst...@gmail.com> wrote: > > > > One step at a time. If they want to throw a single page up *today* rather > > than wait six weeks to fully port their website... I would take the page. > > We already had an inquiry on Druid of where their site is. > > > > A placeholder is better than a 404. Unless, of course, you are personally > > volunteering to quickly move their entire site and workflow... ? > > > > Cheers, > > -g > > > > > >> On Fri, Apr 13, 2018, 22:03 John D. Ament <johndam...@apache.org> > wrote: > >> > >> Gian, Otto, > >> > >> I can tell you that the proposed plan from Druid is not an OK plan from > my > >> perspective. One of your short term goals should be moving > infrastructure > >> over to the ASF. This includes moving your website over. Redirecting > your > >> ASF webpage to your old webpage will not fly. > >> > >> While we can't give the same level of support as you would see on github > >> pages (maybe we'll get there one day), setting up builds in Jenkins or > >> Buildbot is pretty straight forward. Even the incubator website runs in > >> this model. > >> > >> It's perfectly acceptable to link to pre-Apache releases on your > website. > >> I'm not sure if any of the docs lead you to believe otherwise, but this > is > >> a fine thing to do. They just need to be clearly marked as not Apache > >> releases. > >> > >> The disclaimer that we request is meant to be shown on all pages of the > >> podling's website. Not just the landing page. If these are user facing > >> documents, then they must have the disclaimer on them. > >> > >> John > >> > >>> On Fri, Apr 13, 2018 at 5:42 PM Gian Merlino <g...@imply.io> wrote: > >>> > >>> Hi Otto, > >>> > >>> I am just another podling committer, so this isn't authoritative > advice, > >>> but for Druid's incubating page we are planning to put up a placeholder > >>> page with a link to the current community site. It isn't up yet, but > the > >>> html we are planning to use is here: > >>> > >> > https://github.com/apache/incubator-druid-website/blob/asf-site/index.html > >>> > >>> Our rationale was: > >>> > >>> 1) Before the site is migrated, it's better to have a placeholder than > a > >>> 404. > >>> 2) A placeholder with a link can make it more clear that the releases > on > >>> druid.io are not Apache releases. > >>> 3) A placeholder helps satisfy the requirement that podling web sites > >> must > >>> have an incubation disclaimer ( > >>> https://incubator.apache.org/guides/branding.html). > >>> > >>> When we migrate the community site to Apache infra then it would > replace > >>> the placeholder. > >>> > >>> Gian > >>> > >>> On Fri, Apr 13, 2018 at 2:09 PM, Otto van der Schaaf < > osch...@apache.org > >>> > >>> wrote: > >>> > >>>> Hi all, > >>>> > >>>> Currently pagespeed.incubator.apache.org responds with a 404, which > >>> isn't > >>>> very nice. > >>>> > >>>> So now we are wondering if there are any concerns with issueing a > >>> temporary > >>>> redirect to > >>>> modpagespeed.com. > >>>> > >>>> One concern could be that modpagespeed.com links to code / releases > >> that > >>>> have not yet been > >>>> through the formal Apache release process. Would explicitly mentioning > >>> that > >>>> fact > >>>> be sufficient to address it? > >>>> > >>>> I would be grateful for any input / guidance on this topic. > >>>> > >>>> Kind regards, > >>>> > >>>> Otto > >>>> > >>> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
