- openSUSE Project

[opensuse-project] openSUSE GNOME meeting (2007/09/27)
by Rodrigo Moya 28 Sep '07

28 Sep '07

Wiki Status: - Better organisation of GNOME-related wiki content (http://en.opensuse.org/GNOME) - People can help on any task (http://en.opensuse.org/GNOME/Tasks) - Vote for this bug -> https://bugzilla.novell.com/show_bug.cgi?id=325753 - People add themselves to http://en.opensuse.org/GNOME_Team Patch upstreaming: - OSC plugins to help manage patches (osc-plugins-gnome): - http://download.opensuse.org/repositories/home:/maw/ - Rodrigo's branch: http://www.gnome.org/~rodrigo/git/osc-plugins.git - Michael's branch: http://primates.ximian.com/~maw/git/osc-plugins - We're going to force annotation on patches for a better organisation - http://en.opensuse.org/GNOME/Patches **** AI: add info about these plugins to the wiki Bug plan: - Important bugs to be fixed at http://en.opensuse.org/GNOME/Bugs - Use topics to fix bugs related to them, like http://en.opensuse.org/GNOME/Multiscreen - Use voting system in Bugzilla to know what bugs openSUSE community wants fixed - Policy for when upstreaming bugs GNOME:Community policy status: - Clear policy for what should be in GNOME:Community (http://en.opensuse.org/GNOME/Community_Inclusion_Policy) - Need specific GNOME packaging guidelines, templates in the build service **** AI check if the build service can have GNOME templates or write a OSC plugin that creates the basic spec with all the goodies GNOME:STABLE merge status: - Link packages from G:S to FACTORY - What to do with GNOME:UNSTABLE? Features requests and mini-projects - We need a good way for getting feature requests instead of bugzilla/fate. Use the wiki? idea.opensuse.org? **** AI cyberorg, jpr, and captain_magnus volunteering Q&A: - Automated tests. Use LDTP? osc run-tests plugin? - Use GNOME/ prefix for wiki pages, linking when needed **** AI Write more HOWTOs about GNOME on the wiki - More compiz/xgl integration for applications. - Organise next meetings based on user/developer audience -- Rodrigo Moya <rodrigo(a)novell.com> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] STATUS:Communication/Wiki/Events
by Martin Lasarsch 25 Sep '07

25 Sep '07

Hi, * Events - next on my schedule: Practical Linux, Giessen, .de, LWE .nl * Communication - IRC Project meeting tomorrow - IRC GNOME meeting on Thursday * Wiki - new skin is out, some issues we are fixing it right now - top priority - news feed is working again - sv.o.o looks much better now - next: zh wiki change -- with kind regards, Martin Lasarsch, Core Services SUSE LINUX Products GmbH, Maxfeldstr. 5 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) martin.lasarsch(a)suse.de - http://www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] openSUSE Guiding Principles - 2nd draft
by Martin Lasarsch 21 Sep '07

21 Sep '07

Hi, Here is the next version of the guiding principles, the 2nd draft. Cornelius fixed some bugs and changed other stuff from your feedback. I guess it makes sense to start a new thread, the old one is at http://lists.opensuse.org/opensuse-project/2007-05/msg00208.html If this is new for you, i suggest to read also the old thread. It's also available on the wiki: http://en.opensuse.org/Guiding_Principles Let's discuss the new version ... -- with kind regards, Martin Lasarsch, Core Services SUSE LINUX Products GmbH, Maxfeldstr. 5 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) martin.lasarsch(a)suse.de - http://www.opensuse.org

12 15

[opensuse-project] Merchandise articles for openSUSE
by Michael Loeffler 20 Sep '07

20 Sep '07

Hi, find below a status update and backround info on what Robert and myself currently working. And let's start discussion about what to offer in a shop.openSUSE.org. I'd suggest to keep the sortiment at the beginning small. I'd suggest to start with a 3-5 branded items which could be: - a black t-shirt - a cap - a mug - sticker (provided shop offer that) - pin/button (provided shop offer that) Status: We plan to offer merchandise stuff to anybody interested in. As we are not professional in providing such stuff and have budget constraints we need a vendor doing that for us. The vendor needs to offer shipment to EMEA + NA and the best scenario would be world wide shipment. We found cafepress.com offering that, registered a openSUSE shop there (http://www.cafepress.com/openSUSE - filled currently with one sample product) and need to brand the shop and set up a first set of products offered there. We recently found spreadshirt.net offering a similar service but more feature rich for a shopkeeper and offered in different languages but currently they don't ship to NA. I asked them this week if they plan to ship to NA. So, we wait for an aswer by spreadshirt. If they will offer NA shipment as well we tend to start our shop there. Best Michael -- Michael Löffler, Product Management SUSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nuremberg SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

