July 2010 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] How to announce team meetings?
by Andreas Jaeger 25 Nov '10

25 Nov '10

I see different teams announce their team meetings in different ways and suggest to discuss how to do it the best way - and document it. Here's one proposal for this: == Announcing Team Meetings == * Create a meeting page in the wiki to collect the agenda * Add the meeting to http://en.opensuse.org/Portal:Meetings * Get the meeting in the calendar on news.o.o - this way the openSUSE Weekly News Team will add it to their calendar * Announce it via opensuse-announce(a)opensuse.org and news.o.o. for the first meeting or for special meetings * Announce it on your team mailing list * Good practice: Announce a preliminary agenda with topics for the meeting and not only that it will take place Right now we have both the wiki calendar in the meetings portal and the news.o.o calendar, I propose to remove the wiki calendar and point to news.o.o. Thoughts on this? Btw. - I would add the result of our discussion to http://en.opensuse.org/Portal:Meetings, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

10 24

[opensuse-project] Bugzilla is missing in the wiki?
by pistazienfresser 27 Aug '10

27 Aug '10

Hello wiki-list! A) The problem: *There seems to be no article about Bugzilla in the wiki* Maybe someone could help the consumer a bit if she/he needs help from the wiki with bugzilla about the issues: 1) a) to know what bugzilla is - the description and the definition (the wiki helping the consumer to get basic knowledge about a essential part of the openSUSE project - in my opinion the lowest level, according to the telos/meaning of namespaces, namespace definitons and namespace rules: so namespace 0=main or at least namespace 102 = portal) b) to know if someone else has the same problem (troubleshooting/support - I think that would be the most wanted but according to the words of the definition a article only on this issue would be member of namespace SDB) 2) a) wants the developers to tell about a problem that he has so that the developers can help him (article about to get help by by telling the helpers about the problem - namespace SDB) b) wants to help the developers to improve the distribution by telling them about a problem hat she/he had (article about helping the helpers by telling the helpers about the problem - namespace openSUSE) c) wants other users to tell about a workaround/solution he had figured out (the wiki helping to help the potential helper to tell the users/consumer about a possible resolution - namespace openSUSE) B) The plot/the detailed description: The last night I saw a edit according to a problem that prevents users to make live usb devices form DVD images and therefor to install a DVD image on a netbook (which by definition has no DVD or CD drive): This morning I wanted to help the users that had reported that problem in the forums (see: http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq… http://forums.opensuse.org/english/get-help-here/install-boot-login/442070-… and on the wiki by telling him how to escalate that a bit so that in the future the potential users of openSUSE on a netbook do not give up just because they are not able to install a DVD image on a netbook (what would be a bit funny after making the netbook support a highlight of the new version open 11.3 and the mobile things a strategic/tactic target of openSUSE - see the new openSUSE strategy). I thought it would be an easy thing to give them the according article about bugzilla in the wiki (a "what is" including the purpose of bugzilla and may be with a little "how to use" or at least a link to a article about the detailed "how to use"). I gave "bugzilla" in the normal internal search engine of the wiki - with me been logged in and so (differing to the default settings) with the search in namespace SDB = ns102 also enabled so I would get with will (as I understood) the openSUSE-wiki's seach engine make 0) would lead to an article with name/tile "bugzilla" if such would exist (and if not go to 1) and 2) which may be equal to http://en.opensuse.org/index.php?title=Special:Search&limit=20&offset=0&ns0… ) 1) first get articles displayed with with "bugzilla" in the name/tile and 1) will be containing (without a namespace related) order 1.1) articles in the namespace main (ns0) 1.2) articles in the namespace SDB (ns100) 1.2) articles in the namespace Portal (ns102) 2) second get articles displayed with with "bugzilla" in the body/text and 2) will be containing (a namespace related) order 2.1) articles in the namespace main (ns0) 2.2) articles in the namespace SDB (ns100) 2.2) articles in the namespace Portal (ns102) According to the google-like output/display of the output of titles and text around the fitting words in the text of the search results the best fitting but last displayed article of 23 search results was: http://en.opensuse.org/BG-Submitting_Bug_Reports which sees to contain something about the topic 2) but cause of my not existing knowledge of/in that language (my guess: Bulgarian with Cyrillic letters - ISO 639-1 bg) I can understand only the links and the title of that article in English. C) The solution?: Greetings pistazienfresser -- - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

8 13

[opensuse-project] openSUSE Strategy Discussion: For the productive poweruser
by Pavol Rusnak 09 Aug '10

09 Aug '10

Hi all! Okay, you know the drill. This one is the "openSUSE - For the productive poweruser". ---8<------8<------8<------8<------8<------8<--- == openSUSE - For the productive poweruser == === Statement === openSUSE should strive to be the productive distribution for powerusers on modern PCs (workstation, laptop, netbook, server) and having a healthy balance of innovation and stability. We cannot compete with Ubuntu for the übernoob segment, and we shouldn't compete with Fedora on being experimental bleeding edge - instead we should pick the middle ground. This strategy would be nicely in line with SLE and what (open)SUSE has historically been, and what existing users expect from openSUSE. The main purpose of the strategy in my opinion is to help developers, contributors and marketers all pull in same direction, and to clarify for users what openSUSE tries to be and do. NOTE: In my mind you don't have to be a kernel hacker or a guru sysadmin to be a poweruser, in my estimation powerusers cover: * ~10% of all PC users * ~50% of all Linux users * ~75% of existing openSUSE users * ~100% of existing openSUSE contributors == Activities == ==== We need to be excellent in the following ==== * Making sure as much as possible just works out of the box * Having good and sane defaults so the user can do what ''he'' wants to do * Focus on providing tools for being productive/creative (IDEs, editors, authoring tools, graphics manipulation, office productivity, etc.) * Providing admin tools that are powerful yet (reasonably) easy ==== We will try to do the following effectively ==== * Deliver a strong, general purpose distro that anyone can use without too much effort * Innovate and keep up with latest upstream developments === As project, we will not focus on the following anymore === * Dumbing things down for Aunt Tillie * Going out of our way to support old hardware and non-mainstream architectures * Supporting form-factors that are not workstation, laptop, server or netbook ---8<------8<------8<------8<------8<------8<--- -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

14 31

[opensuse-project] openSUSE Strategy Discussion: The Linux Distribution Platform Strategy
by Pavol Rusnak 05 Aug '10

05 Aug '10

Hi all! Today we continue with public discussions about strategy proposals submitted by you, our beloved community. The first one is the "Linux Distribution Platform Strategy": ---8<------8<------8<------8<------8<------8<--- === openSUSE, the Linux distribution platform === == Goals == The goal of openSUSE as a project is to provide a platform for distributing Linux and software running on Linux to a wide range of users. This platform consists of tools for creating software distributions, the openSUSE distribution as base and reference implementation, and the community supporting the tools and the distribution. On top of the platform the openSUSE universe consists of more specific distributions, which make use of openSUSE infrastructure and technology. Examples are SLES, MeeGo, openSUSE Education, KDE and GNOME live systems, and could also be for example developer or cloud oriented distributions and more. So openSUSE provides a way for subteams to address specific user groups and needs. openSUSE also provides means to distribute software independent of the environment of the user to spread Linux based software and make software easily available for use in the openSUSE distribution and systems based on it. The openSUSE distribution acts as a reference distribution, providing an environment for testing the used technology, a stabilizing ground for common components, and a real-life use case for applying technology and distributing Linux software. It's targeted at technically interested users, including programmers and system administrators. It has a focus on good user experience and making technology available to end users. It doesn't target users with highly specific technical needs. == Activities == = Essentials = * Provide stable set of supported core packages distributions can build on * Broad hardware support of components and platforms * Provide tools for package and distribution building and testing (e.g. openSUSE Build Service) * Provide common building blocks for distribution, e.g. installer, configuration tool, maintenance tools, development tools for web, native and other applications, and more * Provide home for overall community and specific openSUSE teams, e.g. bug tracker, wiki, mailing lists, collaboration tools * Create the official openSUSE distribution as reference implementation * Enable, support, and collaborate with specific teams to create their own distributions * Enable and support, and collaborate with upstream developers to build and distribute their software on openSUSE = Good to have = * Provide wide variety of packages for further use * Community for user support * Work on standards which make it easier to mix components, e.g. free desktop standards * Collaboration with other distribution platforms = No focus = * Directly providing a polished distribution for non-technical end users * Bleeding edge technology ---8<------8<------8<------8<------8<------8<--- -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

19 60

[opensuse-project] Confused by Contrib write-up on new wiki
by Greg Freemyer 04 Aug '10

04 Aug '10

All, My impression was that packages in contrib could be upgraded to newer versions with relative ease if the package maintainer wanted to do that. In fact, I thought that was one of the major differences between factory/distro and contrib. Reading http://en.opensuse.org/openSUSE:Contrib#Rules_for_the_repository I see: === The repository is branched at openSUSE release time (openSUSE:Factory:Contrib -> openSUSE:<version>:Contrib) * After the branch no version updates are allowed anymore, unless explicitly allowed by openSUSE:<version>:Contrib maintainers. * Bugfixes happen as patches to the packages === That says to me, it has the same basic update rules as the distro. Can someone clarify if the above is right. If so, it leaves me with one big question. What is the difference between factory and contrib? Reading the contrib page, I see nothing that tries to answer that question. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 3

[opensuse-project] "Legal"/"General disclaimer" has been moved to "Terms of site"
by pistazienfresser (see profile) 03 Aug '10

03 Aug '10

Hello list, dear administrators of all the sub-projects of the openSUSE project, the content of the URL http://en.opensuse.org/Legal or http://en.opensuse.org/openSUSE:General_disclaimer has apparently been moved to http://en.opensuse.org/Terms_of_site . As Redirects get regularly deleted and content gets regularly moved from one namespace to an other or form one title to an other in the new wiki see: http://wiki.opensuse.org/Special:Log/delete http://en.opensuse.org/index.php?title=Special%3ALog&page=Legal the administrators of other openSUSE (sub-) projects which are still referring to one of those or another old URL for this terms/legal issues/standard form contract (e. g.: http://forums.opensuse.org/faq.php?faq=novfor#faq_novellgen https://features.opensuse.org/ "Disclaimers" http://old-en.opensuse.org/Welcome_to_openSUSE.org "Disclaimers" http://software.opensuse.org/113/en "Legal information" ) may think of linking to the new URL or copy the content and use an URL in the according sub-project or make a page with new content in their sub-project. Greetings pistazienfresser P.S.: This is not meant as a comment that includes an opinion about the validity this terms in general... -- - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 6

[opensuse-project] Statistics from the Weekly News
by Sascha 'saigkill' Manns 02 Aug '10

02 Aug '10

Hello Mates, i'm not sure if this is the right Emaillist, but i try it. For me it would be interesting how many hit gets the Weekly News. As Example: en, de an ja. Have we an option to track that? cu Sascha -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

4 7

[opensuse-project] The openSUSE Project welcomes Jos Poortvliet as new Community Manager
by Andreas Jaeger 02 Aug '10

02 Aug '10

We’re proud to announce today that Jos Poortvliet will join the openSUSE project and Novell as openSUSE Community Manager starting on August 1. With Jos we’ve found a leader with excellent community building experience combined with a very welcoming nature, many fresh, promising ideas and a strong drive to grow the openSUSE Project. Jos holds a degree in Organisational Psychology from the University of Utrecht and has gained valuable experience in several professional roles ranging from Project Manager at KPN to Service Level Manager at Royal Bank of Scotland. Last but not least, Jos is a leading member of the KDE Marketing Team and has helped Akademy and the Gran Canaria Desktop Summit attract a vibrant and collaborative audience. Jos commented, “The opportunity to become part of the international openSUSE community is very exciting. There are a great number of interesting developments going on in the free software world, and openSUSE plays a major role in many of them. I look forward to working with the community on these, helping it grow, finding new directions and ways of developing, and delivering its innovative technologies to users and developers around the world.” We enthusiastically welcome Jos and look forward to his working with the openSUSE community to shape the future of the openSUSE project. After his start he will be deeply involved in the openSUSE conference, other community events and activities, and of course he will have the pleasure of promoting openSUSE wherever possible. Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

15 27

[opensuse-project] wiki search, much improved, thank you
by Greg Freemyer 29 Jul '10

29 Jul '10

Greg -- 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 Conference Meeting Thurs, July 29
by Michael Loeffler 28 Jul '10

28 Jul '10

Moin, please join tomorrow's openSUSE conference meeting on Freenode IRC Network in the #opensuse-project channel at 14:00 UTC, 4pm CEST, 10am EST Topics: - Current status of Call for Papers - talks selection, creation of a program - to do's for next 2 weeks Thanks Michael -- Michael Löffler, Product Management 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

1 0

[opensuse-project] openSUSE @ FrOSCon needs you
by Jan Weber 27 Jul '10

27 Jul '10

Hi all, as you might know on August 21st and 22nd the FrOSCon [0] takes place in St. Augustin (near Bonn) in Germany. We have a confirmed booth at FrOSCon and I am now looking for volunteers to man the booth! So if you have some free time and want to help promoting openSUSE at FrOSCon, drop me a note and add yourself to the wiki page [1]. So long, Jan [0] http://www.froscon.org/ [1] http://de.opensuse.org/Veranstaltungen/FrOSCon/2010 -- 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] ICECC / ICECREAM - Two input files?
by Karl Krach 26 Jul '10

26 Jul '10

Hello, I'm looking for the Icecream mailing list. I found many references to http://en.opensuse.org/Icecream - but it looks like as if this page is discontinued. My problem: I'm using Icecream with a toolchain generated by Buildroot. It's a GCC 4.4 which supports the --sysroot flag. When compiling with makefiles generated by qmake, Icecream builds always local because it detects "-isysroot /path/to/toolchain" as second source file: found another non option on command line. Two input files? This patch would solve this problem: --- icecc-0.9.4/client/arg.cpp 2009-04-30 14:35:23.000000000 +0200 +++ icecc-0.9.4-patched/client/arg.cpp 2010-07-26 08:42:23.000000000 +0200 @@ -249,7 +249,8 @@ || str_equal("-iwithprefix", a) || str_equal("-isystem", a) || str_equal("-iwithprefixbefore", a) - || str_equal("-idirafter", a) ) { + || str_equal("-idirafter", a) + || str_equal("-isysroot", a) ) { args.append(a, Arg_Local); /* skip next word, being option argument */ if (argv[i+1]) { How can I submit it? Best regards, Charly -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

3 2

[opensuse-project] How do I delete a directory from my repositories?
by Jim Henderson 25 Jul '10

25 Jul '10

I've spent a little time working with OBS today for a small project I'm working on in Studio, and I noticed that I have a repository for openSUSE 11.0 in my home project at: http://download.opensuse.org/repositories/home:/hendersj/ You can see an openSUSE_11.0 directory there - there's no packages in the structure under that, but I'd like to clear it out if it's possible (just to avoid any confusion). I don't have 11.0 (even the discontinued 11.0 repo) in my obs configuration - all I have is 11.2 in there. Can someone point me in the right direction? Thanks, Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 1

[opensuse-project] Strategy: comment on users and contributors
by Andreas Jaeger 24 Jul '10

24 Jul '10

During the openSUSE Strategy discussions, some questions were raised about users and contributors and their roles within our Community. I'd like to discuss and define these a bit in the context of our discussions. Community - users and contributors ================================== Community is often defined as a collection of people who interact together - but what does this mean concrete for the openSUSE project? I suggest to define the openSUSE community as an open community that includes everybody that likes to be part of it including users installing openSUSE on a system as well as contributors that shape the project. Still this large openSUSE community can be seens as a larger group of users and a smaller group of contributors. The users are an important part of the openSUSE ecosystem. They are a target and beneficiary of what we do in openSUSE and we also strive to reach out to our users to become contributors to the Project. This should be a virtuous circle - the more users we gain, the more our pool of contributors and contributions grow. And the more contributors the Project gains, the more users we gain. And in order to sustain that growth of users and contributors, we must ensure an environment that supports the needs of our contributors by providing them with the tools they need as well as delivering products that our users get excited about. Contribution to the openSUSE project ==================================== A lot has been discussed on what a contribution is and I'd like to highlight a few examples of contributions to the project. Let's start with the distribution first: A user downloads the openSUSE distribution from the Internet, buys a box, or gets the install media in some other way. If a problem is encountered, the user asks for help, e.g. via: * the openSUSE forums * the openSUSE IRC channels * via a social network like twitter, Identi.ca or Facebook * the openSUSE mailing lists * uses a search engine to see what others have said, this might bring him to any of the openSUSE wiki, forum, mail lists or archives I would expect that this new user receives positive answers from forums, IRC channels, social networks and mailing lists. This might be a friendly pointer (not a simple RTFM!) to specific sections of relevant documentation, a more appropriate place to ask or maybe an detailed answer to the concrete question. People helping this new user are contributing to the openSUSE Project. Users also become contributors by writing documentation, moderating discussions, administrating infrastructure, or by with translations existing documentations and openSUSE wiki pages. There are many other forms of contribution that do not require programming ability - for example openSUSE Ambassadors running booths or making presentations at conferences and local Linux user group meetings. Eventually, the user might download a new package from the openSUSE Build Service or report a bug using bugzilla. Obviously software developers are contributing to the community when their original and creative output is made especially for the openSUSE project, e.g. running on our infrastructure and improving the distribution through iterative testing/fixing, packaging FOSS software, integrating them into the openSUSE distribution, and coordinating with the upstream projects. Likewise, as innovations or improvements are made by developers, we spread the word of their efforts and successes through blogging, marketing, and other means, which then attracts even more users. The more users we attract, the more feedback is given to developers through conversations, bug reports, feature requests, and other venues. The large upstream OSS community is contributing with many packages, e.g. the Linux kernel, to the openSUSE project but not in the sense of a core contributor to the project - more as an "independent supplier" that rather than an openSUSE contributor. However, we extend an invitation to upstream developers to become openSUSE users and make it their platform of choice for developing and contributing both upstream and directly to the openSUSE Project. Growing Users and Contributors ============================== During the Strategy Team's discussions, we concluded that our primary goal at this time is to focus on increasing the number of contributors in our community by encouraging our users to grow into those roles and attracting contributors. To do that we know we must provide all with the tools and the ecosystem to "Have a lot of fun". And, by growing the contributor community we automatically support the goal of sparking that virtuous circle of sustained growth benefiting the entire community. Let me also emphasize that the above listed contributions is just a small set of examples. There are many more ways to contribute, and often we encounter fresh and new ideas from users who should be listened to, encouraged, mentored and grown into productive project contributors (where possible). Let us keep in mind that as a project we care about the whole diverse community - and the discussions have shown how diverse it can be - and I'd like to refer to our guiding principles: "We value choice. We accept and respect that there are different ways to work, different preferences for applications, environments, tools or interfaces and different goals of users and contributors. We value diversity and pluralism as a way of addressing the needs of a broad variety of people." What do you think? Is that a common ground? If yes, I'd like to add it the the collection of strategy pages and look forward to edits, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

12 14

[opensuse-project] Regarding codenames and colors
by Stephan Kleine 23 Jul '10

23 Jul '10

Hi guys, regarding the code names and colors discussion. Personally I'm just tired of having a "green" distro cause we are supposed to be "green". Also I liked coolos idea of code names that got drowned for known reasons. So here is my proposal: How about we use an animal as code name and its main colors as the distro colors for a release? This will give us enough room to play and select and as long as older themes still work noone should get harmed. An important part is that not only boot, but also KDM, GDM, OO & Gimp splash screens and so on should be easily exchangeable while maintaining a certain "corporate identity" which should also be adopted every now and then when it is necessary. Point being, if we get those things to adopt to certain colors "automatically" it shouldn't be that much work while choosing a nicely looking animal, it is, probably, pretty easy. E.g. we could use a Zebra for some stylish black and white theme or some exotic fish for some more colorful one or ... the choice is endless. The only important thing is that those themes shouldn't be "pressed" on anyone but it should be easy to revert to a previous one or .... What do you think? regards, Stephan -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

8 23

[opensuse-project] Impovements in a mail list worflow
by Rajko M. 23 Jul '10

23 Jul '10

We often have to refer to some mail list article. Now we have to find article in a mail client, open and browse http://lists.opensuse.org to find that article and then copy link in our email. It is job measured in minutes for active lists. It would be very convenient to have list archive link added to the mail footer with existing links, or even instead of unsubscribe link. Such functionality is provided for forums users that access them via nntp as line in the footer: View this thread: <link to thread> In case of mail list archive that stores messages per month, threads at the end of the month are broken in 2 pieces, so reference to thread is not useful, but pointer to the article will be improvement. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

6 6

[opensuse-project] How to resurrect disappeared wiki pages?
by Michal Marek 22 Jul '10

22 Jul '10

Hi, I found that http://en-old.opensuse.org/Kernel_Git disappeared from the new wiki. Are there any guidelines where to put the old articles back? Other pages from http://old-en.opensuse.org/Category:Kernel are not found in the new wiki either :-(. Michal -- 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] openSUSE Strategy Discussion: another proposal
by Marcus Moeller 21 Jul '10

21 Jul '10

Hi all. As I did not take part in the strategy meeting, I want to add my proposal, here. openSUSE - #1 KDE distribution Statement Most Linux distributions rely on a (more or less customized) GNOME desktop as default environment. openSUSE's advantage has always been the great KDE integration (and now even defaults to KDE in the desktop environment selection dialog). We should focus on that and make openSUSE the best KDE based desktop distribution available. This is not meant to start another flamewar, nor to completely drop GNOME (of course there still could be community supported Spins available), it's just about our primary focus. We need to be excellent in the following * Create a visual unique desktop experience with KDE * Adopt the latest KDE technology early, but care about stability * Offer the best platform for QT/KDE AND Java developers * Integrate MeeGo (focus on QT) * Lobby for KDE We will try to do the following effectively * Deliver a build service for building distribution and applications * Provide best desktop experiences with KDE and MeeGo (focus on QT) * Integrate social service apps, bind to connect.openSUSE.org * Bugfixing * Testing * Improving KDE upstream * Collaboration with other Linux distros As project, we will not focus on the following anymore * other desktop environments -- Greets Marcus -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

37 318

[opensuse-project] Re: openSUSE versioning scheme
by Per Jessen 21 Jul '10

21 Jul '10

Vincent Untz wrote: > (I'm setting Mail-Followup-To to opensuse-project, since that's where > this discussion should happen, but I agree we might want to wait for > the end of the strategy discussion) > > Le samedi 03 juillet 2010, à 09:10 +0200, Martin Schlander a écrit : >> Fredag den 2. juli 2010 17:05:06 skrev Andreas Jaeger: >> > On Friday 02 July 2010 16:56:04 Thomas Schmidt wrote: >> > > Shouldn't we call this 12.0? >> > > Reassigning the features afterwards would be additional work. >> > >> > Naming of the next release is a separate discussion we might have. >> > I'm opposed to both 11.4 and 12.0 and look forward to great >> > proposals, >> >> Let's not get too creative here. No funky codenames! :-) > > We actually have code names, and it's the shades of greens. 11.3 is > Teal. We just don't advertize this -- yet. (I think we should). The codenames are visible on the console. Personally I think codenames ought to remain internal, project-only - like today, but _perhaps_ with a bit more awareness/usage. I really don't like the hip Ubuntu naming and I'd have to use a dictionary to find out what "teal" is. (same goes for most of the Ubuntu names). >> We should go for a simple numbering scheme, that doesn't cause the >> confusion that the old one has (a lot of people give different >> meanings to the numbers, even though they don't mean a thing - other >> than of course x.1 meaning "unusually buggy"). >> >> Either do it the Fedora way. openSUSE 12, 13, 14 etc. >> >> Or the Mandriva way 2011.0, 2011.1, 2012.0 etc. > > (Or the Ubuntu way, except that it doesn't work well with the next > version which would be 11.03: 11.03, 11.12, 12.07) What is wrong with the existing scheme? Two things that come to mind: 1) it's just a continuation of the SuSE Linux numbering 2) there's no implied meaning of '.x' I propose we name the next openSUSE "openSUSE 1.0". Wrt 2), I don't know if we really need/want an implied meaning of the '.x', but maybe we can come up with an idea in the context of strategy. (one thought: even = desktop release, odd = server release?) > One technical side of the decision that was pointed out in an earlier > discussion is that we want to keep some suse_version compatibility. > That means we still need to have, somehow, 11.3 < $nextversion. That did occur to me, but I'm unaware of the details. -- Per Jessen, Zürich (25.1°C) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

