On Tue, Apr 15, 2008 at 11:38 AM, Noel J. Bergman <email@example.com
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
> > 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
> > files. This would need a bit of shell scripting, probably tied into the
> > 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 weNo kidding! I'd really like to see a project objectclass, too. Especially
> really need to handle. And there are a lot of them, in different files
> and different formats !
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.