Details
-
Improvement
-
Status: Done
-
Major
-
Resolution: Done
-
None
-
None
Description
Issue 1
Podling web sites MUST include a clear disclaimer on their website and in all documentation (including releases) stating that they are in incubation. Podlings SHOULD use the following text for all disclaimers (replace the underlined phrases as appropriate):
Apache Podling-Name is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Issue 2
Podlings websites SHOULD contain the Apache Incubator Project logo as sign of affiliation....
Apache Project Web Sites typically include several standard pages. Each page is formatted with a navigation bar on the left and a project standard header that includes the Incubator graphic.
[We need to make the Logo more prominent and move towards the top of the page rather than having it on the bottom like we do]
Issue 3
The sources for every podling site sources should be maintained in the podling's site SVN or git directory
Issue 4
Previous statement of the problem:
A downloads page needs to be created with links per release. The link to the artifact needs to be using the mirror site for apache. For example, the 0.3.0 release would be http://www.apache.org/dyn/closer.lua/incubator/metron/0.3.0/apache-metron-0.3.0-incubating.tar.gz. The MD5, SHA and Signature can be from the apache release site. Look at the storm page as an example: http://storm.apache.org/downloads.html (Note https://maven.apache.org/download.cgi is a better example because it allows changing the mirror if needed.)
A separate Downloads page is needed, rather than the current button, in order to satisfy these three requirements of http://www.apache.org/dev/release-download-pages.html :
- All links to the downloadable distribution artifacts MUST NOT reference the main Apache dist web site (dist.apache.org). Instead, they should use the standard scripting mechanisms to distribute the load between the mirror sites (see http://www.apache.org/dyn/closer.cgi/ ).
- All links to checksums, detached signatures and public keys MUST reference the main Apache dist web site (dist.apache.org), and use https (SSL).
- The site SHOULD provide clear and easy links to the public keys, checksums and detached signatures from the download release page, and include a reminder text with links to more information for users.
Detailed discussion and examples are provided in Comment 15723335 below.
Issue 5
[Lets try to conform as much as possible to the following suggested template]
Project Home Page: the primary entry point to the site; contains project description, news, invitation to join the project.
[We have this, great]
License Page: usually, the Apache License 2.0
[We don't have this, we should probably put it under the about page]
Downloads: many projects in incubation will release code, and this page describes them and has links to the download pages that redirect to Apache Mirror sites.
[We have this, great]
Documentation: this page describes the project documentation, including javadoc for Java projects; guides, tutorials, and links to external documentation.
[We should probably just link to the wiki so we don't have to maintain this in two places]
Committers: a list of current committers on the project.
[We need to update this from our status page that can be found here. Need to make sure both are consistent.
http://incubator.apache.org/projects/metron.html
]
Mailing Lists: there are several mailing lists that the community might be interested in, and this page contains mailto: links that allow easy subscription (and unsubscription) to any of them.
[We should probably put this under our community page and also link to the apache status page to make sure it's consistent]
FAQ: frequently asked questions are answered here.
[We probably want to link to the wiki for this, as they would be easier to update this way]
Road Map: if the project has a vision of future community or development activities, the road map is published here.
[We should probably link to our Jira collection for the next release]
Source Code: links to the browsable source repository and svn commands to check out the sources.
[We have this, great]
Coding Standards: the coding standards for submitted code by the community, along with a description of how strict the project intends to be.
Issue Tracking: links to the JIRA or other issue tracking tool, possibly including frequently used filters for issue lists.
[This exists on our wiki. We should link to that]
Dependencies: other projects that this project depends on.
[We can link to the wiki for this]
favicon: the project's icon in a format suitable for a browser's address bar. If absent, an Apache Feather will be displayed.
[we don't have a feather nor a metron logo. not sure if this is important, but we should probably have something]
Attachments
Issue Links
- is related to
-
METRON-589 Dist area should only contain latest release
-
- Done
-
- links to
