<div dir="ltr">I do not think the package ownership concept is obsolete.<div>We can't ask everybody to feel concerned and competent about every package and some people might join the project just to maintain a few packages that they really care about.</div>
<div><br></div><div>Whatever we do, the question in the end is: who feels responsible for dealing with bugs and updates for a package ?</div><div>I don't really believe in the mode "there are no package maintainer, everybody can update every package", I think this lead to <a href="http://en.wikipedia.org/wiki/Diffusion_of_responsibility">http://en.wikipedia.org/wiki/Diffusion_of_responsibility</a></div>
<div><br>Even if we don't have any contract, I think there is an implicit commitment when you take ownership of a package. Debian even listed for instance what are the responsabilites of a maintainer: <a href="http://www.debian.org/doc/manuals/developers-reference/developer-duties">http://www.debian.org/doc/manuals/developers-reference/developer-duties</a>.</div>
<div><br></div><div>As a user of a package, it's also important to know wether the package you want to use has some maintainers behind or if it's in best effort mode by people who may even not use the package.<br>
</div><div><br></div><div><br></div><div>What is obsolete I think is the to have one maintainer package that is the only one entitled to change the package (we already moved from that), we should instead:<br></div><div><br>
</div><div>- promote team maintenance rather than one maintainer per package, </div><div>- promote non-maintainer uploads with some rules,</div><div>- have a special team for orphaned packages.</div><div><br></div><div><br>
</div><div>Whatever the outcome, we will need anyway to change a bit the infrastructure because it is not adapted to either team maintenance or globally shared maintenance mode:<br></div><div><br></div><div> - the bugtracker will always send the bugs to the last person that uploaded the package and the the bug summary page does the same <a href="http://www.opencsw.org/buglist/maintainer.cgi?maintainer=laurent">http://www.opencsw.org/buglist/maintainer.cgi?maintainer=laurent</a> </div>
<div><br></div><div> - the qa page and maintainer page still list the packages last uploaded by someone like it was maintained by the person (it's still written "maintained by" by the way<font color="#3e5867" face="Lucida Grande, Helvetica Neue, Arial, Lucida Sans Unicode, sans-serif"><span style="line-height:20px">): </span></font><a href="http://www.opencsw.org/maintainers/maciej/">http://www.opencsw.org/maintainers/maciej/</a></div>
<div><br></div><div><br></div><div>Yann</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/11 Maciej (Matchek) Bliziński <span dir="ltr"><<a href="mailto:maciej@opencsw.org" target="_blank">maciej@opencsw.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The current notion throughout our code base is that the user who runs<br>
mgar, and the user who owns the package is the same user. To separate<br>
these two concepts, the code needs modifications in many places.<br>
<br>
But I would also like to challenge Peter's not willing to inherit the<br>
packages. I was hoping that the notion of package ownership has<br>
already eroded. It was different in the times when package sources<br>
were private. Other people did not have access to the build recipes,<br>
so the only way to get the package modified, was to ask the sole<br>
person who had the sources. Fortunately, we're in a different world<br>
now, we share the code. Anybody can get the code and build it.<br>
<br>
We're a volunteer organization, we do not hold any binding contracts<br>
with regards to package maintenance. My name on a package means that I<br>
was the last person to modify the package, which means I might know<br>
something about the package and you have an idea of whom to talk to.<br>
It does not entitle you to any demands with relation to the package. I<br>
might have been the last person to upload the package, but I be no<br>
longer willing to work on the package. Therefore, I would suggest we<br>
do not embed in our infrastructure the outdated concept of package<br>
ownership.<br>
<br>
Let's take a step back: what's wrong with having your name show up<br>
next to a package to which you made a small change?<br>
<span class="HOEnZb"><font color="#888888"><br>
Maciej<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@lists.opencsw.org">maintainers@lists.opencsw.org</a><br>
<a href="https://lists.opencsw.org/mailman/listinfo/maintainers" target="_blank">https://lists.opencsw.org/mailman/listinfo/maintainers</a><br>
.:: This mailing list's archive is public. ::.<br>
</div></div></blockquote></div><br></div>