Jan Schulz wrote:
Just a question: Is it ok if a policy package is that openly available
for changes?
It's not open for changes just because it is co-maintained. The
java-common mainitainers just write down the decisions that are made by
the debian-java list. Just like it's done on debian-policy.
Hallo!
* Stefan Gybas <[EMAIL PROTECTED]> wrote:
> I'll take the package and add it to the pkg-java project on Alioth, if
> you agree. So you and the other project members can co-maintain it.
Just a question: Is it ok if a policy package is that openly available
for changes?
> I have some sugge
Jan Schulz wrote:
Just a question: Is it ok if a policy package is that openly available
for changes?
It's not open for changes just because it is co-maintained. The
java-common mainitainers just write down the decisions that are made by
the debian-java list. Just like it's done on debian-policy
Hallo!
* Stefan Gybas <[EMAIL PROTECTED]> wrote:
> I'll take the package and add it to the pkg-java project on Alioth, if
> you agree. So you and the other project members can co-maintain it.
Just a question: Is it ok if a policy package is that openly available
for changes?
> I have some sugge
retitle 201670 ITA: java-common -- Java policy and FAQ.
thanks
Ola Lundqvist wrote:
I have not been very active as the java policy maintainer the past
... year or so. The reason is that I do not use Java as much as
I did and my work no longer depends on it. Therefore I would like
someone else to ta
retitle 201670 ITA: java-common -- Java policy and FAQ.
thanks
Ola Lundqvist wrote:
I have not been very active as the java policy maintainer the past
... year or so. The reason is that I do not use Java as much as
I did and my work no longer depends on it. Therefore I would like
someone else to t
6 matches
Mail list logo