10 14

[opensuse-project] STATUS:Communication/Wiki/Events
by Martin Lasarsch 19 Sep '07

19 Sep '07

Hi not much this week, busy, fast mail from the Hotel before OpenExpo starts ... * Events - OpenExpo in Zuerich starts in an hour :-) - next on my schedule: Practical Linux, Giessen, .de, LWE .nl * Communication - user directory work is done by darix, some minor stuff need to be done afaik - Robert made some "i support openSUSE" buttons, we will publish them soon * Wiki - since nobody really objected on the list, i will use zh and zh-classic for the Chinese wikis. This means work for me, i hope i can do it next week. - rss feed is not updating on the mainpage, working on it. - new skin very soon -- with kind regards, Martin Lasarsch, Core Services SUSE LINUX Products GmbH, Maxfeldstr. 5 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) martin.lasarsch(a)suse.de - http://www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] foo@opensuse.org is a subscribers only list
by Gerald Pfeifer 18 Sep '07

18 Sep '07

The openSUSE mailing lists do not strike me as particularly open. I have been contributing to free software projects for over ten years, but none I can remember appears as unfriendly when someone not subscribed to a list tries to post to that list. Why do we have such a strict setup? As evidenced by hosts like gcc.gnu.org, it is possibly to keep lists spam free without it. *If* we need such a form of moderation, could this be human moderators? Frankly, with unfriendly a reponse like this, I usually think twice about contributing. If human moderation does not work, how about a simple scheme where one has to follow a URL provided in the auto-response to unlock his previously sent message? w3c does this very nicely, for example. Also, the message refers to a "nomail version of the list" but a regular user certainly will have not idea whatsoever what that is and how to subscribe to that version of the list. </rant> My recommendations are: 1. Abandon this level of strictness and instead use decent spam and virus filtering. 2. If this does not work sufficiently well, employ human moderation or a challenge/reponse schema. 3. Better describe what the "nomail version of the list" refers to. Gerald -- Dr. Gerald Pfeifer E gp(a)novell.com SUSE Linux Products GmbH Director Inbound Product Mgmt T +49(911)74053-0 HRB 16746 (AG Nuremberg) openSUSE/SUSE Linux Enterprise F +49(911)74053-483 GF: Markus Rex ---------- Forwarded message ---------- From: zypp-devel+owner(a)opensuse.org To: gp(a)novell.com Date: Mon, 03 Sep 2007 20:35:22 +0000 Subject: zypp-devel(a)opensuse.org is a subscribers only list Hi, this is the mlmmj program managing the mailinglist zypp-devel(a)opensuse.org You have tried to post from this email address: gp(a)novell.com But this address is not subscribed, and only subscribers may post to the list. If you believe you are correctly subscribed, please check the email address you subscribed with in the welcome message, or check the headers of any message to the mailinglist. If you want to be able to post from more than one email address, you can subscribe the other addresses to the nomail version of the list. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

14 18

[opensuse-project] one addition to the guding principles + status update
by Michael Loeffler 12 Sep '07

12 Sep '07

Hi all, we had a discussion with our General Manager Roger Levy about the Guiding Principles. He appreciates the Guiding Principles very much and fully supports them. One suggestion he made was to emphasize as a task the overall success of Linux. I second this. What about adding in the "We want.." section this sentence: ..to foster the success of Linux everywhere Status on the guiding principles: - we stuff the first Board currently - when that's done we'll launch the Guiding Priniciples and fill the Board with life - we're talking about weeks not months ;-) Best Michael -- Michael Löffler, Product Management SUSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nuremberg SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 4

[opensuse-project] STATUS:Communication/Wiki/Events
by Martin Lasarsch 12 Sep '07

12 Sep '07

Hi, * Events - OpenExpo in Zuerich next week, still need help on the booth - on Monday i will do a openSUSE project presentation on a Novell Partner event - next on my schedule: Practical Linux, Giessen, .de, LWE .nl * Communication - guiding principles are nearly ready, we need something for the users to "sign" it. Not sure how to do it, maybe a new group "openSUSE" ... (which means a lot of work for me to change the groups for everybody). If you know something that would work nice in the wiki, scream! :-) I don't want to have a simple wiki page ... - Erin from Novell openAudio is now at the internal Labs conference. We finished all recordings in Nürnberg last week, some additional will be made via phone/skype. * Wiki - cn.o.o is ready, but cn is the tld and not the iso language code. It should be zh. Wikipedia uses zh and zh-classic for zh-tw, i guess to avoid political problems. When we started the wiki we internally agreed that we want to do as much as possible like wikipedia. Any opinions on that? - Frank published the translation templates for the new skin beta3 testing, new help.o.o looks nice! -- with kind regards, Martin Lasarsch, Core Services SUSE LINUX Products GmbH, Maxfeldstr. 5 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) martin.lasarsch(a)suse.de - http://www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 4

