Hi again Bertrand and everyone, sorry to be late following, see in line comments.
On Mon, Feb 2, 2015 at 1:08 PM, Roberto Galoppini < rgalopp...@slashdotmedia.com> wrote: > > > On Mon, Feb 2, 2015 at 12:45 PM, Bertrand Delacretaz < > bdelacre...@apache.org> wrote: > >> Hi Roberto, >> >> On Fri, Jan 30, 2015 at 7:49 PM, Roberto Galoppini >> <rgalopp...@slashdotmedia.com> wrote: >> > ...Davide (cc-ed) kindly created an alpha >> > version for the new born Apache Maturity Model, you can see it live at >> the >> > following address: >> > >> > Apache Maturity Model (Httpd Server) >> > <http://108.161.134.31:8000/analysis/report/2/4> ... >> >> That's fantastic! >> > > Glad you like that Bertrand. > > Davide would need some help to define the possible answers for the > different questions. > In the SOS Open Source case we took inspirations from QSOS metrics and > came up with a set of possible answers for every question, plus we added > tips and hints to get a better score (actions to be taken). > > Ideally we should aim to do a similar job for the Apache model. > I had an in depth look at those metrics, below some ideas: CD10 The project produces Open Source software, for distribution to the public at no charge. Hypothesis: the project distributes or at least develop a release at the ASF How to Compute: look for it at https://projects-new.apache.org/releases.html. If there are public releases available at the ASF it would be marked as 'public relese available', if the project is still in incubation it would be marked ad 'in incubation, no public release available yet', otherwise it would be marked as 'currently not developed or incubated at the ASF'. CD20 The project's code is easily discoverable and publicly accessible. Hypothesis: code must be easy to discover also for people that doesn't know it's an Apache project. How to Compute: search for it using popular search engines, if it is among the first 3 results one of them is pointing to the ASF it would be marked as 'easy to discover', if it is in the first page it would be 'discoverable with some difficulties' otherwise it would be marked as 'hard to find'. In all cases some SEO-wise suggestions about how to make it more discoverable will be provided. QU50 The project strives to respond to documented bug reports in a timely manner.How to Compute: analyze opened/closed tickets' trends, possibly splitting them by priority, and maybe keeping in mind some sort of 80-20 rule for that (e.g. SEV 1 closed in x days 80% of times).CO10 The project has a well-known homepage that points to all the information required to operate according to this maturity model. Similarly to CO10 we could search for the project home page using popular search engines, and if it is the first result would point to the project homepage it would be marked as 'easy to discover', if it is in the first page it would be 'discoverable with some difficulties' otherwise it would be marked as 'hard to find'. In all cases some SEO-wise suggestions about how to make it more discoverable will be provided. CO40 The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. How to Compute: compare the number/names of current committers with the number/names of committers 6/12 months ago. Set a % of incremental/decremental differences that would let us mark it with different levels of meritocracy+advocacy in action.CS10 The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. How to Compute: list of PMC members could be searched, some human due-diligence probably needed anyway. All in all only a tiny fraction of the metrics included in the Apache Maturity Model seem to be suitable for automation, though. I wish you to have a look at others' efforts in this sense, that could be inspirational and definitely suitable for an heavier automated approach. I'm talking of what the PolarSys project did to put together their Maturity Assessment Dashboard, based on the Goal-Question-Metric approach. http://dashboard.castalia.camp/documentation/quality_model.html I believe they did an excellent job, you can learn more about how they did it here: https://speakerdeck.com/bitergia/the-polarsys-maturity-model-unconference-workshop-session-1 In case you would find that interesting or worth to explore, it would be possible to integrate Grimoire's tools output with OSSEval engine, and eventually get all those metrics in a report ready for everyone's consumption and totally based on objective evaluations. Look forward to your feedback. Thanks, Roberto > > >> >> I'd be happy to include a link to that (once it has a more permanent >> URL) in the maturity model in a new "tools" section. >> > > As soon as we finalise the model we'll find a permanent home, sure. > > Roberto > > > > >> >> -Bertrand >> > > >
