Ekaitz Zarraga <[email protected]> writes: > On 2025-09-21 12:11, Cayetano Santos wrote: >>> dim. 21 sept. 2025 at 10:46, Steve George<[email protected]> wrote: >> I’d say that when you contribute a new package, you’re more or less >> expected to take care of it afterwards. >> > > This is tricky because may discourage people from contributing new packages. > > We don't really have any kind of package-maintainership, like Nix does, for > instance. We do tend to follow this, but we shouldn't feel pressure to keep > the > packages we contributed up to date or anything like that.
I sometimes wonder whether we should not have a (possibly shared) maintainer-ship of packages. We (to a degree) have — with the teams. Are there any historical records on pros and cons, why Guix decided to organize in this way? > Being socially pressured for things when there's no requirement doesn't feel > like the kind of mutual care I'd like to promote. > > We are here to take care of each other. I agree here. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
