Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-05-22 18:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Gump

15 Mar 2017 [Stefan Bodewig / Brett]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

No changes compared to the last quarter, the service is humming along.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

This has been a very quiet quarter for Gump. Gump seems to remain
useful for the projects using it.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

21 Dec 2016 [Stefan Bodewig / Mark]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

vmgump has been replaced with a new VM with most of the installation
being automated via Puppet.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

As indicated in the last report we've freed up the Linux VM named
vmgump so its host Eirene can get decommissioned. The new installation
vmgump-vm3 is based on a Puppet module for most of it, a few manual
steps remain as they require credentials we don't want to store in a
repository.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

21 Sep 2016 [Stefan Bodewig / Brett]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Some low activity on migrating to a new VM and Gump is back on
MacOS X. Gump seems to create useful results for the few projects
that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

The Linux VM we use for our main installation vmgump is scheduled to
get replaced as its host Eirene is about to be decommissioned. Work
hasn't really started on it but is expected to be completed during the
next quarter. As a result the Gump installation will get puppetized
which will make creating future installations easier, should there
ever be a need for them.

After a longish hibernation Gump is back on adam.apache.org thanks to
Sander Temme's work. We know adam is on the list of hosts to get
decommissioned as well but are happy to see it provide results that
may be useful while it lasts.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

15 Jun 2016 [Stefan Bodewig / Mark]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Some development activity fixing a git problem, Gump seems to create
useful results for the few projects that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

We had some back and forth tweaking the git integration as we tried to
make Gump pick up changes to file attributes and realized some builds
had become stale. Other than that the projects that use Gump have
occasionally modified their respective configuration files.

=== Mailing-List Statistics ===

general@gump.apache.org:
49 subscribers (up 2 in the last 3 months) (87 emails sent in the past
3 months, 94 in the previous cycle)

commits@gump.apache.org:
22 subscribers (up 1 in the last 3 months) (41 emails sent in the past
3 months, 25 in the previous cycle)

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

16 Mar 2016 [Stefan Bodewig / David]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

No development activity, Gump seems to create useful results for the
few projects that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

The projects that use Gump have occasionally modified their respective
configuration files.  No other activity.

=== Mailing-List Statistics ===

general@gump.apache.org:
47 subscribers (down -1 in the last 3 months) (93 emails sent in the
past 3 months, 80 in the previous cycle)

commits@gump.apache.org:
21 subscribers (up 2 in the last 3 months) (19 emails sent in the past
3 months, 10 in the previous cycle)

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

16 Dec 2015 [Stefan Bodewig / Bertrand]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==
No development activity, Gump seems to create useful results for the
few projects that use it.

== Releases ==
Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==
The projects that use Gump have occasionally modified their respective
configuration files.  No other activity.

=== Mailing-List Statistics ===

general@gump.apache.org:
48 subscribers (down -1 in the last 3 months) 89 emails sent to list
(63 in previous quarter)

commits@gump.apache.org:
19 subscribers (down -1 in the last 3 months) 11 emails sent to list
(23 in previous quarter)

== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

16 Sep 2015 [Stefan Bodewig / Sam]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

No development activity, Gump seems to create useful results for the
few projects that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

The projects that use Gump have occasionally modified their respective
configuration files.  No other activity.

=== Mailing-List Statistics ===

general@gump.apache.org:
49 subscribers (up 0 in the last 3 months) (64 emails sent in the past
3 months, 92 in the previous cycle)

commits@gump.apache.org:
Currently: 20 subscribers (up 0 in the last 3 months) (42 emails sent
in the past 3 months, 94 in the previous cycle)

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

17 Jun 2015 [Stefan Bodewig / Rich]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Gump has learned to use msbuild/xbuild and NuGet to build .NET
projects.

Gump seems to create useful results for the few projects that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

One of the projects (XMLUnit.NET) built by Gump recently switched to
msbuild/xbuild as its build tool so we had to catch up.  This also
required us to support nuget's command line as a build step.
Currently the support just provides what the project asks for - which
is not the way Gump would be expected to work.  Given the only project
using it doesn't have any dependency on any other project built by
Gump it is unlikely we'll make the implementation more "Gumpy".  With
the move of XMLUnit.NET there no longer is any project using Nant as a
built tool left in the set of projects built by Gump.

As more long running test projects have been added, we needed to
change vmgump's configuration back to perform four runs a day rather
than three. A single run of Gump currently takes about eight and a
half hours. So the setting of "three" in fact meant that we would only
manage two per day.

=== Mailing-List Statistics ===

general@gump.apache.org:
Currently: 49 subscribers (no change in the last 3 months) (92 emails
sent in the past 3 months, 138 in the previous cycle)

commits@gump.apache.org:
Currently: 20 subscribers (no change in the last 3 months) (94 emails
sent in the past 3 months, 142 in the previous cycle)

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

18 Mar 2015 [Stefan Bodewig / Jim]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Gump has learned to use Gradle to build projects.

Gump seems to create useful results for the few projects that use it.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

One of the projects (Hamcrest) built by Gump recently switched to
Gradle as its build tool so we had to catch up.  After figuring out a
way to integrate Gradle, we realized the new Hamcrest version wasn't
compatible with the old one (it's a new major release, so that's to be
expected) and we had to provide a packaged up version of Hamcrest 1.3
anyway.  This means the only gradle build we've got doesn't do much
more than validating Hamcrest can be built.

This quarter was the first time a project tried the support for
different git branches that has been present for some time.

As more long running test projects have been added we needed to change
vmgump's configuration to perform three runs a day rather than four.

=== Mailing-List Statistics ===

general@gump.apache.org:
Currently: 49 subscribers (down -1 in the last 3 months) (139 emails
sent in the past 3 months, 135 in the previous cycle)

commits@gump.apache.org:
Currently: 20 subscribers (down -1 in the last 3 months) (142 emails
sent in the past 3 months, 81 in the previous cycle)

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.

17 Dec 2014 [Stefan Bodewig / Brett]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

During this quarter we've added two new PMC members.

Gump seems to create useful results for the few projects that use it.
The FOP community has decided they no longer need the service provided
by Gump.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

The Gump builds have been updated to run on Java8 which causes a few
builds to break (like the one of Google Guava) and forced us to
replace dependencies with pre-packaged binaries in two cases.


== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

Konstantin Kolinko and Mark Thomas joined the Gump PMC.

