Feature changed by: Adrian Schröter (adrianSuSE) Feature #305591, revision 10 Title: Define Purpose for each openSUSE Build Service Project Buildservice: Evaluation by product manager Priority Requester: Important Info Provider: Pavol Rusnak (prusnak) Requested by: Pavol Rusnak (prusnak) Partner organization: openSUSE.org Description: define purpose for each project, like: * add-on package * fresh packages + libraries (eg. games) * bleeding edge packages (eg. zypp:svn) * backports for older distributions (eg. zypp:Backport) * playground (eg. all home projects) So, * this sets users expectations * purpose could be indicated by naming conventions, or even better by project flags * purpose must be shown in the search result for this method to work References: http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00056.html Discussion: #1: Andreas Jaeger (a_jaeger) (2009-08-11 15:51:09) This sounds like a good idea. What needs to be done to make this happen? #2: Adrian Schröter (adriansuse) (2010-02-20 09:25:34) I think we can fullfill this request by two independend features: * Project classification setting to be set by the project owner (this is handled in #306232) * Automatic QA validation how a package will influence the system, for example: * replace base packages * replace files * replace libaries * just being an add-on + #3: Adrian Schröter (adriansuse) (2013-07-03 10:33:49) + The project classification is possible via setting attribute OBS: + QualityCategory to one of the allowed values: + Stable Testing Development Private + However, there is no webui and osc support yet, so this is basically + unused. webui project creation should make it easy to set it and search + in webui/osc/software needs to use it. -- openSUSE Feature: https://features.opensuse.org/305591