[PROPOSAL][VOTE] Subversion

[Greg Stein-4]

 Subversion is a version control system.  You probably know it well as
it is the version control system employed by the Apache Software
Foundation.

 The Subversion project would like to join the Apache Software
Foundation to remove the overhead of having to run its own
corporation.  The Subversion project is already run quite like an
Apache project, and already counts a number of ASF Members amongst
its committers.

 Work on Subversion was originally started at CollabNet; Karl Fogel
was hired in January 2000.  Jim Blandy, at RedHat, already had an
initial design for the storage system, which was incorporated into the
FS design.  In February Brian Behlendorf invited Greg Stein to
contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
was hired in April 2000 to work on the project.  In that same month
the first "all hands" meeting was held, where a number of "interested
people" came together to talk about the project.

 Subversion was run as an open source project since the early days.
Now, more than nine years later, it retains a healthy community,
and has a good number of committers.  In the life span of Subversion,
several committers have switched employers and have maintained involvement.
The committership is diverse, both geographically as well as in terms of
employment.

 The equivalent of the PMC consists of all the full committers to the
Subversion project (currently around 55 people).  The community uses the
voting process also used at the ASF.  Releases are signed off by gathering
votes/digital signatures of each committer who verified the release
candidate.

 We feel the ASF and Subversion communities are very compatible,
witness the cross interest that already exists. There is both a
vibrant developer as well as a large and active user community.
Technology-wise, Subversion builds on APR, and implements two Apache
HTTP Server modules.

 Note that Subversion has a number of related projects, which are not
part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).

 More information on Subversion can be found at
http://www.subversion.org/ and http://subversion.tigris.org/.

 The Subversion Corporation has a license to all source code, and has
CLAs on file for nearly all it's committers.  That is, we have all but
one or two full committers, and some percentage of partial committers.

 We have a number of *user-configurable* dependencies which are not
compatible with the AL:
 - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
    library under ALv2.)

 - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
under Academic Free License 2.1 or >=GPL-2.
   (This support is for integration for KDE and GNOME's authentication
    providers.)

 - libintl
   (This library provides translation support for systems without
    a proper internationalization library.)

 - BDB
   (This is used by the libsvn_fs_base system which stores its data
    in BDB; an alternative repository system called fs_fs does not
    have this dependency.)

---
Required Resources
 - Mailing lists
   - dev
   - issues
   - users
   - private
   - commits
   - announce
   - breakage (see
http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
   - We will work with the Infrastructure team to transfer the subscriber
     listings to the new destinations.
 - Subversion:
   - We have not made a decision whether we prefer Subversion should be
     imported into the main ASF Subversion repository or be hosted as a
     separate repository to enable early testing of the repository code.  We
     intend to discuss this during the Incubation process before the code is
     imported.  It is also understood that ASF infrastructure team may be
     willing to run custom pre-release Subversion server builds for the
     entire ASF, so this separate repository option may not be required.
   - The Subversion source code can be found at:
     http://svn.collab.net/repos/svn/.
 - Issue tracking
   - We haven't made a decision between JIRA or Bugzilla at this time and
     expect this decision to be made as part of the Incubation process.  Our
     current issue tracking system uses Issuezilla (a fork of Bugzilla) and
     we have not yet decided whether we want to import our previous issues
     into the new system and will decide this in the course of the Incubation
     process.
   - Our current issue tracker is at
     http://subversion.tigris.org/issue-tracker.html.
 - Buildbot
   - We currently use buildbot across a number of platforms and configurations
     for automated builds and testing.  Over time, we would like to migrate
     these services to Apache infrastructure where appropriate.
   - Our current buildbot master is at
     http://buildbot.subversion.org/buildbot/

 Note that we request these resources to be at their final locations,
not an intermediary while going through incubation.  The cost of
switching twice would otherwise be significant due to the size of the
existing community.

 The Subversion team members are happy to work with and assist the ASF
Infrastructure team to enable early deployments of its release candidates if
possible.

Initial Committers

 The list of initial committers is at
http://svn.collab.net/repos/svn/trunk/COMMITTERS.

The initial PMC members are those listed as full committers in that
file (lines 1-74).

Sponsors
 * Champion: Greg Stein
 * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
 * Sponsor:

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Matthias Wessendorf-4]

