It's getting better. For the release part, I just found we need to list all the artifacts which were released in the download page of our website. It's important that we need to go through the [email protected][1], and all the releases must be archived[2]. Please go through these two pages for more information about release.
[1]http://www.apache.org/legal/release-policy.html#release-announcements [2]http://www.apache.org/dev/release-distribution.html#archival Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 7, 2019 at 11:54 AM 申远 <[email protected]> wrote: > > Hi, there > > It took me a few hours to evaluate the maturity for Weex according to The > Apache Project Maturity Model ( > http://community.apache.org/apache-way/apache-project-maturity-model.html), > it seems like there is still a big improvement space for Weex. The detail > is listed below: > Document issueReleaseRE50 > > The release process is documented and repeatable to the extent that someone > new to the project is able to independently generate the complete set of > artifacts required for a release. > > We should list the Apache Release procedure clearly in the document. > QualityQU30 > > The project provides a well-documented, secure and private channel to > report security issues, along with a documented way of responding to them. > > Again, we should list the report channel clearly in the document. > CommunityCO50 > > The way in which contributors can be granted more rights such as commit > access or decision power is clearly documented and is the same for all > contributors. > > Still, we need to list some basic requirement to be a committers. > Consensus BuildingCS10 > > The project maintains a public list of its contributors who have decision > power -- the project's PMC (Project Management Committee) consists of those > contributors. > > The PPMC & Committer is listed in in the weex status page > <http://incubator.apache.org/projects/weex.html>, I think adding a link to > weex status page in our document is enough. > CS20 > > Decisions are made by consensus among PMC members and are documented on the > project's main communications channel. Community opinions are taken into > account but the PMC has the final word if needed. > > Though we follow the normal Apache consensus building and voting procedure, > but we should make it clear in our document. > Long time issueCommunity > > The community is meritocratic and over time aims to give more rights and > responsibilities to contributors who add value to the project. > > The active committer of Weex is not enough, we need get more people > involved, and find more contributors and committers from weex users. > Consensus building > > All "important" discussions happen asynchronously in written form on the > project's main communications channel. Offline, face-to-face or private > discussions that affect the project are also documented on that channel. > > We are getting better at this part, but not enough. > Release > > We may need more release. > > Guys, what do you think of ? > > Best Regards, > YorkShen > > 申远
