Andreas Tille <andr...@an3as.eu> writes: > I wonder if we should reconsider the default assumption of package > ownership.
(This is a reas objective, but) i wasnt sure how the following text would achieve the above) > Instead, we could introduce a file, such as > debian/dont_touch_my_package (or a similarly named file), where > maintainers can document their reasons for discouraging others from > uploading the package. This file could include a timestamp, and we could > establish an agreed-upon timeframe for refreshing the statement to > ensure its continued validity. > Do you think this would lower the barrier between a package and other > people? (I dont see why it would be any different than today -- people who write the file can still lose interest/time and you will stil have to manage your calendar). Isnt the issue that debian's whole processes assume a "heroic" maintainer who does all the work alone. That has advantages, but also disadvantages if the hero disappears. Maybe start with: how does a company/other distros organise its coding teams? are there perhaps some things debian could learn?
