Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: <1965206.FEU36pkKXm@herve-desktop>
References: <3948386.N74mUlsXhp@herve-desktop>
	<CAOGo0VZVr1LPV_Y6arczp-Tt83XKpy+J2HqraSMrJKN64Yo1mg@mail.gmail.com>
	<1965206.FEU36pkKXm@herve-desktop>
Date: Sat, 16 May 2015 00:36:03 +0100
Message-ID: 
 <CAOGo0VbHPCaQjj0b3TTagVrWyJg9EnJ49oXOaPCwXM5ESmuenQ@mail.gmail.com>
Subject: Re: projects-new.a.o updates
From: sebb <sebbaz@gmail.com>
To: dev@community.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 15 May 2015 at 22:08, Herv=C3=A9 BOUTEMY <herve.boutemy@free.fr> wrote:
> Le vendredi 15 mai 2015 14:02:52 sebb a =C3=A9crit :
>> On 14 May 2015 at 23:38, Herv=C3=A9 BOUTEMY <herve.boutemy@free.fr> wrot=
e:
>> > Hi,
>> >
>> > I seriously updated content:
>> > - *every* TLP is listed, even when no DOAP file has been written [1]
>> > - TLP project can be displayed, even without DOAP and provide link to
>> > every
>> > sub-project [2]
>> > - when a TLP has a "main sub-project" with its DOAP file, data from TL=
P
>> > and
>> > data from DOAP subproject are clearly separate [3]
>>
>> The URLs [1] [2] [3] use the same namespace for PMCs and projects as
>> well as generic queries.
>> This may cause name clashes in future - e.g. a PMC called "numbers"
>> would clash with the "numbers" view of the data.
> not exactly: [1] is project*s*.html while the 2 others are project.html
> so no clash between projects listing type and project/PMC

Ah, OK, I'd not noticed the subtle difference.

However there is still a potential name clash: the Ant PMC is not the
same as the Ant project produced by the Ant PMC.

>> It would be better to use distinct namespaces for distinct types of item=
.
> I don't think a clash between a PMC and a project can happen: if they hav=
e the
> same id, it should be TLP's PMC, isn't it?

No, they are not the same thing.
A project is not a PMC, though they may have the same name.

A PMC is a group of people; a project is a software artifact.

>>
>> > This makes more clear what DOAP is used for (and why we need projects
>> > hand-
>> > writing some data, but not everything)
>> >
>> > I didn't update target doap urls [4] since I don't know what precisely=
 to
>> > do: copy doap files that were processed, in appropriate directory, and
>> > with consistent filename than generated json?
>>
>> What are the target DOAP files used for?
> I don't know: I coded what I understood from discussion with Sergio Fern=
=C3=A1ndez
> But I admit I don't really know if this is a good idea or not
>
>> Where do they originate?
> {tlp-id}/pmc.rdf is generated with info parsed from committee-info.txt by
> http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/pa=
rsecommittees.py?view=3Dmarkup
> (with the help of http://www.apache.org/#projects-list scraped info for s=
hort
> description)
>
> And the idea behind rdf copy was just to copy files in a uniform location=
 from
> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects=
/files.xml to ease DOAP finding
> just an idea
>
> Regards,
>
> Herv=C3=A9
>
>>
>> > Feedback expected :)
>> >
>> > Regards,
>> >
>> > Herv=C3=A9
>> >
>> >
>> > [1] https://projects-new.apache.org/projects.html?pmc
>> >
>> > [2] https://projects-new.apache.org/project.html?commons
>> >
>> > [3] https://projects-new.apache.org/project.html?ant
>> >
>> > [4] https://projects-new.apache.org/doap/
>