From: "Matthias Geerdsen (vorlon)" <vorlon@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/security: index.xml
Date: Wed, 02 Apr 2008 19:18:38 +0000 [thread overview]
Message-ID: <E1Jh8Tm-0001xV-FS@stork.gentoo.org> (raw)
vorlon 08/04/02 19:18:38
Modified: index.xml
Log:
new recruitment section
Revision Changes Path
1.46 xml/htdocs/proj/en/security/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/security/index.xml?rev=1.46&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/security/index.xml?rev=1.46&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/security/index.xml?r1=1.45&r2=1.46
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/security/index.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- index.xml 16 Mar 2008 22:49:08 -0000 1.45
+++ index.xml 2 Apr 2008 19:18:37 -0000 1.46
@@ -5,6 +5,7 @@
<project>
<name>security</name>
<longname>Gentoo Linux Security Project</longname>
+ <date>2008-04-02</date>
<description>The Gentoo Linux Security Project ensures that all
vulnerabilities in software provided by Gentoo Portage tree are
@@ -16,6 +17,23 @@
our users remain protected against known vulnerabilities.
</p></longdescription>
+ <recruitment>
+ <job>
+ <summary>GLSA Coordinators</summary>
+ <details>Helping with the coordination of security bugs and GLSAs. More
+ information on the recruitment process can be found
+ <uri link="#doc_chap7">further down</uri> on the project page.</details>
+ <requirements />
+ <contact>security@gentoo.org</contact>
+ </job>
+ <job>
+ <summary>Kernel Security Coordination</summary>
+ <details />
+ <requirements />
+ <contact>security@gentoo.org</contact>
+ </job>
+ </recruitment>
+
<dev role="lead" description="Operational manager">Falco</dev>
<dev role="lead" description="Operational manager">vorlon</dev>
<dev description="GLSA Coordinator">jaervosz</dev>
@@ -56,23 +74,9 @@
</body>
</section>
</extrachapter>
-
<extrachapter position="subproject">
<title>Becoming a Gentoo Security developer</title>
<section>
- <title>Open positions</title>
- <body>
- <p>
- The Gentoo Linux Security Project is currently seeking help in the
- following areas:
- </p>
- <ul>
- <li>GLSA Coordinators</li>
- <li>Kernel Security Coordination</li>
- </ul>
- </body>
- </section>
- <section>
<title>How to join the team</title>
<body>
<p>
@@ -80,7 +84,7 @@
mailing list at
<uri link="/main/en/lists.xml">gentoo-security@gentoo.org</uri>
and sign yourself
- up a <uri link="http://bugs.gentoo.org/createaccount.cgi">Bugzilla
+ up a <uri link="https://bugs.gentoo.org/createaccount.cgi">Bugzilla
account</uri>. You may be able to talk to one of our security
developers and/or users in the IRC channel <e>#gentoo-security</e>
on <e>irc.freenode.net</e> for more information or just to chat about
--
gentoo-commits@lists.gentoo.org mailing list
next reply other threads:[~2008-04-02 19:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 19:18 Matthias Geerdsen (vorlon) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-20 6:42 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/security: index.xml Sergey Popov (pinkbyte)
2013-08-20 0:44 Tobias Heinlein (keytoaster)
2013-05-17 21:52 Jason Donenfeld (zx2c4)
2013-05-17 21:50 Jason Donenfeld (zx2c4)
2013-01-09 12:25 Tobias Heinlein (keytoaster)
2012-02-29 22:15 Tim Sammut (underling)
2012-02-02 11:47 Alex Legler (a3li)
2012-02-02 11:17 Alex Legler (a3li)
2012-02-02 11:09 Alex Legler (a3li)
2012-01-29 16:49 Tim Sammut (underling)
2012-01-05 17:21 Tim Sammut (underling)
2011-12-12 14:21 Tobias Heinlein (keytoaster)
2011-10-19 14:25 Alex Legler (a3li)
2011-04-01 5:47 Tim Sammut (underling)
2010-09-06 10:15 Tobias Heinlein (keytoaster)
2010-09-02 13:25 Tobias Heinlein (keytoaster)
2010-09-02 8:13 Tobias Heinlein (keytoaster)
2010-09-02 8:02 Tobias Heinlein (keytoaster)
2010-09-01 21:26 Alex Legler (a3li)
2010-07-19 15:26 Jorge Manuel B. S. Vicetto (jmbsvicetto)
2009-11-18 22:11 Stefan Behte (craig)
2009-11-18 22:09 Stefan Behte (craig)
2009-09-03 19:55 Alex Legler (a3li)
2009-08-07 19:17 Robert Buchholz (rbu)
2009-06-27 10:56 Tobias Heinlein (keytoaster)
2009-05-15 14:46 Tobias Heinlein (keytoaster)
2009-05-15 14:37 Tobias Heinlein (keytoaster)
2009-05-15 14:36 Tobias Heinlein (keytoaster)
2009-04-02 17:56 Robert Buchholz (rbu)
2009-03-25 14:51 Alex Legler (a3li)
2009-03-23 16:56 Tobias Heinlein (keytoaster)
2009-03-23 16:40 Tobias Heinlein (keytoaster)
2009-03-09 15:22 Raphael Marichez (falco)
2008-08-06 17:23 Robert Buchholz (rbu)
2008-06-03 10:14 Matthias Geerdsen (vorlon)
2008-06-03 10:09 Matthias Geerdsen (vorlon)
2008-05-21 19:40 Jeroen Roovers (jer)
2008-04-28 9:34 Robert Buchholz (rbu)
2008-04-02 21:00 Matthias Geerdsen (vorlon)
2008-03-16 22:49 Raphael Marichez (falco)
2008-03-09 13:48 Lukasz Damentko (rane)
2008-03-09 0:57 Marius Mauch (genone)
2008-02-24 11:12 Robert Buchholz (rbu)
2008-02-13 12:37 Matthias Geerdsen (vorlon)
2007-12-25 11:45 Christian Heim (phreak)
2007-12-12 18:23 Robert Buchholz (rbu)
2007-12-12 18:22 Robert Buchholz (rbu)
2007-12-10 22:36 Raphael Marichez (falco)
2007-11-15 16:17 Jeroen Roovers (jer)
2007-11-03 22:47 Robert Buchholz (rbu)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Jh8Tm-0001xV-FS@stork.gentoo.org \
--to=vorlon@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox