The principle behind the policy is not ridiculous. AIUI, it is important that the general public only downloads artifacts that the PMC has approved as an act of the foundation, otherwise the foundation's ability to provide a legal shield for release managers is weakened.
I mostly agree that the way the word "might" in the policy is being interpreted is "ridiculous". I really don't think the general public is being encouraged to download our nightly builds the way the current site reads. However, both Justin and I warned about the wording on the download page [1] before it went live because we've seen other projects get disrupted by similar nitpicking. AFAICT, the trend at the ASF is to continue to be more restrictive about the word "might" and make it harder to find links to nightly builds on project websites. Other projects that used to have links or links "below the fold" no longer do when I went looking just now. It won't be worth it to fight it, so let's just plan on changing. I see other projects with separate pages, but there is always a chance that someday the word "might" will be restricted even more to include separate pages. I'm not making the changes to the site, so I'll leave it up to those who are doing the work to decide. IMO, with that in mind, when I look at the current site, it is almost entirely tuned towards our users. The only place we invite folks to contribute is way down on the landing page. And the page that takes you to is about mailing lists. I guess you could say that the GitHub link is an implied indicator that we're an open source project and that you should contribute. So, here are my ideas. Feel free to reject them all: 1) Move the nightly build portion of the download page to a wiki page in GitHub. 2) Add a "Get Involved" or "Contributing" menu item similar to what Harbs suggested that goes to a different page like Andrew suggested 3) Replace the GitHub menu item with the "Get Involved" or "Contributing" menu item 4) Add analytics to the nightly build links so we can see how many people click it 5) Add a popup to the link to the nightly build so folks must agree to the disclaimers. I recommend that we just do #1 and move on. We've got plenty of other things to work on. My 2 cents, -Alex [1] https://lists.apache.org/thread.html/8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53@%3Cdev.royale.apache.org%3E On 10/16/19, 7:08 AM, "Josh Tynjala" <joshtynj...@bowlerhat.dev> wrote: Hopefully a separate public page is allowed. What a ridiculous policy! -- Josh Tynjala Bowler Hat LLC <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev&data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112&sdata=KCzYsqmguuSBdHlWZEq7V%2FgPmPMOa2pw9LFaxyZBTEo%3D&reserved=0> On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore <cottag...@gmail.com> wrote: > Can they have their own dedicated page, wreathed around with cautions and > disclaimers to scare away folks who should not be using them? > > On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira <carlosrov...@apache.org> > wrote: > > > Hi, > > > > we get request to remove Nightly builds from download page (see issue in > > GitHub below). > > I open this thread to discuss where is better place for it. > > > > thanks > > > > > > El mié., 16 oct. 2019 a las 14:26, GitBox (<g...@apache.org>) escribió: > > > > > carlosrovira commented on issue #498: Nightly builds must not be > promoted > > > on download pages > > > URL: > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F498%23issuecomment-542675010&data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112&sdata=%2BGvA%2BRakK5gM5gbVv%2BFVTogTh%2Bb4%2BVNpXOxYYoX%2BFH4%3D&reserved=0 > > > > > > > > > I searched to the place in our mailing list that seems to be the > > source > > > of the actual state for nightly on download page: > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2FNeed-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.html&data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112&sdata=ZLZ4e9gIq62avxUPbA%2F9zVKTY1%2FjUPVGXH%2FNhF0pBMM%3D&reserved=0 > > > > > > I think If we want to change it we need to discuss in list how we > want > > > it now > > > > > > > > > > > > ---------------------------------------------------------------- > > > This is an automated message from the Apache Git Service. > > > To respond to the message, please log on to GitHub and use the > > > URL above to go to the specific comment. > > > > > > For queries about this service, please contact Infrastructure at: > > > us...@infra.apache.org > > > > > > > > > With regards, > > > Apache Git Services > > > > > > > > > -- > > Carlos Rovira > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112&sdata=UKrC2WmUUtQhs8Hwx%2FVA2%2Fl66k23ajS6FXMGx8zjqWg%3D&reserved=0 > > > > > -- > Andrew Wetmore > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112&sdata=3W%2FSGSLlBPA4JB8tA4BLy5J%2BeGiMHzNPhC6Lt9nY1so%3D&reserved=0 >
