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

Sebb commented on MRM-1891:
---------------------------

In which case, perhaps it would be clearer to use the more specific SVN URIs 
for the code parts that are still maintained in SVN.
Not sure that the site content is really relevant to the DOAP so I would omit 
that.

Also maybe list the Git repo first, as that has the bulk of the source code.

At present it is quite hard for someone who does not know anything about the 
project to find the main source repo from the DOAP.

> DOAP contains obsolete SVNRepository entries
> --------------------------------------------
>
>                 Key: MRM-1891
>                 URL: https://issues.apache.org/jira/browse/MRM-1891
>             Project: Archiva
>          Issue Type: Bug
>          Components: Documentation
>         Environment: 
> https://git-wip-us.apache.org/repos/asf?p=archiva.git;f=doap_Archiva.rdf;a=blob_plain;hb=HEAD
>            Reporter: Sebb
>
> The DOAP for the project contains both SVNRepository and GitRepository 
> entries.
> However when a project moves to Git, the SVN repo is made read-only and is 
> not kept up to date.
> It is misleading to continue to publish SVN URIs which are not actually 
> maintained.
> The only exception might be where some parts of the source (e.g. website) 
> have not been migrated to Git. In that case, there might be a case for 
> including URIs that point to the part of the SVN repo that is still being 
> maintained.
> Please can you update the project DOAP accordingly?
> Thanks



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

Reply via email to