Security concerns about our Launchpad teams and projects.
Thanks for re-assigning the project. I guess it's not clear if there's a
real need for the pkg-java team to maintain any project pages. I think
the only real point in creating them is to link upstream bug trackers.
But then you can always just assign it to Registry Administrators
(registry) team once it's configured.
On 25/10/11 19:11, Niels Thykier wrote:
> I got an email from Launchpad about the colorpicker project, which is
> currently "maintained" by the pkg-java team in Launchpad. Long story
> short, this is not acceptable because the pkg-java team is under an
> open-subscription policy. For now I have given the maintainership of
> colorpick back to Andrew Ross, which should solve the immediate issue.
> But it does raise the question of how to handle this in general. We
> already have two teams on Launchpad (pkg-java and debian-java, both
> open), so we could close one of them to maintain these projects and
> leave the other one open.
> But this implies that the administrators of the closed team are
> stricter in our acceptance (plus we would have to double check existing
> For reference, the "project pages" in question are launchpad's "upstream
> projects", so I am not even 100% sure it makes sense for the Java Team
> to control these.
> So, should we keep both teams open (and not accept maintainership of any
> "projects") or close one of them for this purpose?
>  I am not certain the rationale is public at the moment, so I will
> not disclose it now.
>  Currently they are both administrated by Torsen Werner, Damien
> Raude-Morvan and myself.
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com