+1 :-)

On Wed, Nov 4, 2009 at 9:12 PM, Greg Stein <gstein@...> wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>    library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>   (This support is for integration for KDE and GNOME's authentication
>    providers.)
>
>  - libintl
>   (This library provides translation support for systems without
>    a proper internationalization library.)
>
>  - BDB
>   (This is used by the libsvn_fs_base system which stores its data
>    in BDB; an alternative repository system called fs_fs does not
>    have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>   - dev
>   - issues
>   - users
>   - private
>   - commits
>   - announce
>   - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>   - We will work with the Infrastructure team to transfer the subscriber
>     listings to the new destinations.
>  - Subversion:
>   - We have not made a decision whether we prefer Subversion should be
>     imported into the main ASF Subversion repository or be hosted as a
>     separate repository to enable early testing of the repository code.  We
>     intend to discuss this during the Incubation process before the code is
>     imported.  It is also understood that ASF infrastructure team may be
>     willing to run custom pre-release Subversion server builds for the
>     entire ASF, so this separate repository option may not be required.
>   - The Subversion source code can be found at:
>     http://svn.collab.net/repos/svn/.
>  - Issue tracking
>   - We haven't made a decision between JIRA or Bugzilla at this time and
>     expect this decision to be made as part of the Incubation process.  Our
>     current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>     we have not yet decided whether we want to import our previous issues
>     into the new system and will decide this in the course of the Incubation
>     process.
>   - Our current issue tracker is at
>     http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>   - We currently use buildbot across a number of platforms and configurations
>     for automated builds and testing.  Over time, we would like to migrate
>     these services to Apache infrastructure where appropriate.
>   - Our current buildbot master is at
>     http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[dims]

+1 from me.

On 11/04/2009 03:36 PM, Matthias Wessendorf wrote:

> +1 :-)
>
> On Wed, Nov 4, 2009 at 9:12 PM, Greg Stein<gstein@...>  wrote:
>>   Subversion is a version control system.  You probably know it well as
>> it is the version control system employed by the Apache Software
>> Foundation.
>>
>>   The Subversion project would like to join the Apache Software
>> Foundation to remove the overhead of having to run its own
>> corporation.  The Subversion project is already run quite like an
>> Apache project, and already counts a number of ASF Members amongst
>> its committers.
>>
>>   Work on Subversion was originally started at CollabNet; Karl Fogel
>> was hired in January 2000.  Jim Blandy, at RedHat, already had an
>> initial design for the storage system, which was incorporated into the
>> FS design.  In February Brian Behlendorf invited Greg Stein to
>> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
>> was hired in April 2000 to work on the project.  In that same month
>> the first "all hands" meeting was held, where a number of "interested
>> people" came together to talk about the project.
>>
>>   Subversion was run as an open source project since the early days.
>> Now, more than nine years later, it retains a healthy community,
>> and has a good number of committers.  In the life span of Subversion,
>> several committers have switched employers and have maintained involvement.
>> The committership is diverse, both geographically as well as in terms of
>> employment.
>>
>>   The equivalent of the PMC consists of all the full committers to the
>> Subversion project (currently around 55 people).  The community uses the
>> voting process also used at the ASF.  Releases are signed off by gathering
>> votes/digital signatures of each committer who verified the release
>> candidate.
>>
>>   We feel the ASF and Subversion communities are very compatible,
>> witness the cross interest that already exists. There is both a
>> vibrant developer as well as a large and active user community.
>> Technology-wise, Subversion builds on APR, and implements two Apache
>> HTTP Server modules.
>>
>>   Note that Subversion has a number of related projects, which are not
>> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>>
>>   More information on Subversion can be found at
>> http://www.subversion.org/ and http://subversion.tigris.org/.
>>
>>   The Subversion Corporation has a license to all source code, and has
>> CLAs on file for nearly all it's committers.  That is, we have all but
>> one or two full committers, and some percentage of partial committers.
>>
>>   We have a number of *user-configurable* dependencies which are not
>> compatible with the AL:
>>   - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>>     library under ALv2.)
>>
>>   - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
>> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
>> under Academic Free License 2.1 or>=GPL-2.
>>    (This support is for integration for KDE and GNOME's authentication
>>     providers.)
>>
>>   - libintl
>>    (This library provides translation support for systems without
>>     a proper internationalization library.)
>>
>>   - BDB
>>    (This is used by the libsvn_fs_base system which stores its data
>>     in BDB; an alternative repository system called fs_fs does not
>>     have this dependency.)
>>
>> ---
>> Required Resources
>>   - Mailing lists
>>    - dev
>>    - issues
>>    - users
>>    - private
>>    - commits
>>    - announce
>>    - breakage (see
>> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>>    - We will work with the Infrastructure team to transfer the subscriber
>>      listings to the new destinations.
>>   - Subversion:
>>    - We have not made a decision whether we prefer Subversion should be
>>      imported into the main ASF Subversion repository or be hosted as a
>>      separate repository to enable early testing of the repository code.  We
>>      intend to discuss this during the Incubation process before the code is
>>      imported.  It is also understood that ASF infrastructure team may be
>>      willing to run custom pre-release Subversion server builds for the
>>      entire ASF, so this separate repository option may not be required.
>>    - The Subversion source code can be found at:
>>      http://svn.collab.net/repos/svn/.
>>   - Issue tracking
>>    - We haven't made a decision between JIRA or Bugzilla at this time and
>>      expect this decision to be made as part of the Incubation process.  Our
>>      current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>>      we have not yet decided whether we want to import our previous issues
>>      into the new system and will decide this in the course of the Incubation
>>      process.
>>    - Our current issue tracker is at
>>      http://subversion.tigris.org/issue-tracker.html.
>>   - Buildbot
>>    - We currently use buildbot across a number of platforms and configurations
>>      for automated builds and testing.  Over time, we would like to migrate
>>      these services to Apache infrastructure where appropriate.
>>    - Our current buildbot master is at
>>      http://buildbot.subversion.org/buildbot/
>>
>>   Note that we request these resources to be at their final locations,
>> not an intermediary while going through incubation.  The cost of
>> switching twice would otherwise be significant due to the size of the
>> existing community.
>>
>>   The Subversion team members are happy to work with and assist the ASF
>> Infrastructure team to enable early deployments of its release candidates if
>> possible.
>>
>> Initial Committers
>>
>>   The list of initial committers is at
>> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>>
>> The initial PMC members are those listed as full committers in that
>> file (lines 1-74).
>>
>> Sponsors
>>   * Champion: Greg Stein
>>   * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>>   * Sponsor:
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Paul Querna-6]

