db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject How Open Source Works (was Re: Spawning Data on Multiple Directories)
Date Thu, 04 May 2006 15:44:42 GMT
derby@segel.com wrote:
> This goes back to the larger issue is the need to consider a look at
> redesigning Derby's framework to allow for options to be installed/removed
> at the time of deployment. (And there are some headaches even there too...)
> The point is that Derby is growing in popularity and certain larger issues
> than just quick fixes that can be addressed in a single JIRA issue need to
> be addressed.  

It's time for a reminder to the list of how software development works
at Apache because it *is* open source and it *isn't* commercial. This
can sometimes be a bit confusing to new users who are familiar with how
commercial products work.

The first thing to understand is *individuals* volunteer to tackle
various tasks. Here are some relevant snippets from
http://www.apache.org/foundation/how-it-works.html :

   "Projects are normally auto governing and driven by the people who
    volunteer for the job. This is sometimes referred to as "do-ocracy"
    -- power of those who do. This functions well for most cases."

   "All of the ASF including the board, the other officers, the
    committers, and the members, are participating as individuals.
    That is one strength of the ASF, affiliations do not cloud the
    personal contributions.

    Unless they specifically state otherwise, whatever they post on any
    mailing list is done *as themselves*. It is the individual
    point-of-view, wearing their personal hat and not as a mouthpiece
    for whatever company happens to be signing their paychecks right
    now, and not even as a director of the ASF."

But, now lest it look like everybody is working diligently solely as an
individual (and possibly at cross purposes with others), a lot of
community coordination and contribution occurs on the Apache mail lists.
The http://www.apache.org/foundation/how-it-works.html page has lots of
helpful context.

At any rate, Derby depends on the community to work together as a whole
to change the product.

How can Derby users actively contribute to these changes?

First, you can open Jira issues to report problems you have stumbled
upon. More information is at
http://db.apache.org/derby/DerbyBugGuidelines.html . However, remember
that volunteers fix issues -- here's a valuable snippet from
http://www.apache.org/foundation/faq.html#what-is-apache-NOT-about :

    What is Apache not about?

    To [... jean deleted text to highlight tail of sentence ...] demand
    someone else to fix your bugs.

Second, you can vote on Jira issues that you feel strongly should be
fixed. The Derby developers do look at the votes.

Third, if you want to participate even more in the Derby development
process, you're welcome to subscribe to derby-dev@db.apache.org. That's
where core development discussions occur and decisions get made.

Fourth, if you want to actually start doing development, the
http://wiki.apache.org/db-derby/ForNewDevelopers page has wonderful
suggestions and tips for new Derby developers.

Whether a particular user decides to volunteer or not, it's still
helpful to understand how Apache works.


View raw message