cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: svn commit: r369374 - /cocoon/trunk/pom.xml
Date Mon, 16 Jan 2006 21:27:07 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 16 Jan 2006, Jorg Heymans wrote:

> Date: Mon, 16 Jan 2006 21:11:06 +0100
> From: Jorg Heymans <jh@domek.be>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: Re: svn commit: r369374 - /cocoon/trunk/pom.xml
> 
>
> Giacomo Pati wrote:
>>
>> Just a shy question. Is this comparable to the @author tag in the sources?
>>
>
> According to the maven pom docs :
>
> Developer:
> Information about one of the committers on this project. Derived from
> Contributor.
>
> Contributor:
> Description of a person who has contributed to the project, but who does
> not have commit privileges. Usually, these contributions come in the
> form of patches submitted.

I can read the Maven docs. But my question was whether we will later 
have the same discussion about it as we had with the @author tag.

I just want to make sure we don't go forwards and than backwards again. 
That's wasted time we can save in adance.

> We can interpret this whichever we want, but i suggest we don't go too
> granular with assigning developers and contributors to each module.

So we can put a dev@cocoon.apache.org in there as well?

> HTH

No, actually, it didn't help.

- -- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDzA+vLNdJvZjjVZARAvBZAKC9StAp3MqX6NA8Y4mUkse+6KwBJACeIILF
TWe5ON+fHFgibd+4y/4c6Tg=
=OSkP
-----END PGP SIGNATURE-----

Mime
View raw message