17 Sep 2014 [Stefan Bodewig / Ross]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Gump seems to create useful results for the few projects that use it.
This quarter showed more activity than usual with Gump learning to
deal with git submodules and vmgump being upgraded to Ubuntu 14.04.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

With Ant and the Antlibs migrated to git and the Antlibs using git
submodules it was necessary to add support for transparent handling of
git submodules, this has been implemented in July and seems to work
well enough.

Mark Thomas was kind enough to upgrade vmgump from Ubuntu 10.04 to
14.04 which freed us from the need of a hand compiled git and provided
us with a few more recent compilers and libraries.  Mark has been
added to the list of sudoers on vmgump.

vmgump's httpd has been added to the lists of services monitored by
infra "the pubsubified way".

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.  The most
recent addition to the PMC was in December 2006 when we added Sander
Temme.

18 Jun 2014 [Stefan Bodewig / Sam]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Gump seems to create useful results for the few projects that use it.
Ant decided to switch from svn to git which might require some real
coding work to be done.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

Ant migrated most of its codebases from svn to git.  When Gump
switched to use the git location we had to learn the ASF's https git
service was not compatible with git 1.7.x which still is the latest
version available as package for Ubuntu 10.04 (which powers vmgump).
A self-compiled git 2.0 on vmgump solved the problem.

While Gump caught up with the change for Ant itself, the Antlib and
Ivy builds are still using the stale svn uris.  The Ant project is
currently pondering the idea of using git submodules for the Antlibs
projects, these are not supported by Gump, yet, which may require some
changes in the git integration.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.  The most
recent addition to the PMC was in December 2006 when we added Sander
Temme.

19 Mar 2014 [Stefan Bodewig / Shane]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Gump seems to create useful results for the few projects that use it.
Activity spiked when JUnit dropped Ant build support, very little
activity apart from that.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.

== Activity ==

The JUnit team decided to drop the Ant build and switch to "Maven
only".  Gump used Ant to build JUnit and the migration caused a few
hiccups along the way.  Three different people modified a few
descriptors over a period of several days until things were back to
normal.  No other activity.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.  The most
recent addition to the PMC was in December 2006 when we added Sander
Temme.

18 Dec 2013 [Stefan Bodewig / Doug]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

Very little activity, Gump seems to create useful results for the few
projects that use it.  A team at Oracle seems to be running Gump for
compatibility tests of Java 8.

== Releases ==

Gump has never done any releases.  One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuosly" philosophy.

Stefan has polled the Gump list and our only known user outside of the
ASF whether anybody would like to see a release but no response was
received.

== Activity ==

Ludmila Shikhvarg who works at Oracle and tests next-Java
compatibility runs Gump internally at Oracle.  Unfortunately the
instance is not a public one.  Occasionally she pings the Gump list to
tells us about build problems she sees, she did so for three projects
and Java8 in October and traffic has been directed to the project
mailing lists.

The Gump installation on vmgump was stuck for several weeks and nobody
noticed it.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.  The most
recent addition to the PMC was in December 2006 when we added Sander
Temme.

18 Sep 2013 [Stefan Bodewig / Sam]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies.  It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.

== Summary ==

The set of projects has been stripped down to those who actively
expressed interest in the service, we seem to be able to handle the
reduced set well.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

In late June we sent an email to the dev lists of all ASF projects
that were built by Gump asking the communities whether they'd still be
interested in the service.  Of all communities only the Tomcat, POI,
XML Graphics and Forrest dev teams asked to continue the Gump builds,
log4net asked to drop the builds and the rest ignored the mail and was
deemed not interested.

Since mid-August Gump only builds the projects who signaled interest
as well as their dependencies, nag mails have been turned off for all
projects who don't want them.  One result was immediate interest by
the Tomcat and FOP communities to get their builds green again.

== Infrastructure ==

We've given back our FreeBSD jail and now concentrate on a single
installation on vmgump.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.  The most
recent addition to the PMC was in December 2006 when we added Sander
Temme.

== Statistics ==

vmgump runs about 130 build jobs for 50 source trees, 32 from ASF
repositories.  A complete builds takes about two-and-half hour by now.

19 Jun 2013 [Stefan Bodewig / Sam]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

The Gump PMC is currently in doubt whether the service is still
needed/appreciated and will query the projects who's code is currently
built by Gump over the course of the next quarter.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

The problems with accessing Maven Central mentioned in the last report
has magically disappeared.  The best guess is Gump was hitting some
misbehaving CDN nodes that have now been fixed.

In theory we could re-enable nagging mails now, but given the very low
interest over the past years and given that not a single PMC has asked
to re-enable mails Stefan Bodewig raised the question whether it might
not be time to stop providing the service at all.  Feedback from the
community so far was along the lines of "this probably is a service
that you only miss when it is gone" but that we shouldn't keep putting
time and energy into keeping the service alive just because it's
there.

Stefan intends to contact the PMCs who's code is currently built by
Gump and we'll discuss our next steps depending on the outcome.

The last quarter didn't see any activity at all.

== Infrastructure ==

Gump hasn't been reinstalled on the MacOS X server after the OS
upgrade reported last quarter.  The FreeBSD jail has seen an OS
upgrade as well and also need Gump to be re-enabled.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

20 Mar 2013 [Stefan Bodewig / Jim]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

Since early this year our self-written maven repository proxy faces
random hangs when requesting artifacts from the central Maven
repository which leads to build processes being killed after the
timeout of one hour.  As a result Gump runs currently take several
days and we disabled nag emails as build failures were more often
related to this problem than a change in the project itself.  The
underlying problem hasn't been fully analyzed so far.

The dataset of projects built by Gump is maintained by only a few
people contributing across all projects and a few additional people
maintaining the metadata of the projects they are interested in the
most.

The Mac OS X server usually running Gump, adam.apache.org, has
undergone an OS upgrade.  The Gump installation is awaiting
restoration.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

19 Dec 2012 [Stefan Bodewig / Roy]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

This has been a very quiet month even by Gump's standard.  Very few
tweaks have been made to metadata and not a single commit to the code
base.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

== Statistics ==

As of Tue, 11 Dec 2012 the ASF installations check out a bit less than
175 source trees (114 from the ASF repository) and try to build a bit
more than 850 "projects".  A complete Gump run takes about ten hours
on vmgump and about eight on the FreeBSD jail and nine and a half on
Adam where more projects fail to build.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

19 Sep 2012 [Stefan Bodewig / Doug]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

