October 2010 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307621] Provide public interface to submit patchinfos
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Dirk Mueller (dirkmueller) Feature #307621, revision 1 Title: Provide public interface to submit patchinfos Buildservice: New Priority Requester: Mandatory Requested by: Dirk Mueller (dirkmueller) Partner organization: openSUSE.org Description: For openSUSE 11.2 it should be possible for external community members to submit maintenance updates. It is already possible to submit the changed packages itself, however the patchinfo file can not be submitted by external members. The feature would be to allow to attach the information needed for a patchinfo file (maybe except for a swampid) to be submitted by an external community member. One possible implementation method would be a new submitrequest type in the buildservice API. Business case (Partner benefit): openSUSE.org: Make use of community members for providing updates -- openSUSE Feature: https://features.opensuse.org/307621

1 3

[openFATE 306849] Drop requests comment have to be public/archived
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Stephan Binner (Beineri) Feature #306849, revision 1 Title: Drop requests comment have to be public/archived Buildservice: Unconfirmed Priority Requester: Mandatory Requested by: Stephan Binner (beineri) Description: Comments of accepted drop requests should appear in opensuse-commit mails which inform about the package being dropped. -- openSUSE Feature: https://features.opensuse.org/306849

1 4

[New: openFATE 309852] improve spec file editor in buildservice
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Michal Seben (mseben) Feature #309852, revision 1 Title: improve spec file editor in buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Michal Seben (mseben) Description: if you try to edit spec file in buildservice you get clean,not highlighted text, it would be fine if we have spec editor build in (with auto-completion and syntax higlight) maybe we could use codemirror : http://marijn.haverbeke.nl/codemirror/jstest.html (http://marijn.haverbeke.nl/codemirror/jstest.html) ? -- openSUSE Feature: https://features.opensuse.org/309852

1 9

[New: openFATE 310390] webui shall show informations about commits of a package
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #310390, revision 1 Title: webui shall show informations about commits of a package Buildservice: Candidate Priority Requester: Mandatory Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: The webui shows the history of all commits. actions to * view old code * go back to old code * show diffs shall be possible -- openSUSE Feature: https://features.opensuse.org/310390

1 1

[openFATE 306232] Quality Classification Of Projects
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #306232, revision 1, last change by Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * BROKEN -- project is known to be not working atm. -- openSUSE Feature: https://features.opensuse.org/306232

1 8

[New: openFATE 310489] Improved diff webui interface
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #310489, revision 1 Title: Improved diff webui interface Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: We want to have an improved interface for showing diffs in the webui. The diff can be between different packages or revisions or from a request. The UI should show only which files have changed (can be done via requesting the md5 sums of files in the merge file list) and offer the user to show the differences between each file. We may want to show the diff between specific files by default (eg files which end with .dsc, .spec, .kiwi or .changes). -- openSUSE Feature: https://features.opensuse.org/310489

1 5

[New: openFATE 310109] 3rd party web site integration support for installing/downloading software from OBS.
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #310109, revision 1 Title: 3rd party web site integration support for installing/downloading software from OBS. Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We lack an easy way to add a link on any 3rd party site for downloading and/or installing a package or software stack from any defined repository. There should be a simple html snippet which either loads a java script based popup or opens a small and easy to use html (without javascript) popup. The popup window should offer to select a base distro (and in best case detect it somehow) and the way for installation: * download rpm/deb * add repository * 1-Click installation via YMP * Pattern installation, if a pattern has been defined on OBS. I think we need different implementations of this snippet, because there are different kind of web designs out there. But having one with javascript popup and one without would be a great start already. The html snippet should contain also a link back to OBS and/or back to the Project in OBS. A html snippet should allow to specify: * Used project and either * * List of packages to show or install step by step or * * A pattern to install AI: adrian, create a more detailed plan in wiki Robert, it would be great to have some mockups how this could look alike -- openSUSE Feature: https://features.opensuse.org/310109

1 5

[openFATE 305907] Support Update Repo Generation
by fate_noreply＠suse.de 17 Apr '12

17 Apr '12

Feature added by: Adrian Schröter (adrianSuSE) Feature #305907, revision 1, last change by Title: Support Update Repo Generation Buildservice: Evaluation Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: The Build Service should offer update repos as repository channel. It is unclear right now, how we will carry in the extra update information texts. This should maybe designed together with a new changelog handling. -- openSUSE Feature: https://features.opensuse.org/305907

1 6

[New: openFATE 310266] APT-Cacher for Opensuse RPM's
by fate_noreply＠suse.de 06 Apr '12

06 Apr '12

Feature added by: Matthew Collinsworth (Avanesov79) Feature #310266, revision 1 Title: APT-Cacher for Opensuse RPM's Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Matthew Collinsworth (avanesov79) Partner organization: openSUSE.org Description: Example setup: https://help.ubuntu.com/community/Apt-Cacher-Server Apt-Cacher creates a local repo on demand so it is not nesasary to download the entire repo at once. Clients using it do not need to modify thier repo addresses. The concept works as follows: A server with enough storage is setup with APT-Cacher running on it. The client PC's have a single file added to them telling them to use the APT-Cacher server as a proxy for all repo downloads. When a request is made the server checks to see if it has an up-to-date version of the package requested. If it does it feeds it along, if it doesnt it downloads it and sends it to the requesting client. It keeps the downloaded package in case another client needs it. Business case (Partner benefit): openSUSE.org: Apt-Cacher makes it very easy to establish a local repo on demand without needing to download the entire repo-cache at once. It also requires minimum configuration on the client PC and no reconfiguration of the clients repo sources. -- openSUSE Feature: https://features.opensuse.org/310266

1 7

[openFATE 307727] Do not install Apparmore per default
by fate_noreply＠suse.de 03 Apr '12

03 Apr '12

Feature added by: Carsten Hoeger (choeger) Feature #307727, revision 1 Title: Do not install Apparmore per default openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Carsten Hoeger (choeger) Description: Do not install AppArmor per default. -- openSUSE Feature: https://features.opensuse.org/307727

1 10