Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

Shall we initiate a vote for the new Security Team Leader then? The following
people have been nominated, can we get seconds on any of them and then I'll
start the vote later this week:
  Thomas Houssin

Any other nominations before the voting starts?

Keep in mind our Voting Rules[0]. ;)

-sandalle

[0] http://wiki.sourcemage.org/index.php?page=Team+Lead+Voting+Process

Quoting Seth Alan Woolley <seth AT positivism.org>:
> As we approach 1.0 release, I think it's time we started to put more
> emphasis on automated utilities to ensure that we properly test our test
> grimoire and/or a staging grimoire before stable grimoire is released.
> Not that this is a terrible problem as I just installed a new system
> from stable and it worked excellently, but I want to make sure
> everything's as close to perfect as possible.
>
> So I've been considering taking on the Q/A team as Team Leader myself.
> I wanted to first revive prometheus and start running it on the test
> grimoire.  After that, we can see if we need a "staging" grimoire for
> stable.  My first plan is to concentrate on basesystem spells only, then
> move up to a list of common spells and then test the rest at a lower
> background level.
>
> But, if I'm to concentrate on this, I'd like to have somebody else take
> over the Security Team Leader role so I can properly become the Quality
> Assurance Team Leader and work on that.  I have a number of helpful
> scripts for security updates that I can pass on to the next person.  So
> I'm hoping to see if anybody out there is interested in becoming
> Security Team Leader.  Preference will go to existing team members,
> developers, and volunteers, but if you can survive a background check, a
> newcomer with interest and experience could be selected.  Each Team
> Leader position is selected via a vote of developers, so we'd need to do
> that as well.
>
> Responsibilities of the Security Team Leader include:
>
> * Handle security updates so that they happen in an efficient manner.
>   This includes access to the stable grimoire and the download update
>   routine.  Make announcements of the updates so people are aware the
>   updates are needed.  Some gurus can make their own updates, but if
>   they do, you should do the announcing (and integrating to stable).
>   Note that I test all the updates (to various degrees) before they go
>   into the stable grimoire.
>
> * Handle and audit security-related areas in Sorcery.  We're pretty
>   secure about how we do things, but the role primarily involves making
>   sure things are sane.  This can always be improved.
>
> * Making sure the base install is secure and default configurations,
>   once enabled, are sane.
>
> * Ensuring the grimoire's md5s are sane and managing the gnupg
>   encryption keyrings.  Most gurus are already pretty well trained in
>   this, so this is pretty minor.
>
> * Any other general security areas.
>
> So if you're interested, please reply to this email to the entire list
> with your interest and why you think you'd be a good candidate.  If
> nobody replies, it looks like I'll have to stay the Security Team Leader
> and we won't have an active Q/A team leader.  Alternatively, if you want
> to start hacking prometheus and working on Q/A, that would work too, but
> I've done hundreds of security updates and I'd like to give somebody
> else the chance to be the patch monkey ;).
>
> Seth
>
> --
> Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
> Key id 00BA3AF3 = 8BE0 A72E A47E A92A 0737  F2FF 7A3F 6D3C 00BA 3AF3
> http://smgl.positivism.org:11371/pks/lookup?op=get&search=0x00BA3AF3
> Security Team Leader Source Mage GNU/Linux http://www.sourcemage.org
>

--
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us PGP: 0xA8EFDD61  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.