Re: [Mageia-dev] Maintainers policy
Le mercredi 13 avril 2011 à 23:33 +0200, Anne nicolas a écrit : > Hi there > > Following tonight's meeting, we will start one week discussion about > maintainers policy. Some questions to be discussed: > > - shall we have ACL's on svn, submits? > - what about having co-maintenership or teams? How shall we manage this? > - what about sensitive packages ? > ... > > Pleas make any comments and proposals we could discus to build it. > Final decisions will be taken during next packagers meeting (20th of > april) So following tnight meeting I created this page : http://mageia.org/wiki/doku.php?id=packagers_policy_discussion Please do not modify it without discussing here the subject, the goal is to track what was discussed, not to write proposal or to discuss on the page. Also, while reading again the log, I was reminded about the system of NMU in debian : http://www.debian.org/doc/developers-reference/pkgs.html#nmu The way is work is the following. A debian developer decide to do a NMU, send the package in a special queue and the package will be uploaded after X days, with X decided by the person who do the NMU. Maintainer can then decide to stop the NMU or to let it go, or maybe to push it. So basically, that would fulfill a requirement , ie that someone that want to prevent a upload could do it if he disagree. One problem is that we are much more fluid and reactive than Debian for the moment, and I am not sure we operate on the same timescale. Also, a NMU for a rpm when the maintainer is busy would not achieve much ( on the other hand, submit restriction wouldn't either ). I am not sure if we can do that, but that's a potential idea to explore. -- Michael Scherer
Re: [Mageia-dev] Maintainers policy
Le mardi 19 avril 2011 à 20:00 +0200, nicolas vigier a écrit : > On Wed, 13 Apr 2011, Anne nicolas wrote: > > > > > - shall we have ACL's on svn, submits? > > I think we should avoid using ACLs on all packages, on commits and submit, > as I think it is too constraining. Except maybe for sensitive packages. +1 and even, something like a simple 2 level system would be enough, as tracking who can do what would IMHO more limit people than prevent bugs. > What could be useful however, is to have an email sent to the maintainer > on commit or submit on his packages by someone who is not the > maintainer. So that maintainers are aware of all changes done on their > packages. in fact, something more generic, ie a whole notification system would be mhh more generic. Then we could build on it some rules : "packagers have mail about commit on their packages, on those of their apprentices, etc" -- Michael Scherer
Re: [Mageia-dev] Maintainers policy
On Wed, 13 Apr 2011, Anne nicolas wrote: > > - shall we have ACL's on svn, submits? I think we should avoid using ACLs on all packages, on commits and submit, as I think it is too constraining. Except maybe for sensitive packages. What could be useful however, is to have an email sent to the maintainer on commit or submit on his packages by someone who is not the maintainer. So that maintainers are aware of all changes done on their packages.
Re: [Mageia-dev] Maintainers policy
On Mon, Apr 18, 2011 at 10:53 AM, Pascal Terjan wrote: > On Thu, Apr 14, 2011 at 10:17, Funda Wang wrote: >> 2011/4/14 Anne nicolas : >>> Hi there >>> >>> Following tonight's meeting, we will start one week discussion about >>> maintainers policy. Some questions to be discussed: >>> >>> - shall we have ACL's on svn, submits? >>> - what about having co-maintenership or teams? How shall we manage this? >>> - what about sensitive packages ? >>> ... >>> >>> Pleas make any comments and proposals we could discus to build it. >>> Final decisions will be taken during next packagers meeting (20th of >>> april) >> >> If we are about to stick to subversion, then only maintainer could >> submit certain package. Of course, if package don't have maintainer, >> then anybody could submit it. > > As a maintainer, I would like to be at least notified when someone > updates one of my packages > >> If we will turn to git, then everybody could have his own clone, but >> the merge request should be reviewed by maintainer. After merging, >> anybody could submit it. The problem is that, we couldn't assure every >> package have a valid maintainer. > > Even if git would make it easier, I think it would in any case be nice > for people to be able to upload somewhere changes for review, and for > maintainer to easily apply them if correct > The use of reviewboard could be nice for this.
Re: [Mageia-dev] Maintainers policy
On Thu, Apr 14, 2011 at 10:17, Funda Wang wrote: > 2011/4/14 Anne nicolas : >> Hi there >> >> Following tonight's meeting, we will start one week discussion about >> maintainers policy. Some questions to be discussed: >> >> - shall we have ACL's on svn, submits? >> - what about having co-maintenership or teams? How shall we manage this? >> - what about sensitive packages ? >> ... >> >> Pleas make any comments and proposals we could discus to build it. >> Final decisions will be taken during next packagers meeting (20th of >> april) > > If we are about to stick to subversion, then only maintainer could > submit certain package. Of course, if package don't have maintainer, > then anybody could submit it. As a maintainer, I would like to be at least notified when someone updates one of my packages > If we will turn to git, then everybody could have his own clone, but > the merge request should be reviewed by maintainer. After merging, > anybody could submit it. The problem is that, we couldn't assure every > package have a valid maintainer. Even if git would make it easier, I think it would in any case be nice for people to be able to upload somewhere changes for review, and for maintainer to easily apply them if correct
Re: [Mageia-dev] Maintainers policy
On Wed, 13 Apr 2011, Anne nicolas wrote: Following tonight's meeting, we will start one week discussion about maintainers policy. Some questions to be discussed: - shall we have ACL's on svn, submits? - what about having co-maintenership or teams? How shall we manage this? - what about sensitive packages ? ... Pleas make any comments and proposals we could discus to build it. Final decisions will be taken during next packagers meeting (20th of april) There seem to be two issues here: 1. A maintainer database, with rules for updating the db This does not have to change package submission or svn access, but can be used for bug assignment, mailing package check reports and package svn commit logs, etc. 2. Restrictions on: a) maintainer db modifications b) package submission and/or svn access, based on the contents of the maintainer db Of course those 2 issues are related: any upload restrictions allowed by policy must be supported in the maintainer db. We don't need to implement everying at once, however. A maintainer db without upload restrictions will already be a big improvement over the current situation. There are 2 kinds of groups: maintainer groups = several people listed as maintainer for one package package groups = several packages that are maintained as if they were a single package, so they always have the same list of maintainers IMHO both features should be supported by the maintainer database: - Restricted packages (if allowed) must have at least 2 maintainers. This should make it less likely that change requests are simply ignored. - Maintainer groups can also be useful for unrestricted packages, e.g. to divide the work on a large source package. - Package groups are likely needed for some software systems like gnome and X11 that are split into many smaller source packages. Here's a partial proposal for phase 1/unrestricted packages: - anyone can register as maintainer for a (source) package - maintainers can unregister at any time - the "oldest" maintainer (first one registered) is primary maintainer, officially responsible for the package - package groups are defined by the project (is there any other way?) - the maintainer db redirects requests on a package in a group to the package group (with an error msg?) Christiaan
Re: [Mageia-dev] Maintainers policy
> I don't think we should have a "games" group. It makes sense to have > groups for packages that needs to be maintained together, for instance > KDE apps and KDE libraries should be maintained by the same group of > people. But for games, it is independent applications that could be > maintained by different people, so I don't think all games should be > maintained by the same group. It was only an example, not a group suggestion ;) But another example could be kde-devel libs and other c-c++ devel libs (e.g. commoncpp2, ucommon, boost,...). Anyway i agree on the fact that game could not be useful :) Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Maintainers policy
On Thu, 14 Apr 2011, Angelo Naselli wrote: > > But the real problem is that some packages could lay > on more than a group. For insntace, game and kde games > or educational and some games... and so on. I don't think we should have a "games" group. It makes sense to have groups for packages that needs to be maintained together, for instance KDE apps and KDE libraries should be maintained by the same group of people. But for games, it is independent applications that could be maintained by different people, so I don't think all games should be maintained by the same group.
Re: [Mageia-dev] Maintainers policy
2011/4/14 Anne nicolas : > Hi there > > Following tonight's meeting, we will start one week discussion about > maintainers policy. Some questions to be discussed: > > - shall we have ACL's on svn, submits? > - what about having co-maintenership or teams? How shall we manage this? > - what about sensitive packages ? > ... > > Pleas make any comments and proposals we could discus to build it. > Final decisions will be taken during next packagers meeting (20th of > april) If we are about to stick to subversion, then only maintainer could submit certain package. Of course, if package don't have maintainer, then anybody could submit it. If we will turn to git, then everybody could have his own clone, but the merge request should be reviewed by maintainer. After merging, anybody could submit it. The problem is that, we couldn't assure every package have a valid maintainer.
Re: [Mageia-dev] Maintainers policy
mercoledì 13 aprile 2011 alle 23:33, Anne nicolas ha scritto: > - what about having co-maintenership or teams? How shall we manage this? I'm not against of that. I believe it could be a good way out when people leave or can't/stop to work on their packages. Missing all members of a team is a little bit harder :D I know some people prefer being the only owner, we could decide case by case but finding packages that can be part of a group and a team that can manage it could help either in bug management. Easy groups could be for instance: kde gnome developer libraries toolchain & co. But the real problem is that some packages could lay on more than a group. For insntace, game and kde games or educational and some games... and so on. I thought that a first try could be to have mentor and their padawans seen as a team to maintain packages they've released togheter. From that it should be easy to move maintainership from one team member to another. But as ennael said that could be more work for mentors. So i don't have a real solution :) but something to discuss on... Cheers, Angelo signature.asc Description: This is a digitally signed message part.
