Feature added by: Sebastian Oliva (tian2992)
Feature #312804, revision 1
Title: Hermes integration on the openSUSE wiki
openSUSE Infrastructure: Unconfirmed
Priority
Requester: Desirable
Requested by: Sebastian Oliva (tian2992)
Partner organization: openSUSE.org
Description:
An extension to the wiki software, to add Hermes support to the Wiki software, enabling digests and advanced notifications to the Watch List.
Use Case:
Anna edited the openSUSE wiki, adding a tutorial to configure repositories. She subscribes to the page and enables notifications.
When John edits the page, Anna gets a twitter notification, letting her know, there was an edition in the page.
--
openSUSE Feature:
https://features.opensuse.org/312804
Feature added by: Adrian Schröter (adrianSuSE)
Feature #320681, revision 1
Title: Admin Issue Dashboard
Buildservice: Evaluation by project manager
Milestone: 2.8
Priority
Requester: Important
Projectmanager: Important
Requested by: Adrian Schröter (adriansuse)
Requested by: Adrian Schröter (adriansuse)
Partner organization: openSUSE.org
Description:
Turn the admin warning and error mails into a dash board. These are problems which get detected by the api or backend code and needs a helping hand by the admin. It is not supposed to be a replacement for errbit, which is for debugging developer issues.
The issues need to be stored in a way that they can be identified again. If the problem get fixed they must be removed by the system again. If the same problem is changing (eg. more data becomes out-of-sync between api and backend) the same entry must get updated.
--
openSUSE Feature:
https://features.opensuse.org/320681
Feature added by: Adrian Schröter (adrianSuSE)
Feature #319313, revision 1
Title: Keep showing running maintenance incidents to packager
Buildservice: New
Milestone: 2.7
Priority
Requester: Important
Requested by: Adrian Schröter (adriansuse)
Partner organization: openSUSE.org
Description:
Package maintainers want to be able to see running maintenance updates. Currently they see an update, which they have prepared only when: - their maintenance update request is not yet accepted - they keep their bugzilla entry open (which is referenced in patchinfo).
This is good for the "my work" view, which should only show tasks where the packager has to act. But there is currently no easy way to see all running updates on request.
There are two possible scenarios of not-yet-released updates: - open incident, still building or collecting updates - frozen incident, running release request (read being tested by QA).
The open incident can be covered by a search for patchinfos where the user is listed as packager and where the project is not locked.
The frozen incident situation should be covered by monitoring the request. There is fate #310145 which wants a generic monitoring of requests. We can use this by adding the packager from _patchinfo to the release request.
--
openSUSE Feature:
https://features.opensuse.org/319313
Feature added by: Adrian Schröter (adrianSuSE)
Feature #318339, revision 1
Title: Clone repo API support
Buildservice: Evaluation by engineering manager
Milestone: 2.7
Priority
Requester: Mandatory
Projectmanager: Important
Requested by: Adrian Schröter (adriansuse)
Requested by: Stephan Kulow (coolo)
Partner organization: openSUSE.org
Description:
Coolo wants the obs_admin support for cloning repos as command. Rudi may also wants this.
I assume we need this as background/invoked job like the project copy is implemented.
--
openSUSE Feature:
https://features.opensuse.org/318339
Feature added by: Adrian Schröter (adrianSuSE)
Feature #308899, revision 1
Title: allow repository specification in project meta xml
Buildservice: Evaluation
Priority
Requester: Important
Projectmanager: Important
Requested by: Adrian Schröter (adriansuse)
Description:
We have currently to set Type, Repotype and Patterntype in project conf data. That makes it hard to add an images repo easily with a gui that works.
Before creating code interpreting the prjconf, I would like to suggest to extend repository xml element to define this as default.
Opinions ?
Feature is completed when we have an "Add kiwi images repository" button.
--
openSUSE Feature:
https://features.opensuse.org/308899
Feature added by: Jimmy Berry (boombatower)
Feature #308619, revision 1
Title: Provide Kwallet integration for Firefox
openSUSE-11.3: Unconfirmed
Priority
Requester: Desirable
Requested by: Jimmy Berry (boombatower)
Description:
I have wanted such a feature for sometime and recently discoved https://addons.mozilla.org/en-US/firefox/addon/49357 via identi.ca talk. Since openSUSE 11.2 includes KDE integration for Firefox, I think this would be a great thing to either add/finish/polish or just defaultly include as part of integration.
--
openSUSE Feature:
https://features.opensuse.org/308619
Feature added by: Ludwig Nussel (lnussel)
Feature #310922, revision 1
Title: central system user registry
openSUSE-11.4: Unconfirmed
Priority
Requester: Important
Requested by: Ludwig Nussel (lnussel)
Partner organization: openSUSE.org
Description:
Once upon a time all systems users were defined in aaa_base via the default /etc/passwd file. When the uid space below uid 100 got too small a new dynamic range between 100 and 499 was introduced. So nowadays packages dynamically create a user in %pre which gets a random uid in this range. Disadvantage: uids are different on every system. Usually this is not a problem but for programs that export files over the network it is. TV recordings made by VDR for example. useradd has a --preferred-uid option for such cases. It's possible to specify a uid and useradd tries to use it. If it's already taken another one is chosen.
Thefore I'd propose to leverage that feature: - introduce a central uid registry for system users, e.g a file in aaa_base - lower SYSTEM_UID_MAX (/etc/login.defs) to e.g. 349 and assign "preferred uids" in the rage 350-499. - change useradd calls in packages to a macro that transparently decides whether a preferred uid needs to be used.
Use Case:
- two systems running vdr, one for recording, the other one for playback on a TV want to share recordings via nfs.
--
openSUSE Feature:
https://features.opensuse.org/310922
Feature added by: Ludwig Nussel (lnussel)
Feature #322072, revision 1
Title: support multiple back references in issue_trackers
Buildservice: New
Priority
Requester: Important
Requested by: Ludwig Nussel (lnussel)
Partner organization: openSUSE.org
Description:
Someone thought it's a good idea to refer to github issues as gh#project/repo#number according to the packaging guidelines: https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_o…
OBS however only supports one capture group in the parser. It needs to support multiple and allow to place them arbitrarily in the output.
--
openSUSE Feature:
https://features.opensuse.org/322072
Feature added by: Максим Муруев (slimy)
Feature #310464, revision 1
Title: Changer text console color
openSUSE-11.4: Unconfirmed
Priority
Requester: Important
Requested by: Максим Муруев (slimy)
Description:
Feature for yast change console color. And green color for console by default. I think green is opensuse color. For first console stay white, for best look boot log.
--
openSUSE Feature:
https://features.opensuse.org/310464
Feature added by: 6tr6tr 6tr6tr (6tr6tr)
Feature #310680, revision 1
Title: Make Icon Theme installer only show .tar.gz themes
openSUSE-11.4: Unconfirmed
Priority
Requester: Important
Requested by: 6tr6tr 6tr6tr (6tr6tr)
Description:
I recently tried installing new icon themes into openSUSE 11.3 via the Configure Desktop app. It showed a lot of themes with an "install" button, but when I pressed it, nothing happened. It turns out, that's because it only installs .tar.gz files and a number of the themes listed are in other formats. So the "Get New Themes..." popup should only show files it can actually install.
--
openSUSE Feature:
https://features.opensuse.org/310680