Hi Michael and Simon,
On Wed, Dec 18, 2024 at 10:16:12PM +0900, Simon Richter wrote:
> Postfix's "master" process effectively implements an orchestrator for a
> microservice architecture, similar to what systemd does. This could be
> replaced by systemd by writing a generator that creates units fr
On Sat, 21 Dec 2024 07:33:46 +0100, Andreas Metzler
wrote:
>On 2024-12-19 Andrey Rakhmatullin wrote:
>> On Thu, Dec 19, 2024 at 04:58:06PM +0100, Samuel Thibault wrote:
And it is actively harmful as if one edits the example configuration to
have a useful configuration as dpkg will start
On Sat, 21 Dec 2024 22:23:19 +0100, Gioele Barabucci
wrote:
>This branch of the discussion started by pointing out the fact that some
>maintainers _do_ in fact orphan their packages to remove the "feeling of
>being responsible", and then go on maintaining these packages.
Its a way to visibly sa
On 2024-12-22 Sean Whitton wrote:
> On Sat 21 Dec 2024 at 06:15pm +01, Chris Hofstaedtler wrote:
>> Uploads to the archive are not irreversible. You can just as well
>> upload a new version reverting whatever was done.
>> Please everybody stop treating the archive as the holy thing that
>> only
On 2024-12-22 Sean Whitton wrote:
> On Sat 21 Dec 2024 at 10:23pm +01, Gioele Barabucci wrote:
>> We have a mechanism for when you feel responsible: "Maintainer: $me".
>> What is being discussed here is a mechanism for shared, collective,
>> diffused responsibility: "If this package is in bad sh
> From
> https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group:
>
> The debian group is for CollaborativeMaintenance (the old collab-maint
> on Alioth).
>
> The group is accessible to all Debian developers upon linking their
> SSO Account, and are granted Maintain
> > Commits onto a git repo can be reversed easily (via `git revert`
> > or forced push, if one really wants to), but problematic uploaded
> > packages to the archive are irreversible and might cause broader
> > damages. That is why people are okay with allowing random git commits
> > to Debian gro
> The https://go-team.pages.debian.net/ pages may have some flaws, but one
> key social function is that it establishes the group as a team effort.
> That goal is something to take after. I'm trying migrate my
+1
> pkg-auth-maintainers packages to pkg-security just because
> https://wiki.debian.
Hello,
On Sat 21 Dec 2024 at 10:23pm +01, Gioele Barabucci wrote:
> We have a mechanism for when you feel responsible: "Maintainer: $me".
>
> What is being discussed here is a mechanism for shared, collective, diffused
> responsibility: "If this package is in bad shape, the whole Debian project
>
Hello,
On Sat 21 Dec 2024 at 06:15pm +01, Chris Hofstaedtler wrote:
> Uploads to the archive are not irreversible. You can just as well
> upload a new version reverting whatever was done.
>
> Please everybody stop treating the archive as the holy thing that
> only blessed maintainers can touch. T
Hello,
On Sat 21 Dec 2024 at 09:37am +01, Simon Josefsson wrote:
> I've long though about changing maintainer to QA for my packages like
> you suggest, but there has been at least on reason I haven't done so:
> lack of clear effective written down team policy in what the conventions
> are. I don
Hello,
Another thought I had was just to use the packages.d.o address.
E.g.
Maintainer: Debian developers
It would be invalid to use this in maintainers without any human
uploaders. Only q...@packages.debian.org is valid without human
uploaders.
--
Sean Whitton
On Fri, Dec 20, 2024 at 08:37:33AM -0600, rhys wrote:
>
>
> > Right now, the model we have is "some packages use the empty /etc model,
> > some packages install commented-out defaults, and there's no
> > consistency". I'd love to move to the model of "all packages use
> > whichever model the sysa
(Also looping in -devel and -dak this time around)
On Thu, Nov 28, 2024 at 4:49 PM Debian FTP Masters
wrote:
>
>
>
> Source-only uploads to NEW are not allowed.
>
> Mapping bookworm-backports to stable-backports.
> binary:wesnoth is NEW.
> binary:wesnoth-core is NEW.
> binary:wesnoth-music is NEW
On 21/12/24 15:32, Tobias Frost wrote:
On Sat, Dec 21, 2024 at 02:09:28PM +0100, Gioele Barabucci wrote:
On 21/12/24 10:15, Pirate Praveen wrote:
We could use collab maint list, which was specifically created for this
https://wiki.debian.org/CollaborativeMaintenance
Good idea.
To sum up all
On 2024-12-19 05:13, Sean Whitton wrote:
> On Sun 15 Dec 2024 at 11:21pm +01, Philipp Kern wrote:
>> Or introduce some subtle bugs that get ironed out only when it sees
>> usage.
>
> Indeed, but this work can end up being very costly. A lot of knowledge
> might be built into the old code. Even i
On Sat, Dec 21, 2024 at 12:09:57PM -0500, Boyuan Yang wrote:
> Commits onto a git repo can be reversed easily (via `git revert`
> or forced push, if one really wants to), but problematic uploaded
> packages to the archive are irreversible and might cause broader
> damages. That is why people are ok
* Boyuan Yang [241221 18:10]:
> 在 12/21/2024 12:02 PM, Jeremy Sowden 写道:
> > On 2024-12-21, at 17:55:39 +0100, Marc Haber wrote:
> > > On Sat, 21 Dec 2024 12:08:35 +0100, Tobias Frost wrote:
> > > > We DO already have the debian namespace on salsa, everything in this
> > > > namespace is "team mai
在 12/21/2024 12:02 PM, Jeremy Sowden 写道:
On 2024-12-21, at 17:55:39 +0100, Marc Haber wrote:
On Sat, 21 Dec 2024 12:08:35 +0100, Tobias Frost wrote:
We DO already have the debian namespace on salsa, everything in this
namespace is "team maintained by everyone.",
Is that so? I know that I agre
On 2024-12-21, at 17:55:39 +0100, Marc Haber wrote:
> On Sat, 21 Dec 2024 12:08:35 +0100, Tobias Frost wrote:
> > We DO already have the debian namespace on salsa, everything in this
> > namespace is "team maintained by everyone.",
>
> Is that so? I know that I agree that anybody can commit to my
On Sat, 21 Dec 2024 12:08:35 +0100, Tobias Frost
wrote:
>We DO already have the debian namespace on salsa, everything in this
>namespace is "team maintained by everyone.",
Is that so? I know that I agree that anybody can commit to my
repositories that are in Salsa's debian namespace, but I actual
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-awslabs-soci-snapshotter
Version : 0.4.1-1
Upstream Author : Amazon Web Services - Labs
* URL : https://github.com/awslabs/soci-snapshotter
* License : Apache-2.0
Programmi
On Sat, Dec 21, 2024 at 02:09:28PM +0100, Gioele Barabucci wrote:
> On 21/12/24 10:15, Pirate Praveen wrote:
> > We could use collab maint list, which was specifically created for this
> > https://wiki.debian.org/CollaborativeMaintenance
>
> Good idea.
>
> To sum up all suggestions until now:
>
Package: wnpp
Owner: Roland Rosenfeld
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libharfbuzz-shaper-perl
Version : 0.027+ds
Upstream Author : Johan Vromans
* URL : https://metacpan.org/release/HarfBuzz-
On 21/12/24 10:15, Pirate Praveen wrote:
We could use collab maint list, which was specifically created for this
https://wiki.debian.org/CollaborativeMaintenance
Good idea.
To sum up all suggestions until now:
Some packages will be maintained in a default-open way and outside a
specific team
On Sat, Dec 21, 2024 at 10:11:55AM +0800, Sean Whitton wrote:
> Hello,
>
> On Thu 12 Dec 2024 at 10:43am +01, Gioele Barabucci wrote:
>
> > an alternative that I was thinking of, is making this "everybody is onboard"
> > policy more explicit by having a special email to use for the Maintainer
> >
Le 21 décembre 2024 10:15:35 GMT+01:00, Pirate Praveen
a écrit :
>
>Please don't. We did the opposite for javascript team, we created a dedicated
>discussion list since the volume of mails were too huge, go and ruby teams do
>this too. All accepted, processed mails come to this list.
+1
W
Em 20 de dezembro de 2024 23:11:55 GMT-03:00, Sean Whitton
escreveu:
>Hello,
>
>On Thu 12 Dec 2024 at 10:43am +01, Gioele Barabucci wrote:
>
>> an alternative that I was thinking of, is making this "everybody is onboard"
>> policy more explicit by having a special email to use for the Maintain
On ശ, ഡിസം 21 2024 at 04:44:01 വൈകു +08:00:00
+08:00:00, Sean Whitton wrote:
Hello,
On Sat 21 Dec 2024 at 08:09am +01, Gioele Barabucci wrote:
On 21/12/24 03:11, Sean Whitton wrote:
an alternative that I was thinking of, is making this "everybody
is onboard"
policy more explicit by hav
Hello,
On Sat 21 Dec 2024 at 08:09am +01, Gioele Barabucci wrote:
> On 21/12/24 03:11, Sean Whitton wrote:
>>> an alternative that I was thinking of, is making this "everybody is onboard"
>>> policy more explicit by having a special email to use for the Maintainer
>>> field. For example:
>>>
>>>
Gioele Barabucci writes:
> Hi,
>
> an alternative that I was thinking of, is making this "everybody is
> onboard" policy more explicit by having a special email to use for the
> Maintainer field. For example:
>
> Maintainer: Debian community
>
> The stewards of the package could be listed a
31 matches
Mail list logo
