Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=AqdzulSlRExT8Nw6MHikAsIvUq9MFhkl7YWVsm8U2zfNDzI0fKeZ2dxrd+1KBCOkW9VU8vYPNeyp9PsveGrQ+hIaqr/yfj09tLx7+91lzC8EKqOB26ftAvNeAcdh/lfz20zXMtw05aXeO8nXpJOXZKCsBMk50TT5Ub+5YQmf1/k=;
References: 
 <CAJjMeYNPPVT4sBOUo3VcUq8c=d1aP5hurWP+w7yq1mNckfH4xw@mail.gmail.com>
Message-ID: <1322842442.30546.YahooMailNeo@web27806.mail.ukl.yahoo.com>
Date: Fri, 2 Dec 2011 16:14:02 +0000 (GMT)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: [PROPOSAL] Apache Bloodhound
To: "general@incubator.apache.org" <general@incubator.apache.org>
Cc: Ian Wild <ian.wild@wandisco.com>, Greg Stein <gstein@gmail.com>
In-Reply-To: 
 <CAJjMeYNPPVT4sBOUo3VcUq8c=d1aP5hurWP+w7yq1mNckfH4xw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

so this is basically Trac ++ and a fork of Trac ?=0A=0AOr is it a completel=
y rewritten new approach?=0A=0Ajust curious :)=0A=0A=0ALieGrue,=0Astrub=0A=
=0A=0A=0A----- Original Message -----=0A> From: Hyrum K Wright <hyrum.wrigh=
t@wandisco.com>=0A> To: general@incubator.apache.org=0A> Cc: Ian Wild <ian.=
wild@wandisco.com>; Greg Stein <gstein@gmail.com>=0A> Sent: Friday, Decembe=
r 2, 2011 4:53 PM=0A> Subject: [PROPOSAL] Apache Bloodhound=0A> =0A> Hello =
Incubator!=0A> =0A> WANdisco would like to propose the inclusion of a new p=
roject, Apache=0A> Bloodhound, to the Incubator.=C2=A0 The proposal has bee=
n posted to the=0A> wiki[1], and is also included below.=C2=A0 We've privat=
ely discussed this=0A> project with a number of individuals, but would now =
like to get the=0A> discussion rolling here.=C2=A0 Bloodhound is new effort=
, based on Trac[2],=0A> to provide issue tracking and collaboration tools f=
or developers.=0A> =0A> We realize the proposal is a work-in-progress, and =
as such look=0A> forward to feedback and discussion.=C2=A0 We hope to attra=
ct mentors and=0A> other interested parties through the incubation proposal=
 process, and=0A> further diversify the community as we move through incuba=
tion.=C2=A0 In=0A> particular, this project is an opportunity to build a ne=
w community=0A> around the codebase, and we look forward to doing so at the=
 ASF.=0A> =0A> -Hyrum=0A> =0A> [1]=C2=A0http://wiki.apache.org/incubator/Bl=
oodhoundProposal=0A> [2] http://trac.edgewall.org/=0A> =0A> =0A> =3D Bloodh=
ound - Collaborative development tools based on Trac =3D=0A> =0A> =3D=3D Ab=
stract =3D=3D=0A> =0A> Bloodhound will be a software development collaborat=
ion tool,=0A> including issue tracking, wiki and repository browsing.=C2=A0=
 Essentially=0A> an improved distribution of the well-known Trac project, B=