Gump on vmgump now runs on Oracle Java7 since more an more projects
depend on it.  As a result other projects - most notably those who
implement JDBC interfaces - have been broken.

The dataset of projects built by Gump is maintained by only a few
people contributing across all projects and a few additional people
maintaining the metadata of the projects they are interested in the
most.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

== Statistics ==

As of Mon, 10 Sep 2012 the ASF installations check out a bit more than
175 source trees (115 from the ASF repository) and try to build a bit
more than 850 "projects".  A complete Gump run takes about eight and a
half hours on vmgump and about ten on the FreeBSD jail and eight on
Adam where more projects fail to build.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

20 Jun 2012 [Stefan Bodewig / Roy]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

Spammers have forced us to enable the ContributorsGroup feature on our
Wiki.

== Activity ==

Some development activity on the code base to deal with expanding
artifact names that are specified as wildcards.

The dataset of projects built by Gump is maintained by only a few
people contributing across all projects and a few additional people
maintaining the metadata of the projects they are interested in the
most.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

== Statistics ==

As of Tue, 12 Jun 2012 the ASF installations check out a bit more than
170 source trees (114 from the ASF repository) and try to build a bit
more than 850 "projects".  A complete Gump run takes about eleven and
a half hours on vmgump and about eight on the FreeBSD jail and seven
and a half on Adam where more projects fail to build.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

21 Mar 2012 [Stefan Bodewig / Brett]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

The site now uses svnpubsub.  If we ever want to create a release,
we'll use svnpubsub right from the start.

We encountered only a few minor hick-ups after the upgrade to FreeBSD
9.0, mostly due to upgrading svn and having to upgrade all working
copies.  Many thanks to the infra team.

== Activity ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  During this quarter we've tweaked
git support to allow pulling from branches other than "master".

There are only a few people contributing across all projects and a few
additional people maintaining the metadata of the projects they are
interested in the most.

We've finally given up waiting for expat to build on libtool2 systems
and now provide a system installed expat, this means we've started to
successfully build APR and projects depending on APR for the first time
since at least a year, probably longer.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

== Branding and Naming ==

We believe to meet all branding requirements.

== Statistics ==

As of Tue, 13 Mar 2012 the ASF installations check out a bit less than
180 source trees (115 from the ASF repository) and try to build a bit
more than 850 "projects".  A complete Gump run takes about nine and a
half hours on vmgump and about nine on the FreeBSD jail and ten on
Adam where more projects fail to build.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

21 Dec 2011 [Stefan Bodewig / Larry]

Apache Gump is a cross-project continuous integration server.  Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No Board level issues.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Activity ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.

There are only a few people contributing across all projects and a few
additional people maintaining the metadata of the projects they are
interested in the most.

This quarter we've seen quite a few of the external projects Gump
builds move to either hg or git (usually to github in the later case).
This probably is no new development, we mostly only notice it if the
old SCM stops working.

== Changes to the Roster ==

All ASF committers have write access to the metadata that configure
the ASF installations.

No new committers to the code base, no changes to the PMC.

== Branding and Naming ==

We believe to meet all branding requirements.

== Statistics ==

As of Thu, 1 Dec 2011 the ASF installations check out a bit more than
180 source trees (114 from the ASF repository) and try to build a bit
less than 850 "projects".  A complete Gump run takes about ten hours
on vmgump and about eight and a half on the FreeBSD jail and nine on
Adam where more projects fail to build.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
 FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a
 Mac OS X Server at http://adam.apache.org/gump/

21 Sep 2011 [Stefan Bodewig / Shane]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No development activity at all, no issues.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

The past quarter several projects built by Gump have been moved to the
Attic and now are no longer built by Gump, the only notable addition
is the Tomcat 7 branch.

== Development ==

None.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

No new is good news.

== Project Branding Requirements ==

We believe to meet all requirements by now.

== Statistics ==

As of Sat, 17 Sep 2011 the ASF installations check out a bit more than
170 source trees (114 from the ASF repository) and try to build a bit
less than 800 "projects".  A complete Gump run takes about eight hours
on vmgump.  Timings for the FreeBSD jail and the MacOS X server are
currently not available as either build is having issues.

Some builds have been removed since the projects moved to the Attic
(Cactus, for example).

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

15 Jun 2011 [Stefan Bodewig / Geir]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

No development activity at all, no issues.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

All in all the community is pretty small by now and it has been a long
time since a new project has been added to the Gump runs because the
project had asked for it - when we've added new projects over the past
two years the driver has been the Gump community.  It looks as if most
projects are content with the existing vanilla CI options.

== Development ==

None.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

The infra team has provided us with a VM to run Gump on top of Apache
Harmony but it is currently not used, we'll hand it back to infra so
it doesn't waste resources.

At one point in time a Gump run on the FreeBSD jail created many core
dumps that filled up the disk space shared by all jails.  Gump is now
set up to not allow core dumps since nobody would want to look at them
anyway.

== Project Branding Requirements ==

We've updated the first sentence of the description to match the
revised requirement.

Thanks to David Crossley the main site logo now contains a TM and we
are confident we will manage to add a TM to the logo Gump uses in its
reports soon as well.  We believe to meet all other requirements.

== Statistics ==

As of Fri, 10 Jun 2011 the ASF installations check out a bit less than
180 source trees (115 from the ASF repository) and try to build a bit
less than 800 "projects".  A complete Gump run takes about seven and a
half hours on vmgump or the FreeBSD jail about six and a half hours on
the MacOS X server where more projects fail to build and thus less
time is spent building dependent projects.

Some builds have been removed since the projects moved to the Attic
(regexp, for example) or were unmaintained and always failed to build
anyway.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/

16 Mar 2011 [Stefan Bodewig / Greg]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

Low development activity to adapt to a difference between mvn 2.x and
3.x, the Mac OS X machine went live, no issues.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

Support requests for the non-public Gump installation running on top
of OpenJDK7 dribble in and get addressed.

== Development ==

Only minor changes that lead to separate "install" builders for mvn2
and mvn3.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

The Mac OS X instance called Adam is now running the full set of
projects.

The infra team has provided us with a VM to run Gump on top of Apache
Harmony but it is currently not used.  We expect to either start using
it or give it back during the next quarter.

== Project Branding Requirements ==

Logos still need a "TM" symbol, waiting for somebody with the skills
required to make the change.  Unfortunately the Gump community doesn't
seem to include a person with said skills.

The website now uses Forrest 0.9 which allowed us to remove our own
custom skin that was only added in order to enable the trademark
footer.

