Looks much better, thanks. Someone should update the twitter account's description now that goeagle.io has gone away: https://twitter.com/TheApacheEagle.
On Mon, Aug 1, 2016 at 2:16 AM, Michael Wu <[email protected]> wrote: > Hi there, > > Ticket Eagle-380 is closed, and eagle site has been updated with all the > modifications. This time, in pages, we add footnotes to indicate some words > representing Apache projects, such as "hadoop", "hbase", "storm", etc, and > tag the corresponding footnote number at the top-right corner of these > words for readers to refer to. The reason we use this approach is that it > not only claims the branding of Apache, but also keeps the best readability > of the entire documentation tree. > > BTW, in this update, we also move Disclaimer up to the middle of the home > page so that it's easier to be found. > > If convenient, please help review it at: https://eagle.incubator.apache.org/ > and https://eagle.incubator.apache.org/docs/. > > @Julian, the "fork me on github" has been removed, and we are working on > the task to cite steps on readme file into development-quick-quide page. > > > Anything missed, please do let me know. Thanks. > > Michael > > On Wed, Jul 20, 2016 at 4:22 AM, Julian Hyde <[email protected]> wrote: > >> I’ve replied to the JIRA ticket. Let’s move the conversation there. >> >> > On Jul 19, 2016, at 12:43 AM, Michael Wu <[email protected]> wrote: >> > >> > @ Julian, or you may give your further comments on ticket EAGLE-380 >> > <https://issues.apache.org/jira/browse/EAGLE-380>. Thanks. >> > >> > On Tue, Jul 19, 2016 at 3:28 PM, Michael Wu <[email protected]> wrote: >> > >> >> Hi Julian, >> >> >> >> Could you take a look at the 1st (disclaimer more prominent) and 3rd >> >> (remove forking flag) topic in the last sending, please? I may need your >> >> confirmation to make it clear in my mind, thanks a lot! >> >> >> >> Michael >> >> >> >> On Mon, Jul 18, 2016 at 5:09 PM, Michael Wu <[email protected]> wrote: >> >> >> >>> @Julian, >> >>> >> >>> (copy my reply from another thread and paste it as below) >> >>> >> >>> Just copy your comments here and adding my comments. Thank you for the >> >>> suggestions. >> >>> >> >>> [Julian] - Also, make the disclaimer more prominent on the front page. >> It >> >>> is buried at the bottom of a very long page. I think it should appear >> in >> >>> the first screen-full. >> >>> [Michael] - a find an example from Apache Blur Incubating, do you mean >> >>> something similar to its disclaimer appears on front page? Such as: >> >>> http://incubator.apache.org/blur/. >> >>> >> >>> [Julian] - In the docs, qualify all Apache projects with Apache. I >> think >> >>> you can skip "Apache" in the tag line "Secure Hadoop in real time" but >> you >> >>> must acknowledge trademarks. >> >>> [Michael] - >> >>> 1. in the new site doc, I have added "Apache" preceding first mention >> of >> >>> "eagle" on every page, and commented the following "Eagle" on the page >> is >> >>> pointing to "Apache Eagle (incubating)". >> >>> 2. "acknowledge trademarks", do you mean the trademarks of "hadoop". >> If I >> >>> understand right, the "tag line" you mentioned has been modified, it >> would >> >>> never mention "Hadoop" again. >> >>> >> >>> [Julian] - In the docs, remove "fork me on github" from the top right >> >>> corner. The call to action is to join the Apache community. >> >>> [Michael] - Not quite clear with this tip. I'm wondering, where is the >> >>> appropriate position for us to place the "forking" element on the >> page? As >> >>> least, people may contribute by firstly forking a git repository. Do >> you >> >>> think the top-nav tag bar is good to add forking components? >> >>> >> >>> >> >>> Thanks. >> >>> Michael >> >>> >> >>> On Mon, Jul 18, 2016 at 4:02 PM, Julian Hyde <[email protected]> wrote: >> >>> >> >>>> I added the following comments to the JIRA case: >> >>>> >> >>>> * Also, make the disclaimer more prominent on the front page. It is >> >>>> buried at the bottom of a very long page. I think it should appear in >> the >> >>>> first screen-full. >> >>>> >> >>>> * Apply these guidelines throughout the site, in particular to the >> docs, >> >>>> https://eagle.incubator.apache.org/docs/. >> >>>> >> >>>> * In the docs, qualify all Apache projects with Apache. I think you >> can >> >>>> skip "Apache" in the tag line "Secure Hadoop in real time" but you >> must >> >>>> acknowledge trademarks. >> >>>> >> >>>> * In the docs, remove "fork me on github" from the top right corner. >> The >> >>>> call to action is to join the Apache community. >> >>>> >> >>>> Julian >> >>>> >> >>>>> On Jul 17, 2016, at 8:32 PM, Michael Wu <[email protected]> wrote: >> >>>>> >> >>>>> BTW, here is a jira ticket for trying to fix this issue: EAGLE-380 >> >>>>> <https://issues.apache.org/jira/browse/EAGLE-380>. It'll be thankful >> >>>> to see >> >>>>> your comments on it. :) >> >>>>> >> >>>>> On Mon, Jul 18, 2016 at 11:29 AM, Michael Wu <[email protected]> >> >>>> wrote: >> >>>>> >> >>>>>> Hi guys, >> >>>>>> >> >>>>>> To my understanding on your suggestions, we could modify our docs in >> >>>> the >> >>>>>> following ways, please help review if they are satisfying the >> request: >> >>>>>> 1. if "eagle" is in doc page title, change it to "Apache Eagle >> >>>>>> (incubating)". >> >>>>>> 2. if there are many "eagle"s appear in the doc page content, change >> >>>> the >> >>>>>> first mention of it to "Apache Eagle (incubating, called Eagle in >> the >> >>>>>> following)". >> >>>>>> 3. change logo size or position. >> >>>>>> >> >>>>>> Anything missed, please DO correct me. Thanks. >> >>>>>> Michael >> >>>>>> >> >>>>>> >> >>>>>> On Thu, Jun 30, 2016 at 11:05 PM, Henry Saputra < >> >>>> [email protected]> >> >>>>>> wrote: >> >>>>>> >> >>>>>>> Yeah, thinking moving the link and incubator logo up in the header >> >>>> and >> >>>>>>> keep >> >>>>>>> the incubator disclaimer as footer. >> >>>>>>> >> >>>>>>> Also move some content in between to separate page to make visitor >> >>>> scroll >> >>>>>>> less for homepage. >> >>>>>>> >> >>>>>>> Thoughts? >> >>>>>>> >> >>>>>>> - Henry >> >>>>>>> >> >>>>>>> On Thu, Jun 30, 2016 at 6:31 PM, John D. Ament < >> >>>> [email protected]> >> >>>>>>> wrote: >> >>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> On 2016-06-29 20:48 (-0400), Henry Saputra < >> [email protected] >> >>>>> >> >>>>>>>> wrote: >> >>>>>>>>> Probably we could move this section to Powered By Eagle page so >> >>>>>>> homepage >> >>>>>>>>> could be more clear it is part of ASF and also include Incubator >> >>>>>>>>> description on top of page. >> >>>>>>>> >> >>>>>>>> So you're thinking about moving some of the ASF logos up, not >> >>>> buried in >> >>>>>>>> the footer? >> >>>>>>>> >> >>>>>>>>> >> >>>>>>>>> On Thursday, June 30, 2016, arunkarthick m < >> [email protected] >> >>>>> >> >>>>>>>> wrote: >> >>>>>>>>> >> >>>>>>>>>> The eBay logo and Paypal logo under who uses Eagle part is >> taking >> >>>> up >> >>>>>>>> too >> >>>>>>>>>> much screen space. Apart from that ebay is mentioned only in one >> >>>>>>> place. >> >>>>>>>>>> >> >>>>>>>>>> Thanks, >> >>>>>>>>>> Arun >> >>>>>>>>>> >> >>>>>>>>>> On Wed, Jun 29, 2016 at 2:40 PM, Julian Hyde <[email protected] >> >>>>>>>>>> <javascript:;>> wrote: >> >>>>>>>>>> >> >>>>>>>>>>> Check what the branding guide says. I think only the first >> >>>>>>> occurrence >> >>>>>>>>>>> needs to be fully-qualified. >> >>>>>>>>>>> >> >>>>>>>>>>> But also ask yourself: Does this page make it look like the >> >>>>>>> project >> >>>>>>>> is >> >>>>>>>>>>> controlled by a particular company? >> >>>>>>>>>>> >> >>>>>>>>>>>> On Jun 29, 2016, at 1:57 PM, arunkarthick m < >> >>>>>>>> [email protected] >> >>>>>>>>>> <javascript:;>> >> >>>>>>>>>>> wrote: >> >>>>>>>>>>>> >> >>>>>>>>>>>> There are lots of places where we mentioned "Eagle". We need >> to >> >>>>>>>> change >> >>>>>>>>>>> them >> >>>>>>>>>>>> to be Apache Eagle. >> >>>>>>>>>>>> >> >>>>>>>>>>>> Thanks, >> >>>>>>>>>>>> Arun >> >>>>>>>>>>>> >> >>>>>>>>>>>> On Wed, Jun 29, 2016 at 11:52 AM, arun karthick manoharan < >> >>>>>>>>>>>> [email protected] <javascript:;>> wrote: >> >>>>>>>>>>>> >> >>>>>>>>>>>>> I'm looking at the branding guide will send what I find. >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> Thanks, >> >>>>>>>>>>>>> Arun >> >>>>>>>>>>>>> >> >>>>>>>>>>>>> Sent from my iPhone >> >>>>>>>>>>>>> >> >>>>>>>>>>>>>> On Jun 29, 2016, at 11:15 AM, Hao Chen <[email protected] >> >>>>>>>>>> <javascript:;>> wrote: >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>> Will continue to verify and update the fix. >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>> - Hao >> >>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> On Wed, Jun 29, 2016 at 10:21 AM, Julian Hyde < >> >>>>>>> [email protected] >> >>>>>>>>>> <javascript:;>> >> >>>>>>>>>>> wrote: >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> Did you find any other violations of branding policy? >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> On Jun 29, 2016, at 10:13 AM, Hao Chen <[email protected] >> >>>>>>>>>> <javascript:;>> wrote: >> >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> Updated with (incubating), thanks for advising. >> >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>> - Hao >> >>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>> On Wed, Jun 29, 2016 at 9:48 AM, Julian Hyde < >> >>>>>>>> [email protected] >> >>>>>>>>>> <javascript:;>> >> >>>>>>>>>>>>> wrote: >> >>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>> There is a discussion on general@incubator about >> podlings’ >> >>>>>>>> web >> >>>>>>>>>>> sites >> >>>>>>>>>>>>>>> and >> >>>>>>>>>>>>>>>>> URLs, and Eagle came in for some criticism. Can someone >> >>>>>>> please >> >>>>>>>>>>> review >> >>>>>>>>>>>>>>> the >> >>>>>>>>>>>>>>>>> site for compliance with Apache’s branding guidelines for >> >>>>>>>>>> podlings? >> >>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>> For instance, the first mention of Eagle on each page >> must >> >>>>>>> be >> >>>>>>>>>>> followed >> >>>>>>>>>>>>>>> by >> >>>>>>>>>>>>>>>>> “(incubating)”, and that does not happen. There may be >> >>>>>>> other >> >>>>>>>>>>>>> violations >> >>>>>>>>>>>>>>>>> too. During incubation we are looking to see whether the >> >>>>>>> PPMC >> >>>>>>>> is >> >>>>>>>>>>>>>>> capable of >> >>>>>>>>>>>>>>>>> proactively enforcing the Apache brand. >> >>>>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>>>> Julian >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>>>> >> >>>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> -- >> >>>>>>>>>>>> Arun Karthick >> >>>>>>>>>>>> 201-850-9399 >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> -- >> >>>>>>>>>> Arun Karthick >> >>>>>>>>>> 201-850-9399 >> >>>>>>>>>> >> >>>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>> >> >>>> >> >>> >> >> >> >>
