Hi all,
April 16-17 in Antwerp, Belgium, the Linux Open Administration Days will
take place. This free event offers a chance for LPI certification as
well as meeting and talking to linux sysadmins. There is a call for
presentations here: http://www.loadays.org/content/call-presentations
If you want to go and give a talk there about openSUSE tech - that's be
awesome. If you can't afford to go there due to travel or hotel costs,
let me know, we might be able to work something out ;-)
cheers,
Jos
Hi openSUSE people,
I'm not an openSUSE member (I don't do software development any more) but
would like to get fixed a serious security flaw: there is no way to check
the validity of a repository / build signing key.
[You are welcome to correct me if I'm wrong - I'd love to know how to check
this]
I would suggest that, as a minimum, signing / build keys for main repos
associated with openSUSE are signed by a main openSUSE key after (in some
fashion) the requester's identity is verified. We can then (individually)
decide to trust that signing process (and hence the signatures) or not.
There would have to be a clear statement of both the identity verification
process and also the full extent of the assurance this signature gives. I
would suggest there should also be some kind of quality threshold (e.g. bug
fix statistics) as well as a method to revoke the key / signature.
Or, does one of the openSUSE security experts have a better simple
suggestion?
What would I need to do to effect this change?
Any advice or comment is very welcome,
Yours
David Hodgson
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Apologies for the cross posting, but I want to be sure to get as many interested parties involved possible
I'm volunteering to co-ordinate an openSUSE stand at FOSDEM this February
I have to confess to being a FOSDEM beginner, but I know enough that I'm getting myself involved in a big thing, and I'm going to need help.
Even if you're not coming this year, I especially welcome advice and guidance from FOSDEM veterans. What worked in previous years? what do I need to know? what do I need to avoid?
To have a stand, we need to have our proposal in by 12th December.
For both days, FOSDEM can provide either one or two 1m80 x 80cm tables, with 2 chairs per table.
We'll need at least 2 people to man the stand, though the more the merrier, and the less time we'll each have to spend working the stand.
As it's a big event my plan is to ask for 2 tables, but I need to have an idea of how many of you will be willing to help make our presence at FOSDEM felt
So if you're coming to FOSDEM, and would like to help out, please either reply to me directly or ideally to the opensuse-marketing mailing list
If any of you who work in NUE are coming to FOSDEM, please let me know, we might need your help to ferry goodies and stuff from SUSE offices to save on shipping.
Many Thanks
Richard Brown
openSUSE Ambassador
Richard Brown
Systems Engineering Team Leader
City College Brighton and Hove
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hey,
these are the meeting minutes for the standup meeting of the openSUSE
Boosters.
-------
General
-------
* Christmas Party
Robert will organize it. All of us will help.
-------
Standup
-------
Robert
* nothing
* Work on the documentation card
* Google Code-In mentoring. Do some artwork for cndegen/aj. Installed
12.1. Learned about gnome3
Ismail
* push python packages to devel project/factory
* push python packages to devel project/factory
* nothing
Klaas
* Analyzed the dvstack install script. Learned about rabbit mq.
* Setup the machine for the test cloud. Work on the python packages
with Ismail
* nothing
Tom
* Worked on the Diablo OBS project to get it installable on our test
cloud
* install openstack on our test cloud
* Leftover tasks from obs.org page (Appliance downloads).
Michal
* Learned more about openstack. Worked on a openSUSE Appliance on
studio.
* More polishing of the appliance
* Prepare the Prague Launch Party on Friday
Pavol
* Discussed the repo layout with cthiel: Cancel the testing repo.
Have release-name named repos and one general for Factory.
Work on rabbit mq updating to match the erlang version in Factory.
Think about what to do about systemd/init scripts.
* Rabbit mq update. Push everything to Factory.
* Prepare the Prague Launch Party on Friday
Christopher
* Push python packages to Factory.
* Help Vincent with the testing repo
* nothing
Coolo
* nothing
* Help people with pushing stuff to Factory
* 12.1/Factory distribution cleanup.
Henne
* Organized a big fat machine from the arch team for the test cloud
and installed 12.1 on it. Worked on the V:C:OS:D repo to get it
installable on 12.1.
* Get the test cloud up and running.
* obs.org milestone leftovers
--
Henne Vogelsang
http://www.opensuse.org
Everybody has a plan, until they get hit.
- Mike Tyson
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Heya all,
Going back to the discussion we had a while ago about moving to
Tumbleweed in openSUSE 12.1.
After a little bit of thinking* I concluded that of course all (new)
tumbleweed users need to move over to this setup of using the
'current' instead of the 12.1 repositories. So I changed the
Tumbleweed page to reflect this:
http://en.opensuse.org/Portal:Tumbleweed
And also: http://en.opensuse.org/SDB:Change_from_12.1_to_Tumbleweed
It makes the text a bit complicated. And I suck at un-complicating it,
I suppose, help is welcome.
But there is another matter I'm sure some of you object to much more
strongly: I use a self-made one-click-install file for adding
Tumbleweed**. I dunno if OCI can remove repo's but at least I can add
the right ones... However. I have no idea where to host the file. So
for now I put it on my *anathema* public dropbox...
/me hides
Yes, horrible, I know. I'm however sure our sysadmins can find a much
better spot for this one-click install. And maybe also for the
one-click-install for ownCloud, if we have one that works better?!?
http://en.opensuse.org/Portal:Tumbleweed
I just decided to go ahead, make the OCI and put it somewhere to have
at least an improvement over the current situation ;-)
Cheers,
Jos
* yes, I do it sometimes and yes, it usually hurts and leads to bad
stuff, I'll try not to do it again
** Credit to Greg KH who made it, I just added the 'current' repo's to it too
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi All,
I'm (also) going to be standing for the upcoming elections.
I won't bore you with my ideas as campaigning isn't meant to start until Friday.
I'm looking forward to doing my little bit to help this process and the project as a whole
Regards
Richard
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
scipy, numpy and matplotlib in my experience have to be packaged in
the same place... taking them from different sources calls for
trouble.
We shall arrange a meeting to devise a clear policy on education and
science repos as at the moment they have some overlap and duplications
that shall not happen.
Alin
On 28 November 2011 11:12, Lars Vogdt <lrupp(a)suse.de> wrote:
> Hi
>
> On Sun, 27 Nov 2011 04:42:09 +0100 todd rme wrote:
>> This makes sense. What about the packages that are currently in
>> Education and devel:languages:python, should they be removed from
>> Education and just live in devel:languages:python?
>
> IMHO nearly all python related packages should be moved over the
> devel:languages:python - the only exceptions might be packages that are
> clearly education related - like (as example, this app is not only
> using python as programming language) gcompris.
>
>
>> There are also
>> some packages that are not in devel:languages:python but perhaps
>> should be, specifically:
>>
>> python-scipy
>> spyder
>> pysycache and related packages
>>
>> What should be done with each of these?
>
> pysycache: clearly education related - leave in Education repo
> spyder, python-scipy: move to devel:languages:python
>
> I hope that makes sense?
>
> With kind regards,
> Lars
>
> --
> To unsubscribe, e-mail: opensuse-edu+unsubscribe(a)opensuse.org
> To contact the owner, e-mail: opensuse-edu+owner(a)opensuse.org
>
>
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
The openSUSE Board Election 2011 is starting today .
In this election we will have 3 seats to get elected, These seats are
currently held by Rupert Horstkotter, Pavol Rusnak, and Bryen
Yunashko. Only Pavol Rusnak is available to get re-elected.
The candidates:
Pascal Bleser
Richard Brown
Manu Gupta
Marcus Moeller
Chuck Payne
Pavol Rusnak
Will Stephenson
Andrew Wafaa
Details on http://en.opensuse.org/openSUSE:Board_election_2011#Candidates
Following the calendar:
November 25, 2011 – Start of campaign - Announcing the candidates of
this years election.
December 2, 2011 – Ballots open
December 16, 2011 – Ballots close – End of voting
December 19, 2011 – Announcement of the results - Announcing the
results and new board members
The openSUSE board was setup to lead the overall project. The main
tasks for members of the board are:
- Act as a central point of contact
- Help resolve conflicts
- Communicate community interests to SUSE
- Facilitate communication with all areas of the community
- Facilitate decision making processes where needed.
Greetings
---
Izabel Valverde
openSUSE Marketing
openSUSE Election Officials
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello mates,
i've just read the Election Rules again
(http://en.opensuse.org/openSUSE:Board_election_rules). The rules are saying:
The board consists of six members. Five seats are elected by the Members of
openSUSE Project and a chairperson is seperatly appointed by SUSE.
I'm proposing to give the chairman's chair to the Community. So we can give
the Community more Control about the Project.
--
Sincerly yours
Sascha Manns
Community &Support Agent
open-slx GmbH
http://www.open-slx.de
This mail is written with Balsam Professional 12.1