diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/attachments/20110308/fd14a85b/attachment-0001.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/attachments/20110308/fd14a85b/attachment-0001.html | 54 |
1 files changed, 54 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/attachments/20110308/fd14a85b/attachment-0001.html b/zarb-ml/mageia-webteam/attachments/20110308/fd14a85b/attachment-0001.html new file mode 100644 index 000000000..a5338e8aa --- /dev/null +++ b/zarb-ml/mageia-webteam/attachments/20110308/fd14a85b/attachment-0001.html @@ -0,0 +1,54 @@ +<br><br><div class="gmail_quote">On 8 March 2011 16:07, Romain d'Alverny <span dir="ltr"><<a href="mailto:rdalverny@gmail.com">rdalverny@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div class="im">On Tue, Mar 8, 2011 at 16:54, nicolas vigier <<a href="mailto:boklm@mars-attacks.org">boklm@mars-attacks.org</a>> wrote:<br> +> On Tue, 08 Mar 2011, Romain d'Alverny wrote:<br> +</div><div class="im">>> * through the CLI, would it auth against the maintdb app or through<br> +>> the buildsystem that, in turn, would notify the maintdb?<br> +</div>> [...]<br> +<div class="im">> Or the buildsystem can do the auth, and forward the request to maintdb<br> +> private method without doing any check, but including in the request<br> +> the login name of the user requesting the change so that maintdb can<br> +> check the permission. This one is probably better if we want to allow<br> +> changes using both website and CLI as it avoids doing the same checks<br> +> in two different places.<br> +<br> +</div>Looks better that way, yes.<br> +<br> +So maintdb will need to know who is admin (can be checked later with a<br> +flag). Not sure, can be updated later:<br> +<a href="http://mageia.org/wiki/doku.php?id=web:maintdb#break_a_maintainer_package_association" target="_blank">http://mageia.org/wiki/doku.php?id=web:maintdb#break_a_maintainer_package_association</a><br> +<br> +>> <a href="http://mageia.org/wiki/doku.php?id=web:maintdb#specs_actions" target="_blank">http://mageia.org/wiki/doku.php?id=web:maintdb#specs_actions</a> [...]<br> +<div class="im">><br> +> But I would change this :<br> +><br> +> * POST <a href="https://maintdb/packages" target="_blank">https://maintdb/packages</a><br> +> user - string - optional - login of the user pushing the package<br> +><br> +> The user string should not be optional but mandatory.<br> +<br> +</div>Right. Fixed.<br> +<div class="im"><br> +> * GET <a href="https://maintdb/packages" target="_blank">https://maintdb/packages</a><br> +> Returns a list such as:<br> +> packagename / maintainers login / last commit date / url to bugs report / url to package repo<br> +><br> +> I don't think we should return url to bugs report and url to package<br> +> repo here.<br> +<br> +</div>Ok. Then we must have clearly spec'd URLs for both so we can use them for sure.<br> +<div class="im"><br> +> For the "last commit date", we don't have this info. The<br> +> info we can have is "last sucessful submit date" (the last time the<br> +> private method was called on that package).<br> +<br> +</div>Right, updated as well.<br> +<br> +<br> +Kosmas, would you have time this week to work on maintdb to port these<br> +interfaces to it or do you need help too?<br> +<br> +I can devote some time on it this week, but I'll have to figure out<br> +how to... well, I've got a conflict (RubyGem version error: rack(1.2.1<br> +not ~> 1.1.0)) to make it run.<br></blockquote><div><br> Romain,<br><br> Yes it seems very likely that I would get some time this week, as I'm finishing a project that I had to do today.<br> By all means to help if you want to :-)<br> + I'll be available tomorrow if you would like to have a look at the conflict that you have.<br><br> I will also go through the proposed changes and the spec that you have put in the wiki, and ask if I have any questions.<br> +<br> Kosmas<br></div></div> |