October 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310652] Have an Etherpad install on openSUSE infrastructure
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

Feature added by: Jos Poortvliet (jospoortvliet) Feature #310652, revision 1 Title: Have an Etherpad install on openSUSE infrastructure openFATE: Unconfirmed Priority Requester: Important Requested by: Jos Poortvliet (jospoortvliet) Partner organization: openSUSE.org Description: Currently the marketing team in particular makes use of lots of piratepad's to work collaboratively on articles, announcements, plans and other things. Wiki's don't offer the ease and real-time collaboration features needed so piratepad is perfect. Except that it isn't. Piratepad has some serious issues (see "Why do we want this?"). So we would like to have an Etherpad install on openSUSE infrastructure. Having our 'own' Etherpad instance on an openSUSE server would solve these issues. Even just having it as a SUSE Studio virtual image so it can be run somewhere would be good enough. In general, the openSUSE servers are pretty dependable and even when not, we know who to ping to solve problems. Use Case: Usecase would be pretty much half the work the marketing team does - writing announcements, articles, planning... Business case (Partner benefit): openSUSE.org: The current 'solution' to use Piratepad has a bunch of issues: Stability is a big one - Piratepad is down quite frequently, sometimes for a whole day, making our work difficult. Another serious issue is oversight. We can't see what pads we have, resulting in lost pads (and the work we put into them) and duplication of efforts. Then there is the lack of control. All piratepads are fully public - but we have sometimes things we'd like to keep under the lid like announcements we are working on, articles, board things etcetera. Etherpad provides access control which would help us immensely. Part of that control issue is the ability (or lack there off) of deleting pads - we can't do that on Piratepad. Finally, we don't OWN Piratepad. If it went away RIGHT NOW, we would loose MANY important articles, announcements and other good work. It would be a small disaster for the marketing team and it's getting potentially worse as we do more and more work on Etherpad. -- openSUSE Feature: https://features.opensuse.org/310652

1 19

[New: openFATE 312804] Hermes integration on the openSUSE wiki
by fate_noreply＠suse.de 28 Mar '18

28 Mar '18

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

1 2

[New: openFATE 319313] Keep showing running maintenance incidents to packager
by fate_noreply＠suse.de 27 Mar '18

27 Mar '18

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

1 5

[New: openFATE 318339] Clone repo API support
by fate_noreply＠suse.de 27 Feb '18

27 Feb '18

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

1 4

[New: openFATE 308899] allow repository specification in project meta xml
by fate_noreply＠suse.de 27 Feb '18

27 Feb '18

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

1 4

[New: openFATE 308619] Provide Kwallet integration for Firefox
by fate_noreply＠suse.de 25 Feb '18

25 Feb '18

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

1 3

[New: openFATE 310922] central system user registry
by fate_noreply＠suse.de 12 Feb '18

12 Feb '18

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

1 15

[New: openFATE 310464] Changer text console color
by fate_noreply＠suse.de 30 Jan '18

30 Jan '18

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

1 5

[New: openFATE 310680] Make Icon Theme installer only show .tar.gz themes
by fate_noreply＠suse.de 30 Jan '18

30 Jan '18

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

1 2

[openFate 305144] [Feature-request] Yast as a Linux learning tool
by fate_noreply＠suse.de 30 Jan '18

30 Jan '18

Feature added by: Arvin Schnell <aschnell(a)novell.com> Feature #305144, revision 1, last change by Title: [Feature-request] Yast as a Linux learning tool openSUSE-11.1: New Priority Requester: Desirable Requested by: Alexey Eremenko <al4321(a)gmail.com> Partner organization: openSUSE.org Description: Hi All ! I Have very good new idea: converting Yast into a Linux learning tool. This is very simple to achieve: Yast must show the commands it executes and files it modifies, in a nice GUI dialog. It will allow all kinds of Linux users understand how things really work. Enable learn new things or remind how old-but-forgotten things work for seasoned people. Great, isn't it ? P.S. Jay Vollmer recommends, that among the commands that Yast shows as it executing, it should also recommend "man pages" for the relevant underlying commands. -- -Alexey Eromenko "Technologov", 29.jul.2008. Discussion: #1: Alexey Eremenko <al4321(a)gmail.com> (2008-07-29 12:09:11) Rajko M. wrote: If one wants to see what is gong on in background, than look at logs in realtime. There is console (Konsole) and command tail. Run as root: tail -f /var/log/YaST2/y2log and then start YaST and play with. -- -Alexey Eromenko "Technologov", 29.jul.2008. #2: Jerry Houston <jerry.houston(a)comcast.net> (2008-07-29 15:41:34) Sounds like a great way for new users to learn more about what's under the hood. Or, what's under the bonnet, for the Brits. #3: Cyril Hrubis <chrubis(a)novell.com> (2008-07-31 07:11:21) Moving to maintainers to decide. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305144

1 19