openSUSE Project January 2009

project@lists.opensuse.org

46 participants
23 discussions

Re: [opensuse-project] Novell?s plans for the comming releases

by Cristian Rodríguez

Birger Kollstrand escribió: > Patents on SW is not valid in Europe. I know, however openSUSE, is produced by legal means, by an US based company. > Patens on SW/Processes in the US > is also a movig target with the Supreeme court reexamening the paent > couts. In the meanwhile the situation improves, we have to live with them (I wouldnt hold my breath though) > Yes, but this discussion is not where I want to raise them. I would > like to see if there was som strategy from SUSE´s main contributor. As Henne told you, there isn't a single strategy. -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/

12 years, 5 months

[opensuse-project] Re: [opensuse-announce] openSUSE Project Opens Feature Tracking with openFATE

by Rob OpenSuSE

2009/1/16 Joe 'Zonker' Brockmeier <jzb(a)zonker.net>: > openSUSE Project Opens Feature Tracking with openFATE > > The openSUSE Project is pleased to announce that feature tracking and requests > are now available to the larger openSUSE Community. The openSUSE feature > tracking system, openFATE[1], is now live and accessible to anyone with an > openSUSE account. This is nice! It was frustrating when Bug Enhancement request was resolved by an inacessible fate #. The comments actually seem to work to. Great improvment, thank you. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] openSUSE GNOME meeting (2009/1/15)

by Rodrigo Moya

