diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/attachments/20110308/bec52acb/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/attachments/20110308/bec52acb/attachment.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/attachments/20110308/bec52acb/attachment.html b/zarb-ml/mageia-webteam/attachments/20110308/bec52acb/attachment.html new file mode 100644 index 000000000..e94c84f37 --- /dev/null +++ b/zarb-ml/mageia-webteam/attachments/20110308/bec52acb/attachment.html @@ -0,0 +1,135 @@ +<br><br><div class="gmail_quote">On 8 March 2011 08:48, Michael Scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</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;"> +Le mardi 08 mars 2011 à 03:53 +0100, nicolas vigier a écrit :<br> +<div class="im">> Here is a proposal for an API that can be used on the maintainers<br> +> database, with the list of URLs and what they should do :<br> +><br> +> ***<br> +> An html page with the list of all packages, and their maintainer :<br> +> <a href="http://maintdb.mageia.org/packages.html" target="_blank">http://maintdb.mageia.org/packages.html</a><br> +> As we have many packages, the page will be long, so maybe we want to<br> +> split the list by first letter of package name :<br> +> <a href="http://maintdb.mageia.org/packages_a.html" target="_blank">http://maintdb.mageia.org/packages_a.html</a><br> +> <a href="http://maintdb.mageia.org/packages_b.html" target="_blank">http://maintdb.mageia.org/packages_b.html</a><br> +> <a href="http://maintdb.mageia.org/packages_c.html" target="_blank">http://maintdb.mageia.org/packages_c.html</a><br> +<br> +</div>Hi,<br> +<br> +Thee is other paging system in rails and similar framework, no need to<br> +specify this ( and I also think this is not part of a API ).<br></blockquote><div><br><br> Indeed that is the case, so we can have a paging system, with no need for different pages.<br> If on the other hand we want to split them by the first letter, again that is possible.<br> + So we could try with the simple paging system and if people find it more useful to have them split by name, we can do that later on.<br> <br></div><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"><br> +> The list of all packages and their maintainers, in text format :<br> +> <a href="http://maintdb.mageia.org/packages.txt" target="_blank">http://maintdb.mageia.org/packages.txt</a><br> +> With the output like this :<br> +> package1:maintainerlogin1<br> +> package2:maintainerlogin2<br> +> package3:maintainerlogin3<br> +> ...<br> +><br> +> ***<br> +> An html page to show the maintainer of one package (with<br> +> [packagename] replaced with the name of a package) :<br> +> <a href="http://maintdb.mageia.org/packages/[packagename].html" target="_blank">http://maintdb.mageia.org/packages/[packagename].html</a><br> +> The same in text format :<br> +> <a href="http://maintdb.mageia.org/packages/[packagename].txt" target="_blank">http://maintdb.mageia.org/packages/[packagename].txt</a><br> +> With output like this (only one line):<br> +> packagename:maintainerlogin<br> +> If the package is unmaintained, it appears like this :<br> +> packagename:nobody<br> +> If the package does not exist, an empty file is returned.<br> +<br> +</div>I would rather say :<br> +packagename:<br> +<br> +Using a name with a special meaning is just a special case to be placed<br> +everywhere.<br> +<div class="im"><br></div></blockquote><div><br> It currently uses the package id for displaying information, but I could have a look to see if it's possible to have it using the package name, which I have the feeling that it is.<br> +At the moment you can find information about a package by using the All link at the top.<br>There will also be a search box that gives the same information.<br>For finding information about a specific package the format used is:<br> +url/spackage/id<br>(spackage was named like that to dinstinguish it from the compiled packages - cpackage. If there is no need for compiled packages information as I've seen somewhere that can be removed)<br> <br></div> +<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"> +> ***<br> +> The list of maintainers (all maintainers who maintain at least one<br> +> package) :<br> +> <a href="http://maintdb.mageia.org/people.html" target="_blank">http://maintdb.mageia.org/people.html</a><br> +><br> +> ***<br> +> The list of packages maintained by someone (with [loginname] replaced by<br> +> a login) :<br> +> <a href="http://maintdb.mageia.org/people/[loginname].html" target="_blank">http://maintdb.mageia.org/people/[loginname].html</a><br> +> And the same in text format :<br> +> <a href="http://maintdb.mageia.org/people/[loginname].txt" target="_blank">http://maintdb.mageia.org/people/[loginname].txt</a><br> +> With the same format for output :<br> +> package1:loginname<br> +> package2:loginname<br> +> package3:loginname<br> +> ...<br> +> If the login does not exist, an empty file is returned.<br> +<br> +</div>A REST API would give a 404, that's also something everybdy doing HTTP<br> +should grasp and understand.<br> +<div class="im"><br></div></blockquote><div><br> That's what is used at the moment (REST-404).<br> For the list of maintainers the url is:<br> <a href="http://maintdb.mageia.orgl/maintainers">http://maintdb.mageia.orgl/maintainers</a> <br> +The extra information in there about first name, surname can be removed.<br><br></div><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"> + +<br> +> ***<br> +> The list of unmaintained packages :<br> +> <a href="http://maintdb.mageia.org/people/nobody.html" target="_blank">http://maintdb.mageia.org/people/nobody.html</a><br> +> And the same in text format :<br> +> <a href="http://maintdb.mageia.org/people/nobody.txt" target="_blank">http://maintdb.mageia.org/people/nobody.txt</a><br> +> With this output :<br> +> package1:nobody<br> +> package2:nobody<br> +> package3:nobody<br> +> ...<br> +<br> +</div>I would use a different url for unmaintained packages rather than<br> +nobody. Adding special case is not very clean, as said before.<br></blockquote><div><br> I agree with Michael, and say that probably a url like:<br> <a href="http://maintdb.mageia.org/umaintained">http://maintdb.mageia.org/umaintained</a><br> + would give the list of all umaintained packages<br> <br></div><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"><br> +> ***<br> +> The URL to add a package, used by the buildsystem when a package is<br> +> uploaded on the repository :<br> +> <a href="https://maintdb.mageia.org/admin/setnewpackage" target="_blank">https://maintdb.mageia.org/admin/setnewpackage</a><br> +> Protected with basic http authentication (with a login/password that was<br> +> set in maintdb or apache configuration).<br> +> Accessed with a POST request and the following two arguments :<br> +> package: [packagename]<br> +> maintainer: [maintainername]<br> +> If the package already exists in the database, it is not updated.<br> +><br> +> ***<br> +> The same as the previous URL, but the package maintainer is updated when<br> +> the package already exists in the database :<br> +> <a href="https://maintdb.mageia.org/admin/setpackage" target="_blank">https://maintdb.mageia.org/admin/setpackage</a><br> +<br> +</div>IMHO, it would be easier to have just 1 url :<br> +<br> +/upload/$package/$login/ ( and either protect this at http level, or<br> +using a key somewhere in the url )<br> +<div class="im"><br></div></blockquote><div><br> Agree. Either way is possible so if there a preferred way we can try that first.<br> <br></div><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"> +<br> +> If we compare with the maintainers db website used at mandriva, their<br> +> version also has :<br> +> - media name for each package, with pages to list packages from only<br> +> one media<br> +> - a search box to search for a package<br> +> - links to bugzilla for each package<br> +> But I don't think we should store the media name in maintdb.<br> +<br> +</div>That's indeed inflexible, if we want to have a package in more than one<br> +media.<br></blockquote><div><br> That shouldn't be any problem.<br> We would only need to change the relationship between media and packages, which is fine.<br> Again, if we don't want it to look like the mandriva, then we are flexible to decide how it would work and what we can display.<br> + We had to base it on something to start, but that could change easily.<br> <br></div><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"><br> +> maintdb should mainly be used in the following cases :<br> +> - by sophie, mageia-app-db and other package databases which want to show<br> +> maintainers of packages. They download the full list of packages and<br> +> maintainers every day (or hours) from the text file, to synchronize<br> +> with their database.<br> +<br> +</div>So then we should ask them what they would prefer. I knw for usre that<br> +reusing the mandriva format, or the fedora format will ease the work on<br> +sophie side.<br> +<br></blockquote><div><br> Not sure which format was used before, but again I don't see any problem using whatever makes it easier for people that use it.<br> Let me know what you would like it to do and then I'll try and do it.<br> +<br><br>Kosmas<br></div></div><br> |