5 7

[opensuse-project] Possible strategy discussion topic: Education and Training
by Jim Henderson 21 Jul '10

21 Jul '10

I've been kicking this around for a little bit now in my own head, and I'd like to propose that the project develop a strategy around user education and training. For those who don't know, in my "day job", I work for Novell's Technical Training department as the testing program manager. In particular, I have responsibility for the business end of the practicum exam delivery (and if you want to talk about that with me, feel free to contact me off- list, I'm always happy to talk to people about their exam experiences, even if I can't get into specific details for their exam). In my role, I also am involved in technical certification, and work closely with people who develop training (I used to be a trainer myself for eDirectory, and developed the training materials to meet objectives we had for that product) as well as being involved to some extent in developing the next generation of training delivery. I was intrigued by an article in this month's Linux Format about Ubuntu's "Lernid" training system. It sounds like that project has a plan of sorts for training users on using their system, and this seems to me to be a way in which we could grow the community from which we are looking to draw contributors. In the forums, we've also had a couple of people express that some training on openSUSE would be very helpful and useful for them (either personally or to help people they knew learn about Linux and start using it). The way I see it, we could break down training into a few classifications: 1. End-user training 2. Contributor training (for example, how to write effective bugs, code style conventions, things like that) 3. Community training (where to ask what, what to expect, that sort of thing). In items 2 & 3, a lot of that content is in the wiki already - I see the largest opportunity as being #1. There may be a loose collection of things that fit in there as well (such as the howtos for configuring certain video cards), but from a training perspective, some structure and flow between the topics (along with analysis of how the topics can/should flow from one to another) is something that's I think is missing (I may be wrong and just haven't looked in the right places). What I'd like is for the project team to consider that end-user education (in particular) is something that could help us attract more users and help them achieve a more comprehensive view of how to use openSUSE more effectively. Things like skills migration from Windows to openSUSE would be something I see as key; one forum user put it as "people learn by making connections to that which they already know"; I see that in my official job role as well - the students who are most successful are the ones who can associate what they're learning with something they already know - even if it's not a direct 1:1 mapping. Thoughts? Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

11 23

[opensuse-project] Well done on 11.3 release
by Chris Jones 21 Jul '10

21 Jul '10

I just wanted to congratulate the openSUSE development team on a fine job for a fine release of openSUSE 11.3. It's great! I have not had any luck with previous releases of oS, but finally along came 11.3 and reignited my interest in the oS distro. Well done guys. With a rock-solid 2.6.34 kernel and a very (now) mature KDE4.4, it's super quick. Coming from a Ubuntu and Fedora Gnome background, I feel I am back to square one as the oS and KDE way of doing things is very different from what I'm used to. But I'm willing to give it another shot as openSUSE 11.3 remains my current distro of choice. Cheers and congrats. -- Chris Jones Freelance Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 PHOTO RESOLUTIONS - Photo - Graphic - Web W: http://photoresolutions.freehostia.com E: <chrisjones(a)comcen.com.au> or <ubuntu_cj(a)comcen.com.au> Fedora Design Suite Developer and Co-Maintainer E: <foxmulder881(a)fedoraproject.org> GnuPG v2.0.15 (GNU/Linux) keys.gnupg.net KeyID: 769A8262 Public Key Fingerprint: 94D0 BFAE 87A5 376E FCB2 CEBD C717 CD87 769A 8262 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

5 7

[opensuse-project] Seeking MirrorBrain/distribution folks responsible for 11.3
by R. Tyler Ballance 21 Jul '10

21 Jul '10

I am aching to write a blog post[1] about "what it takes" to distribute a release like 11.3, focused around MirrorBrain and openSUSE's use of it along with "conventional" methods for distribution for large files (Akamai, BitTorrent). I'm wondering if the responsible parties would stand up and be recognized :) Hoping a few questions won't be too invasive :) Cheers, -R. Tyler Ballance -------------------------------------- GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero -------------------------------------- [1] I write for http://www.omgsuse.com