== Statistics ==

As of Thu, 10 Mar 2011 the ASF installations check out a bit less than
180 source trees (113 from the ASF repository) and try to build a bit
less than 800 "projects".  A complete Gump run takes about nine hours
on vmgump or the FreeBSD jail and a bit less than seven hours on the
MacOS X server where more projects fail to build and thus less time is
spent building dependent projects.

The time taken on vmgump has almost halved when compared to last
quarter mostly due to migrating to a new virtual host; it is now back
where it used to be half a year ago.  The time for the FreeBSD jail
remains more or less the same.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
 FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a
 Mac OS X Server at http://adam.apache.org/gump/

15 Dec 2010 [Stefan Bodewig / Doug]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

A new Gump instance running on Mac OS X, Some development that lead to
support for Maven 3.x, work on project branding requirements, no
issues.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

In November we've been told that somebody was running Gump on top of
OpenJDK7 and encountered some compatibility issues[2] - which is no
surprise, we've always seen problems when we upgraded Java versions.
One of the issues identified led to changes inside Ant's trunk to work
around backwards incompatible changes in javac.  Unfortunately the
results of said Gump installation do not seem to be available to the
public.

== Development ==

Gump now supports Maven 3.x as a builder.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

Sander Temme installed Gump on an XServe running Mac OS X Server.
This installation is currently only running the small subset of
projects we use for testing.

We've asked the infra team for a new VM to run Gump on top of Apache
Harmony.  Mark Hindess of the Harmony community volunteered to help
with the Harmony side of things.

== Project Branding Requirements ==

=== Project Website Basics ===

The Gump website matched the requiremens ever since Gump became a TLP.

=== Project Naming And Descriptions ===

Many pages only referred to "Gump" - this has been fixed.  The home
page starts with a description and there is no download page.

=== Website Navigation Links ===

We had to add a link to www.apache.org and the security link.  Our
license link points to the 2.0 license directly.

=== Trademark Attributions ===

The requirements are met now.

=== Logos and Graphics ===

Logos still need a "TM" symbol, waiting for somebody with the skills
required to make the change.

It would be good if there was any (at least one) logo to take
inspiration (or steal the typography of "TM") from, but even the
feather at www.apache.org lacks the required "TM" as of this writing.

=== Project Metadata ===

Has been in place already.

== Statistics ==

As of Wed, 8 Dec 2010 the ASF installations check out a bit less than
190 source trees (119 from the ASF repository) and try to build a bit
more than 700 "projects".  A complete Gump run takes more than sixteen
hours on vmgump and seven and a half on the FreeBSD jail.

The time taken on vmgump has almost doubled when compared to last
quarter while it remains more or less constant on the FreeBSD jail.
Given that we don't have significantly more failures on FreeBSD the
difference is likely related to other things that happen in parallel
on the machines hosting the VM/jail.

[1] the main instance at http://vmgump.apache.org/gump/public/ , a
 FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a
 Mac OS X Server at http://adam.apache.org/gump/

[2] http://mail-archives.apache.org/mod_mbox/gump-general/201011.mbox/%3C4CD8A848.4000502@oracle.com%3E

Good news that a Gump user is using OpenJDK7 and reporting compatibility issues that resulted in changes to Ant.

22 Sep 2010 [Stefan Bodewig / Roy]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Summary ==

Big infrastructure changes, light development, no issues.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

== Development ==

While migrating to the new servers a few issues with Gump's database
access have been identified and fixed.  A new "builder" has been added
that removes the boilerplate code previously required when installing
a file to the local Maven repository.

We've managed to build a few projects that have been failing for a
long time in Gump - among them the ASF projects Forrest, Lucene,
Cactus and big parts of Cocoon.  We've also added builds for Solr,
Tika and PDFBox.

