Re: Reply for Call for help from KDE Team
On 05/07/2014 10:32 AM, sibi kanagaraj wrote: //, I would say that cleaning some old bugs would help us. That means checking bugs that have no activity for quite some time (let's say 6 months), verify that the bug is still there and close it otherwise. In any case, add a new entry in the bug log saying what you found.// I have not done this before . So , I decided to wait for few days and observe the happenings and thought that I could figure out what is to be done . Daily I see some 10-12 bug tracking mails .Apart from that , I have not been able to trace out whats happening . If there is any documentation on what is to be read , I will read it and start checking the bugs . You could start here: https://www.debian.org/Bugs/ The best is to validate if you can reproduce the bugs on your setup. If yes, further investigate whether it is a packaging bug or a bug in KDE upstream. If an upstream bug, check in upstream tracker if there is already a bug filed. If not filed, file a bug upstream and associate the Debian bug to it. If it is a packaging bug, please add that detail in the bug report. Over time you will start fixing the bugs. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/0sto3b-2og@news.researchut.com
Re: Reply for Call for help from KDE Team
¡Hola sibi! El 2014-05-07 a las 10:32 +0530, sibi kanagaraj escribió: //, I would say that cleaning some old bugs would help us. That means checking bugs that have no activity for quite some time (let's say 6 months), verify that the bug is still there and close it otherwise. In any case, add a new entry in the bug log saying what you found.// I have not done this before . So , I decided to wait for few days and observe the happenings and thought that I could figure out what is to be done . Daily I see some 10-12 bug tracking mails .Apart from that , I have not been able to trace out whats happening . It's not always easy to know what's happening. :) I think the motto for this call for help could be don't be affraid to ask for help. So you are encouraged to ask, using irc has some advantages for this, but it's perfectly fine if you prefer mail. Rereading what I ask you to do, it's a quite hard task, as it's phrased in a way that makes me think do this query and work on the results, but the query part is not easy at all. I finally managed to get a list with a very unefficient sql query to udd.debian.org: select distinct bs.id, bs.status, bs.last_modified from public.all_packages as ps join public.all_bugs bs on (ps.package = bs.package) where ( ps.maintainer_email = 'debian-qt-kde@lists.debian.org' or ps.maintainer_email = 'pkg-kde-ext...@lists.alioth.debian.org' ) and bs.status != 'done' and bs.status != 'fixed' and (bs.last_modified + interval '6 months') now(); For which you need to do the query from alioth as is documented here: https://wiki.debian.org/UltimateDebianDatabase/ And sort of understand the database schema: https://udd.debian.org/schema/udd.html#public.view.all-bugs All of it is way beyond what I intended as a first task, I'm really sorry. Please, if someone has a better way to get this results, tell me. If there is any documentation on what is to be read , I will read it and start checking the bugs . There is some, but its quite dispersed, improving the documentation to become a more welcomming team is one of the things that we need to do, please don't forget your first doubts so you can help us improve the experience. -- If a million people believe a foolish thing, it is still a foolish thing. -- France's Rule of Folly Saludos /\/\ /\ `/ -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140507084823.gp14...@gnuservers.com.ar
Re: Reply for Call for help from KDE Team
Good afternoon, I too am planning on helping out and have been reading the recommended web pages. On 7 May 2014 09:48, Maximiliano Curia m...@gnuservers.com.ar wrote: It's not always easy to know what's happening. :) Is this part of the problem? It seems that there isn't a clear bug tracker like launchpad for ubuntu or bugzilla or Fedora. There appears to be no concise dashboard of work items and tickets for the group. I thought that the ideal list to work with was: https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-qt-kde@lists.debian.org;dist=unstable#_0_3_4 However you are implying better data can be gotten from udd: https://udd.debian.org/bugs/?release=jessiemerged=ignfnewerval=7flastmodval=7rc=1sortby=idsorto=ascformat=html#results It would be nice if someone gave direction for a sprint in which we have a group start with sid, a group with jessie and perhaps another with wheezey on virtual machines. Then in week one we work through the Outstanding Important - Unclassified to classify them either by marking as upstream, wontfix or reproducible. Then work on the next set. Perhaps make it the first week of each month to do the same thing? I've been wondering how much automation is surrounding the whole packaging process? I've not yet found a code review for the packaging process. It appears to rely on packagers testing and hoping that others also test: https://wiki.debian.org/DebianMentorsFaq#How_do_I_add_a_new_package_to_the_archive.3F I was hoping that a system that automates building the package, installing it and then throwing up any warnings from the install process, possibly for x86 and amd64, however I've not yet bumped into anything. These are just some of my work in progress thoughts so far. I've not discovered everything about debian yet, but I am getting to understand things a little better each day. Regards Phil Hannent
Re: Reply for Call for help from KDE Team
Hi all , //, I would say that cleaning some old bugs would help us. That means checking bugs that have no activity for quite some time (let's say 6 months), verify that the bug is still there and close it otherwise. In any case, add a new entry in the bug log saying what you found.// I have not done this before . So , I decided to wait for few days and observe the happenings and thought that I could figure out what is to be done . Daily I see some 10-12 bug tracking mails .Apart from that , I have not been able to trace out whats happening . If there is any documentation on what is to be read , I will read it and start checking the bugs . -Sibi On Fri, May 2, 2014 at 8:37 PM, Maximiliano Curia m...@gnuservers.com.arwrote: ¡Hola sibi! El 2014-05-02 a las 18:39 +0530, sibi kanagaraj escribió: I saw a mail in mailing list , on call fro help from the KDE team . I would like to know if I could be of any help . Assigning tasks is way too hard, it's easier for us if you tell us which of the tasks listed in the call for help [1] interest you and how can we help you with it. If you still prefer to have a task assigned, I would say that cleaning some old bugs would help us. That means checking bugs that have no activity for quite some time (let's say 6 months), verify that the bug is still there and close it otherwise. In any case, add a new entry in the bug log saying what you found. [1]: https://lists.debian.org/debian-devel/2014/05/msg8.html Have fun, -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. -- Dennis Ritchie Saludos /\/\ /\ `/
Reply for Call for help from KDE Team
Dear team , I saw a mail in mailing list , on call fro help from the KDE team http://mail.kde.org/pipermail/kde-india/2014-May/001237.html. I would like to know if I could be of any help . -Sibi
Re: Reply for Call for help from KDE Team
¡Hola sibi! El 2014-05-02 a las 18:39 +0530, sibi kanagaraj escribió: I saw a mail in mailing list , on call fro help from the KDE team . I would like to know if I could be of any help . Assigning tasks is way too hard, it's easier for us if you tell us which of the tasks listed in the call for help [1] interest you and how can we help you with it. If you still prefer to have a task assigned, I would say that cleaning some old bugs would help us. That means checking bugs that have no activity for quite some time (let's say 6 months), verify that the bug is still there and close it otherwise. In any case, add a new entry in the bug log saying what you found. [1]: https://lists.debian.org/debian-devel/2014/05/msg8.html Have fun, -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. -- Dennis Ritchie Saludos /\/\ /\ `/ signature.asc Description: Digital signature