On Wed, Nov 4, 2009 at 12:12 PM, Greg Stein <gstein@...> wrote:
>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.

+1, good luck on the incubation :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Felix Meschberger-2]

+1

Regards
Felix

Greg Stein schrieb:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>     library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>    (This support is for integration for KDE and GNOME's authentication
>     providers.)
>
>  - libintl
>    (This library provides translation support for systems without
>     a proper internationalization library.)
>
>  - BDB
>    (This is used by the libsvn_fs_base system which stores its data
>     in BDB; an alternative repository system called fs_fs does not
>     have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>    - dev
>    - issues
>    - users
>    - private
>    - commits
>    - announce
>    - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>    - We will work with the Infrastructure team to transfer the subscriber
>      listings to the new destinations.
>  - Subversion:
>    - We have not made a decision whether we prefer Subversion should be
>      imported into the main ASF Subversion repository or be hosted as a
>      separate repository to enable early testing of the repository code.  We
>      intend to discuss this during the Incubation process before the code is
>      imported.  It is also understood that ASF infrastructure team may be
>      willing to run custom pre-release Subversion server builds for the
>      entire ASF, so this separate repository option may not be required.
>    - The Subversion source code can be found at:
>      http://svn.collab.net/repos/svn/.
>  - Issue tracking
>    - We haven't made a decision between JIRA or Bugzilla at this time and
>      expect this decision to be made as part of the Incubation process.  Our
>      current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>      we have not yet decided whether we want to import our previous issues
>      into the new system and will decide this in the course of the Incubation
>      process.
>    - Our current issue tracker is at
>      http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>    - We currently use buildbot across a number of platforms and configurations
>      for automated builds and testing.  Over time, we would like to migrate
>      these services to Apache infrastructure where appropriate.
>    - Our current buildbot master is at
>      http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Richard S. Hall]

