search

TheProjecter / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

Create a openness / community health rating #218

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
This is a tricky one, we want to be able to indicate which projects appear
to be viable, but at the same time we don't want this to appear to be a
judgement on any particular project.

By calling it community health (as opposed to project health) we can focus
on openness and activity of the community. We should avoid making any
observations about the technical suitability of a solution as this varies
so much from use case to use case.

It is also important to (eventually) allow users to provide their own
priorities with respect to the final calculation of this rating.

A good start is the work OSS Watch and Pia Waugh did on the Foundations of
Openness (http://pipka.org/blog/2008/07/23/the-foundations-of-openness/),
but we also need to consider actual activity.

Ohloh will provide activity on the code base, but does not take into acount
activity on documentation, mailing lists etc.

Original issue reported on code.google.com by rgardler...@gmail.com on 23 Nov 2008 at 1:50

GoogleCodeExporter commented 8 years ago 
This issue looks to me like the openness rating currently available at 
http://oss.ly/j

This should be modelled as a Wookie widget much like the doapcreator widget.

I think it would be best to use a generic questionnaire ontology to avoid 
having to model all questions in a new ontology. We can infer results from that 
later.
Initial research for a questionnaire ontology revealed mostly academic papers 
such as [1], mostly by Matt-Mouley Bouamrane [2], and an example ontology from 
a book [2].

[1] 
http://delivery.acm.org/10.1145/1790000/1786549/p574-bouamrane.pdf?key1=1786549&
key2=7264897721&coll=GUIDE&dl=GUIDE&CFID=93521050&CFTOKEN=84992626 
[2] 
http://www.gla.ac.uk/departments/generalpracticeprimarycare/ourstaff/matt-mouley
bouamrane/publications/ 
[3] http://workingontologist.org/Examples/index.html

Original comment by sander.v...@oucs.ox.ac.uk on 1 Jul 2010 at 12:38

GoogleCodeExporter commented 8 years ago 
This is not the same as the openness rating, although they are related.

This is much bigger, we can pull statistics from SVN/Mailing list etc. and come 
up with some ratings. However, in the first instance we need to implement the 
questionaire as you indicate. This work is underway already (although stalled) 
at 
http://code.google.com/p/simal/source/browse/#svn/trunk/uk.ac.osswatch.simal.ssm
m

There is also a partial implementation of an openness rating calculation within 
Simal itself, see Project.getOpennessRaring() at 
http://code.google.com/p/simal/source/browse/trunk/uk.ac.osswatch.simal.core/src
/main/java/uk/ac/osswatch/simal/model/jena/Project.java#506

Before implementing the frameowrk I did look at what was out there already, but 
they all seemed to be overly complicated for what we needed (just a few basic 
question types, no branching etc.). This is now implemented at the above SVN 
module.

There is currently no UI, it's all done through the command line and there is 
no mechanism for recording the questions in a config file. Furthermore, results 
are currently output in a raw text format. Maybe the ontologies you link to can 
be leveraged here.

I'd suggest the first goal is to:

- create the question sets
- create a wookie widget to display questions and collect answers
- dump results to text in the wookie widget
- encode results in RDF
- have Simal perform the calculations on the RDF back end
- display results in Wookie widget

Original comment by ross.gardler on 1 Jul 2010 at 1:13

GoogleCodeExporter commented 8 years ago

Original comment by ross.gardler on 10 Mar 2011 at 12:13