[ 
https://issues.apache.org/jira/browse/OOZIE-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135204#comment-14135204
 ] 

Sebb commented on OOZIE-1795:
-----------------------------

bq. No. The current setting is fine, and means that the DOAP is stored at
Sorry, my comment above was misleading.

There are actually two RDF files involved.
One for the PMC, and one for each project overseen by the PMC.

The project DOAP points to the PMC RDF, which has already been created for you 
in
{{http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/oozie.rdf}}

This can indeed have a list of the PMC members.
If the PMC wishes to maintain this then it may be easier to move it to an Oozie 
repo and change the link to it.
But note that there are other sources of info about the PMC membership:
http://people.apache.org/committers-by-project.html#oozie-pmc
and
https://svn.apache.org/repos/private/committers/board/committee-info.txt (*)
These are also published via whimsy:
https://whimsy.apache.org/roster/committee/oozie (*)

(*) ASF committer login required

> Please create a DOAP file for your TLP
> --------------------------------------
>
>                 Key: OOZIE-1795
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1795
>             Project: Oozie
>          Issue Type: Task
>            Reporter: Sebb
>            Assignee: Rohini Palaniswamy
>         Attachments: OOZIE-1795-1.patch
>
>
> As per my recent e-mail to your dev list, please can you set up a DOAP for 
> your project and get it added to files.xml?
> Please see http://projects.apache.org/create.html
> Once you have created the DOAP and committed it to your source code 
> repository, please submit it for inclusion in the Apache projects listing as 
> per:
> http://projects.apache.org/create.html#submit
> Remember, if you ever move or rename the doap file in future, please
> ensure that files.xml is updated to point to the new location.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to