[01:13] السلام عليكم :) [01:14] السلام هليكم [01:14] عليكم [01:37] السلام عليكم [01:48] وعليكم السلام ورحمة الله وبركاته [01:51] هوا الاجتماع الساعة كام؟ [01:56] https://www.facebook.com/events/398385313509721/ [01:56] from 2nd of March till 4th [01:56] at 12:00am until Sunday at 11:30pm [06:10] helllo [06:10] fee 7ad hena [06:10] helooo [08:14] Hello [08:14] Where is everyone? [08:26] Mornin' [09:40] any coders here ? [09:56] egyDev, not me X) [10:14] élsäläm älýköm !! [12:12] seiflotfy, dude, when are you going to give your session? [12:24] show me the schedule [12:24] there's no schedule [12:24] oh [12:24] ok [12:25] seiflotfy, it's just me and you, I'll give bug triage and you what you zg :-) [12:25] so, just make your schedule and I'll announce it :) [12:25] today or tomorrow [12:25] like when od u want to give [12:25] i have a meeting from 18:15 to 19:15 [12:25] but then i am all open [12:26] today, and you can make it before that ? [12:36] gimmie 30 minutes to know [12:37] cool, thnx [14:18] السلام عليكم [14:19] منورين يا رجالة الأوبن سورس [14:19] Hi [14:19] cobra-the-joker, ?????? ?????? ????? ???? ??????? [14:19] Menopia: ?! [14:19] hi Eslam === mohamed is now known as Guest38582 [14:19] eh el a5bar, bttklmo 3n eh ? [14:20] طيب شكلكو مش بتتكلمو عن حاجة :D [14:20] انا كنت عايز اقول اني لسا مبرمج مبتدأ و اشتغلت بايثون [14:21] في مشاريع شغالة ... ولا لسه بتفكرو هتعملو ايه ؟ [14:21] و كنت عايز اتكلم في موضوع ال gtk [14:21] و ال qt [14:21] el sa3a 8 pm Ahned shams haydy session 3an el bug triaging [14:22] Menopia: سيشن صوتي علي سكايب ولا هنا ؟ [14:22] cobra-the-joker, hena [14:23] هنا [14:24] Eslam: هنا [14:24] ana awel mara ad5ol el IRC [14:24] momken 7ad yole hana ah el be7sal [14:25] mhassan01: كل خير إن شاء الله .. المفروض إنهم النهاردة هيددو محاضرة عن الbug tracing [14:25] و مكتوب علي الفيس إنهم هيعملو مشروع لخدمة أوبنتو و تحسينه [14:26] teab 3lshan asht3'al m3ko [14:26] a3mal ah w el mafrod akoon 3aref ah ? [14:26] mhassan01: شارك بإللي تقدر عليه [14:27] mhassan01, fe toro2 kter [14:27] momken targma aw development [14:27] aw 7ata artwork [14:27] w momken tenazl nos5et ubuntu 12.04 w tgarbha w law la2et ay bug te3mlha report [14:28] ana badres computer scince , momken afeed fe el 7ta bt3e development [14:28] ah [14:28] mhassan01: جامعة ايه ؟ [14:29] cairo uni [14:29] سنة كام :D [14:29] 3 [14:29] تمام ... أنا في رابعة CS [14:29] CS_IS [14:29] hhhhh [14:29] mhassan01, momken teshta4al be lo3'et eh? [14:29] cairo uni ? [14:29] اها [14:30] sory disconected [14:30] disconnected* [14:30] tamam , [14:30] Eslam: np [14:30] mhassan01: أنت كنت في الbooth إللي كان في الكلية ؟ [14:30] طيب انا كنت عايز اعرف هي ايه الفكرة عموماً من تجمعنا هنا [14:30] إللي كان تبع أوبنتو [14:31] da mash el sanade [14:31] enahrda elcommunity betetgama3 3ashan tetawar fee ubuntu [14:31] kan el sana el fateet [14:31] كنت فيه ؟ [14:31] ah [14:31] momken tetawar bee kaza taree2a [14:31] أنت إللي كنت بتوزع CD's ? [14:31] guys see this video http://youtu.be/ITk8PGBkMXQ :) [14:31] development, translation, bug triaging [14:31] mash bazabt kada [14:31] da sa7be [14:31] asmo shaker [14:32] أيواً [14:32] عرفته ... أنا كنت فاكرك هو [14:32] تشرفنا يا معلم [14:32] brb [14:32] w ana el 3amlt install l el ubuntu fe lab 7 , [14:32] shofto [14:32] i guess development a7sn [14:33] 1- فكرة مشروع [14:33] 2- تحديد لغة البرمجة [14:33] 3- المكتبة اللي هتُستخدم لعمل ال [14:33] gui [14:34] انا كدا بفكر صح ؟ [14:34] بس كنت محتاج اقرأ عن ubuntu api [14:37] Eslam: https://wiki.ubuntu.com/UbuntuDevelopment [14:37] ashams: can i help you [14:38] ashams: can u translate ofr me since i cant write arabic [14:38] but i can read it [14:38] so [14:38] @EgyParadox Thanks [14:38] Eslam: Error: "EgyParadox" is not a valid command. [14:38] Eslam: you are approaching the thing to sophsiticatedly [14:39] yes [14:39] i would like to approach to something advanced [14:39] Thanks EgyParadox for the link [14:40] you're welcome [14:40] have any one worked on Rapid PHP on windows ? [14:40] i wish i could see such a software on linux [14:40] fast, easy, simple, comfortable [14:41] also the shortcuts (keyboard shortcuts) are perfect [14:41] Eslam: u have an idea rightÜ? [14:42] i thought of something but it may not be useful [14:42] anyway i will say it in arabic [14:42] go ahead [14:42] هي الفكرة انا كنت بدأت فيها ووقفت لاني حسيت انها مش مفيدة [14:42] الفكرة استوحيتها [14:43] من Chrome OS [14:43] شاشة واحدة من خلالها بتعمل كل حاجة [14:43] في لينكس او اي نظام عموما [14:43] لما بتحب تفتح ملف [14:43] بتشغل ال file manager [14:43] لو حبيت تشغل اغنية [14:43] هتضطر تشغل [14:43] mp3 player [14:43] لو حبيت تشغل ملف ضغط [14:44] هتفتح برنامج برضوا [14:44] و هكذا و هكذا [14:44] but same things goes for chrome [14:44] i know [14:44] u open an app that however runs insdie the chrome browser [14:44] هقولك دلوقتي الاختلاف [14:44] neverthe less it is an app [14:44] لو ستمع عن elementary [14:44] i am in the board of elementary [14:45] :D [14:45] كانوا كاتبين عن تشغيل الملفات المضغوطة [14:45] و تصفحها [14:45] wow nice [14:45] :D [14:45] داخل ال file manager [14:45] marlin [14:45] هي غالبا اتطبقت بالفعل في مارلن [14:45] yeah [14:45] انا فكرتي ان ممكن كل حاجة تتعمل جوا مصتفح الملفات [14:46] زي مثلا تشغيل الأغاني [14:46] ممكن يبقي [14:46] بار من فوق [14:46] u want one UI to rule them all [14:46] و ال playlist [14:46] ok [14:46] ليها زرار [14:46] i got someting for you [14:46] show/hide [14:46] انا كنت مسمي البرنامج [14:46] something i worked on 3 years ago that does exactly that [14:46] gearbox [14:46] و كنت بفكر ف نظام Plugins [14:47] يعني فكرتي طلعت محروقة :D [14:48] http://seilo.geekyogre.com/uploads/2009/09/organise-fw.ogv [14:48] :D [14:49] watch this Eslam [14:50] okay minute [14:51] the idea of the journal manager is brilliant [14:51] Eslam: u know zeitgeist [14:51] ? [14:51] or gnome-activity-journal [14:51] seiflotfy, is the project maintainor of zeitgeist [14:51] yeah i know zeitgeist [14:52] Eslam: we need ppl to help us port activity-journal from gtk2 to gtk3 [14:52] i am ready to mentor [14:53] see i am still a beginner, can you in brief explain the porting process [14:53] as i understand the code is written for gtk2, you need it edit it to be suitable for gtk3 ? [14:54] yeah [14:54] or we can write from scratch which is my preference tbh [14:55] yeah from scratch is a good idea [14:55] there is also "Ahmad Sadiq" he is an ubuntu lover [14:55] he is from palestine [14:56] we worked on a simple text editor [14:56] but he preferes Qt [14:57] :D [14:57] بس انا عندي سؤال [14:57] فلنتفرض اننا جمعنا فريق [14:58] ازاي هنقدر نظبط الشغل [14:58] مثلأ [14:58] انا لسا مبتدأ [14:58] و اكيد هيبقي في ناس زي حضرتك [14:58] مستواها عالي [14:58] يعني ازاي نوفق بين مهاراتنا [14:58] انا و احمد صداق كنا بنشتغل علي موقع scrum do [14:59] بنحط مهمات و بنحدد اهميتها و صعوبتها [14:59] و بنشوف مين اللي يقدر يعملها [14:59] ok [14:59] 1) no hadretak [14:59] :P [14:59] 2) I dont use scrum really [14:59] i dont believe in scrum and i dont believe in what unis teach us [14:59] i never finished uni and never studies CS [15:00] علي فكرة انا كلية تجارة :D [15:00] سنة تانية [15:00] و فاشل [15:01] لو مكنتش فاشل مكنش زماني قاعد معاك دلوقتي :D [15:01] HAHAHA [15:01] i love u already [15:01] lol [15:01] so please read [15:01] http://programming-motherfucker.com/ [15:02] lol the domain is very funny [15:04] does that mean i am a programming motherfucker :D ? [15:06] very nice site, very nice t-shirt i want to buy one :D [15:08] Eslam: I learned that when it comes to programing what counts most is passion [15:08] anything else can be learned [15:08] totally agree ! [15:09] علي فكرة انا متحمس جدا و حابب البرمجة اوي [15:09] بس مشكلتي اني مشتت [15:09] مش بعرف استقر [16:01] شباب عندى سؤال [16:01] ؟ [16:01] منين اقدر احصل على اوبنتو 10.10 [16:01] لان موقع اوبنتو مش علية غير [16:02] 10.4 [16:02] ؟؟؟؟؟ [17:29] :D [17:36] hey Menopia o/ [17:36] hi ashams [17:38] Hi all, Your time to shine Shams :D [17:39] iahvector, hope I won't breake it :P [17:39] It's going to be great isA [17:39] I hope so, Thanks :) [17:41] ashams, yall hawol .. ana el sa3a 3andy tel3et UTC [17:41] ma3lesh bgd ma5detsh baly 5ales :(:( [17:42] Menopia, it is not a probelm at all, it's just 19:42 [17:42] so we didn't miss anything [17:42] not yet :D [17:42] hello guys [17:43] Hi sarhan o/ [17:43] UGJ was ok? [17:43] We did not have a venue [17:43] it's tooo cold in here [17:43] brrrrrrrrrrrr [17:43] why? :( [17:44] cold and raining all the day [17:44] on tunisia it's hot :D [17:44] * ashams feels envy :P [17:44] ashams, so you will did it on irc? [17:44] yep [17:45] it's almost the same :D [17:45] you will make a workshop? [17:45] ah, yeah a session then some q&a [17:46] and best practices [17:47] in english? [17:47] yes [17:47] or arabic [17:47] eng [17:47] :( [17:47] it was very hard to right it in arabic [17:47] write* [17:47] :) [18:01] ok, it's time to go [18:01] SA Everybody, This is Ubuntu Global Jam; [18:01] Should we start? [18:02] OK [18:03] Ok [18:03] I was announcing to the fb group [18:03] ok [18:04] A Class on Bug Triaging is happening NOW! [18:04] What is a bug?. [18:04] A bug is a problem with some software that makes it behave in a way different from it should! [18:04] If you have incorrect or unexpected result from your software that makes you *unable* to complete your work, then you found a bug!. However, not all problems are bugs... [18:05] What is not a bug? [18:05] Not all issues that obstacle your way are not always bugs, sometimes you miss a feature that would help a lot and help avoiding many other redundant work. Users may report such problems to the bug tracker and Triager should recognize it at once. [18:06] For example, *Support Requests*, these are when the user needs help with using the features of the software, but all problems s/he is facing are not related to software itself but to how s/he uses it. [18:06] Another example can be, *Feature Requests*, these are when you find that a software is lacking some feature, whether this feature is essential or trivial, it's not a bug, it's a request to add a new feature. [18:07] Another example can be, *Feature Requests*, these are when you find that a software is lacking some feature, whether this feature is essential or trivial, it's not a bug, it's a request to add a new feature. [18:07] But, this does NOT mean that Support Requests and Feature Requests shouldn't be reported, but each has it's own method to request. [18:07] To get support, a user can simply go to https://answers.launchpad.net/ubuntu and ask his/her question, this is the traditional way, however, there are many other successful ways, like http://AskUbuntu.com . #ubuntu and #ubuntu-beginners on Freenode, and even by contacting some friends from your LoCo Team.... [18:08] Getting back to bugs... [18:08] What are types of bugs? [18:08] Generally, there are 2 different types of bugs: 1)Crash bugs, and 2)non-crash bugs. [18:08] Let's start form the end, 1) *non-crash bugs* are any form of problem that obstacles or slowing the intended productivity. These should be reported by running "ubuntu-bug (Make use of it: http://pad.lv) [18:09] The other type [18:09] 2) *Crash bugs* are that kind of problems that cause the software to collapse either while loading or while running. This kind of bugs has it's very special nature and gets handled in a special way too. Will come to this later, in detail. [18:10] Ther's another type of bugs, that's bugs related to Ubuntu itself [18:10] not to the software generally [18:11] and those should be fixed by Ubuntu Developers [18:11] Ubuntu has it's own patches to software to adjust it for other Ubuntu specific Components and configurations. [18:11] A good example of Ubuntu-specific changes are making all applications recognize Unity Launcher and notification behaviours across the system, these changes should be applied to all applications. Ubuntu Developers reserve the right, by nature, to change software code to meet Ubuntu's needs. [18:12] Now its' almost clear about bugs itself, but what is bug triaging? [18:13] A Triager is a person who do almost everything for a bu but fixing it :D [18:13] A Triager's work starts when there's a report on the Tracker [18:14] Simply, A Triager's job is to answer the the following questions about a Bug: [18:14] a)Where does that bug *REALLY* come from? [18:15] b)How did it happen, Steps to reproduce. [18:15] c)Does the Report has all information needed to start with fixing it? [18:15] We can understand it better by knowing what it is NOT [18:16] It always worthy to acknowledge that Bug Triaging is not Fixing Bugs, it's just to do everything with a bug till it gets ready to get Fixed, But NOT fixing... Fixing is another story. [18:16] Answering these questions is a matter of practice and changes per bug [18:17] Why Bug Triaging is that important? [18:17] A bug takes 2 to 8 months from the minute it reported to the minute it Fix Released. Long period... [18:17] Now imagine if a developer has to deal with users to ask them to give more information about how and where the bug occurred? [18:18] That would waste a lot of time, right? [18:18] So, what if we made developers work on fixing bugs only, and we do everything else. Won't that save us more time? [18:18] Well, that's why Bug Triaging is Important, because without it, Ubuntu can not actually fit into 6 months development cycle. Or it will be released every 6 months without any significant changes or bug fixes ;O [18:19] A bug triager's work can be like hell some times and other times it can be pretty clear and direct [18:19] Bug Triaging can be realy hard if s/he doesn't get enough information for the reporter [18:20] but unluckily, not all bug reporters can give all needed info [18:20] so, there's *Apport* [18:20] What is Apport? [18:21] Apport is the Bug tracing and reporting in Ubuntu, it detects crashes(in non-stable releases) and automates the process of collecting needed information from the victim machine and auto reports the bug to Launchpad Bug Tracking System. [18:21] Apport is not enabled by default in stable releases, even if it is installed, and there are two ways to enable it: [18:22] First One: If you want to debug a specific program once, just open your Terminal and run: [18:22] sudo service apport start force_start=1 [18:22] Then you can simply trigger the crash again, and Apport's dialog will show up with instructions to report a bug with traces. Apport will be automatically disabled on next start. [18:23] Second One: If you want to enable it permanently. Open your Terminal and run: [18:23] sudo nano /etc/default/apport [18:23] then change "enabled" from "0" to "1". [18:24] But Why Ubuntu has Apport and doesn't just use any other bug reporting application? [18:24] Why Apport? [18:24] That answer is pretty direct: [18:25] In 3 Points..... [18:25] 1) Not all users know how to collect needed information for reporting a bug, right? [18:25] This would make Ubuntu receive a not-enough amount of feedback and thus it affects development action. Plus, there's no such easy bug reporting application that Ubuntu can get into the distro. So, Ubuntu developers had to make it by hand and from scratch. [18:26] 2) It detects Crash bugs and auto reports it(in non-stable releases). Crash bugs may not be reportable without it. [18:26] 3) Existing bug reporting applications like bug-buddy or krash are specific to a particular desktop environment and it's not easy for a distro developer to utilize it to adapt to the specific needs of his distro. Also, other bug reporting solutions do not work for crashes of background servers (like a database or an email server), and do not integrate well with existing debug packages that a distribution might provide, like hooks. [18:27] What are Apport hooks? [18:27] Apport Hooks, are scripts added to a package that tells Apport what are the needs information(i.e. logs and config files) when reporting a bug in that package. [18:28] needed* [18:28] When installing a package that has a Apport Hook, it extacts it to */usr/share/apport/package-hooks*. While reporting a bug about *hot-pkg* (for example), Apport will look in /usr/share/apport/package-hooks to find if there's a hook named *source_hot-pkg.py*, if it found it, it runs it. [18:29] The job of that script is to collect all needed information about that package and save it to a directory, then Apport uploads these information to Launchpad BTS while reporting the bug. [18:30] and it'll be attached to the bug report as seen on this image: http://ubuntuone.com/65GvZqmIYZ56ceEinI2YKu [18:30] Find more about Apport here: https://wiki.ubuntu.com/Apport [18:31] Apport would not be able to do this without full compatibility from Launchpad [18:32] Launchpad BTS is a great way to track bugs..... [18:33] What is launchpad BTS? [18:33] Every peace of software should have it's own BTS(Bug Tracking System), that receives bug reports from users and manages it during the life cycle of that bug. [18:33] Ubuntu uses the Launchpad BTS, also called *Malone*, for all bug work. [18:33] Malone, receives bug reports, keeps information files and tracks the status of a bug on the upstream BTS. [18:34] Upstream: Ubuntu is a distro that collects it's components from everywhere and puts it into one place. A distro is like a fall, of a river, that all components fall into, thus it has a stream of development above all other development happen in Ubuntu. [18:35] Bug Triagers deal with Malone all the time... and it's quite lovely [18:36] More on bugs living on Malone. [18:36] Bug Status [18:36] What is bug status? [18:36] A bug has a life cycle that can take from 2 to 8 months to get fixed. All effort happens in Ubuntu is solely a collaborative work. Means, everybody has the right/needs to see what is happening in every bit of the system. [18:37] what kind of bug it can be ? [18:38] any type of bug [18:38] like !!!!!!! [18:38] Without that, a real big problems and waste of time can occur. Simply because, if two developers know about one bug and each one of them don't know about each other's activity with that bug, they can work against each other and waste time on fixing the same bug, instead of fixing *two*. [18:38] samman, you need an example of a bug? [18:39] YEs [18:39] https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/24061 [18:39] Launchpad bug 24061 in apt (Ubuntu Precise) "GPG error with apt-get/aptitude/update-manager behind proxy (BADSIG 40976EAF437D05B5)" [High,In progress] [18:40] That's a well known one [18:42] !bug 1 [18:42] Launchpad bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/1 [18:42] For discussion on Microsoft software, or help with same, please visit ##windows. See http://launchpad.net/distros/ubuntu/+bug/1 http://linux.oneandoneis2.org/LNW.htm and /msg ubottu equivalents [18:42] see how ppl change bug status to reflect what they do, like on: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/24061/comments/43 [18:42] Launchpad bug 24061 in apt (Ubuntu Precise) "GPG error with apt-get/aptitude/update-manager behind proxy (BADSIG 40976EAF437D05B5)" [High,In progress] [18:43] We'll discuss bug status in detail [18:43] Thus, a bug status should always acknowledge what's happening with that bug till it gets fixed. [18:43] Launchpad Bug Tracking System(lp bts) has some realistic status options: [18:44] *New*: Bugs are submitted with this status and they still need to be triaged. [18:45] Incomplete: Set bug to this status if you need to ask the *original* reporter a question. [18:45] Note: Bugs with this status will give the reporter 60 days to reply and change status, else lp bts will auto-set bug status to *Expired*, so use it with care. [18:45] See status on launchpad either by getting to the previous bug link, or by just veiwing this screen shot: http://ubuntuone.com/5vKRiVnJQjKSNYnJX51pva [18:46] Status: *Opinion*: Use this bug status to mark that the community did not decide whether it's a bug to be fixed or not a bug at all. [18:47] This status acknowledges that the report is *Closed* and developers can look at something else, but lp bts will allow discussing and commenting till a decision shows up, then anyone can set it back to *New* and Triaging work will be started over. [18:48] Status: *Invalid*: This status declares that this is not a bug at all, but rather an intended behaviour. [18:48] It will close the report and won't allow further discussion. [18:48] Status: *Expired*: It came to be a bug status after 60 days of setting it to *Incomplete*. Or, a Triager can set it him/herself but it's not a recommended action, just ask your question and set it to *incomplete* and a bot will take care of it. [18:50] Status: *Confirmed*: Set it to acknowledge that you're sure that the described bug is really there. [18:50] Status: *Triaged*: After being set to *Confirmed*, a Bug Control member will come and check if that report has all needed information to start working on it. [18:50] AND to here, the bug triage is almost done. [18:51] From now on, a developer will be almost in charge of that bug, but a triager still can change status as part of his/her work [18:52] Status: *In Progress*: This status will be set the person working on that bug, and that declares that s/he is now in charge of it so bug triagers should ask him/her for update before changing Status/Importance. [18:52] Status: *Fix Committed*: That shows that a developer has fixed it but it wasn't uploaded to the Public Archive yet OR it was fixed somewhere Upstream. [18:53] Fix Committed is also used when an updated package exists in a -proposed repository i.e. lucid-proposed. [18:53] that wil be waiting to get moved to the main archive [18:54] Status: *Fix Released*: That shows that a bug is now fixed and uploaded to Archive and people can now update their systems. [18:54] If a bug is fixed in the current development release, it is Fix Released. If the bug also needs to be fixed in a stable release, use the "Target to release" link to nominate it for that release. [18:55] We still have one Status; [18:55] Status: *Won't Fix*: Bug Reports with this status are almost not pure bugs, but rather a change to some feature that some ppl see it doesn't behave correctly that way and others see it behaves correctly :) [18:55] Thus, it can be used with bugs too controversial. [18:55] Triager can also use it to mark a bug that was nominated to be fixed in some release, but it won't be fixed for some reason! [18:56] Plus, it can be used for *Feature Requests*(reported as bugs), to declare that developers do not want to implement that feature for some reason. [18:56] More Here: https://wiki.ubuntu.com/Bugs/Status [18:57] Last thing, is to be a good triager and that's the hardest part..... [18:57] No body knows everything and no body born with Linux Knowledge. [18:57] If I tried to triage bugs for some software I do not use or know about, I'll hate bug triage for ever. [18:58] Start triaging with the simplest bugs first to get used to lp bts. [18:58] Then get a bit deeper as you go by time.. [18:58] If you need anything any time, join to #ubuntu-bugs , #ubuntu-beginners or #ubuntu and ask. [18:58]