+1

-> richard

On 11/4/09 15:50, Felix Meschberger wrote:

> +1
>
> Regards
> Felix
>
> Greg Stein schrieb:
>    
>>   Subversion is a version control system.  You probably know it well as
>> it is the version control system employed by the Apache Software
>> Foundation.
>>
>>   The Subversion project would like to join the Apache Software
>> Foundation to remove the overhead of having to run its own
>> corporation.  The Subversion project is already run quite like an
>> Apache project, and already counts a number of ASF Members amongst
>> its committers.
>>
>>   Work on Subversion was originally started at CollabNet; Karl Fogel
>> was hired in January 2000.  Jim Blandy, at RedHat, already had an
>> initial design for the storage system, which was incorporated into the
>> FS design.  In February Brian Behlendorf invited Greg Stein to
>> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
>> was hired in April 2000 to work on the project.  In that same month
>> the first "all hands" meeting was held, where a number of "interested
>> people" came together to talk about the project.
>>
>>   Subversion was run as an open source project since the early days.
>> Now, more than nine years later, it retains a healthy community,
>> and has a good number of committers.  In the life span of Subversion,
>> several committers have switched employers and have maintained involvement.
>> The committership is diverse, both geographically as well as in terms of
>> employment.
>>
>>   The equivalent of the PMC consists of all the full committers to the
>> Subversion project (currently around 55 people).  The community uses the
>> voting process also used at the ASF.  Releases are signed off by gathering
>> votes/digital signatures of each committer who verified the release
>> candidate.
>>
>>   We feel the ASF and Subversion communities are very compatible,
>> witness the cross interest that already exists. There is both a
>> vibrant developer as well as a large and active user community.
>> Technology-wise, Subversion builds on APR, and implements two Apache
>> HTTP Server modules.
>>
>>   Note that Subversion has a number of related projects, which are not
>> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>>
>>   More information on Subversion can be found at
>> http://www.subversion.org/ and http://subversion.tigris.org/.
>>
>>   The Subversion Corporation has a license to all source code, and has
>> CLAs on file for nearly all it's committers.  That is, we have all but
>> one or two full committers, and some percentage of partial committers.
>>
>>   We have a number of *user-configurable* dependencies which are not
>> compatible with the AL:
>>   - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>>     (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>>      library under ALv2.)
>>
>>   - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
>> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
>> under Academic Free License 2.1 or>=GPL-2.
>>     (This support is for integration for KDE and GNOME's authentication
>>      providers.)
>>
>>   - libintl
>>     (This library provides translation support for systems without
>>      a proper internationalization library.)
>>
>>   - BDB
>>     (This is used by the libsvn_fs_base system which stores its data
>>      in BDB; an alternative repository system called fs_fs does not
>>      have this dependency.)
>>
>> ---
>> Required Resources
>>   - Mailing lists
>>     - dev
>>     - issues
>>     - users
>>     - private
>>     - commits
>>     - announce
>>     - breakage (see
>> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>>     - We will work with the Infrastructure team to transfer the subscriber
>>       listings to the new destinations.
>>   - Subversion:
>>     - We have not made a decision whether we prefer Subversion should be
>>       imported into the main ASF Subversion repository or be hosted as a
>>       separate repository to enable early testing of the repository code.  We
>>       intend to discuss this during the Incubation process before the code is
>>       imported.  It is also understood that ASF infrastructure team may be
>>       willing to run custom pre-release Subversion server builds for the
>>       entire ASF, so this separate repository option may not be required.
>>     - The Subversion source code can be found at:
>>       http://svn.collab.net/repos/svn/.
>>   - Issue tracking
>>     - We haven't made a decision between JIRA or Bugzilla at this time and
>>       expect this decision to be made as part of the Incubation process.  Our
>>       current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>>       we have not yet decided whether we want to import our previous issues
>>       into the new system and will decide this in the course of the Incubation
>>       process.
>>     - Our current issue tracker is at
>>       http://subversion.tigris.org/issue-tracker.html.
>>   - Buildbot
>>     - We currently use buildbot across a number of platforms and configurations
>>       for automated builds and testing.  Over time, we would like to migrate
>>       these services to Apache infrastructure where appropriate.
>>     - Our current buildbot master is at
>>       http://buildbot.subversion.org/buildbot/
>>
>>   Note that we request these resources to be at their final locations,
>> not an intermediary while going through incubation.  The cost of
>> switching twice would otherwise be significant due to the size of the
>> existing community.
>>
>>   The Subversion team members are happy to work with and assist the ASF
>> Infrastructure team to enable early deployments of its release candidates if
>> possible.
>>
>> Initial Committers
>>
>>   The list of initial committers is at
>> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>>
>> The initial PMC members are those listed as full committers in that
>> file (lines 1-74).
>>
>> Sponsors
>>   * Champion: Greg Stein
>>   * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>>   * Sponsor:
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>>
>>      
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Ate Douma]

