Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 209.85.198.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=hXF2qmtdE/aAuuQw8e4Qfh6EZ7Y1i+zgtNXVGmKsV+J8Y4s5bYVerV4LTSQyA1cq4s/QA4cj2tUrOIlLElnQe/RbnT6B8OHRSjL0zhNEGnJ9emi2Ghjqsw9HIP0goPorEy6V9kvhsxFsYNjxlf9V5cifyF8h70XV71n6STHCB1M=
Message-ID: <a32f6b020804151135md8f0053m5cc356d6773ec7dd@mail.gmail.com>
Date: Tue, 15 Apr 2008 14:35:24 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: ApacheDS for ASF
In-Reply-To: <NBBBJGEAGJAKLIDBKJOPIEIHDOAD.noel@devtech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2863_6704203.1208284529768"
References: <d45b08f00804121001x9db78b1u6b970a875fdd7df4@mail.gmail.com>
	 <NBBBJGEAGJAKLIDBKJOPIEIHDOAD.noel@devtech.com>

------=_Part_2863_6704203.1208284529768
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, Apr 15, 2008 at 11:38 AM, Noel J. Bergman <noel@devtech.com> wrote:

> Emmanuel Lecharny wrote:
>
> > Graham Leggett wrote:
>
> > > This brings a discussion as to where the "authoritative" source of
> data
> > > lies. Right now today that authoritative source is svn, and I also
> imagine
> > > people would want this to stay that way for some time. As a result,
> our
> > > first task would be to synchronise LDAP with the various members.txt
> (etc)
> > > files. This would need a bit of shell scripting, probably tied into
> the
> svn
> > > server so the synchronise is triggered on commit.
> > This is where the Use-Case descriptions are needed : they will exhibit
> > the data we will manipulate, plus the workflow we have to follow.
>
> > > This brings a potential ASF schema into the picture.
> > > objectclass: asfMember
> > > objectclass: asfCommitter
>
> > This has to be discussed, but we first have to analyze what data we
> > really need to handle. And there are a lot of them, in different files
> > and different formats !
>
> No kidding!  I'd really like to see a project objectclass, too.
>  Especially
> for some of the things that we have in the Incubator.  The redundant
> meta-data is really hurting.  I want one canonical definition of a
> project,
> including reporting dates, PMC members, Committers, etc.


Right and we can leverage DOAP files for most of this information I think.
Importing it into an Apache Project schema will be trivial.

Alex

------=_Part_2863_6704203.1208284529768
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><div class="gmail_quote">On Tue, Apr 15, 2008 at 11:38 AM, Noel J. Bergman &lt;<a href="mailto:noel@devtech.com">noel@devtech.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Emmanuel Lecharny wrote:<br>
<div class="Ih2E3d"><br>
&gt; Graham Leggett wrote:<br>
<br>
&gt; &gt; This brings a discussion as to where the &quot;authoritative&quot; source of data<br>
&gt; &gt; lies. Right now today that authoritative source is svn, and I also<br>
imagine<br>
&gt; &gt; people would want this to stay that way for some time. As a result, our<br>
&gt; &gt; first task would be to synchronise LDAP with the various members.txt<br>
(etc)<br>
&gt; &gt; files. This would need a bit of shell scripting, probably tied into the<br>
svn<br>
&gt; &gt; server so the synchronise is triggered on commit.<br>
&gt; This is where the Use-Case descriptions are needed : they will exhibit<br>
&gt; the data we will manipulate, plus the workflow we have to follow.<br>
<br>
</div><div class="Ih2E3d">&gt; &gt; This brings a potential ASF schema into the picture.<br>
&gt; &gt; objectclass: asfMember<br>
&gt; &gt; objectclass: asfCommitter<br>
<br>
</div><div class="Ih2E3d">&gt; This has to be discussed, but we first have to analyze what data we<br>
&gt; really need to handle. And there are a lot of them, in different files<br>
&gt; and different formats !<br>
<br>
</div>No kidding! &nbsp;I&#39;d really like to see a project objectclass, too. &nbsp;Especially<br>
for some of the things that we have in the Incubator. &nbsp;The redundant<br>
meta-data is really hurting. &nbsp;I want one canonical definition of a project,<br>
including reporting dates, PMC members, Committers, etc.</blockquote><div>&nbsp;<br>Right and we can leverage DOAP files for most of this information I think.&nbsp; Importing it into an Apache Project schema will be trivial.<br><br>
Alex<br></div></div>

------=_Part_2863_6704203.1208284529768--