Thanks Taylor and others for the suggestions, and here are some fixes as following:
- Add download link in home page [1] - Fix git link to apache git-wip-us repository in eagle download page [2] - Add signatures (md5,asm, sha1) [3] and verification KEYS [4] [1] http://eagle.incubator.apache.org [2] http://eagle.incubator.apache.org/docs/download-latest.html [3] https://dist.apache.org/repos/dist/release/incubator/eagle/apache-eagle-0.4.0-incubating/ [4] https://dist.apache.org/repos/dist/release/incubator/eagle/KEYS - Hao On Thu, Dec 8, 2016 at 1:34 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > The main download page [1] is a little off, but shouldn’t be terribly hard > to fix. > > - The main download link correctly uses closer.cgi, but is missing links > to dist.a.o for the signatures/checksums and instructions on how to verify > the archive. > - The release notes link correctly links to git-wip-us.a.o. > - The git tag link incorrectly links to GitHub. It should link to the ASF > git repository. > - The git commit link also incorrectly links to GitHub. > > The last two aren’t required and could be removed or simply changed to > point to the right place. > > The signatures/checksums are in the right place on dist.a.o [2] so adding > links to them is fairly trivial. I’d also just change the GitHub link on > the home to be a download link. > > I would think the above issues could be addressed before the graduation > discussion completes. Post graduation I’d recommend a thorough review of > the website from an ASF branding perspective. > > -Taylor > > > [1] http://eagle.incubator.apache.org/docs/download-0.4.0.html < > http://eagle.incubator.apache.org/docs/download-0.4.0.html> > [2] https://dist.apache.org/repos/dist/release/incubator/eagle/ > apache-eagle-0.4.0-incubating/ > > > > On Dec 7, 2016, at 12:02 PM, Julian Hyde <jh...@apache.org> wrote: > > > > Looking a the home page http://eagle.incubator.apache.org/ < > http://eagle.incubator.apache.org/> I think that Eagle should make > Apache branding clearer for people who do not scroll down past the fold, > remove the prominent GitHub link, and add a “Download” button to a standard > download page with instructions on check-sums. > > > > I will make sure that this happens immediately after graduation. > > > > Julian > > > > > > > >> On Dec 7, 2016, at 4:30 AM, John D. Ament <johndam...@apache.org> > wrote: > >> > >> I believe this page is also relevant to what Stian's pointing out > >> http://www.apache.org/dev/release-download-pages.html#links > >> > >> I will say this line looks wrong on the page, and probably is missing a > >> "not" - which would preclude pointing to github for downloads (I added > the > >> *not*) > >> > >> Artifacts which are not full official releases (for example, milestones, > >> betas and alphas) may *not* be linked from the download page. Links to > >> these artifacts should be removed in a timely fashion. > >> > >> It is a bit odd that your downloads page is not linked from the > homepage, > >> but it is available within the docs. But that's an optimization not a > rule. > >> > >> On Wed, Dec 7, 2016 at 7:16 AM Stian Soiland-Reyes <st...@apache.org> > wrote: > >> > >>> This download page does not fully comply with the ASF distribution > policy, > >>> which says there should also be a link to the signature and > description of > >>> how to check it: > >>> > >>> http://eagle.incubator.apache.org/docs/download-0.4.0.html > >>> > >>> http://www.apache.org/dev/release-publishing.html#distribution_dist > >>> > >>> > >>> Is a direct link from front page to an ( implicitly "endorsed"?) > >>> third-party site GitHub (and no link to ASF downloads) OK according to > >>> policy? I would have included a traditional Download link - it's OK for > >>> that page to include both the source code and Maven coordinates, but I > >>> don't think we should encourage downstream to "download from GitHub" at > >>> this stage as it conflates what is a PMC-voted ASF release or not. > >>> > >>> On 6 Dec 2016 11:22 pm, "Roman Shaposhnik" <ro...@shaposhnik.org> > wrote: > >>> > >>>> On Tue, Dec 6, 2016 at 3:06 PM, Henry Saputra < > henry.sapu...@gmail.com> > >>>> wrote: > >>>>> HI Roman, John, > >>>>> > >>>>> Most of the mentors have full plate to do and especially need to help > >>>>> existing podling to be successful in incubator. > >>>>> > >>>>> Taylor has been very gracious to stay as initial member of PMCs, so > >>>>> we have 1 ASF member, which I think good enough and will be seed to > >>>>> invite more Apache Eagle PMCs to be ASF member. > >>>>> > >>>>> Other than that, I don't the the current members should have good > >>>>> level of diversity. > >>>>> > >>>>> If you looked at Apache Geode when it proposed for graduation, it has > >>>>> 22 PMCs from Pivotal only one or two from different orgs. > >>>> > >>>> The majority of podlings that come as projects from a single vendor > >>>> struggle > >>>> with PMC diversity. But this gives them even more of a reason to come > up > >>>> with creative ways to mitigate it. This is exactly what Geode had to > >>> think > >>>> about > >>>> and I hope Eagle will think about as well. > >>>> > >>>>> ALL mentors in Eagle believe that the community have been operating > in > >>>>> the Apache way, create releases, invite new committers, and follow > all > >>>>> communications in Apache resources. > >>>> > >>>> Good to know! The mentor's vouching for it helps me a lot. > >>>> > >>>> Quick question to the community: why is there no way to download > releases > >>>> of the software that are linked from the > http://eagle.incubator.apache. > >>>> org/ ? > >>>> Is GitHub being treated as the way to distribute it? > >>>> > >>>> Thanks, > >>>> Roman. > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>> For additional commands, e-mail: general-h...@incubator.apache.org > >>>> > >>>> > >>> > > > >