+1

Ate

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained
> involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>     library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>    (This support is for integration for KDE and GNOME's authentication
>     providers.)
>
>  - libintl
>    (This library provides translation support for systems without
>     a proper internationalization library.)
>
>  - BDB
>    (This is used by the libsvn_fs_base system which stores its data
>     in BDB; an alternative repository system called fs_fs does not
>     have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>    - dev
>    - issues
>    - users
>    - private
>    - commits
>    - announce
>    - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>    - We will work with the Infrastructure team to transfer the subscriber
>      listings to the new destinations.
>  - Subversion:
>    - We have not made a decision whether we prefer Subversion should be
>      imported into the main ASF Subversion repository or be hosted as a
>      separate repository to enable early testing of the repository code.
> We
>      intend to discuss this during the Incubation process before the code
> is
>      imported.  It is also understood that ASF infrastructure team may be
>      willing to run custom pre-release Subversion server builds for the
>      entire ASF, so this separate repository option may not be required.
>    - The Subversion source code can be found at:
>      http://svn.collab.net/repos/svn/.
>  - Issue tracking
>    - We haven't made a decision between JIRA or Bugzilla at this time and
>      expect this decision to be made as part of the Incubation process.
> Our
>      current issue tracking system uses Issuezilla (a fork of Bugzilla)
> and
>      we have not yet decided whether we want to import our previous issues
>      into the new system and will decide this in the course of the
> Incubation
>      process.
>    - Our current issue tracker is at
>      http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>    - We currently use buildbot across a number of platforms and
> configurations
>      for automated builds and testing.  Over time, we would like to
> migrate
>      these services to Apache infrastructure where appropriate.
>    - Our current buildbot master is at
>      http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates
> if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker,
> Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jim Jagielski]

On Nov 4, 2009, at 3:12 PM, Greg Stein wrote:

>
> The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>

Nah -1...


"Bazinga!"  :)

*snicker* *snicker*

Of course, a big +1 !

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Garrett Rooney]

On Wed, Nov 4, 2009 at 3:12 PM, Greg Stein <gstein@...> wrote:
>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.

+1

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Martin Cooper-2]

+1

--
Martin Cooper


On Wed, Nov 4, 2009 at 12:12 PM, Greg Stein <gstein@...> wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>    library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>   (This support is for integration for KDE and GNOME's authentication
>    providers.)
>
>  - libintl
>   (This library provides translation support for systems without
>    a proper internationalization library.)
>
>  - BDB
>   (This is used by the libsvn_fs_base system which stores its data
>    in BDB; an alternative repository system called fs_fs does not
>    have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>   - dev
>   - issues
>   - users
>   - private
>   - commits
>   - announce
>   - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>   - We will work with the Infrastructure team to transfer the subscriber
>     listings to the new destinations.
>  - Subversion:
>   - We have not made a decision whether we prefer Subversion should be
>     imported into the main ASF Subversion repository or be hosted as a
>     separate repository to enable early testing of the repository code.  We
>     intend to discuss this during the Incubation process before the code is
>     imported.  It is also understood that ASF infrastructure team may be
>     willing to run custom pre-release Subversion server builds for the
>     entire ASF, so this separate repository option may not be required.
>   - The Subversion source code can be found at:
>     http://svn.collab.net/repos/svn/.
>  - Issue tracking
>   - We haven't made a decision between JIRA or Bugzilla at this time and
>     expect this decision to be made as part of the Incubation process.  Our
>     current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>     we have not yet decided whether we want to import our previous issues
>     into the new system and will decide this in the course of the Incubation
>     process.
>   - Our current issue tracker is at
>     http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>   - We currently use buildbot across a number of platforms and configurations
>     for automated builds and testing.  Over time, we would like to migrate
>     these services to Apache infrastructure where appropriate.
>   - Our current buildbot master is at
>     http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[jaaronfarr]

On Wed 04 Nov 2009 12:12, Greg Stein <gstein@...> wrote:

> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:

Quite a collection of shady characters, but... +1

:-)

