May 2012

[opensuse-project] How we will use the GSoC money
by Vincent Untz 18 Jul '24

18 Jul '24

Hi, (let's see how a public discussion about money goes :-)) The Google Summer of Code brings us great students, but also means that the openSUSE project will get $8000 (if I'm not mistaken) at the end of the summer. That's $500 per student. A while ago, I requested comments on my blog about what to do with the money, but didn't get any feedback. So I take this as "do what you feel is best", and this mail is about the plan. As a reminder, the main issue is that we will likely not have the … [View More]

22 38

[opensuse-project] download.opensuse.org IPV6 address breaks updates
by Gerald Pfeifer 15 Nov '13

15 Nov '13

I am seeing this with an openSUSE 12.1 system at home, and also a Factory system at work: % host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 And then, when running zypper patch or zypper up, I see Retrieving: repomd.xml [error] Download (curl) error for 'http://download.opensuse.org/update/12.1/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to 2001:67c:… [View More]

12 41

[opensuse-project] Scanny: week report
by Piotr Niełacny 20 Aug '12

20 Aug '12

Hi guys, this is my first report about scanny for #1 week: http://ruby-blog.pl/GSoC/2012/05/28/scanny-week-1/ -- Piotr Niełacny -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 12

[opensuse-project] Improving the bug management lifecycle/process
by Jim Henderson 20 Jun '12

20 Jun '12

OK, so this is something I'd like to start trying to get my arms around so we can have a more comprehensive approach to dealing with bug reports and increase the rate of resolution as well as the follow-up rate when additional information is needed. It seems that we have a few areas that we should be looking at: 1. There should be some sort of "screening" that takes place before a bug is accepted - to ensure that the devs aren't seeing multiple copies of the same bugs. I think it's … [View More]fair to say that those who write code would far rather *write code* than try to sort through duplicate bug entries. While it's likely there still would be dupes with a screening process, the incidence should be reduced. 2. There needs to be more of a "human" reply, especially on older bugs, that are being addressed. Looking at the current Bugzilla stats, I see that (for example) 12.1 has 183 bugs in a "NEEDINFO" state - there needs to be some sort of consistent follow-up to ensure that the info needed to fix the issues is provided, and if it isn't and the information can't be obtained (because the issue cannot be duped, those looking at it don't have the necessary hardware, etc), then the bug needs to be closed. 3. For older bugs, (such as on 10.3-11.3, which there are still open bugs on), a determination needs to be made as to whether the current supported releases have those issues, and if they do, the bugs need to be updated. If they don't, then the bugs need to be flagged in an appropriate way. 4. It would be extremely useful, I think - especially for the non-techie audience - to put some specific training together on things like (a) how to submit a bug and include the relevant information, (b) what to expect with your bug and how to monitor progress, (c) how to provide additional information when requested (and what to do if you've upgraded/moved to another version/changed distributions/decided to go back to Windows/MacOS/ whatever) so the bug can continue to be evaluated by those evaluating it. Ultimately, the goal of this project is to increase resolution rates, reduce the time to resolution as much as possible, and to visibly improve the bug resolution process so more people don't perceive (correct or not) that reporting bugs is useless because they don't get resolved (and actually, looking at the stats on bug status, I think it's pretty unfair to say bugs aren't getting resolved. I see, for example, that of the reported bugs on 11.1, for example, over 3/4 of the bugs are marked as resolved.) And overall across all releases of openSUSE, and SUSE Linux Professional/ SUSE Linux from 8.2 on, the bugs marked resolved are 13026/18285, which is nearly 3/4. 75% isn't bad (the Pareto rule is 80/20, and on 11.1 we're actually around 78% "resolved"), but I'm sure that if we can guide the process and streamline it, we can increase that. Of course those are just rough statistics and the reason bugs are marked as 'resolved' isn't included in that - and there is a further breakdown that can be done that might help identify trends that would be useful. There's clearly more that we should be looking at, but these four areas are a good place to start. For my own part, I'm willing to do more than talk and discuss the ideas, but it's going to take more than just one person working in his spare time to move this along. I also think something similar to this should be done for FATE, but that's perhaps a topic for another day. :) Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org [View Less]

19 101

[opensuse-project] Upstream Tracker Project - GSoC 2012 - Week 1 Report
by N B Prashanth 29 May '12

29 May '12

Hello! This is my first week work report for the Upstream Tracker Project. I have chosen to start my work by implementing the web interface first. This is because, by having a functional web interface, we could start crowd sourcing the data to proceed further. Also, the base work for the python scripts are already in place. Here is the list of things I have managed to do this week. 1. Created a rails application to manipulate records. Each record consists of data required to obtain the … [View More]

4 7

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 20:00 UTC
by openSUSE Meeting Reminder 29 May '12

29 May '12

Hello all, The biweekly project meeting will be held tomorrow at 20:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=30&month=5&year=2012&h… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, … [View More]

1 0

[opensuse-project] GSoC Weekly Report #1
by Saurabh Sood 29 May '12

29 May '12

Hi, This is my first GSoC report for the new One Click Install system. I had been busy with exams for some time, so, this is an update on the progress so far. I have started the user interface, and am closely following the mockup. So far, I have implemented two menus for the main screen and the settings. I am planning to implement the dynamic part of the interface as a set of Widgets which I will integrate in the main UI. On the backend side, I have implemented the parser for the YMP file, … [View More]

1 0

[opensuse-project] fdisk project - GSoC weekly report 1
by Davidlohr Bueso 25 May '12

25 May '12

Hi, This is my first report of what we've been doing regarding the fdisk redesign project. 1) What's been done in previous weeks, before SoC development officially started: - Consolidate and agree on internal fdisk API and data structures with Petr and mainstream util-linux community. - Isolate DOS specific label logic. This is important since DOS partition table context was deeply embedded in the heart of fdisk logic, making it impossible to implement a new API. Now DOS, like all other … [View More]

1 0

[opensuse-project] Does the project have a publicly accessible project management tool?
by Jim Henderson 22 May '12

22 May '12

General question to those more closely involved in oS project management - is there a tool we have access to that can help track tasks and progress on projects within the oS project? I'm thinking something like a Kablink (or Vibe OnPrem) task list. I've got Vibe installed at home with a limited number of users, but I'd rather track the bugzilla/bug process project in a more visible way than on a private server in my house. :) If we don't, I can set something on on the Kablink site so … [View More]

9 35

[opensuse-project] LinuxTag update
by Jos Poortvliet 21 May '12

21 May '12

Heya all, The current status of http://en.opensuse.org/openSUSE:LinuxTag Berlin - We've got a booth. I'm quite confident it'll be 14m2, have 2 tables and 6 chairs. Nothing else, LT is out of budget for furniture :( - We will have 40 crates of openSUSE beer to hand out for €1 donation to LT - We'll do that in collaboration with Fedora, which hands out hotdogs - I have a few hundred DVD's, some flyers and some posters here. Will probably walk into a copy shop to create some more. - don't know … [View More]

4 7

Main

Development

Information

Community

Social Media

Other

openSUSE Project