Some projects that have been failing for a long time and will likely
never become buildable again have been removed.  Also we've disabled a
few builds (mostly running some sort of tests) that caused Gump to
hang for an hour (Gump's timeout for build processes).

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

Our main machine vmgump has been replaced by a brand new virtual
Ubuntu machine.  The old database has been migrated to keep history.
Since the new machine now runs OpenJDK6 rather than an "official" Java
environment a few dependencies on Sun VMs have shown up in some
project's builds.

We used to have a Solaris zone which has now been replaced by a
FreeBSD jail.  The installation is working very well and we see almost
the same build failures and successes on FreeBSD as on Linux.

Many thanks to the infrastructure team for the support during the
migration - and for all the other stuff you do.

== Statistics ==

As of Sun, 12 Sep 2010 the ASF installations check out a bit less than
200 source trees (113 from the ASF repository) and try to build a bit
less than 600 "projects".  A complete Gump run takes more than nine
hours on vmgump and eight on the FreeBSD jail.

[1] the main instance at http://vmgump.apache.org/gump/public/ and a
 FreeBSD jail at http://gump.zones.apache.org/gump/public/

Shane appreciates the great report and a lifetime of build services.

16 Jun 2010 [Stefan Bodewig / Roy]

Apache Gump is a cross-project continuous integration server.  It is
different from "usual" CI servers in that it expects the individual
project builds to succeed; its purpose is to check the integration of
a project with the latest code rather than a fixed version of the
project's dependencies.  If you want a more traditional nightly build
server, Gump is not for you.  Use Gump if you want to know when a
change in your dependencies breaks your project or when your changes
break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle
that makes people look beyond their project's boundaries and helps the
projects to collaborate.

Gump is written in Python and supports several build tools and version
control systems.  The Apache installation of Gump builds many ASF
projects and their dependencies.  It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.

== Issues ==

There are no Board level issues.

== Community ==

The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't
much development going on at all.  No new committers have been added.

All ASF committers have write access to the metadata that configure
the ASF installations.  There are a few people contributing across all
projects and a few additional people maintaining the metadata of the
projects they are interested in the most.

No changes to the PMC.

== Development ==

The last quarter has seen a minor improvement that allows output file
names to be specified with wildcards.  Since Gump cannot influence the
names of jars created by Maven 2.x the paths had to be adjusted with
every release of a project built by it so far.

We've managed to build a few projects that have been failing for a
long time in Gump - among them the ASF projects Portals, ActiveMQ,
Directory Server, Tapestry and parts of Camel.

== Releases ==

The ASF installations of Gump work on the latest code base almost all
of the time.  The project is in a state of a perpetual beta.  There
have been no releases.

== Infrastructure ==

Access to vmgump has been tightened up, the number of people with sudo
has been reduced and OPIE is now required.

== Statistics ==

As of Sun, 06 Jun 2010 the ASF installations check out a bit less than
200 source trees (114 from the ASF repository) and try to build a bit
more than 600 "projects".  A complete Gump run takes more than eleven
hours on vmgump and eight and a half on the Solaris zone.

[1] the main instance at http://vmgump.apache.org/gump/public/ and a
 Solaris zone at http://gump.zones.apache.org/gump/test/

The board views the lack of releases as a non-issue for Gump.

17 Mar 2010 [Stefan Bodewig / Shane]

 Infrastructure:

 * No news is good news.

Technical:

 * the installation is chugging along with active metadata
   maintenance.

 * we've updated the installed version of Maven to 2.2.1 which has
   tightened its verification process for plugins or so it seems.
   The current approach taken by Gump won't work anymore when we'd
   want to perform integration tests for Maven plugins themselves,
   but fortunately there currently is none followed by Gump that
   would be under active development.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

16 Dec 2009 [Stefan Bodewig / Shane]

 Infrastructure:

 * the main Gump (virtual) machine vmgump has been down for a few
   days in November because of problems with its host, fortunately
   we have a Solaris zone so integration builds could continue.

Technical:

 * the installation is chugging along with active metadata
   maintenance.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

23 Sep 2009 [Stefan Bodewig / Brian]

 Infrastructure:

 * many thanks to the infra team for upgrading the OS on vmgump.

Technical:

 * the installation is chugging along with active metadata
   maintenance.  Excalibur moving to Maven 2 builds and Tomcat
   restructuring its svn tree caused a few hiccups that have been
   resolved by now.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

General discussion as to whether projects which don't have releases should be allowed to continue. In the case of Gump, folding into Infra was discussed as a potential alternative. No action was taken.

17 Jun 2009 [Stefan Bodewig / Jim]

 Infrastructure:

 * no news is good news.

Technical:

 * during this quarter Gump has gained support for Bazaar, darcs,
   git and Mercurial - only git support is currently required
   because JUnit moved to github but we expect projects to pick up
   the new scm options at Sourceforge or Google Code sooner or
   later as well.

 * the installation is happily chugging along with active metadata
   maintenance

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

The board is pleased to see support for more SCMs.

18 Mar 2009 [Stefan Bodewig / Jim]

 Infrastructure:

 * no news is good news.

Technical:

 * Gump has seen some development activity sparked by JUnit
   migrating to github but we don't expect too much to happen in
   the future.  Gump is more of a service by now, not a typical
   development project - which is fine with us.

 * the installation is happily chugging along with active metadata
   maintenance

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Question: Should this move to infra? Answer: would not solve any problem, will leave it as is.

17 Dec 2008 [Stefan Bodewig / Henning]

 Infrastructure:

 * we've added the Java packages Gump doesn't build but needs to
   the private svn repo (and consider putting them somewhere else
   later).

   For historical reasons there also exists a password protected
   collection of them in the public svn repo (we needed to get
   reminded of them by infra, thanks!) but these can be removed and
   we don't need the history either - the infrastructure team is
   aware that files and history can be deleted from the public repo
   at any time.

Technical:

 * the installation is happily chugging along but no active
   development

 * Stefan has support for git/hg/bzr and darcs on his personal TODO
   list, but no other development seems to be planned right now

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

17 Sep 2008 [Stefan Bodewig / Henning]

 Infrastructure:

 * no news is good news.

Technical:

 * the installation is happily chugging along but no active development

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

25 Jun 2008 [Stefan Bodewig / Bill]

 Infrastructure:

 * no new is good news.

Technical:

 * the installation is happily chugging along but no active development

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

19 Mar 2008 [Stefan Bodewig / Jim]

 Infrastructure:

 * no new is good news.

Technical:

 * we finally have more than just basic Maven2 support working and
   now build Maven2 projects against the most recent code of their
   dependencies as well.

   There are still some issues to iron out like cases where one jar
   built by Gump is known by more than one id in the repository or
   a project really needs to build against an older version of its
   dependency (think intentional API breakage on a new major
   version).  We also need to migrate more projects and then can
   start adding more projects if they want to.

 * Sooner or later we will need to add support for more VCSes like
   git or hg, so far we didn't have to add a project that uses
   anything but svn or CVS, though.

Other:

 * Crypto: apart from some code that calculates MD5 and SHA1 hashes
   in the Maven Repository Proxy there isn't anything in Gump that
   would go near crypto at all.  As far as we can see there is no
   need for any sort of notification in Gump's code base.

 * still all Apache committers have access to metadata in svn.

 * no releases.

19 Dec 2007 [Stefan Bodewig / J Aaron]

 Infrastructure:

 * no news is good news.

Technical:

 * the Maven 2 experiments on the Solaris zone have been
   encouraging but limited because many projects either don't build
   on Java6 or depend on projects that don't.  Stefan plans to
   merge the experimental stuff into the main Gump line of
   development during the next quarter.

 * We've turned off the Kaffee build.  We never got far due to
   various Kaffee internal problems and right now no Gump
   contributor has spare cycles to spend on keeping the build
   going.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Approved by General Consent.

19 Sep 2007 [Stefan Bodewig / J. Aaron]

 Infrastructure:

 * during the reporting time we've received a brand new machine to
   replace the old vmgump.  Gump was switched over to the new
   machine with very little downtime, which really was awesome.
   Many thanks to the infrastructure team and Leo.


Technical:

 * we've migrated a few more projects to use Maven2 builds and
   managed to get above 85% successful builds on vmgump, which is
   quite nice.  Still we need to do something to make the Maven2
   builds work the Gump way.  Some experiments have been started in
   svn, but nothing that could be used as the real solution has
   been reached, yet.

 * Looking at the Gump zone[1], switching to Java6 would bring our
   success ratio down immediately.  As usual some of the core APIs
   in Java have changed (this time it's JDBC again, as it was with
   Java 1.4 - in Java5 it was JAXP) and projects relying on them
   have been broken.  This is nothing Gump could fix, but it gives
   a good indication of how widely supported (or not) Java6 may be
   right now in the projects we build.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

[1] http://gump.zones.apache.org/gump/test/project_todos.html

Approved by General Consent.

20 Jun 2007 [Stefan Bodewig / Sam]

 Infrastructure:

 * vmgump is in serious disk space trouble by now.  Since we've
   started building Maven2 projects the number of things that get
   built successfully has become large enough to cause problems.
   On some days we can't finish the Gump run because we run out of
   disk.  We need to hope a project with many dependencies fails
   every now and then 8-).