--
   J. Aaron Farr
   馮傑仁
   www.cubiclemuses.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[mnour]

Big +1 :)

On Wed, Nov 4, 2009 at 11:06 PM, J Aaron Farr <farra@...> wrote:

>
> On Wed 04 Nov 2009 12:12, Greg Stein <gstein@...> wrote:
>
>> Initial Committers
>>
>>  The list of initial committers is at
>> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>>
>> The initial PMC members are those listed as full committers in that
>> file (lines 1-74).
>>
>> Sponsors
>>  * Champion: Greg Stein
>>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>>  * Sponsor:
>
> Quite a collection of shady characters, but... +1
>
> :-)
>
> --
>   J. Aaron Farr
>   馮傑仁
>   www.cubiclemuses.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
Thanks
- Mohammad Nour
- LinkedIn: http://www.linkedin.com/in/mnour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Alexey Petrenko]

+1

2009/11/4 Greg Stein <gstein@...>:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>    library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>   (This support is for integration for KDE and GNOME's authentication
>    providers.)
>
>  - libintl
>   (This library provides translation support for systems without
>    a proper internationalization library.)
>
>  - BDB
>   (This is used by the libsvn_fs_base system which stores its data
>    in BDB; an alternative repository system called fs_fs does not
>    have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>   - dev
>   - issues
>   - users
>   - private
>   - commits
>   - announce
>   - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>   - We will work with the Infrastructure team to transfer the subscriber
>     listings to the new destinations.
>  - Subversion:
>   - We have not made a decision whether we prefer Subversion should be
>     imported into the main ASF Subversion repository or be hosted as a
>     separate repository to enable early testing of the repository code.  We
>     intend to discuss this during the Incubation process before the code is
>     imported.  It is also understood that ASF infrastructure team may be
>     willing to run custom pre-release Subversion server builds for the
>     entire ASF, so this separate repository option may not be required.
>   - The Subversion source code can be found at:
>     http://svn.collab.net/repos/svn/.
>  - Issue tracking
>   - We haven't made a decision between JIRA or Bugzilla at this time and
>     expect this decision to be made as part of the Incubation process.  Our
>     current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>     we have not yet decided whether we want to import our previous issues
>     into the new system and will decide this in the course of the Incubation
>     process.
>   - Our current issue tracker is at
>     http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>   - We currently use buildbot across a number of platforms and configurations
>     for automated builds and testing.  Over time, we would like to migrate
>     these services to Apache infrastructure where appropriate.
>   - Our current buildbot master is at
>     http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jean-frederic Clere-3]

On 11/04/2009 09:12 PM, Greg Stein wrote:

>   Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>   The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>

+1

Cheers

Jean-Frederic

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Bill Stoddard-3]

+1

Bill