loodhound=0A> will include the common and useful plugins to enable a more c=
omplete=0A> distribution than a typical Trac installation.=0A> =0A> =3D=3D =
Proposal =3D=3D=0A> =0A> Bloodhound will be a software development collabor=
ation tool, based on=0A> the existing Trac project, which will include a re=
pository browser,=0A> wiki, and defect tracker.=C2=A0 In addition to the st=
andard Trac=0A> installation, Bloodhound will incorporate a number of popul=
ar modules=0A> into the core distribution, and include additional improveme=
nts=0A> developed (as [[http://trac-hacks.org/|plugins]]) outside the Trac=
=0A> project.=0A> =0A> =3D=3D Background =3D=3D=0A> =0A> The [[http://trac.=
edgewall.org/|Trac project]] is a BSD-licensed=0A> collaboration tool used =
to assist in software development.=C2=A0 It has a=0A> wide user base, a plu=
ggable infrastructure, and is generally=0A> considered stable.=0A> =0A> By =
it's own recognition, however, the development community=0A> surrounding Tr=
ac has largely dissipated, with little mailing list=0A> traffic, and very f=
ew commits to the source code repository (see [2]).=0A> Private efforts to =
engage the existing developers in implementing=0A> features have been negat=
ively received.=C2=A0 At the same time, other=0A> individuals and companies=
, such as=0A> [[http://www.wandisco.com|WANdisco]], have expressed interest=
 in=0A> helping continue to develop Trac.=C2=A0 These entities would prefer=
 this=0A> effort to be at a vendor-neutral location, with the clear process=
 for=0A> intellectual property management that comes from the Foundation.=
=C2=A0 As=0A> such, the Apache Software Foundation feels like the best fit =
for this=0A> new project based on Trac.=0A> =0A> =3D=3D Rationale =3D=3D=0A=
> =0A> As discussed earlier, the current Trac development community is smal=
l=0A> and reluctant to accept outside contributions.=C2=A0 Given the Founda=
tion=E2=80=99s=0A> reputation for building and maintaining communities, we =
feel a new=0A> project, based on Trac but incubated under the Apache umbrel=
la, would=0A> help re-build the developer community, jump started by develo=
per time=0A> donated by WANdisco.=C2=A0 Additionally, as a developer tool, =
Bloodhound is=0A> a good fit with other, similarly-focused developer tools =
at the ASF.=0A> =0A> Private discussions have shown there is some interest =
by third-parties=0A> to release internal improvements to Trac, and Bloodhou=
nd gives them an=0A> additional venue to do so.=0A> =0A> =3D=3D Initial Goa=
ls =3D=3D=0A> =0A> The initial goals for Bloodhound primarily revolve aroun=
d migrating=0A> the existing code base and integrating external features to=
 make the=0A> project easy to deploy.=C2=A0 Additional ideas will of course=
 follow, but=0A> the following goals are sufficiently difficult to be consi=
dered early=0A> milestones.=0A> =0A> Some of the initial goals include:=0A>=
 * Migrate the existing BSD-licensed Trac code base to the ASF.=0A> * Attra=
ct developer and user interest in the new Bloodhound project.=0A> * Incorpo=
rate externally developed features into the core Bloodhound project.=0A> * =
Package the most popular plugins into the core project, so=0A> installation=
s and administration of Bloodhound becomes dead simple.=0A> =0A> =0A> =3D C=
urrent Status =3D=0A> =0A> =3D=3D Meritocracy =3D=3D=0A> =0A> Although init=
ially corporate-sponsored, any interested developers=0A> would be granted c=
ommit access.=C2=A0 Even developers employed by the=0A> sponsoring companie=
s would be required to demonstrate competency to=0A> gain commit privileges=
.=C2=A0 Individuals with corporate affiliations would=0A> understandably be=
 known within the community, but would not have=0A> bearing on the granting=
 of commit privileges.=0A> =0A> =3D=3D Community =3D=3D=0A> =0A> One of the=
 primary purposes of this proposal is to develop a strong=0A> developer com=
munity around the Trac code base.=C2=A0 The current developers=0A> and supp=
orting institution have moved on to other things, and this has=0A> caused s=
tagnation in the existing community.=C2=A0 We want to use the=0A> experienc=
e of the Incubator PMC, and the incubation process, to reboot=0A> the devel=
oper community, while at the same time incorporating=0A> oft-requested feat=
ures into the existing product.=0A> =0A> Building communities carries with =
it an initial investment, and the=0A> corporate sponsors behind this propos=
al are willing to make that=0A> investment in seeing a vibrant and self-sus=
taining community result=0A> from incubation.=C2=A0 We recognize this as so=
mething of an experiment, and=0A> that incubation is not a guarantee of suc=
cess and graduation a given.=0A> However, we feel that the ASF represents t=
he best opportunity to build=0A> the vibrant community that this project ne=
eds.=0A> =0A> =3D=3D Core Developers =3D=3D=0A> =0A> The initial set of dev=
elopers will be primarily individuals from=0A> WANdisco, and may be augment=
ed with other interested persons we have=0A> privately contacted.=C2=A0 Thi=
s list contains at least one Apache Member,=0A> as well as others who have =
participated in Apache projects in various=0A> capacities (patch contributo=
rs, bug reports, etc.).=C2=A0 It also includes=0A> people who are familiar =
with open source development, but have not=0A> previously participated in A=
pache projects.=0A> =0A> Realizing that incubation is an opportunity to gro=
w the community, we=0A> plan to make every attempt possible to invite addit=
ional developers=0A> from the existing Trac user and developer communities,=
 including those=0A> involved in plugin development.=0A> =0A> =3D=3D Alignm=
ent =3D=3D=0A> =0A> Bloodhound aligns well with the Apache Software Foundat=
ion.=C2=A0 It makes=0A> extensive use of Apache Subversion, and includes to=
ols to browse and=0A> interact with Subversion repositories.=C2=A0 As previ=
ously mentioned,=0A> Bloodhound is primarily a developer-oriented tool, whi=
ch follows the=0A> historical Apache philosophy of providing high-quality d=
eveloper=0A> tools.=C2=A0 Eventually, Bloodhound could become a viable alte=
rnative to=0A> Jira or Bugzilla for projects hosted at Apache.=0A> =0A> =3D=
 Known Risks =3D=0A> =0A> This proposal is not without its risks, some of w=
hich are outlined below.=0A> =0A> =3D=3D Orphaned Projects =3D=3D=0A> =0A> =
The current Trac project lacks much developer interest.=C2=A0 Although the=
=0A> entities behind this proposal desire to make a viable developer=0A> co=
mmunity, there is no guarantee that such a community will develop.=0A> Shou=
ld this happen, there will likely be insufficient heterogeneity in=0A> the =
project to warrant graduation.=0A> =0A> =3D=3D Inexperience with Open Sourc=
e =3D=3D=0A> =0A> The initial groups of developers have extensive experienc=
e with open=0A> source, primarily with the [[http://subversion.apache.org/|=
Apache=0A> Subversion]] project.=C2=A0 The target audience for growing the =
developer=0A> community is the current Trac user and developer communities,=
 many=0A> members of which are familiar with open source in general.=C2=A0 =
There may=0A> be some learning curve as community members familiarize thems=
elves=0A> with the ASF and the Apache Way, including individuals employed=
=0A> specifically to work on the project.=0A> =0A> =3D=3D Homogeneous Devel=
opers =3D=3D=0A> =0A> The current list of committers are primarily from WAN=
disco.=C2=A0 One of=0A> the key purposes of proposing Bloodhound for incuba=
tion is to=0A> resurrect a currently-small (~3 key developers, but very few=
 commits=0A> per week) development community by attracting and infusing it =
with new=0A> code and new individuals.=C2=A0 The ASF has a well-deserved re=
putation of=0A> fostering and building open source communities, which makes=
 it the=0A> ideal location to attempt this community reboot.=0A> =0A> =3D=
=3D Reliance on Salaried Developers =3D=3D=0A> =0A> Most of the initial com=
mitters are supported by their employers to=0A> work on Bloodhound, and may=
 be assigned to work on other projects in=0A> the future.=C2=A0 However, th=
e employers of these salaried individuals have=0A> an interest in seeing Bl=
oodhound thrive as a long-term, sustaining=0A> project.=C2=A0 WANdisco unde=
rstands that their employees are acting as=0A> individuals when contributin=
g to Apache projects, but has already=0A> brought additional staff on board=
 to assist with Bloodhound=0A> development.=0A> =0A> =3D=3D Relationship wi=
th Other Apache Projects =3D=3D=0A> =0A> Bloodhound integrates heavily with=
 Apache Subversion, although that=0A> integration is becoming more de-coupl=
ed making it possible to replace=0A> with other version control systems. Bl=
oodhound optionally runs on=0A> Apache httpd.=0A> =0A> =3D=3D An Excessive =
Fascination with the Apache Brand =3D=3D=0A> =0A> One of the primary motiva=
tors in creating the Bloodhound project as=0A> part of the Incubator is to =
leverage the vendor-neutral nature of the=0A> Apache Software Foundation.=
=C2=A0 The ASF has a strong and recognized brand=0A> as being a leader in o=
pen source, and by hosting Bloodhound at the=0A> Foundation, we hope to att=
ract developers to build a viable community=0A> for the project.=0A> =0A> =
=3D Initial Source =3D=0A> =0A> The original Trac code base has been under =
development for more than 8=0A> years, though development has become minima=
l over the past 2 years.=0A> We have sync'd the existing Trac repository, i=
ncluding history, and=0A> are using it as the basis for Bloodhound.=C2=A0 W=
e also plan to incorporate=0A> appropriately-licensed plugins into the core=
 Bloodhound system.=0A> =0A> =3D=3D Source and Intellectual Property Submis=
sion Plan =3D=3D=0A> =0A> The initial source will be from the Trac reposito=
ry.=C2=A0 Additional=0A> functionality may come from private development, a=
nd will be folded=0A> into the open source version after Bloodhound is load=
ed in the main=0A> ASF repository.=C2=A0 Any relevant Trac-hacks with appro=
priate licenses may=0A> also be migrated.=0A> =0A> =3D=3D External Dependen=
cies =3D=3D=0A> =0A> The bulk of the initial code will be from the Trac pro=
ject, which is=0A> licensed under the BSD license.=C2=A0 Bloodhound also re=
lies upon=0A> BSD-licensed subcomponents for HTML templating.=0A> =0A> =3D =
Required Resources =3D=0A> =0A> =3D=3D Mailing lists =3D=3D=0A> =0A> The in=
itial set of mailing lists will be:=0A> * bloodhound-private (with moderate=
d subscriptions)=0A> * bloodhound-dev=0A> * bloodhound-commits=0A> * bloodh=
ound-user=0A> =0A> =3D=3D Subversion Directory =3D=3D=0A> =0A> https://svn.=
apache.org/repos/asf/incubator/bloodhound=0A> =0A> =3D=3D Issue Tracking =
=3D=3D=0A> =0A> Bloodhound would like to self-host its issue tracking, see =
below.=0A> =0A> =3D=3D Other Resources =3D=3D=0A> =0A> In the interests of =
eating our own dogfood, Bloodhound would like to=0A> self-host the issue tr=
acker and related tools. The team will work with=0A> Infrastructure to defi=
ne and manage this configuration.=0A> =0A> =3D=3D Initial Committers =3D=3D=
=0A> =0A> * Mat Booth (mat.booth at wandisco dot com)=0A> * Mark Poole (mar=
k at wandisco.com)=0A> * Hyrum Wright (hyrum.wright at wandisco dot com)=0A=
> * John Chambers (john.chambers at wandisco.com)=0A> * Gary Martin (gary.m=
artin at wandisco.com)=0A> =0A> =3D=3D Affiliations =3D=3D=0A> =0A> * Mat B=
ooth, WANdisco=0A> * Mark Poole, WANdisco=0A> * Hyrum Wright, WANdisco=0A> =
* John Chambers, WANdisco=0A> * Gary Martin, WANdisco=0A> =0A> =3D Sponsors=
 =3D=0A> =0A> =3D=3D Champion =3D=3D=0A> =0A> Hyrum Wright=0A> =0A> =3D=3D =
Nominated Mentors =3D=3D=0A> =0A> * Hyrum Wright=0A> * Greg Stein=0A> =0A> =
=3D=3D Sponsoring Entity =3D=3D=0A> =0A> The Apache Incubator=0A> =0A> ----=
-----------------------------------------------------------------=0A> To un=
subscribe, e-mail: general-unsubscribe@incubator.apache.org=0A> For additio=
nal commands, e-mail: general-help@incubator.apache.org=0A> 

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