Technical:

 * we've decided to become pragmatic WRT Maven2 and build non-leaf
   projects that use Maven2 against the repository jars instead of
   the latest builds.  This at least allows the upstream
   dependencies of said project to build against the latest code.
   There are ideas how to make Maven2 support complete, but not
   enough time/people to see it implemented.

Other:

 * Stefano left the Gump PMC for personal reasons.  We want to
   thank him for his support and time in the past.

 * still all Apache committers have access to metadata in svn.

 * no releases.

Jim asked about the disk space concerns noted in the report. Justin indicated that infrastructure did some cleanup for Gump folks, but discussions underway to procure more resources for Gump.

Approved by General Consent.

28 Mar 2007 [Stefan Bodewig / Justin]

 Infrastructure:

 * Justin was kind enough to bring vmgump's Debian packages up to
   more recent versions, many thanks.

 * vmgump probably is at its limits of disk space as well as CPU.
   A full run of what we currently build is taking more than 6 and
   a half hours.


Technical:

 * vmgump is now running Mono 1.2.3 and successfully builds NAnt.
   The next step is making Gump's NAnt support actually work and
   start building log4net.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Sander noted that the reported limits need more investigation since the VMware graphs[1] do not seem to show us hitting the limits. Justin will work with Infra to see if upgraded s/w will address this.

[1] https://loki.apache.org/vmkusage/index.html

Approved by General Consent.

20 Dec 2006 [Stefan Bodewig / Greg]

 Infrastructure:

 * We had a little outage after the colo migration since vmgump
   didn't come up properly.  Yet another reason to look forward to
   the beefer machine Justin hinted at last time.

Technical:

 * Stefano has set up a Gump build running on top of Harmony[1]
   which currently is stuck by not finding a javac command line
   compatible compiler.

 * Much of the gump side of Maven2 support is done, Bill Barker now
   also wants to give the Maven side a try - we need to make Maven
   use the jars created by gump instead of those from any local or
   remote repository.  There is hope.

 * sourceforge has found a new way to keep us moving stuff around.
   They are now moving the subversion repositories to virtual hosts
   per project, which means changing descriptors and deleting
   working copies on all Gump instances again.  Won't be the last
   time.

Other:

 * Sander Temme has been added to the PMC on 2006-12-01.

 * still all Apache committers have access to metadata in svn.

 * no releases.

Footnotes:
[1]  http://67.86.14.213:10000/gump/

Justin asked if we should dedicate more resources for Gump builds. A beefier machine would likely address any concerns. Justin will discuss this with the project and Infrastructure.

Approved by General Consent.

20 Sep 2006 [Stefan Bodewig / Jim]

Infrastructure:

* During the past weeks we've repeatedly run into disk usage problems,
 we are slowly but steadily outgrowing the resources provided by
 vmgump.  We'll shortly engage in a discussion with the
 infrastructure team to see, what our options are.

* We've informed osuosl and the infrastructure team that we'd like to
 give back gump.osuosl.org.

Technical:

* Maven2 support hasn't improved during the past quarter.

 To tell the truth, we don't have any people actively developing
 anything right now, so we don't expect this to change unless anybody
 jumps in.

 Gump is more and more moving into the direction of a pure
 infrastructure/service type of project with a handful of people
 maintaining it.  This isn't necessarily a bad thing since Gump's
 code is pretty stable and - except for Maven 2 support - does what
 it is supposed to do.

* All CVS locations for sourceforge projects have been fixed by now.

Other:

* still all Apache committers have access to metadata in svn.

* no releases.

Justin reported that he had relayed info on machines plans for VMWare to the Gump PMC as requested.

Approved by General Consent

19 Jul 2006 [Stefan Bodewig / Ken]

 Infrastructure:

 * We are in the process of giving back gump.osuosl.org since we
   simply lack the people to take care of it.

Technical:

 * Our biggest problem right now is the lack of support for and by
   Maven 2 which needs to get addressed if we don't want to see more
   Java projects become unbuildable.

 * SourceForge CVS has been having problems since late March, when
   anonymous CVS dropped out of sync with the private
   repositories. In mid-may the site moved from having one CVS server
   for everything, to having a separate hostname for every project's
   repository. For Gump, this means that every sourceforge-hosted
   project needs to have their own repository file and the existing
   builds need to be completely purged. Currently only a few projects
   have been migrated due to their ubiquitousness (JUnit) or due to
   the effort of the project members themselves. Obviously, only
   project members who are also apache committers can do this
   unaidedely, which pushes more work onto the gump team.

   Until a full migration takes place, sourceforge-hosted projects
   will be built using a source snapshot of early May. This is going
   to lead to problems the longer the migration is put off.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Approved by General Consent

27 Jun 2006 [Stefan Bodewig / Ken]

 Infrastructure:

 * We are in the process of giving back gump.osuosl.org since we
   simply lack the people to take care of it.

Technical:

 * Our biggest problem right now is the lack of support for and by
   Maven 2 which needs to get addressed if we don't want to see more
   Java projects become unbuildable.

 * SourceForge CVS has been having problems since late March, when
   anonymous CVS dropped out of sync with the private
   repositories. In mid-may the site moved from having one CVS server
   for everything, to having a separate hostname for every project's
   repository. For Gump, this means that every sourceforge-hosted
   project needs to have their own repository file and the existing
   builds need to be completely purged. Currently only a few projects
   have been migrated due to their ubiquitousness (JUnit) or due to
   the effort of the project members themselves. Obviously, only
   project members who are also apache committers can do this
   unaidedely, which pushes more work onto the gump team.

   Until a full migration takes place, sourceforge-hosted projects
   will be built using a source snapshot of early May. This is going
   to lead to problems the longer the migration is put off.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Tabled due to time constraints.

15 Mar 2006 [Stefan Bodewig / Dirk]

 Infrastructure:

 * Sander Temme has installed Gump on one of the donated Macs, see
   http://clarus.apache.org/

 * gump.osuosl.org is still more or less dormant because we
   couldn't find the time to install a Gump instance there.

Technical:

 * After JUnit started to require Java 5 to compile, we finally
   switched to use it on vmgump.  The alternative would have been
   to be content with 35% success.

Other:

 * still all Apache committers have access to metadata in svn.

 * no releases.