1 0

[opensuse-project] Re: openSUSE versioning scheme (was Re: [opensuse-factory] Re: [opensuse-buildservice] Can we please get ARM builds for 11.3+1?)
by Michael Loeffler 20 Jul '10

20 Jul '10

On Tuesday 06 July 2010 15:41:43 Peter Nikolic wrote: > On Tuesday 06 Jul 2010 12:37:58 Jakub Rusinek wrote: > > Dnia 06-07-2010 o 13:34:25 Stephan Kulow <coolo(a)novell.com> napisał(a): > > > Am Dienstag 06 Juli 2010 schrieb Jakub Rusinek: > > >> Dnia 06-07-2010 o 11:12:13 Martin Schlander > > >> <martin.schlander(a)gmail.com> > > >> > > >> napisał(a): > > >> > Mandag den 5. juli 2010 17:34:35 skrev Jakub Rusinek: > > >> >> Ubuntu does their numbering job well. > > >> > > > >> > In my experience noone intuitively understands the Ubuntu versioning > > >> > scheme - > > >> > it always needs to be explained. > > >> > > > >> > But at least there _is_ a reasonably good explanation for it :-) > > >> > > >> Well, nobody says openSUSE should follow their numbering guidelines ;) > > >> . Whether they prefer year written as two digits or not, it's their > > >> choice. > > >> I'd personally vote for eg. 2010.1/2010.2, where the year represents > > >> year > > >> of the release and number after the point represents number of release > > >> that year. > > >> > > >> So - 2010.1 would be first release in 2010, 2010.2 would be second, > > >> 2011.1 > > >> would be first in 2011 etc. > > > > > > Try to say "KDE 4.4.4 won't be ready for 2010.1, but it's in 2011.1" > > > three > > > times quickly. > > > > Then it's your turn to work out another solution ;) . > > > > After criticizing my invention, Ubuntu's way seems pretty resonable. > > Year.month. > > What exactly is wrong with the current system > IS this yet another change for the sake of change or does someone have a > rock solid reason for changing what seems to work very well for Opensuse > note We are NOT Ubuntu we are NOT Fedora we are NOT Debian . > > My vote is we stay exactly as we are now and don't wreak a system that > works just because someone fancies mucking things up for something to do / > get their name mentioned .. +1, I still don't see what's wrong with the current scheme nor real benefits from a new scheme. M > > > There is a saying don't fix what ain't broken or dow yow fix what ay > bosted > > > Pete > > > > -- > Powered by openSUSE 11.2 (x86_64) Kernel: 2.6.30-rc6-git3-4-default > KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" > 14:36 up 3 days 16:20, 4 users, load average: 1.98, 1.84, 1.51 > -- Michael Löffler, Product Management 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

