[haiku-depot-web] [haiku-depot-web-app.wiki] push by - Deleted wiki page Goals through web user interface. on 2014-08-04 01:53 GMT
- From: haiku-depot-web-app@xxxxxxxxxxxxxx
- To: haiku-depot-web@xxxxxxxxxxxxx
- Date: Mon, 04 Aug 2014 01:53:56 +0000
Revision: 75203982bee3
Author: haiku.lindesaya <haiku.lindesaya@xxxxxxxxx>
Date: Mon Aug 4 01:53:36 2014 UTC
Log: Deleted wiki page Goals through web user interface.
http://code.google.com/p/haiku-depot-web-app/source/detail?r=75203982bee3&repo=wiki
Deleted:
/Goals.wiki
=======================================
--- /Goals.wiki Sun Sep 22 15:51:12 2013 UTC
+++ /dev/null
@@ -1,13 +0,0 @@
-#summary Outlines the goals of the project.
-
-= 10,000 feet view from above =
-
-The Haiku Depot Web App may become a part of the Haiku Package Management
infrastructure.
-
-Haiku includes a graphical front end to the package management sub-system,
called HaikuDepot, which allows to list available packages, perform package
actions such as install, de-activate or uninstall, and show information
about packages. That information goes far beyond that included in the
packages themselves. Instead, the information can be considered
to "decorate" packages. For an application, there might be an icon,
screenshots, translations of the package description, and a rating and
comment system which tracks user ratings and comments per package version.
Perhaps even user provided guides or tutorials.
-
-All this additional information needs to be hosted somewhere. This is
where this project comes into play. The first goal is therefore, to provide
users and developers of Haiku a way to collaborate on package decorating
information.
-
-But it doesn't have to stop there. We also strive to create the technical
infrastructure to collaborate on managing the flow of packages between
unstable and stable release channels: Haiku users may subscribe to software
repositories. These may be attributed, among other things, as hosting
stable (for daily use) or unstable (for testing, experimenting) packages.
Subscribers of the unstable channel(s) can then mark package versions as
working well or having problems. We envision a scoring system in which the
input given by individual users is weighted, perhaps based on previous
activity on specific packages, or other measures of "expertise". A package
could then eventually migrate _automatically_ from the unstable to the
stable repository.
-
-As a result, there wouldn't be the need anymore for a limited group of
people, or even a single release manager, to work towards a release.
Instead, it would be distributed among all interested contributors in a
constant rolling release software eco-system.
Other related posts:
- » [haiku-depot-web] [haiku-depot-web-app.wiki] push by - Deleted wiki page Goals through web user interface. on 2014-08-04 01:53 GMT - haiku-depot-web-app
