Re: [Mageia-dev] buildsystem = maintainers db link test
On Thursday, March 24, 2011 11:24:44 am Romain d'Alverny wrote: Cool. Thanks to pterjan and boklm we now have a post on maintdb test platform on each upload. That will help setting things up further. On Wed, Mar 23, 2011 at 20:45, Maarten Vanraes maarten.vanr...@gmail.com wrote: Op woensdag 23 maart 2011 20:32:42 schreef Michael Scherer: ( nota : xml rpc interface could be a good idea to add later if not on the roadmap ) Why not yes. Personally, i want an app where i can log in, search a package, and grab / drop it (last packager could be shown if you have the info anyway...), and a link to the bugs of that package, and also a way to show my maintained packages. that's it. This whole thing may be a mashup of several apps in the end (profile page for you, profile page for a package, for a team, etc.), among which the maintdb is only one piece. Let's just build the minimal set needed for now for maintainer/package association and build from that. Heard comments about having a more straight association between the actual maintainer and the package (and not considering people pushing a rebuild as a co-maintainer). Will see how to manage that. Any other point? Thanks! Romain Let's start to get this running. -- Thomas
Re: [Mageia-dev] buildsystem = maintainers db link test
Op woensdag 23 maart 2011 18:00:40 schreef nicolas vigier: On Wed, 23 Mar 2011, Romain d'Alverny wrote: Misc righly pointed out that: * someone triggering a massive rebuild may not want to be seen as a maintainer of packages uploaded by this; several possible solutions: - first uploader is set as the maintainer by default; - this will be manually editable from the maintdb app anyway; - would a specific flag be raised in the buildsystem (or a package) when such a massive rebuild is triggered? - instead of strict associations, we can associate maintainership by frequency of uploads/activity on a given package (unless massive rebuilds are triggered more often by a single packager than regular package uploads by the actual maintainer) * submissions stats publishing may require your validation (and actually, for that specifically and future topics, we'll need to see how we can publish contributors activity stats through our platform - as a de-facto feature or as a preference, per contributor). I think submissions stats can be interesting to keep, to see who is the most active on a package. But comaintainers should not be added automatically when package is submitted by someone. For instance you don't want to become comaintainer of a package because you fixed a typo in the description. I think becoming comaintainer should be something that you decide, not something done automatically. i agree, maintainership should be done manually. but preferably with some kind of package search and checkboxes, to select multiple ones. (to minimize the work; i can't see jq finding package by package and selecting himself for it) sophie already keeps packager data, afaik. if the work with searching package and checkboxes is too much work at this time, perhaps we could enable that autosetting code for a short while so that most are set.
Re: [Mageia-dev] buildsystem = maintainers db link test
Le mercredi 23 mars 2011 à 20:16 +0100, Maarten Vanraes a écrit : i agree, maintainership should be done manually. but preferably with some kind of package search and checkboxes, to select multiple ones. (to minimize the work; i can't see jq finding package by package and selecting himself for it) jq would likely use his super scripting ability for that, and we do have access to the db, so this can be easier to achieve for those without super power. ( nota : xml rpc interface could be a good idea to add later if not on the roadmap ) sophie already keeps packager data, afaik. Technically, Sophie fetch them from external sources. The db is just for caching purpose. if the work with searching package and checkboxes is too much work at this time, perhaps we could enable that autosetting code for a short while so that most are set. The process must be seamless. Ie, people should not think of it at all. -- Michael Scherer
