On 12/21/18 1:14 AM, Jordan Zimmerman wrote:
I believe the JClouds download page is _not_ in compliance. Curator was
just told:
Also the page links directly to
http://www.apache.org/dyn/closer.cgi/curator/
This is not allowed.
Why would that not be allowed? That's exactly what we want you to do.
The one thing we *don't* allow is linking to www.a.o/dist/curator/... as
that's intended for fallback purposes.
The JClouds download page has a direct link to the "closer" (
https://www.apache.org/dyn/closer.cgi/jclouds/). Or am I missing
understanding something (wouldn't be a surprise)?
-JZ
On Thu, Dec 20, 2018 at 5:57 PM Ignasi Barrera <n...@apache.org> wrote:
We had the same issue recently in jclouds. Although I can't speak for the
minimum set of concrete links required, you may find our page useful:
Page: https://jclouds.apache.org/start/install/
Source:
https://github.com/jclouds/jclouds-site/blob/master/start/install.md
HTH,
I.
On Thu, Dec 20, 2018, 23:36 Jordan Zimmerman <randg...@apache.org wrote:
Hi Folks,
Maybe it's just me but I've been having a heck of a time getting the
Apache
Curator download page to conform to spec. A template with correct links
(with simple replacements for project name and version) would be
very helpful. I've been using other project download pages as a guide but
apparently many of those don't conform either.
I realize there is
https://www.apache.org/dev/release-distribution#download-links but
that's
rather thin. At minimum that section can be expanded with examples of
each
link that must be on a download page. I'd be willing to do this though I
haven't yet succeeded in getting Curator's page to conform so I need help
here.
Comments/advice appreciated,
Jordan Zimmerman
PMC Chair
Apache Curator
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