Greg Stein wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>     library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>    (This support is for integration for KDE and GNOME's authentication
>     providers.)
>
>  - libintl
>    (This library provides translation support for systems without
>     a proper internationalization library.)
>
>  - BDB
>    (This is used by the libsvn_fs_base system which stores its data
>     in BDB; an alternative repository system called fs_fs does not
>     have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>    - dev
>    - issues
>    - users
>    - private
>    - commits
>    - announce
>    - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>    - We will work with the Infrastructure team to transfer the subscriber
>      listings to the new destinations.
>  - Subversion:
>    - We have not made a decision whether we prefer Subversion should be
>      imported into the main ASF Subversion repository or be hosted as a
>      separate repository to enable early testing of the repository code.  We
>      intend to discuss this during the Incubation process before the code is
>      imported.  It is also understood that ASF infrastructure team may be
>      willing to run custom pre-release Subversion server builds for the
>      entire ASF, so this separate repository option may not be required.
>    - The Subversion source code can be found at:
>      http://svn.collab.net/repos/svn/.
>  - Issue tracking
>    - We haven't made a decision between JIRA or Bugzilla at this time and
>      expect this decision to be made as part of the Incubation process.  Our
>      current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>      we have not yet decided whether we want to import our previous issues
>      into the new system and will decide this in the course of the Incubation
>      process.
>    - Our current issue tracker is at
>      http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>    - We currently use buildbot across a number of platforms and configurations
>      for automated builds and testing.  Over time, we would like to migrate
>      these services to Apache infrastructure where appropriate.
>    - Our current buildbot master is at
>      http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jean T. Anderson]

+1

 -jean

Greg Stein wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>     library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>    (This support is for integration for KDE and GNOME's authentication
>     providers.)
>
>  - libintl
>    (This library provides translation support for systems without
>     a proper internationalization library.)
>
>  - BDB
>    (This is used by the libsvn_fs_base system which stores its data
>     in BDB; an alternative repository system called fs_fs does not
>     have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>    - dev
>    - issues
>    - users
>    - private
>    - commits
>    - announce
>    - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>    - We will work with the Infrastructure team to transfer the subscriber
>      listings to the new destinations.
>  - Subversion:
>    - We have not made a decision whether we prefer Subversion should be
>      imported into the main ASF Subversion repository or be hosted as a
>      separate repository to enable early testing of the repository code.  We
>      intend to discuss this during the Incubation process before the code is
>      imported.  It is also understood that ASF infrastructure team may be
>      willing to run custom pre-release Subversion server builds for the
>      entire ASF, so this separate repository option may not be required.
>    - The Subversion source code can be found at:
>      http://svn.collab.net/repos/svn/.
>  - Issue tracking
>    - We haven't made a decision between JIRA or Bugzilla at this time and
>      expect this decision to be made as part of the Incubation process.  Our
>      current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>      we have not yet decided whether we want to import our previous issues
>      into the new system and will decide this in the course of the Incubation
>      process.
>    - Our current issue tracker is at
>      http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>    - We currently use buildbot across a number of platforms and configurations
>      for automated builds and testing.  Over time, we would like to migrate
>      these services to Apache infrastructure where appropriate.
>    - Our current buildbot master is at
>      http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Emmanuel Lecharny]

+1

