Task:Karma for applications - Revision history

bergie at 08:50, 5 May 2009

bergie — Tue, 05 May 2009 08:50:37 GMT

← Older revision		Revision as of 08:50, 5 May 2009
Line 9:		Line 9:
	* Provide a simple, unified way for users and developers to judge an application's quality.		* Provide a simple, unified way for users and developers to judge an application's quality.
	* Provide a distributed [[Extras repository process definition\|quality assurance]] system for handling package promotion.		* Provide a distributed [[Extras repository process definition\|quality assurance]] system for handling package promotion.
		+	* Provide a fast-updating list of "currently hot" applications
		+	* Provide a way to rate applications remotely

	== Metrics for judging "quality" ==		== Metrics for judging "quality" ==
Line 44:		Line 46:

	current karma = (yesterday's karma - age modifier) + (total download count - yesterdays downloadcount - lastweeks daily average)		current karma = (yesterday's karma - age modifier) + (total download count - yesterdays downloadcount - lastweeks daily average)
		+
		+	== Remote rating of applications ==
		+
		+	Maemo applications will be featured in other services outside the regular Maemo.org website scope, including the application manager in the device itself.
		+
		+	To support rating applications through these, we should implement an API for rating and commenting applications remotely.
		+
		+	The API could be modeled after [http://web.archive.org/web/20060203035137/http://wellformedweb.org/story/9 CommentsApi].

bergie: /* Metrics for judging "quality" */

bergie — Tue, 05 May 2009 08:39:50 GMT

Metrics for judging "quality"

← Older revision		Revision as of 08:39, 5 May 2009
Line 29:		Line 29:
	* Number of contributors in Garage		* Number of contributors in Garage

-	All karma items are counted once per day, and stored so that the development of application karma can be followed on a graph.	+	All karma items are counted once per day, and stored so that the development of application karma can be followed on a graph. The total karma of an application will be available in the application's [http://www.midgard-project.org/documentation/mgdschema-metadata-object/ metadata.score].

	== Counting currently "hot" applications ==		== Counting currently "hot" applications ==

bergie at 08:36, 5 May 2009

bergie — Tue, 05 May 2009 08:36:02 GMT

← Older revision		Revision as of 08:36, 5 May 2009
Line 30:		Line 30:

	All karma items are counted once per day, and stored so that the development of application karma can be followed on a graph.		All karma items are counted once per day, and stored so that the development of application karma can be followed on a graph.
		+
		+	== Counting currently "hot" applications ==
		+
		+	To make a dynamic listing of applications that are "hot right now", we need to store some additional download statistics per application:
		+
		+	* Total amount of downloads
		+	* Average downloads per day during last week
		+	* Yesterday's downloads
		+
		+	These can then be used to calculate whether an application is getting more downloads on a given day than usual, meaning that it is "currently hot".
		+
		+	This should be possible to count via:
		+
		+	current karma = (yesterday's karma - age modifier) + (total download count - yesterdays downloadcount - lastweeks daily average)

bergie: /* Metrics for judging "quality" */

bergie — Tue, 05 May 2009 08:14:22 GMT

Metrics for judging "quality"

← Older revision		Revision as of 08:14, 5 May 2009
Line 29:		Line 29:
	* Number of contributors in Garage		* Number of contributors in Garage

-	All karma items are counted once per ~~week~~, and stored so that the development of application karma can be followed on a graph.	+	All karma items are counted once per day, and stored so that the development of application karma can be followed on a graph.

bergie: /* Metrics for judging "quality" */

bergie — Mon, 04 May 2009 17:18:06 GMT

Metrics for judging "quality"

← Older revision		Revision as of 17:18, 4 May 2009
Line 26:		Line 26:
	* Freshmeat.net stats (when the new Freshmeat [http://help.freshmeat.net/discussions/questions/39-where-are-the-rdf-files-from-the-backend-directory#comment_120399 reimplements their APIs])		* Freshmeat.net stats (when the new Freshmeat [http://help.freshmeat.net/discussions/questions/39-where-are-the-rdf-files-from-the-backend-directory#comment_120399 reimplements their APIs])
	* Blog mentions (via Technorati, using "unixname" as tag)		* Blog mentions (via Technorati, using "unixname" as tag)
-	* Screenshots uploaded (via ~~Flickr, using "unixname" as tag, see~~ http://www.flickr.com/services/api/flickr.photos.search.html)	+	* Screenshots uploaded (via [http://www.flickr.com/services/api/flickr.photos.search.html Flickr], using "unixname" as tag)
	* Number of contributors in Garage		* Number of contributors in Garage

	All karma items are counted once per week, and stored so that the development of application karma can be followed on a graph.		All karma items are counted once per week, and stored so that the development of application karma can be followed on a graph.

bergie: More karma providers

bergie — Mon, 04 May 2009 16:56:58 GMT

More karma providers

← Older revision		Revision as of 16:56, 4 May 2009
Line 1:		Line 1:
	{{task\|ongoing}}		{{task\|ongoing}}

-	~~This task is to define a~~ karma ~~system for applications as a basis for judging their~~ "~~quality~~".	+	Application karma seeks to provide plausible "score number" for each application in the Maemo application catalog.
		+
		+	The application karma will follow a pattern familiar from Maemo's user karma (see http://maemo.org/profile/list/ and http://maemo.org/profile/view/bergie/), utilizing various sources of information about the application to calculate its activity and importance.

	== Goals ==		== Goals ==
Line 10:		Line 12:
	== Metrics for judging "quality" ==		== Metrics for judging "quality" ==

-	~~In no particular order~~.	+	These are calculated using information inside maemo.org Midgard database:
		+
		+	* Number of downloads
		+	* Number of ratings
		+	* Average rating
		+	* Frequency of updates
		+	* Number of releases available
		+	* Number of OS versions supported
		+
		+	As well as from outside it:
		+
		+	* Bug activity (in Bugzilla)
		+	* Freshmeat.net stats (when the new Freshmeat [http://help.freshmeat.net/discussions/questions/39-where-are-the-rdf-files-from-the-backend-directory#comment_120399 reimplements their APIs])
		+	* Blog mentions (via Technorati, using "unixname" as tag)
		+	* Screenshots uploaded (via Flickr, using "unixname" as tag, see http://www.flickr.com/services/api/flickr.photos.search.html)
		+	* Number of contributors in Garage

-	* Number of ~~downloads.~~	+	All karma items are counted once per week, and stored so that the development of application karma can be followed on a graph.
-	* Number of ratings.	+
-	* Level of ratings.	+
-	* Actively maintained.	+
-	** Frequency of updates.	+
-	** Bug activity (assuming a ~~tracker on bugzilla).~~	+
-	* Number of releases available for.	+

generalantilles: New page: {{task|ongoing}} This task is to define a karma system for applications as a basis for judging their "quality". == Goals == * Provide a simple, unified way for users and developers to j...

generalantilles — Fri, 06 Mar 2009 09:38:42 GMT

New page: {{task|ongoing}} This task is to define a karma system for applications as a basis for judging their "quality". == Goals == * Provide a simple, unified way for users and developers to j...

New page

{{task|ongoing}}

This task is to define a karma system for applications as a basis for judging their "quality".

== Goals ==

* Provide a simple, unified way for users and developers to judge an application's quality.
* Provide a distributed [[Extras repository process definition|quality assurance]] system for handling package promotion.

== Metrics for judging "quality" ==

In no particular order.

* Number of downloads.
* Number of ratings.
* Level of ratings.
* Actively maintained.
** Frequency of updates.
** Bug activity (assuming a tracker on bugzilla).
* Number of releases available for.