Hi all,
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
As of now, policy[1] states that:
Thus if you bring some packages into the team, you can keep your
name in the Maintainer field. You will receive bug reports and
Hello,
Sandro Tosi wrote:
Hi all,
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
As of now, policy[1] states that:
Thus if you bring some packages into the team, you can keep your
name in the Maintainer field. You will
Hi,
[Sandro Tosi, 2008-03-09]
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
my turn. How I understand the team relationship: [0]
* if DPMT/PAPT is in our repo. (no matter where the team name is, in
Maintainer or in
On Sun, Mar 09, 2008, Emilio Pozuelo Monfort wrote:
For example, in the pkg-gnome team, it's even discouraged to put the team
as the Maintainer, but everybody's welcome to touch any package, no
matter who's listed as the Maintainer.
The rationale here is that packages with an assigned
[Piotr Ożarowski, 2008-03-09]
* if DPMT/PAPT is in our repo. (no matter where the team name is, in
s,DPMT/PAPT,package
sorry
pgpN28nSzs0aN.pgp
Description: PGP signature
5 matches
Mail list logo
