My apologies for point #3, I volunteered to fix it on the day it was reported but then life got in the way. I understand the fix to be done and will attempt it before next week starts. I'll also remove release links per #1 and update the contributor guidelines per #2.
Finally, we had some issue getting the website stabilized with the ad-hoc SVN release system the foundation uses; I need to clean up a few things and then write up a short documentation so other committers can update the website without depending on me. I'll circulate that doc on our wiki unless people prefer some other place. Apologies for the delay and thanks for helping us learn the Apache way! On Thursday, February 6, 2014, Jake Farrell <[email protected]> wrote: > Recently there has been a lot of discussions about issues seen in releases > and tagging as well as concerns raised about podlings learning the ASF > ways. As we continue to progress towards the first Apache Usergrid release > and eventually graduation I want to make sure that everyone is on the same > page and aware of the ASF requirements and necessary procedures that are in > place. > > Looking at the Usergrid website and docs we have some items that will need > to be addressed before the next report is due and the status for each of > these items should be added to the report. > > 1. The website has a recent releases section and download links. No votes > have taken place so far for Apache UserGrid and therefore no release have > occurred. The links point to github for the available downloads. Releases > must be voted on and then accepted be the IPMC as the project is still in > incubation and the releases must be distributed using the ASF mirror system > . These must be removed. Everyone please familiarize yourself with the > guide for releases [1][2]. If you have any questions on this please ask, > everyone needs to be aware of these requirements as they are not optional. > > 2. There is no documentation about the github workflow the project opted to > go with. Going to the website and clicking on contributing guidelines send > you to [3] where it references submitting pull requests to > apigee/usergrid-stack. The workflow that has been selected is different > than Apache JClouds and any other project in the incubator or any TLP. > JClouds is using Github for reviews only and no source is committed to > their Github repository [4]. This process needs to be documented throughly > to ensure that the committers are following all required ASF legal > obligations for any contributions. > > 3. The website does not meet the required ASF branding guidelines [5]. This > was initially brought up in the beginning of January and still is an issue. > > There is a lot of hard work going on and I appreciate everyone working to > help address these items to ensure that all ASF requirements and policies > are being adhered to. If anyone has any questions on these please do not > hesitate to ask > > -Jake > > > [1]: http://www.apache.org/dev/release.html > [2]: http://incubator.apache.org/guides/releasemanagement.html > [3]: https://github.com/usergrid/usergrid/tree/master/stack#contributing > [4]: http://wiki.apache.org/jclouds/Committers%20Guide > [5]: http://www.apache.org/foundation/marks/pmcs.html#websites >
