Re: [Mageia-dev] looking for a padawan
Dnia czwartek 03 lutego 2011 o 18:58:05 Jerome Quelin napisał(a): if there are lots of candidates (and looking at http://mageia.org/wiki/doku.php?id=packaging#list_of_registered_people, there should be quite a lot), i'll priorize on the following criteria in order: - people with packaging experience (this way, we can increase the packagers pool faster) Hi, I see on the [dev], you have already found someone, but maybe I can join too? I've some experience in creating rpms, I've made some for my mandriva (ie gcc, kernel, firefox, and some less known soft ;) ) The only problem is that currently i don't have much time, I'd like to start in a few/several days/weeks. Is it ok? regards ps I'm from poland so I guess it's only +1h ;) -- Michał Walenciak gmail.com kicer86 http://kicer.sileman.net.pl gg: 3729519
Re: [Mageia-dev] FOSDEM 2011
Hi, I wonder, where do the long distance people could get a video / presentation of conference I found http://www.youtube.com/watch?v=0RntO4dH0tU , hopefully someone will have a link to the same video in a free format :) Christophe
Re: [Mageia-dev] New mockups about mageia-app-db
On 6 February 2011 23:17, Fabrice Facorat fabrice.faco...@gmail.com wrote: 2011/2/6 Marcello Anni marcello.a...@alice.it: 2011/2/6 Marcello Anni marcello.a...@alice.it: 2011/2/6 Marcello Anni marcello.a...@alice.it: homepage: http://img209.imageshack.us/i/mageiafindouthomepage.jpg/ browsing page: http://img696.imageshack.us/i/mageiafindoutbrowsingpa.jpg/ sorry but who is supposed to use mageia-app-db ? power users ? dev ? casual/normal users ? Samuel said that the application must be useful both for newbies and power users ok for power users, but for normal users the Ui is too cluttered [remember that this is only a first mockup made by me (the developer is Samuel), my goal is to provide to him all the most interesting infos and ideas to develop the app as best as possible.] 1. left pane : Release Alpha vs Cauldron ? for a normal user, this means pretty nothing. If the user is looking for an application/package, then don't talk about release or repositories. well, if you have mandriva installed, do you think you don't know what release is? alpha release vs. cauldron could be Mageia 2011 and Mageia 2012 whereas eventually I may know about release ( Mageia 2011 ), I may not know about updates/backports/testing/ What's the point fo browsing by release ? It's an application database, so you should browse by applications. this mockup depends for some aspects on the current implementation: http://88.191.121.20/madb/master/index.php/?source=0distrelease=8application=1arch=1 i agree about browsing only by applications, but for power users is important also the updates/backports/testing/ option. What about using instead rpm categories, and then display theses kind of information in the package infos do you mean showing only amarok field and when you get into it you'll download different versions depending on the release installed? it can be an interesting idea. first I see the main categories : Office, Sound Video, Tools, ... Then the sub-category and then the application : Sound Video - Sound - Amarok The left pane should only show categories, the application list will be displayed in the center pane. See tthe way you navigate in this : http://download.cnet.com/windows/mp3-and-audio- software/?tag=rb_content;contentNav this reflect the current mockup of the navigation page, did you see it? is it moreover similar to your preferences? 2. right pane : Alpha vs Beta ? also here, i mean something like this: Mageia 2011 and Mageia 2012 this won't scale when you will have more and more release, except if you plan to show only 2 releases, and so to support a mandriva release only during 2 releases cycles. about this i should hear the developer, depending on how is implemented it could be useful or cluttering. Close the World, Open the Net http://www.linux-wizard.net I like the ratings and the news about new packages on the right, however the centre pane is a little cluttered, maybe if the info there was put into topics with turn down boxes it would make it clearer and cleaner as the information is a little distracting atm. Donald. you're right, it is a little cluttered, the home-page mockup is only a first version to improve. to better satisfy user needs and preferences, we could use the user preferences and settings, as: - show only a release - show only specific packages (+ notifications?) - etc... other ideas/critics? cheers, Marcello
Re: [Mageia-dev] New mockups about mageia-app-db
2011/2/7 Marcello Anni marcello.a...@alice.it: On 6 February 2011 23:17, Fabrice Facorat fabrice.faco...@gmail.com wrote: 2011/2/6 Marcello Anni marcello.a...@alice.it: 2011/2/6 Marcello Anni marcello.a...@alice.it: 2011/2/6 Marcello Anni marcello.a...@alice.it: whereas eventually I may know about release ( Mageia 2011 ), I may not know about updates/backports/testing/ What's the point fo browsing by release ? It's an application database, so you should browse by applications. this mockup depends for some aspects on the current implementation: http://88.191.121.20/madb/master/index.php/?source=0distrelease=8application=1arch=1 i agree about browsing only by applications, but for power users is important also the updates/backports/testing/ option. It's depend on the workflow. Do you want to : - quickly be able to see all backports packages for a release - or see the differents versions for a package IMHO for the former, you'd better add a query/report page where the user could select some filters and then have an answer. Some of the filters category : release = distribution_version1, distribution_version_2 category = release, backport, testing sort by = category, release date You should keep the UI simple, and then add a query page to allow complex queries for power users. -- Close the World, Open the Net http://www.linux-wizard.net
Re: [Mageia-dev] Packager meetings for tonight
On Mon, Feb 7, 2011 at 12:08, Thierry Vignaud thierry.vign...@gmail.com wrote: On 3 February 2011 17:06, Michael Scherer m...@zarb.org wrote: So as discussed tonight ( but if you couldn't be present at the meeting, do not hesitate to express yourself now ), we proposed to have some order in the import of rpm ( ie avoid the resulting anarchy due to lack of process for bootstrap ). In order to start by something tangible and easy to manage, let's take a concrete case. The sysadmin team discussed to use mageia on the servers ( once the stable release is out ie, not now ) for obvious reasons of dogfooding. But for this, we will have to import the needed rpms. I extracted from puppet logs the lists of rpm, and I have a list of the major component needed. The rule would be to take 1 and only 1 rpm ( or family ) at the time, to make sure it work fine ( ie, compile for the moment, and also install ), to make sure the package is cleaned ( ie, patchs sent upstream, commented, etc ), and to make sure that everybody can find something to do. And that of course requires to do the same for missing BuildRequires, and Requires ( but since lots of rpm have been imported without being fully cleaned, and since there is now a fast web interface for svn, people have no excuse to not check ). I will place the list on the wiki tomorrow, and people wishing to work on importing a rpm should add their name/login/whatever after the rpm, and then to work on it. If there is already someone working on a rpm, just take another one, or try to work with this person. So it seems that my list of 20 rpms is now much lower than needed, as most servers applications needed have been imported. The only thing left are : What would really help us is the list of actually successfully build package rather than the list of submitted packages that we previously have on pkgsubmit.mga.org It has been replaced by the list of missing BR for currently submited packages (http://pkgsubmit.mageia.org/data/missing-deps.i586.txt) but having the list of succesfully rebuild packages would help too. OK, I removed the list of built one when removing the (empty) list of missing one to get rid of the ugly temporary code I can add it back until having something better... Or maybe add the generation of those lists to the script run every 15 minutes that lists missing deps.
[Mageia-dev] [ ANNOUNCE] Cauldron Update to rpm 4.8.1 ( After Alpha 1 ISOS )
Hello all, in svn we now have the new rpm 4.8.1 ( the last stable release of rpm.org ). We will push it after the Alpha1 iso ( not a good idea to potentially break something before an iso :) ) What is left to do : - Port perl-RPM4 to new rpm 4.8.1 Have a good day.
Re: [Mageia-dev] New mockups about mageia-app-db
Le lundi 07 février 2011 à 00:17 +0100, Fabrice Facorat a écrit : 2011/2/6 Marcello Anni marcello.a...@alice.it: also here, i mean something like this: Mageia 2011 and Mageia 2012 this won't scale when you will have more and more release, except if you plan to show only 2 releases, and so to support a mandriva release only during 2 releases cycles. Technically, that not mandriva, but mageia :) And since one of the goal of the tool is to manage people who ask for backports, as said on http://mageia-app-db.tuxette.fr/projects/1/wiki , it make sense to limit this to supported releases. From a ressource point of view, I do not think it would be wise to keep everything ( ie, to still keep stuff server side to change all releases ). And limiting the releases supported on every tools we use would also remove clutter on various part of the interface ( ie bugzilla among others, or forums ). So yes, just show only X releases by default make perfect sense, IMHO -- Michael Scherer
Re: [Mageia-dev] 26/01/2011 meeting
Romain d'Alverny a écrit : On Wed, Jan 26, 2011 at 16:35, Marcello Annimarcello.a...@alice.it wrote: we will be able to create a LiveCD version of Mageia for this alpha release? this is really important as interested people that don't want problems may want to try it and then install it only when a stable release is ready for everyday use. As pointed out several times (and will be underlined in all announcements) this Alpha 1 is - NOT a stable release - NOT for the average user, it's a developper release - NOT ready for everyday use in fact, a livecd version allow to keep the funny side of linux without having any risk. so? Again, that's not the focus of this alpha release. We don't want people to try it around just to see what Mageia has in reserve, because they will be disappointed in this regard: take this alpha as an alpha-developer/packager-technical-raw-preview. It will be ugly. It will scare Santa Claus. It will make the rain vaporize. It may even break your neighbour's TV set. Right -- Mageia is powerful stuff :) Point well made. Our alpha release will be far from ready for the average user. But an essential step in the process. Romain -- André
Re: [Mageia-dev] 26/01/2011 meeting
Le lundi 07 février 2011 à 21:30 +0200, Ahmad Samir a écrit : On 26 January 2011 20:20, Michael Scherer m...@zarb.org wrote: Le mercredi 26 janvier 2011 à 18:13 +0200, Ahmad Samir a écrit : More DE's will be in soon; note that the big hurdle of importing the most basic packages is over, so importing packages now is much easier :) Yeah, but personally, i would prefer to see that people focus more on cleaning ( and sending patches upstream ) than importing And who said that when we import a package we didn't clean it too? Well, most of the time, patches are not commented nor send upstream :/ -- Michael Scherer
Re: [Mageia-dev] 26/01/2011 meeting
On 7 February 2011 22:24, Michael Scherer m...@zarb.org wrote: Le lundi 07 février 2011 à 21:30 +0200, Ahmad Samir a écrit : On 26 January 2011 20:20, Michael Scherer m...@zarb.org wrote: Le mercredi 26 janvier 2011 à 18:13 +0200, Ahmad Samir a écrit : More DE's will be in soon; note that the big hurdle of importing the most basic packages is over, so importing packages now is much easier :) Yeah, but personally, i would prefer to see that people focus more on cleaning ( and sending patches upstream ) than importing And who said that when we import a package we didn't clean it too? Well, most of the time, patches are not commented nor send upstream :/ -- Michael Scherer Personally, as I said before about upstreaming patches, I don't think I have enough experience to judge if a patch should go upstream or not, so that part I can't do. What do you mean by commented? -- Ahmad Samir
Re: [Mageia-dev] packaging for Mageia
On Fri, 04 Feb 2011, Florent Monnier wrote: Le vendredi 04 février 2011 17:49:39, Maarten Vanraes a écrit : Op vrijdag 04 februari 2011 17:16:09 schreef Florent Monnier: Hi, I was (or I still am?) maintainer for these packages: http://maint.mandriva.com/listpkgs.php?owner=105 I have not read the 5000 mails of the lists yet, but I have seen the occurrence of buildsystem, so my question is should I join the team now to provide the equivalent packages, or should I wait (maybe wait that the first installable mageia is out) ? Yes, you can join now, no need to wait for first release ! the keypoint is that everyone who wants to be a packager (including mandriva packagers) needs some training (mentoring), so, the best way is There is no mentoring needed for previous mandriva packagers. My Mandriva mentor was Guillomovitch, but now as you said I've just seen the thread of Jérôme looking for a padawan, so Jérôme (or someone else) do you want to mentor me to become a Mageia packager / maintainer ? You can get a packager account directly and start importing and submiting packages. I see you created an account with login blue_prawn on https://identity.mageia.org, so you can send me your ssh key and I will upgrade your account to packager status.
Re: [Mageia-dev] New mockups about mageia-app-db
Le dimanche 6 février 2011 13:00:00, vous avez écrit : hi Samuel, these are my last 2 mockups about mageia-app-db project. i've added mageia- discuss and mageia-dev in the CC list so anyone can share his opinion about these mockups, giving us comments and ideas that can improve the tool. please, tell me what do you think about it homepage: http://img209.imageshack.us/i/mageiafindouthomepage.jpg/ browsing page: http://img696.imageshack.us/i/mageiafindoutbrowsingpa.jpg/ Hi, I'll answer directly to the other mails and then if I have more to add I'll add something in another reply. cheers, Marcello PS= i've noticed 0.1 release is ready, is it time for a blog post? Yes, we tagged the 0.1 release, but we haven't planned to communicate before version 0.2 because there are many many things that people are going to tell and that we just already know (like : usability is not good, filtering summary takes too much space, and so on). Moreover, counting from version 0.2 mageia- app-db will have regular synchronization from sophie (ie it will become alive :)), which is not the case at the moment. Regards Samuel Verschelde
Re: [Mageia-dev] New mockups about mageia-app-db
Le dimanche 6 février 2011 23:23:43, Fabrice Facorat a écrit : 2011/2/6 Marcello Anni marcello.a...@alice.it: 2011/2/6 Marcello Anni marcello.a...@alice.it: homepage: http://img209.imageshack.us/i/mageiafindouthomepage.jpg/ browsing page: http://img696.imageshack.us/i/mageiafindoutbrowsingpa.jpg/ sorry but who is supposed to use mageia-app-db ? power users ? dev ? casual/normal users ? Samuel said that the application must be useful both for newbies and power users ok for power users, but for normal users the Ui is too cluttered 1. left pane : Release Alpha vs Cauldron ? for a normal user, this means pretty nothing. If the user is looking for an application/package, then don't talk about release or repositories. What about using instead rpm categories, and then display theses kind of information in the package infos At the moment, I don't plan to put the different distribution releases in the left menu. In mageia-app-db, you browse one release at a time, which is already the case in version 0.1 : http://88.191.121.20/madb/master/ (in fact, you can browse packages from several releases at a time, but that's not the standard use case). Here is how we will determine what release to show by default to you : - if you are logged in and defined a preferred release (version 1, latest stable version, cauldron...), then it's used - else, we will try to detect what release your system has, from your user agent - and in last resort (not logged in, cleaned user agent or browsing from another system), the default is the latest stable release (this is the current behaviour). And you can switch from one version to the other by the filter in the banner (it will likely look like simple dropdown, or something else simple to use). Samuel
Re: [Mageia-dev] Dev Team Call To Action...
Le jeudi 27 janvier 2011 15:50:43, Colin Guthrie a écrit : 'Twas brillig, and Maarten Vanraes at 27/01/11 00:17 did gyre and gimble: - mageia-app-db (Stormi: PHP) would like some help. I've been a lot busier with work and other real life commitments of late , so have not had nearly as much time for Mageia stuff as I'd hoped. But in principle, I can help out here with the PHP side of things. IIRC Stormi is using Zend Framework which I'm very familiar with. Hi, thanks for the proposal (even if the framework is not Zend Framework but Symfony :)) ! However, you proved too useful on real distribution development stuff on Mandriva to be wasted on a side project, in my opinion... Unless you really want to be part of the mageia-app-db project, in which case you are more than welcome ! I remember you said you could help for security review. I don't know how to proceed, but if you have tips on that side (or want to try to find existing security flaws), it could help. Regards Samuel
Re: [Mageia-dev] 26/01/2011 meeting
Le 07/02/2011 22:11, Ahmad Samir a écrit : Personally, as I said before about upstreaming patches, I don't think I have enough experience to judge if a patch should go upstream or not, so that part I can't do. What do you mean by commented? A thing like: #patch from to fix truc Patch0: glibc-2.12-truc.fix.patch