[opensuse-project] STATUS: Action Items
by Christian Boltz 12 Sep '07

12 Sep '07

Hello, again I'm not sure if I can attend the project meeting, therefore I'm posting a short overview of Action Items here. Things done since the last meeting: - newsfeed integration in the wiki went public (#293725) News on open AIs: - "online help" icon: - In beta3, KDE has got two new desktop icons for new users: - "online help" -> opens help.opensuse.org in a browser - "openSUSE" -> starts opensuse-greeter - On Gnome, the icons are still missing in beta3 (#300773) - help.opensuse.org was redesigned, however there are no translation and/or no automatic language detection yet. AIs which should be handled soon: - discuss merchandise items to sell (part of #173961) - SDB style guide - ETA expired... (#164757) - announce cn wiki - ETA expired (#238355), additionally there's the question if the domain name should be changed (see status mail from Martin some hours ago) Oh, and #309085 (clarify handling of action item status) is also still open - Henne, feel free to ping me on IRC whenever you see me online. As always: all other AIs have no news - not very surprising, probably everybody is busy with 10.3 beta3 ;-) Regards, Christian Boltz, AI bot (random sig!) -- >Gibt es hier in dieser Liste eigentlich ausser mir noch jemanden ?? Nein, aber es laufen einige Robots, die Traffic vortäuschen. Ich bin auch einer davon. [Tobias Korb und Thorsten Haude in suse-programming] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

[opensuse-project] YAST software installer. - QT version vs GTK version
by Clayton 11 Sep '07

11 Sep '07

I have raised an issue regarding the new GTK version of the YAST software installer over on the user mailing list, and it was suggested I start a new thread here. There has been a lot of work done on YAST to give the Gnome version of the frontend a GTK look and feel. For the most part, the layout and workflow of all the components remained the same with the changes focused only on GTK theming. This is a good idea as it brings YAST in line with the Gnome look and feel for the Gnome users. One change stands out though, the changes made to the software installer component. The Gnome version of the YAST software component has been completely reworked. From what I read, there were several very valid reasons for this, including (among many reasons): - a simplification of the interface - the QT based backend is in dire need of rework The result is a GTK YAST component that is radically different from the QT version. This raises an important usability issue... with a totally different software maintenance component between Gnome and KDE, there is a major impact to documentation, support and the development path. Documentation must now maintain conditional procedural information (If Gnome then do this, if KDE then do the other). Support must consider which window manager the customer is using and adapt their support processes accordingly. Development must now continue down two paths (development resources are hard to come by as it is... for example, a reason given for using only Tango icons in YAST was a lack of resources to maintain 2 icon sets). While these kinds of changes are important, and in many cases badly needed to keep openSUSE a viable product, this impact is critical to consider. I would like to propose a couple of things to help the improvement process. 1. Whenever a major change is introduced that radically changes the workflow of core components (like YAST), there must be a simple and clear way to switch between the new way of working and the old. My preference is to keep the old default in place, but make it clear there is a new tool in place that is being tested and provide the user the choice to switch. This is very important to people like myself who support openSUSE in the real world because there are massive processes built up around existing workflows. A radical change like the GTK software installer costs time and money for people who now have to contend with this change. 2. If a radical change or improvement is in the works for a YAST component, then that change must include BOTH the GTK and QT versions. (or as a bare minimum, there must be a plan to synch the two tools within one release cycle). The GTK and QT versions of YAST need to be in synch.... not in look, but in workflow. The same options need to be present in BOTH versions of YAST. If a major change is planned for QT, then the GTK version needs to reflect that change as well, and vice versa. 3. The GTK software installation component of YAST should either be reworked to bring the workflow back in line with the existing QT one, or the QT version needs to be reworked to bring its workflow in line with the GTK one. Of course this would also include usability improvements and fixing the old backend (something both versions are in real need of). I am sure that there is more I can add here, but these 2 points would go a long way towards keeping openSUSE (and SLED/SLES) consistent and usable. YAST is a highly important and critical part of openSUSE. It is this tool that really makes openSUSE stand out as a better choice (in addition to the very professional "polish" that we give the product). This critical part of openSUSE must remain consistent regardless of theming for one one window manager or another. C. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

6 8