August 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306933] Integrate Social Desktop into our Desktop
by fate_noreply＠suse.de 10 Feb '10

10 Feb '10

Feature added by: Michael Löffler (michl19) Feature #306933, revision 1 Title: Integrate Social Desktop into our Desktop openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Michael Löffler (michl19) Description: Social interaction between people becomes more important than ever. Communicating over the Internet via mails, forums and internet platforms is just normal. Just think of Facebook, Flickr, BitTorrent... One of the strongest assets of the free software community is its worldwide community of contributors and users who believe in free software and who work hard to bring the software and solutions to the mainstream. Core idea of the Social Desktop is to connect to your peers in the community, making sharing and exchanging knowledge easier to integrate into applications and the desktop itself. The concept behind the Social Desktop is to bring the power of online communities and group collaboration to desktop applications and the desktop shell itself. This feature is about the integration of such a social desktop into our desktop. If integrated it should be simply to use its functionalities but everybody needs to have free choice to use it or not. The targetgroup of the new community / social network is not only developers but also the end users who are not familiar with technical stuff and can with an integrated social desktop get easily in contact with people in the same area or people with same interests or software issues. Creation of some kind of facebook for openSUSE may stimulate the openSUSE adoption and bind existing users to the distribution. This could be beneficial for the marketshare of openSUSE. Another aspect is that this kind of communities can transform users into contributors. References: http://www.open-collaboration-services.org/ http://www.opendesktop.org -- openSUSE Feature: https://features.opensuse.org/306933

1 4

[openFATE 307200] Replace ifconfig by iproute2 - add warning messages to old tools
by fate_noreply＠suse.de 08 Feb '10

08 Feb '10

Feature added by: Jan Engelhardt (jengelh) Feature #307200, revision 1 Title: Replace ifconfig by iproute2 - add warning messages to old tools openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jan Engelhardt (jengelh) Description: Because Novell once again cannot be convinced, I am putting https://bugzilla.novell.com/show_bug.cgi?id=492665 to public vote here. net-tools (/sbin/ifconfig, /sbin/route, arp, etc.) has numerous problems, not to mention that it is not developed since April 2001 anymore. Since April 2004, iproute2 is available as a replacement for ifconfig, but users still use the old tools with the seemingly-crippled functionality. I propose printing a warning message upon invocation to try and educate users to finally use the modern tools. -- openSUSE Feature: https://features.opensuse.org/307200

1 7

[openFATE 307196] Buildservice: Accepting of Submissions only with Successfully Build Packages
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Andreas Jaeger (a_jaeger) Feature #307196, revision 1 Title: Buildservice: Accepting of Submissions only with Successfully Build Packages Buildservice: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: I recently noticed that somebody submitted a package to openSUSE:Factory (and it got checked in) that has never ever build in the build service since it has obvious packaging problems (the %setup step did not work at all plus many more problems). I propose that "osc request show" informs the reviewer about the build status of the package. Additionally, "osc accept" should ask for confirmation if the package has not build successfully. Business case (Partner benefit): openSUSE.org: This will help to not have packages that do not build at all. -- openSUSE Feature: https://features.opensuse.org/307196

1 3

[openFATE 307480] Development of .spec files - .specfile editor and wizard
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Glenn Doig (doiggl) Feature #307480, revision 1 Title: Development of .spec files - .specfile editor and wizard Buildservice: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Hello, Can this tool be included to help and assist on the creation of .spec files ?. http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide (http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide) The Specfile Editor plug-in provides a wizard for creating new .spec files too. Cheers Glenn -- openSUSE Feature: https://features.opensuse.org/307480

1 1

[openFATE 307474] Show link-tooltip also in stage succeeded with info from build-compare
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Jan-Simon Möller (dl9pf) Feature #307474, revision 1 Title: Show link-tooltip also in stage succeeded with info from build-compare Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Jan-Simon Möller (dl9pf) Description: Use-Case: If a package is in status "Finished" we already display e.g. "new build"/"no change" info. We should show the same data also in state succeeded when hovering the link. It helps on large projects to keep easily track on unchanged build. -- openSUSE Feature: https://features.opensuse.org/307474

1 1

[openFATE 306006] btrfs in openSUSE
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Marek Stopka (m4r3k) Feature #306006, revision 1, last change by Title: btrfs in openSUSE openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Marek Stopka (m4r3k) Description: I think it is time to make btrfs as a part of upcoming openSUSE 11.2, probably with BIG warning but still there should be possibility to use btrfs and even better with some kind of integration in YaST disk module... Fedora is going for btrfs with next release either. -- openSUSE Feature: https://features.opensuse.org/306006

1 12

[openFATE 306529] Deactivate build if home:user:branch:foo is inactive for 1 or 2 weeks
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Jan-Simon Möller (dl9pf) Feature #306529, revision 1 Title: Deactivate build if home:user:branch:foo is inactive for 1 or 2 weeks Buildservice: Unconfirmed Priority Requester: Important Requested by: Jan-Simon Möller (dl9pf) Description: It would save quite some cpu-cycles if branches which are not in active use - e.g. no change in 1 or 2 weeks - would just get the build disabled. Thus the wave during each factory checkin wouldn't be that high. Or even delete branches if they're inactive for 1 or 2 weeks and only the pristine _link is there. This could be extended to disable the build for factory repos in user's home-dir if there're no checkin's for some time. I don't want to prevent ppl from tracking factory in their home: , but a plain _link is just pointless and build should be disabled automagically after some time. -- openSUSE Feature: https://features.opensuse.org/306529

1 3

[openFATE 306426] Add Package Wishlist
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Klaas Freitag (kfreitag) Feature #306426, revision 1, last change by Title: Add Package Wishlist Buildservice: Unconfirmed Priority Requester: Important Requested by: Klaas Freitag (kfreitag) Description: In the Buildservice, the package wishlist should be accessible. That would make it easy to pick packages and build it if bored. -- openSUSE Feature: https://features.opensuse.org/306426

1 5

[openFATE 306589] Improve help for CA Management
by fate_noreply＠suse.de 15 Jan '10

15 Jan '10

Feature added by: Michael Calmer (mcalmer) Feature #306589, revision 1 Title: Improve help for CA Management openSUSE-11.2: New Priority Requester: Desirable Requested by: Michael Calmer (mcalmer) Description: This Module should offer a Hyperlink to far more text - possible online. Relations: - CA Management Module has Virtually No Help (novell/bugzilla/id: 515863) https://bugzilla.novell.com/show_bug.cgi?id=515863 -- openSUSE Feature: https://features.opensuse.org/306589

1 2

[openFATE 306590] Yast Common Server Certificate should support modify, delete, export
by fate_noreply＠suse.de 15 Jan '10

15 Jan '10

Feature added by: Michael Calmer (mcalmer) Feature #306590, revision 1 Title: Yast Common Server Certificate should support modify, delete, export openSUSE-11.2: New Priority Requester: Desirable Requested by: Michael Calmer (mcalmer) Description: More features for Common Server Certificate requested: * Ability to Modify/change the certificate * Ability to Delete * Ability to Export Relations: - Yast Common Server Certificate (novell/bugzilla/id: 510798) https://bugzilla.novell.com/show_bug.cgi?id=510798 -- openSUSE Feature: https://features.opensuse.org/306590

1 3