Greg Stein wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>    (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>     library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>    (This support is for integration for KDE and GNOME's authentication
>     providers.)
>
>  - libintl
>    (This library provides translation support for systems without
>     a proper internationalization library.)
>
>  - BDB
>    (This is used by the libsvn_fs_base system which stores its data
>     in BDB; an alternative repository system called fs_fs does not
>     have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>    - dev
>    - issues
>    - users
>    - private
>    - commits
>    - announce
>    - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>    - We will work with the Infrastructure team to transfer the subscriber
>      listings to the new destinations.
>  - Subversion:
>    - We have not made a decision whether we prefer Subversion should be
>      imported into the main ASF Subversion repository or be hosted as a
>      separate repository to enable early testing of the repository code.  We
>      intend to discuss this during the Incubation process before the code is
>      imported.  It is also understood that ASF infrastructure team may be
>      willing to run custom pre-release Subversion server builds for the
>      entire ASF, so this separate repository option may not be required.
>    - The Subversion source code can be found at:
>      http://svn.collab.net/repos/svn/.
>  - Issue tracking
>    - We haven't made a decision between JIRA or Bugzilla at this time and
>      expect this decision to be made as part of the Incubation process.  Our
>      current issue tracking system uses Issuezilla (a fork of Bugzilla) and
>      we have not yet decided whether we want to import our previous issues
>      into the new system and will decide this in the course of the Incubation
>      process.
>    - Our current issue tracker is at
>      http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>    - We currently use buildbot across a number of platforms and configurations
>      for automated builds and testing.  Over time, we would like to migrate
>      these services to Apache infrastructure where appropriate.
>    - Our current buildbot master is at
>      http://buildbot.subversion.org/buildbot/
>
>  Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
>  The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release candidates if
> possible.
>
> Initial Committers
>
>  The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall
>  * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>
>  

--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[brettporter]

+1

On 04/11/2009, at 12:12 PM, Greg Stein wrote:

> Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
> The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
> Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
> Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained  
> involvement.
> The committership is diverse, both geographically as well as in  
> terms of
> employment.
>
> The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses  
> the
> voting process also used at the ASF.  Releases are signed off by  
> gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
> We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
> Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
> More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
> The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
> We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
> - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>    library under ALv2.)
>
> - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>   (This support is for integration for KDE and GNOME's authentication
>    providers.)
>
> - libintl
>   (This library provides translation support for systems without
>    a proper internationalization library.)
>
> - BDB
>   (This is used by the libsvn_fs_base system which stores its data
>    in BDB; an alternative repository system called fs_fs does not
>    have this dependency.)
>
> ---
> Required Resources
> - Mailing lists
>   - dev
>   - issues
>   - users
>   - private
>   - commits
>   - announce
>   - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>   - We will work with the Infrastructure team to transfer the  
> subscriber
>     listings to the new destinations.
> - Subversion:
>   - We have not made a decision whether we prefer Subversion should be
>     imported into the main ASF Subversion repository or be hosted as a
>     separate repository to enable early testing of the repository  
> code.  We
>     intend to discuss this during the Incubation process before the  
> code is
>     imported.  It is also understood that ASF infrastructure team  
> may be
>     willing to run custom pre-release Subversion server builds for the
>     entire ASF, so this separate repository option may not be  
> required.
>   - The Subversion source code can be found at:
>     http://svn.collab.net/repos/svn/.
> - Issue tracking
>   - We haven't made a decision between JIRA or Bugzilla at this time  
> and
>     expect this decision to be made as part of the Incubation  
> process.  Our
>     current issue tracking system uses Issuezilla (a fork of  
> Bugzilla) and
>     we have not yet decided whether we want to import our previous  
> issues
>     into the new system and will decide this in the course of the  
> Incubation
>     process.
>   - Our current issue tracker is at
>     http://subversion.tigris.org/issue-tracker.html.
> - Buildbot
>   - We currently use buildbot across a number of platforms and  
> configurations
>     for automated builds and testing.  Over time, we would like to  
> migrate
>     these services to Apache infrastructure where appropriate.
>   - Our current buildbot master is at
>     http://buildbot.subversion.org/buildbot/
>
> Note that we request these resources to be at their final locations,
> not an intermediary while going through incubation.  The cost of
> switching twice would otherwise be significant due to the size of the
> existing community.
>
> The Subversion team members are happy to work with and assist the ASF
> Infrastructure team to enable early deployments of its release  
> candidates if
> possible.
>
> Initial Committers
>
> The list of initial committers is at
> http://svn.collab.net/repos/svn/trunk/COMMITTERS.
>
> The initial PMC members are those listed as full committers in that
> file (lines 1-74).
>
> Sponsors
> * Champion: Greg Stein
> * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker,  
> Daniel Rall
> * Sponsor:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Justin Erenkrantz]

On Wed, Nov 4, 2009 at 12:12 PM, Greg Stein <gstein@...> wrote:
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
> Sponsors
>  * Champion: Greg Stein
>  * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall

+1 for acceptance.

w...0...0...t.  =)  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Philip M. Gollucci]

Justin Erenkrantz wrote:
> On Wed, Nov 4, 2009 at 12:12 PM, Greg Stein <gstein@...> wrote:
>>  The Subversion project would like to join the Apache Software
>> Foundation to remove the overhead of having to run its own
>> corporation.  The Subversion project is already run quite like an
>> Apache project, and already counts a number of ASF Members amongst
>> its committers.
+1


--
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci@...) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer,                        FreeBSD Foundation
Sr. System Admin,                 Ridecharge Inc.
Consultant,                       P6M7G8 Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...