Re: Issues with Apache Impala (incubating) website
> Almost. It really would be better to spell it explicitly (and avoid a phrase > Cloudera's Hadoop distribution -- since this is something ASF is not > looking too kindly on as per http://www.apache.org/foundation/marks/) > > I'd suggest something along the lines: >"Documentation for previous versions of Impala in CDH" Done.
RE: Issues with Apache Impala (incubating) website
Cloudera has already transferred all the Impala marks to Apache. The marks are owned by Apache at this point. *From:* Jim Apple [mailto:jbap...@cloudera.com] *Sent:* Tuesday, September 20, 2016 4:03 PM *To:* dev@impala <dev@impala.incubator.apache.org> *Cc:* r...@apache.org; John Russell <jruss...@cloudera.com>; Laurel Hale < lau...@cloudera.com>; David Middler <dmidd...@cloudera.com> *Subject:* Re: Issues with Apache Impala (incubating) website Roman, thank you for taking the time to write to us. Oddly, just as you were sending this, I was resolving https://issues.cloudera.org/browse/IMPALA-4068 with this commit https://github.com/apache/incubator-impala/commit/90ffefd1140e3fcfbbdc26496a7e177eb752ae1c It removes the links to download, install, try as VM, try as Docker, and try in cloud. We have started migrating our docs to ASF, though John and Laurel (cced) have not finished yet. Their organizing JIRA is here: https://issues.cloudera.org/browse/IMPALA-3398 In the meantime, the commit above changed the docs link to be a page about available documentation. This page includes a link to the Cloudera docs, but it calls them out as such. Does that meet the guidelines, in your opinion? The guidelines do allow "links to external documentation". As far as the docs saying "Apache Impala (incubating)", I have cc:ed David Middler, a lawyer for Cloudera. I am not a lawyer and I do not quite understand what words one should use to refer to this Impala thing between the TM transfer and the first release - "Cloudera Impala"? just "Impala"? The patch I linked to above also changes the github link to point to the Apache github repo for Impala. I think that touches on each of the issues you raised. Thanks again, Jim On Tue, Sep 20, 2016 at 3:43 PM, Roman Shaposhnik <r...@apache.org> wrote: Hi! while reviewing Impala website http://impala.incubator.apache.org/ I've come across a few issues that need to be corrected soon in order to get the site in line with ASF branding guidelines for podling websites: http://incubator.apache.org/guides/sites.html First of all, since your community hasn't had a single release yet, you need to get rid of Dowload (at the top) Install Try as VM Try as Docker Image Try in the Cloud buttons since they all point to something that clearly has no relationship to Apache Impala (incubating) and is very confusing to the users who may assume that these are links to official releases. I also suggest that you start migrating your docs to ASF and get rid of Docs button linking to cloudera.com published Impala Docs. If you click on that Docs link it says (at the top of the page) This is the documentation for Cloudera Enterprise 5.8.x. and then it proceeds to talk about Apache Impala (incubating). This is misleading for the same reasons -- there's no such thing as publicly available Apache Impala (incubating) until you have your first release. Contribute and Git Hub buttons at the top still point to Cloudera's GitHub. This has to change ASAP. Please CC me directly if you have any further questions. I'm not subscribed to this mailing list. Thanks, Roman.
Re: Issues with Apache Impala (incubating) website
On Tue, Sep 20, 2016 at 4:02 PM, Jim Applewrote: > Roman, thank you for taking the time to write to us. > > Oddly, just as you were sending this, I was resolving > > https://issues.cloudera.org/browse/IMPALA-4068 > > with this commit > > https://github.com/apache/incubator-impala/commit/90ffefd1140e3fcfbbdc26496a7e177eb752ae1c > > It removes the links to download, install, try as VM, try as Docker, and try > in cloud. Odd indeed. But also kind of fun. This is the fastest any podling reacted to my feedback ;-) The website looks much better now. > We have started migrating our docs to ASF, though John and Laurel (cced) > have not finished yet. Their organizing JIRA is here: > > https://issues.cloudera.org/browse/IMPALA-3398 Great! > In the meantime, the commit above changed the docs link to be a page about > available documentation. This page includes a link to the Cloudera docs, but > it calls them out as such. Does that meet the guidelines, in your opinion? > The guidelines do allow "links to external documentation". Almost. It really would be better to spell it explicitly (and avoid a phrase Cloudera's Hadoop distribution -- since this is something ASF is not looking too kindly on as per http://www.apache.org/foundation/marks/) I'd suggest something along the lines: "Documentation for previous versions of Impala in CDH" > As far as the docs saying "Apache Impala (incubating)", I have cc:ed David > Middler, a lawyer for Cloudera. I am not a lawyer and I do not quite > understand what words one should use to refer to this Impala thing between > the TM transfer and the first release - "Cloudera Impala"? just "Impala"? The confusion was due to the context -- that link pretending to be an official Apache Impala (incubating) documentation. I think with the clarification we're talking above -- your doc usage is fine now. > The patch I linked to above also changes the github link to point to the > Apache github repo for Impala. > > I think that touches on each of the issues you raised. Indeed! Still, perhaps you can take one extra suggestions I've articulated above. Thanks, Roman.
Re: Issues with Apache Impala (incubating) website
Roman, thank you for taking the time to write to us. Oddly, just as you were sending this, I was resolving https://issues.cloudera.org/browse/IMPALA-4068 with this commit https://github.com/apache/incubator-impala/commit/90ffefd1140e3fcfbbdc26496a7e177eb752ae1c It removes the links to download, install, try as VM, try as Docker, and try in cloud. We have started migrating our docs to ASF, though John and Laurel (cced) have not finished yet. Their organizing JIRA is here: https://issues.cloudera.org/browse/IMPALA-3398 In the meantime, the commit above changed the docs link to be a page about available documentation. This page includes a link to the Cloudera docs, but it calls them out as such. Does that meet the guidelines, in your opinion? The guidelines do allow "links to external documentation". As far as the docs saying "Apache Impala (incubating)", I have cc:ed David Middler, a lawyer for Cloudera. I am not a lawyer and I do not quite understand what words one should use to refer to this Impala thing between the TM transfer and the first release - "Cloudera Impala"? just "Impala"? The patch I linked to above also changes the github link to point to the Apache github repo for Impala. I think that touches on each of the issues you raised. Thanks again, Jim On Tue, Sep 20, 2016 at 3:43 PM, Roman Shaposhnikwrote: > Hi! > > while reviewing Impala website > http://impala.incubator.apache.org/ > > I've come across a few issues that need > to be corrected soon in order to get the site > in line with ASF branding guidelines for podling > websites: > http://incubator.apache.org/guides/sites.html > > First of all, since your community hasn't had a single > release yet, you need to get rid of >Dowload (at the top) >Install >Try as VM >Try as Docker Image >Try in the Cloud buttons > since they all point to something that clearly has no > relationship to Apache Impala (incubating) and is > very confusing to the users who may assume that > these are links to official releases. > > I also suggest that you start migrating your docs to > ASF and get rid of Docs button linking to cloudera.com > published Impala Docs. If you click on that Docs link > it says (at the top of the page) >This is the documentation for Cloudera Enterprise 5.8.x. > and then it proceeds to talk about Apache Impala (incubating). > This is misleading for the same reasons -- there's no such > thing as publicly available Apache Impala (incubating) > until you have your first release. > > Contribute and Git Hub buttons at the top still point to > Cloudera's GitHub. This has to change ASAP. > > Please CC me directly if you have any further questions. I'm not > subscribed to this mailing list. > > Thanks, > Roman. >