Approved by General Consent.

21 Dec 2005 [Stefan Bodewig / Ken]

 Infrastructure:

 * vmgump ran into trouble after a kernel update.  Many thanks to
   Noel and Leo for reviving it.

 * gump.osuosl.org is still more or less dormant because we
   couldn't find the time to install a Gump instance there.

Technical:

 * Work continues on Gump3. It is slowly and steadily progressing
   into a codebase that does useful stuff.

Other:

 * Bill Barker has been added to the PMC.

 * still all Apache committers have access to metadata in svn.

 * no releases.

Approved by General Consent.

21 Sep 2005 [Stefan Bodewig / Sam]

 Infrastructure:

 * we are using vmgump and our zone at helios, we managed to get
   Mono on vmgump and Kaffe on helios working well enough to get
   reasonable results.

 * gump.osuosl.org is still more or less dormant because we
   couldn't find the time to install a Gump instance there.

 * metadata have been moved to svn, we are a svn-only project now.

Technical:

 * Work continues on Gump3. It is slowly and steadily progressing
   into a codebase that does useful stuff.

Other:

 * Brett Porter has been added to the PMC.  It was about time.

 * still all Apache committers have access to metadata in svn.

 * no releases.

 * our two Google SoC projects finished with results that we
   are quite happy with.  On the other hand we feel we didn't
   manage to involve the students with the community as we wanted
   to do.  The reasons for this are not totally clear to us -
   having at least three PMC members (Leo, Adam and Stefan) go
   through major changes IRL hasn't helped.

Approved by General Consent.

22 Jun 2005 [Stefan Bodewig]

 Infrastructure:

 * we've moved off of Brutus and are now spread over three
   machines.  vmgump.apache.org is a VMWare instance on Loki,
   gump.zones.apache.org a Solaris zone on helios and
   gump.osuosl.org a MacOS X server of the Oregon State University
   that we can use. Many Thanks!

 * vmgump will become our primary machine for now, we are slowly
   progressing to the state of stability we had on brutus.

 * the other instances are not yet fully up and running.

Technical:

 * Work continues on Gump3. It is slowly and steadily progressing
   into a codebase that does useful stuff.

Other:

 * Nick Chalko has taken a leave of absence from the PMC, we hope
   to get him back next year.

 * still all Apache committers have access to metadata in CVS.

 * no releases.

 * There are three proposed Summer of Code projects for Gump, all
   focused on Gump3 development. Mentors include Scott Sanders,
   Adam Jack and Leo Simons. Since Gump is one of the few
   python-based projects in the programme, we expect some of these
   will be successfully followed up on.

Approved by General Consent.

30 Mar 2005 [Stefan Bodewig]

 Brutus:

 * access to brutus has been granted to Brett Porter

 * access to brutus has also been granted to David Crossley,
   Reinhard Poetz and Dave Brondsema to use brutus for Forrest

 * we are rather low on disk space. This is no emergency situation
   yet, we are dealing with it, so no action is required. If we
   want to expand the variations of Gump builds to more VMs, this
   will become a problem, though.

 * we've received a few requests for nightly builds on Brutus but
   not acted on it so far. One reason is the disk space problem,
   another that we consider Brutus "insecure as hell" (to quote
   Leo). Since Gump downloads and runs scripts from all over the
   world it could potentially taint the nightly build system as
   well, even if we are doing our best to prevent this (they don't
   share anything but the JDK installation).

Technical:

 * We are happily building C based projects using configure/make by
   now. On our roster are APR, HTTPD and Log4CXX so far.

 * There is slow progress on a Gump redesign that aims at making
   Gump less monolithic and using Python like Python instead of
   Java.

Other:

 * no PMC changes, still all Apache committers have access to
   metadata in CVS, no releases

Apache Gump Project report approved as submitted by general consent.

15 Dec 2004 [Stefan Bodewig]

 Brutus:

 * access to brutus has been granted to Niclas Hedhman

 * we've established an experimental Gump-independent nightly build
   system on http://brutus.apache.org/~nightlybuild/ that is
   currently used by Excalibur and Ant.

Other:

 * no PMC changes, still all Apache committers have access to
   metadata in CVS, no releases

It was also noted that Gump has progressed to the point where it can build APR and HTTPD.

Apache Gump Project report approved as submitted and discussed by general consent.

22 Sep 2004 [Stefan Bodewig]

Gump code was migrated to SVN[1], with Gump metadata continuing to
remain in CVS[2] (to be less of a community barrier, until SVN usage
has matured as the norm with ASF-wide). At this same time
'traditional' Gump (the Java/Shell/XSLT/Perl combination) was finally
archived. Python Gump is re-structuring itself (within SVN) to attempt
to become more intuitive to new users.

The Gump PMC voted to allow 'Gumped artifacts' to be publically
available in a repository. These artifacts are to be specifically
marked as '-gump' so as to attempt remove/reduce any confusion with
releases. Also, each directory listing in the repository is to be
marked with a disclaimer explaining that the contents can not be
trusted, and are not releases. [3]

The Gump PMC voted to grant 'root access' to ajack@apache.org (a
non-member) to Brutus. Since Brutus is managed by the Gump team (and
is standalone/untrusted) infrastructure felt this did not constitute a
security concern.

After some discussion on community@apache.org regarding the need for
PMC oversight of mailing lists, the Gump PMC voted to sponsor
python@apache.org. The intent is to discuss "Python w.r.t ASF", and
allow the various Python projects to collaborate. Unfortuantely, the
request has sat (seemingly untouched) in JIRA since August 4th
2004. [5]

Nicola Ken Barozzi has resigned from the Gump PMC.  We want to thank
him for his past contributions and are happy that he still wants to
keep in touch by retaining his committer status.

Gump now can generate XHTML output directly without the need of a
Forrest webapp (although still a supported option). This reduction in
dependency is intended to ease Gump installation (and hence adoption)
by new users.

Gump has received some technical improvements recently. Gump was
migrated from Python 2.2 to Python 2.3 (and benefits from many new
language features). Multithreading support for CVS|SVN downloads
removed latency delays from Gump's total run time. MySQL integration
(for historical results data) is currently live. RDF is generated
describing projects and their interactions (at dependency level) using
a work-in-progress Gump Ontology.

Gump's current focus is on opening itself up to more developers (via
documentation) and new users.  As part of reaching beyond Java Mono
1.0 has been installed on Brutus and we are collaborating with the
NAnt[4] community to take on .NET projects.

