I'm working on new patches for OPENJPA-772 now. From years of pain on
Geronimo, I now that keeping a well maintained project pom can go a long
way in minimizing build surprises (like not using pinned maven plugins
which can break builds when newer plugin versions are released) and
making the release process less error prone (like using the ianal plugin
during normal builds to catch missing legal files.)
As far as contributors, over on Geronimo, we'll add anyone to our
geronimo-contributors group who asks, as long as they have an ICLA on
file. That allows new community members to assign existing unassigned
JIRAs to themselves, so we don't end up with multiple people working the
same issue. We also use it to control edit access to our Confluence
user docs (other spaces like our main site can only be edited by
committers), so that all web content we produce is covered by an ICLA.
-Donald
Kevin Sutter wrote:
Hi Don,
Thanks for your enthusiasm to work with and contribute to the OpenJPA
project. Normally, we like to see some continued participation on our
forums and JIRAs before just adding people to the Contributor list. Maybe
that's different from the Geronimo project. Is there a specific JIRA issue
that you are interested in working on?
Thanks,
Kevin
On Wed, Jan 28, 2009 at 10:58 AM, Donald Woods <dwo...@apache.org> wrote:
Can someone grant my Apache id=drwoods contributor rights in JIRA, so I can
assign items to myself to work on and have more JIRA karma than just a
normal user?
Thanks,
Donald Woods
Apache Geronimo Committer and PMC Member
