Hi,

While we wait for the new committer accounts to start coming in,
here's some basic information to all the new Apache committers. This
information is based on a template used to welcome new committers to
Apache. Others may also find this interesting, so I'm posting this as
a generic message to chemistry-...@.

Once your Apache account has been created, you will receive an email
with information on how to use it. You should use one of the many ssh
clients to login and change both your account password, using the
passwd command, and your subversion password using the svnpasswd
command (we recommend using different passwords).

Many developers also place their public

    ssh keys in ~/.ssh/authorized_keys
    pgp/gpg key in ~/.pgpkey
    pgp/gpg key fingerprint summary in ~/.pubkey

in their home directory on the people.apache.org server.

Version Control
===============

After setting up your account, you can check out the latest Chemistry
trunk with write access is enabled (note the https scheme):

    svn checkout https://svn.apache.org/repos/asf/incubator/chemistry/trunk

More committer and subversion info can be found at

    http://www.apache.org/dev/
    http://www.apache.org/dev/committers.html

    http://subversion.tigris.org/
    http://svnbook.red-bean.com/
    http://svnbook.red-bean.com/svnbook/apa.html  (quick guide for cvs users)

BEFORE COMMITTING anything using subversion, please set up your local
configuration so that it adds native eol properties to the common text
files.  Instructions can be found at

    http://www.sipfoundry.org/tools/svn-tips.html#line-ends
    http://www.apache.org/dev/svn-eol-style.txt


Issue Tracking
==============

We are using the following Jira project to track issues in Apache Chemistry:

    https://issues.apache.org/jira/browse/CMIS

I've added the relevant Jira accounts I could find as Chemistry
committers, so you can now edit, resolve, and close issues. If you
don't yet have a Jira account, go register one and let me know the
account name so I can grant you the required access rights.


Mailing Lists
=============

The following mailing list is where all technical decisions about what
goes in (or out) of the Chemistry code get made:

    [email protected]

As a committer, you should also subscribe to the automated change
notices that will be sent to

    [email protected]

Archives of the all the public lists can be found at

    http://mail-archives.apache.org/mod_mbox/

All the initial committers and mentors have been subscribed to the private list

    [email protected]

which exists *only* for discussion of private matters within the
Chemistry PPMC (podling project management committee), such as
personnel issues (like proposing a new committer), licensing issues,
or security issues that have not yet been made public.  Please note
that normal technical discussion and project decisions (such as voting
on a release) are never done on the private list.  Although the
mailing list has a small membership, as described below, it is also
archived so that any member of the Apache Software Foundation can read
it later for oversight.

BTW, the Chemistry PPMC is the group created to make technical
decisions regarding the Apache Chemistry software, as delegated by the
Apache Incubator project. The Chemistry PPMC consists of all the
committers and mentors of the project.


Other useful information
========================

There exists a general sandbox for all projects, the committers
module, that contains various Apache tools and information about the
Apache projects and their committee info.

    svn co https://svn.apache.org/repos/private/committers

If you are interested in general Apache discussion, like how the
community works (or complaints about how it doesn't work), you can
subscribe to the [email protected] mailing list. All committers are
also subscribed to a broadcast list called [email protected] which
is limited to important announcements from the ASF board or
infrastructure team.

Speaking of which, if you have an account or machine problem to
report, please send it to [email protected] or create an issue
at

    http://issues.apache.org/jira/browse/INFRA

BR,

Jukka Zitting

Reply via email to