Back to weekly meetings 11.2 plan: • AI: add 11.1 ideas that were not finished (http://en.opensuse.org/index.php?title=GNOME/Ideas/11.2) • Focus on 3 things: ∘ Community building (building new tools, mails, etc) ∘ Integration (Remove more little niggles in openSUSE with how GNOME and other pieces work) ∘ Features: ‣ 3-5 big issues for upstream this year to be delivered back to openSUSE via GNOME releases 11.2 ideas: • DeviceKit integration to replace HAL • Package review (excessive build requires, splitting) • further PulseAudio adoption • sound themes • P2P integration (bittorrent) • podcast creation platform • remove bonobo from libslab • scheduled jobs tool • flickr slideshow screensaver • time machine • new desktop default setups • PolicyKit deeper integration (RunAsRoot in .desktop/AdminKit) • Color management on the desktop • ship a selection of screensavers • fix the applications menu ∘ the structure (too complex, too many submenus, etc.) ∘ the desktop files appearing in many places ∘ hiding desktop files that we don't care about • fix the GenericName vs Name vs Comment stuff in desktop files • move packages to Contrib • HIG improvements in upstream and opensuse-specific things • Find 10 common items people do on 1st install and make those work really well • Boot/desktop loading performance improvement • More marketing: ∘ tips&tricks on linux, non-opensuse specific, things (screencast howto, hardware usage (TV cards, webcams, GPS, etc), etc, etc) to get more people to try openSUSE ∘ Daily ISO/live CDs? ∘ Prebuilt VM images? ∘ More blogging • Upstream: ∘ Working-out-of-the-box jhbuild ∘ build brigade/build service integration ∘ more housekeeping in g-s-d ∘ move gconf schemas to /usr/share (schemas are data, so will remove lots of rpmlint warnings) Next meeting (Thu 22nd Jan) • Prepare package days/bug squashes • Discuss features -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] new security checks of the installation media for 11.1

by David Bolt

I'm the present maintainer of makeSUSEdvd[0] and am trying to figure out what's changed between the release of 11.1a2 and 11.1 that results in broken ISOs. Previously, makeSUSEdvd was able to take the contents of any of the release DVDs, allow extra packages/patterns to be added and, after the contents file was updated and signed, would create a bootable ISO that allowed installation without complaints. However, there was a change somewhere between alpha 2 and gold master, and this is no longer the case. Now, although the contents file on the DVD is signed, the installation routines check the contents file on the new image, claim it isn't signed and so aborts the installation. So, if anyone has any helpful pointers as to what needs to be done to satisfy the new 11.1 security checks, they would be most helpful. [0] built packages are here: <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_11.1/…> <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_11.0/…> <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_10.3/…> Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s | openSUSE 10.3 32b | openSUSE 11.0 32b | openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.6 | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)

by Eric Springer

On Thu, Jan 8, 2009 at 2:19 AM, Dirk Müller <dmueller(a)suse.de> wrote: > In one of my previous mails I and several other people have proposed to split > openSUSE into a "common core" base that contains the newest hardware > enablement and base system (compiler, kernel etc), and the addons, like the > desktops. both can be released independently and the common core can be > released in a staged fashion, allowing people to use a stable base system or > the most recent base system, one of which might be ideal for their hardware. > > It was dismissed as "very hard to promote a new openSUSE release which only > changes the base system", but I have the counter argumetn: it is a lot easier > to promote a new desktop on a stable openSUSE base system (that was released > and fixed already). > > Greetings, > Dirk For what it's worth, I think it's a fantastic idea. It'd be short sighted to dismiss this for marketing reasons, when (imo) we'd end up with a clearly superior product. I know it's not exactly the marketing being referred to, but I recently recommended and offered to install openSUSE on a colleague's laptop. After using it for a little, I was forced to eat my words -- ask around for an XP cd -- and put it back on. It was simply far too buggy/crashy/unstable, and I can't very well say "Oh, just wait a couple weeks and the updates should/might sort it out". So we can have something that we can market (Shiny new release!) or something that is actually marketable. =) Besides, if we used this to be the first major distro to release for new versions of gnome, kde and xfce that in itself would be more publicity than we currently receive. -- Eric Springer (Erikina) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] openSUSE GNOME meeting (2009/1/8)

by Rodrigo Moya

2008 accomplishments + We now have a community around GNOME that didn't exist in 2007, Novell people not from the desktop team +, more importantly, external people + 2 GNOME-ish people on the openSUSE board + Improved collaboration with upstream, but still lots of work to do: intl clock, multihead + Bug triaging, package days were a good thing, but lack the regularity to engage more community + Build service usage and osc gnome plugins were awesome + FOSDEM was a big success 2009 plans + Testing and bug filing is working ok, but need to get community people more involved - users.opensuse.org could be a place for external people to meet up in areas of interest - Novell infrastructure (iChain, closed bugzilla) sometimes doesn't help, maybe openSUSE could be decoupled from Novell? - Market openSUSE as a great platform for software development? - Mentor university students (outside of Google SoC) - Internal people are online working hours, but not always on weekends or evenings, which is when most external people come - Will come back to weekly meetings + Should we innovate more? On what? - Automating stuff, like in osc gnome, helps a lot (weekly meetings) + Leadership - Some activities (bug days, meetings, etc) are not done by a dedicated "team", so sometimes they don't get organized + Upstream - Package jhbuild with all needed dependencies - Participate more in new UI designs (3.0, drive usability tests, experiment with new UIs, etc) Next meeting + Everyone brings a goal and ways to to achieve it for discussion + Discuss having regular bug days, patch upstreaming, etc days + Discuss more ways of getting people involved + Discuss working on more new upstream features + Discuss 11.2 features (http://en.opensuse.org/GNOME/Ideas/11.1) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] Development release: How to make it better,

by Eric Springer

On Sat, Jan 3, 2009 at 3:00 AM, Cristian Rodríguez <crrodriguez(a)suse.de> wrote: > nordi escribió: > Just replace the binaries with >> >> xmessage "OpenOffice is currently broken. We're working on it." > > What is happening in this thread ? suggestions are getting more and more > ridiculous everyday.. how you will ever figure that openOffice is broken > if you dont include the binaries ? Oh please. The meaning was extremely clear and obvious. It was _well known_ that the package X (in this case, openoffice) was broken, meaning every person who used it came across had the same issues. Wasn't able to use it. Had to search for search for a bug report, see that it's been confirmed a dozen times. Nobody is saying that things need to be perfect, but what we are saying is to not waste our time with things already known. These packages should lie in some sort repository intended for developers of the package until you believe that it actually requires _testing_. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

Re: [opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)

by Eric Springer

On Wed, Jan 7, 2009 at 12:33 AM, jdd <jdd(a)dodin.org> wrote: > > knowing what kde or gnome version we have is plain ridiculous if we > can't have a working computer... > Absolutely -- it's seriously a major issue for openSUSE. I haven't encountered anything nearly as bad with other distros (or even bsd for that matter). Anyone want to put forward a concrete plan/proposal that we can hopefully discuss/vote/implement? -- Eric Springer (Erikina) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] release as an add-on?

by James Tremblay aka SLEducator

Hey guys, What are the obstacles to the idea of marketing a full release at X.0 and then releasing\marketing "patch CD updates" instead of full community sub-releases(still a fully installable dvd if desired, specifically for the x.3)? We would definitely be doing something different than the rest of the distro's (good PR) and if the patch cd could accomplish the same kinds of updates that we offer in our current sub-releases with less work and more stability for the end user, it would be a win\win\win: openSUSE team gets to show off YaST and Build Service, marketing gets to differentiate openSUSE, the end users need for a fresh install could be reduced. Extra possible "win" - "long term support "could more easily be moved to x.3 releases citing the x.1\x.2 as support levels for x.0. with the bonus side effect of reducing update channel bandwidth. i.e. security only on x.0 then nothing unless x.1 is applied (This is nothing new to major software vendors, can't tell you how many times I've heard "we only support that product at x.1.2.3, please upgrade.") then x.3s could also be easily translated to SLEs. It seems a waste that SuSE built YaST with all this functionality to not let openSUSE benefit from it's heritage. Any way , openSUSE is yet again filled with many exciting things while still delivering the hope of many more. I'm happy to play with 11.1, while drooling for 11.2 , just as I was the day after 11.0 released. Thanks for all the fun! JT -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

[opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)

by Kevin Dupuy

Starting last night I've begun to see people on both the support mailinglist and the forums complain they've received an email from the Novell Shop telling them their pre-ordered boxed editions won't ship until January 5th. Does anyone know what's going on? I've seen this happen with previous versions of openSUSE, but I thought there was something done to correct the problem. It seems to me people paying $60USD then not receiving their product until 3 weeks after the free download will think twice about buying the box again. -- Kevin "Yeaux" Dupuy - openSUSE Member Public Mail: <kevin.dupuy(a)opensuse.org> Merry Christmas & Happy Holidays from the Yeaux! -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

12 years, 5 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project January 2009