Build Service/Workflows
From openSUSE
[edit]
Browse for software
- See the latest changes (history page)
- Browse the best rated applications
- Browse by Categories (trove/freshmeat ?)
- Browse by Keywords (The keywords may be grouped under some categories for browsing)
[edit]
Searching for software
- Enter a string. The search function should look in following data in this order of relevance
- exact package name
- Keywords
- categories (trove/freshmeat ?
- description (optionally)
The rating of the application should have influence on the order.
Cornelius, we need your help here :)
[edit]
Download a package for installation
- Search or Browse for an application
- View the public project page
- Click on download link
- package will be sent by the server and handled by the browser
[edit]
Subscribe a repository
- Search or Browse for an application
- View the public project page
- Click on link
- browser will call external application to handle the repository information
comments: for YUM, the user can click on 'go to repository' like, then copy the url to the .repo file. Then on command line (with an example URL):
su cd /etc/yum.repos.d wget http://download.opensuse.org/repositories/openSUSE:/Tools/Fedora_7/openSUSE:Tools.repo
for Debian: what is the equivalent? needs to be documented.
[edit]
User gives feedback about the software
- Rating works by clicking on a certain star from a row of stars
- User enters a text and submit it
[edit]
Simple, easy package creation
It will be done by a wizard later. TBD
[edit]
Create a modified version of a package with minimal technical details
AI Adrian: upload workflow
[edit]
Suggest package changes / Request for merge
- Click on a button for request merge
- linked package only: The admin of the linked project will get notified
- not linked package: prompt the user for the desired project to get merged in
- the original project owner may refuse the merge and reply a comment about it
- otherwise package gets merge into the project
TBD: what happens with the merged package ?
[edit]
Receive notifications for specific project updates
- Go to a project page
- Press on notification button
- select what kind of changes you want to get notified about (source, rpm releases)
- select the kind of notification
[edit]
Track changes of the projects
- Watch the check in history
- Watch the package build history
- Watch the release history
[edit]
Possibly create his own distribution
TBD
[edit]
Trigger an update of a package
- Click the update button
- version prompter may appear
- download or svn/cvs checkout will happen
- changelog entry gets added
- rebuild will be triggered
[edit]
Create a new project
- click a button
- mandatory items to setup on creation:
- name (id)
- title
- description
- category
- optional (discuss if added at creation and
- 'hide project' checkbox
- tags (labels)
- special urls (screenshots, wiki, bug tracker)
- logo/icon?
- adding additional user
[edit]
Edit Projects
- information that appears on the main project page is edited directly on that page
- all other options are edited/set on a project subpage
- config page could be done using tab-like navigation
[edit]
Create all different kinds of packages
TBD
- create package from scratch
- create package using template
- all fields are editable on the main project page
- mandatory fields are highlighted specially on the main package page
[edit]
Edit Packages
- add files
- add sources (http source, svn/cvs source)
- edit spec file (using web ui)
- add/remove users
- change version

