Hello Kernel Team,
I have been maintaining iproute2 for more than four years now. And to
be clear I am happy to continue, and don't need help with anything in particular.
But thinking about core packages and team maintainership in general, I
think it would be good to have iproute2 under a team umbrella, given
it's prio: important.
What do you think about moving the Salsa repo to the kernel team area
and the the maintainer field to the kernel mailing list? After all,
it's maintained upstream in the kernel infrastructure too, and it's
very closely related.
(previous maintainers CC'ed as FYI)
Thoughts?
On Fri, 2022-04-01 at 22:05 +0100, Luca Boccassi wrote:
Hello Kernel Team,
I have been maintaining iproute2 for more than four years now. And
to
be clear I am happy to continue, and don't need help with anything
in
particular.
But thinking about core packages and team maintainership in
general, I
think it would be good to have iproute2 under a team umbrella,
given
it's prio: important.
What do you think about moving the Salsa repo to the kernel team
area
and the the maintainer field to the kernel mailing list? After all,
it's maintained upstream in the kernel infrastructure too, and it's
very closely related.
(previous maintainers CC'ed as FYI)
Thoughts?
Yes, I think this would be a good fit for the kernel team.
On Sun, 2022-04-10 at 20:31 +0200, Ben Hutchings wrote:
On Fri, 2022-04-01 at 22:05 +0100, Luca Boccassi wrote:
Hello Kernel Team,
I have been maintaining iproute2 for more than four years now. And
to
be clear I am happy to continue, and don't need help with anything
in
particular.
But thinking about core packages and team maintainership in
general, I
think it would be good to have iproute2 under a team umbrella,
given
it's prio: important.
What do you think about moving the Salsa repo to the kernel team
area
and the the maintainer field to the kernel mailing list? After all,
it's maintained upstream in the kernel infrastructure too, and it's
very closely related.
(previous maintainers CC'ed as FYI)
Thoughts?
Yes, I think this would be a good fit for the kernel team.
Thank you!
I've opened a request for the Salsa admins to move the repo:
https://salsa.debian.org/salsa/support/-/issues/295
Could you please add me to the kernel-team Salsa group?
As soon as the repository move is sorted, I will do a new upload
switching the Maintainer field to Debian Kernel Team.
On Sun, 2022-04-10 at 21:48 +0100, Luca Boccassi wrote:
On Sun, 2022-04-10 at 20:31 +0200, Ben Hutchings wrote:
On Fri, 2022-04-01 at 22:05 +0100, Luca Boccassi wrote:
Hello Kernel Team,
I have been maintaining iproute2 for more than four years now.
And
to
be clear I am happy to continue, and don't need help with
anything
in
particular.
But thinking about core packages and team maintainership in
general, I
think it would be good to have iproute2 under a team umbrella,
given
it's prio: important.
What do you think about moving the Salsa repo to the kernel
team
area
and the the maintainer field to the kernel mailing list? After
all,
it's maintained upstream in the kernel infrastructure too, and
it's
very closely related.
(previous maintainers CC'ed as FYI)
Thoughts?
Yes, I think this would be a good fit for the kernel team.
Thank you!
I've opened a request for the Salsa admins to move the repo:
https://salsa.debian.org/salsa/support/-/issues/295
Could you please add me to the kernel-team Salsa group?
As soon as the repository move is sorted, I will do a new upload
switching the Maintainer field to Debian Kernel Team.
OK, I've invited you to the group.
Ben.
On Sun, 2022-04-10 at 23:58 +0200, Ben Hutchings wrote:
On Sun, 2022-04-10 at 21:48 +0100, Luca Boccassi wrote:
On Sun, 2022-04-10 at 20:31 +0200, Ben Hutchings wrote:
On Fri, 2022-04-01 at 22:05 +0100, Luca Boccassi wrote:
Hello Kernel Team,
I have been maintaining iproute2 for more than four years now.
And
to
be clear I am happy to continue, and don't need help with
anything
in
particular.
But thinking about core packages and team maintainership in
general, I
think it would be good to have iproute2 under a team umbrella,
given
it's prio: important.
What do you think about moving the Salsa repo to the kernel
team
area
and the the maintainer field to the kernel mailing list? After
all,
it's maintained upstream in the kernel infrastructure too, and
it's
very closely related.
(previous maintainers CC'ed as FYI)
Thoughts?
Yes, I think this would be a good fit for the kernel team.
Thank you!
I've opened a request for the Salsa admins to move the repo:
https://salsa.debian.org/salsa/support/-/issues/295
Could you please add me to the kernel-team Salsa group?
As soon as the repository move is sorted, I will do a new upload switching the Maintainer field to Debian Kernel Team.
OK, I've invited you to the group.
Ben.
Thank you!
Could you also please add me as a maintainer/admin of the iproute2
repo? I can't push right now:
Writing objects: 100% (4/4), 428 bytes | 428.00 KiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
remote: GitLab: You are not allowed to push code to protected branches on this project.
To salsa.debian.org:kernel-team/iproute2.git
! [remote rejected] debian/sid -> debian/sid (pre-receive hook declined) error: failed to push some refs to 'salsa.debian.org:kernel-team/iproute2.git'
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 299 |
Nodes: | 16 (2 / 14) |
Uptime: | 84:34:41 |
Calls: | 6,696 |
Calls today: | 1 |
Files: | 12,229 |
Messages: | 5,348,007 |