The current website includes on several out of date dependencies. These need to be updated and the corresponding website rebuilt.

Document our voting process (see: https://www.apache.org/foundation/voting.html)

CS-40 It's important to spell out that In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30.

The current contributor guide (https://milagro.apache.org/docs/contributor-guide/) is out of date and needs to be updated with the new repositories, archiving the old ones.

Currently the documentation for these three repos describes how to build by cloning the repos. They should be updated to build from the official Apache source release archives.

Note that the installation instructions in each repo's readme files should remain unchanged.

The current list is maintained at Whimsy. Other pages/files that need updating:

• https://incubator.apache.org/projects/milagro.html
• https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/milagro.yml
• https://cwiki.apache.org/confluence/display/MILAGRO/Committers

This is the list of the places I have found - so far -. If you know about more places, please add them here

The page http://milagro.apache.org/docs/milagro-intro/ has the following sentence:

"In certain use cases, this removes the need for a PKI infrastructure eliminates the root key 'single point of compromise' weakness, as the main reason to issue certificates is used to bind a public / private key pair to an identity."

This does not read well - maybe some missing words?
Probably should be split into multiple sentences.

Milagro, in all aspects, needs a refresh. The project website and documentation sites are both horribly out of date. For the proposal, go to https://cwiki.apache.org/confluence/display/MILAGRO/Home

https://incubator.apache.org/guides/branding.html#disclaimers

Quick start examples are a great way for people to start playing around with our libraries. We should have them written for our core libraries and have them on our homepage.

This is a placeholder ticket to document everything that needs to happen to satisfy this benchmark and discuss it further.

We do want to be open to corporate involvement, but contributors should act as themselves. One way to do so is to subscribe to the communication channels using personal or apache-provided e-mail addresses, to ensure people can keep contributing outside of their professional involvement. This should probably be a policy at least for committers.

On the page: https://milagro.apache.org/docs/amcl-c-api-2.0.0/

the "Next" button breaks when told to go to https://milagro.apache.org/docs/cryptojs/amcl-javascript-api-1.0.0

https://github.com/apache/incubator-milagro-java

has been archived with no notice on why it is archived or where the current project can be found.

The project is still registered on maven, but points to a removed repository in the milagro foundation:

https://search.maven.org/artifact/org.miracl.milagro.amcl/milagro-crypto-java/0.4.0/jar

Is the java project terminated?

I could not find a link to the issue tracker on the website.

I'm hoping this is it...

Please ensure that it is easy to find the issue tracker from the website

In the previous archived repos https://github.com/apache/incubator-milagro-crypto/tree/master/version3/go
I see there are golang implementation there.
Where is it migrated to now?