21 88

[opensuse-project] #opensuse-es channel
by Javier Llorente 18 Jul '10

18 Jul '10

Hello listmates, #opensuse-es channel's topic says that openSUSE 11.2 is the latest release. Furthermore, the URL for this channel is wrong. It has been like this for a long time. Could anyone with the appropriate privileges change it? Thanks, -- Javier Llorente

5 4

[opensuse-project] openSUSE is hard to say and write. Rename it.
by Otso 14 Jul '10

14 Jul '10

Hello, This issue shouldn't be unfamiliar to people following this mailing list. Even enthusiasts on this list tend to shorten openSUSE to oS, OS, os or plain suse. I do not know how valuable openSUSE is as a brand name, or how affected Novell is with it, but please consider these points before trashing the idea of renaming: 1) openSUSE is pain to pronounce understandably for non-native english speakers. I experienced this first time lately when trying to explain what distro I'm using to an american person face-to-face. I had thought I had perfect pronouncication. Even for native speakers, it's a mouthful. 2) It's even worse to write. SMS'ing someone to install Gentoo is easier than telling them to get openSUSE. Same applies to fast IRC/MSN/Facebook etc chattings, and BBS's + chans. It's a pain. 3) Plain SUSE doesn't exist. There's SLED/SLES, and then there's openSUSE. Reverting back to good old SUSE is thus an option. Make it officially something like SUSE Linux Community Edition (SLiCE... just came up with that one btw!) 4) Does it actually need an obvious referrer to rest of SUSE family? Fedora doesn't have referrer to RedHat (aside fedora being a hat, which isn't obvious for ~5 billion humans). We could just shorten it to Opsus, Osus, Suso or something similar. New shorter name from scratch, with some referrer to origins? Why not. 5) As long as it's easy to say, write, remember and isn't insulting in any language, it'll also be globally accessible, searchable and mentionable with a lot less hassle. Take it easy, Otso -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

9 8