public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Thomson (wltjr)" <wltjr@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/java: index.xml
Date: Thu, 03 Apr 2008 17:55:21 +0000	[thread overview]
Message-ID: <E1JhTej-0007Sj-JR@stork.gentoo.org> (raw)

wltjr       08/04/03 17:55:21

  Modified:             index.xml
  Log:
  Added recruitment tags and current staffing needs.

Revision  Changes    Path
1.55                 xml/htdocs/proj/en/java/index.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/java/index.xml?rev=1.55&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/java/index.xml?rev=1.55&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/java/index.xml?r1=1.54&r2=1.55

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/java/index.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- index.xml	2 Feb 2008 00:48:27 -0000	1.54
+++ index.xml	3 Apr 2008 17:55:21 -0000	1.55
@@ -5,7 +5,7 @@
 <project>
 <name>Java</name>
 <longname>The Java Project</longname>
-<date>2008-01-31</date>
+<date>2008-04-03</date>
 
 <author title="author">
   <mail link="nichoj@gentoo.org">Joshua Nichols</mail>
@@ -44,6 +44,100 @@
 </p>
 </longdescription>
 
+  <recruitment>
+    <job>
+      <summary>General package maintainer</summary>
+      <details>
+        General java package maintainer to help out with managing the herd.
+        Along with java packages in other herds. Revision bumping, bug
+        filing/fixing, stabilizing, updating ebuilds per eclass or syntax
+        changes, etc.
+      </details>
+      <requirements>
+        Experience with Java on Linux, ideally Gentoo. Building java
+        applications from source. Some experience with ant, build.xmls,
+        patching java sources, and package build systems. 
+      </requirements>
+      <contact>java@gentoo.org</contact>
+    </job>
+    <job>
+      <summary>Glassfish package maintainer</summary>
+      <details>
+        Package from source and maintain
+        <uri link="https://glassfish.dev.java.net/">Glassfish</uri>
+        and related packages. Due to the size of Glassfish, many ebuilds will
+        need to be created for the various pieces. Possibly even a eclass.
+        Along with maintaining it all for at least 1 year or longer. Which
+        includes keeping package current with upstream. Glassfish has several
+        dependenies required to build from source, that will also need to be
+        packaged and maintained as well.
+      </details>
+      <requirements>
+	6 months - 1 year experience with Glassfish. Ideally in a production 
+        environment running Gentoo or some flavor of Linux. Ability to work
+        with Glassfish sources, and build it from source.
+      </requirements>
+      <contact>java@gentoo.org</contact>
+    </job>
+    <job>
+      <summary>JBoss package maintainer</summary>
+      <details>
+        Package from source and maintain
+        <uri link="http://www.jboss.com/products/platforms/application">JBoss</uri>
+        and related packages. Due to the size of JBoss, many ebuilds will
+        need to be created for the various pieces. Possibly even a eclass.
+        Along with maintaining it all for at least 1 year or longer. Which
+        includes keeping package current with upstream. JBoss has several
+        dependenies required to build from source, that will also need to be
+        packaged and maintained as well.
+      </details>
+      <requirements>
+	6 months - 1 year experience with JBoss. Ideally in a production 
+        environment running Gentoo or some flavor of Linux. Ability to work
+        with JBoss sources, and build it from source.
+      </requirements>
+      <contact>java@gentoo.org</contact>
+    </job>
+    <job>
+      <summary>Jetty package maintainer</summary>
+      <details>
+        Package from source and maintain
+        <uri link="http://www.jboss.com/products/platforms/application">JBoss</uri>
+        and related packages. Along with maintaining it all for at least 1
+        year or longer. Which includes keeping package current with upstream.
+      </details>
+      <requirements>
+	6 months - 1 year experience with Jetty. Ideally in a production 
+        environment running Gentoo or some flavor of Linux. Ability to work
+        with Jetty sources, and build it from source.
+      </requirements>
+      <contact>java@gentoo.org</contact>
+    </job>
+    <job>
+      <summary>Maven package maintainer and portage integrator</summary>
+      <details>
+        Package from source and maintain
+        <uri link="http://www.jboss.com/products/platforms/application">JBoss</uri>
+        and related packages. Maven itself is packaged from source in the
+        java-overlay, but needs to be updated, maintained, and added to tree.
+        At which time Maven, along with Maven repositories need to be 
+        integrated with Gentoo's Java build system. Which presently is designed 
+        entirely around ant. Then maintaining it all for at least 1 year or
+        longer. Which includes keeping package current with upstream. Most
+        all dependenies required to build from source have been package 
+        in the java-overlay. They will need to be added to tree and maintained
+        as well.
+      </details>
+      <requirements>
+	6 months - 1 year experience with Maven on Gentoo or some flavor 
+        of Linux. Ability to work with Maven sources, and build it from source.
+        Experience with the Gentoo Java build system and our Java specific 
+        eclasses.
+      </requirements>
+      <contact>java@gentoo.org</contact>
+    </job>
+  </recruitment>
+
 <dev role="lead" description="Primary, Packager and bug squasher">betelgeuse</dev>
 <dev role="member" description="Maintainer of Resin, Sun JWSDP and few other ebuilds, Java/PPC32">nelchael</dev>
 <dev role="member" description="Maintainer of Tomcat and related packages">wltjr</dev>



-- 
gentoo-commits@lists.gentoo.org mailing list



             reply	other threads:[~2008-04-03 17:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 17:55 William Thomson (wltjr) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-06 17:42 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/java: index.xml James Le Cuirot (chewi)
2014-12-18  2:54 Tim Harder (radhermit)
2014-07-11 15:05 Tom Wijsman (tomwij)
2014-02-16 10:38 Pacho Ramos (pacho)
2013-08-31 10:24 Tom Wijsman (tomwij)
2013-05-09  8:46 Ralph Sennhauser (sera)
2013-03-07  3:02 Tim Harder (radhermit)
2013-03-07  3:00 Tim Harder (radhermit)
2011-11-07 21:53 Vlastimil Babka (caster)
2011-10-16 11:31 Petteri Raty (betelgeuse)
2010-08-31 22:55 Krzysztof Pawlik (nelchael)
2010-07-13 13:31 Jorge Manuel B. S. Vicetto (jmbsvicetto)
2008-10-30 16:06 Lukasz Damentko (rane)
2008-10-08 20:55 Serkan Kaba (serkan)
2008-05-21 20:38 Serkan Kaba (serkan)
2008-04-03 18:39 William Thomson (wltjr)
2008-02-02  0:48 Joshua Nichols (nichoj)
2008-01-31 16:24 William Thomson (wltjr)
2008-01-10 10:41 Jean-Noel Rivasseau (elvanor)
2007-12-25 11:56 Christian Heim (phreak)

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=E1JhTej-0007Sj-JR@stork.gentoo.org \
    --to=wltjr@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