Along these lines, and with little to no help from the Gump community,
Peter Janes took Python Gump and integrated it with Perforce [6]. He
supplied patches that added Perforce repository capabilities to
complement CVS and SVN. This patch included documentation [7] [8] and
was very high quality work.

Gump now build artifacts and stores them in an online repository, and
(as such) can build projects using historical artifacts in it's
repository. This will allow Gump to smooth out the problems of
'prerequisite failure' Further, Gump also works with Depot to download
artifacts from artifact repositories to automate package processing,
and/or allow cascaded Gumps. None of this code is well tested/mature
at this point, and some problem reports exist.

[1] http://cvs.apache.org/viewcvs.cgi/gump/?root=Apache-SVN
[2] http://cvs.apache.org/viewcvs.cgi/gump
[3] http://cvs.apache.org/viewcvs.cgi/gump/trunk/ARTIFACT_DISCLAIMER.html?root=Apache-SVN
[4] http://nant.sf.net/ - the build tool used by most open source .NET projects.
[5] http://nagoya.apache.org/jira/browse/INFRA-100
[6] http://www.perforce.com/
[7] http://gump.apache.org/metadata/repository.html#Perforce+Usage
[8] http://gump.apache.org/metadata/module.html#p4

Approved by General Consent.

23 Jun 2004 [Stefan Bodewig]

We've been very happy playing with the new machine and brutus has been
turned into the "official" Gump instance, i.e. the one that is sending
nightly nag mails when things go wrong and that people use as
reference.  Many thanks to Sam Ruby and Leo Simons who provided
personal infrastructure for this purpose in the past.

The speed of Brutus combined with a new way to generate the website
dynamically allows us to run Gump more than once per day and has
already led to some new uses, like sending out "good news nags" when
things are no longer broken. Notifications are also now sent "when
first detected" (as well as on the nightly 'official' run) which can
dramatically shorten the detection/discussion/resolution cycle.

Gump has assisted in detecting a number of issues, including a big one
with log4j deprecation which raised excellent discussion and awareness
on Apache's and "good" deprecation/release policies. More information
is available on Gump's Blog[1].

Gump has started to successfully build its first live project using
Maven, we hope to extend this success to Geronimo soon. The main
integration issue is that of 'artefact id' (how a collection of code
is identified). This is good practical community work; a precursor to
an (automated/shared) Apache Repository[2].

Gump is starting to see more 'personal Gumps', as folks install Gump
for their own private (and public) projects.

Footnotes:
[1]  http://gump.chalko.com/gb/blog/

[2]  http://wiki.apache.org/old/ASFRepository

Stefano lamented lack of participation time on his part. No other comments.

17 Mar 2004 [Stefan Bodewig]

Most of the past few weeks has been filled with infrastructure stuff.

We've successfully migrated web-site, CVS module, bug-tracking and the
mailing list to gump.apache.org - many thanks to the infrastructure
team for making the transition that smooth.

All Apache committers have been Gump committers with the old setup and
this still remains true.  We want to get as many people involved as
possible when it gets to maintaining the project metadata.  This is
the reason that we've been sticking to CVS for now since we can reach
most Apache committers that way.  Gump will probably be one of the
last projects that make the transition to Subversion.

Work on the project bylaws has started and we expect to have them
ready for the next board meeting.  Gump is unique when it comes to
committer status so we'll have to put some thoughts into the
definition of that role.

Gump has been quite successful in pointing out problems in some builds
recently and we are happy that most of them have been resolved between
projects easily.  Our biggest problem right now is building Avalon,
but this may be due to the fact that Gump is using a different build
system than Avalon more than anything else.  Once Gump supports Maven
as a build option, things may become easier for Avalon.

We continue improving the Python rewrite of Gump and have come quite a
long way already.  Since nobody of us is anywhere near a Python guru,
we may be doing things far more complicated than necessary.  Any help
is welcome. 8-)

The short-to-mid-term future steps for Gump are

 * get dedicated ASF hardware to run Gump on - [currently working on
   getting it running on Moof but we are really looking forward to
   the new gump-dedicated machine].

 * expand Gump's reach beyond building Java projects.

 * improve the way Gump works by trying to find an computationally
   feasible way to nagging the offender and not the offended, improve
   the usability/effectiveness of gump reports, find ways to increase
   adoption by making social pressure of nagging more effective and
   ease the effort required for users to update their project
   descriptors.

 * start thinking on how to provide feedback for legal dependencies
   checkings

Approved by General Consent.

18 Feb 2004

Establish Gump PMC

  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software related to continuous integration, for
  distribution at no charge to the public.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache Gump PMC", be and
  hereby is established pursuant to Bylaws of the Foundation; and
  be it further

  RESOLVED, that the Apache Gump PMC be and hereby is responsible
  for the creation and maintenance of software related to
  promotion and facilitation of automated integration of the
  software produced by other projects, based on software licensed
  to the Foundation; and be it further

  RESOLVED, that the office of "Vice President, Apache Gump" be
  and hereby is created, the person holding such office to serve
  at the direction of the Board of Directors as the chair of the
  Apache Gump PMC, and to have primary responsibility for
  management of the projects within the scope of responsibility
  of the Apache Gump PMC; and be it further

  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Gump PMC:

    Adam Jack <ajack@apache.org>
    Stefan Bodewig <bodewig@apache.org>
    Davanum Srinivas <dims@apache.org>
    Leo Simons <leosimons@apache.org>
    Martin van den Bemt <mvdb@apache.org>
    Nick Chalko <nickchalko@apache.org>
    Nicola Ken Barozzi <nicolaken@apache.org>
    Scott Sanders <sanders@apache.org>
    Stefano Mazzocchi <stefano@apache.org>

  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stefan Bodewig
  be and hereby is appointed to the office of Vice President,
  Apache Gump, to serve in accordance with and subject to the
  direction of the Board of Directors and the Bylaws of the
  Foundation until death, resignation, retirement, removal or
  disqualification, or until a successor is appointed; and be it
  further

  RESOLVED, that the initial Apache Gump PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Gump Project; and be it further

  RESOLVED, that the initial Apache Gump PMC be and hereby is
  tasked with the migration and rationalization of the Apache
  Jakarta PMC Gump subproject; and be it further

  RESOLVED, that all responsibility pertaining to the Jakarta
  Gump sub-project encumbered upon the Apache Jackarta PMC be
  herewith considered discharged.

 Approved by Unanimous Vote.