Search Results: "zobel"

3 January 2007

Felipe Augusto van de Wiel: 2 Jan 2007

Happy New Year! Happy 2007!

And a really happy one!
After the cloud of ideas and subjects on the last post, giving the clear idea that I should keep this blog more up-to-date, here is an important note that is missing (including old news that I should had post but didn't, sorry for that). I'm aware that a few people are interested in how the Debian NM process evolves from person to person, on my last update on that topic, I told you that I was recommended to the DAM by my AM. Almost three months later (2006-11-18) Myon (Christoph Berg, Front Desk Member) couldn't find my final report, he pinged my AM and one week later everything was fine again and I got approved to the next step: DAMnation. On the Christmas' evening I got a nice gift from Joerg, DAM approval. Yesterday (2007-01-02) I got the nice e-mail with the subject: New Debian maintainer Felipe Augusto van de Wiel (Thanks to James Troup, aka, elmo). The entire process took me 8 months and 10 days. I would like to say thanks to everybody that helped me pass thru this experience: Otavio Salvador (my advocate and mentor), Christian Perrier and Luk Claes (Mentors and Uploaders), Clément Stenac (my AM), Christoph Berg (Front Desk), Joerg Jaspert and James Troup (DAMs). They are directly involved in my NM process, but they were not alone, thanks for every single person that helped me with tips and hints, that took some time to teach me and all the people behind different projects in Debian (I really start naming everybody but then I realize that it got very large for Planet): Debian Brasil, Debian Volatile (aba, zobel, sgran), Release Team, Debian Women, Debian i18n Task Force and Debian l10n Brazilian Portuguese, Debian Weekly News Team, buildd.net project, Alioth admins and staff, Debian Installer Team, Debian Kernel Team, Debian Mentors, DebConf Team, OFTC Staff, Debian QA Team, Debian Doc Team, Debian WWW Team, Debian Admin Team (DSA)! People, you know who you are, thank you VERY much! You can check my Status Page to see more details about my NM process and more information about the acronyms used on this post. Now, Brazil has 17 Debian Developers (not counting the one that already retired). :-)

7 December 2006

Martin Zobel-Helas: Preparation for r5 started

I just sent the first preparation mail for r5, which will either happen end of December or 48h before the release of Etch, whatever comes first. It currently does not cover all packages, as there are still quite a couple (more then 20) packages that need to be accepted from p-u-new by ftpmaster. Stay tuned for more information during the next days.

20 November 2006

Andreas Barth: Bugs to sell

There are a couple of bugs around where it would be a shame to remove the package (or where it is next to impossible), which are hard to fix for outsiders but should be way easier for people inside: There are a couple of more such bugs available, please feel free to visit our RC bugs list yourself.

12 November 2006

Andreas Barth: Experimental and autobuilding

Experimental is autobuild, but on an best-effort basis (which is a different thing than what happens with unstable). In other words, it can happen that a package is not build on all architectures, and nobody does anything to fix that. If that happens to one of your packages, please contact us (Martin Zobel or me), and we'll try to fix that. I just have rescheduled glibc in experimental on two architectures.

11 November 2006

Aurelien Jarno: Experimental is not autobuilt (at least for glibc)

Martin, I can’t let you say that experimental is autobuilt. I have uploaded a few versions of the glibc to experimental in the last few months and only arm, hppa and alpha have tried to build them. Before the summer mips and mipsel also have tried to build the experimental glibc. And the last version has not been tried on alpha, despite the fact it includes a fix and should now build correctly on this architecture.

Hopefully I have most Debian architectures at home, but alpha, m68k and ia64, so I can build the glibc on my own machines. For m68k and ia64, I can use debian.org machines. Concerning alpha, the debian porting machine, ie escher.debian.org, is locked down since the compromise about 4 months ago. And no answer to my mail to debian-admin… Hopefully a user kindly gave me an access on his machine, thanks. The glibc 2.5 is now building correctly on this machine, but I can’t upload the package because I can’t trust the machine. That really sucks. What about removing alpha from the release architectures? After all, it fails to comply with the etch candidate release architecture criteria for months. Update: Some build daemons had glibc in “weak-no-autobuild”. Thanks Martin for fixing that.

10 November 2006

Martin Zobel-Helas: Does anyone actualy read mails from the release-team?

Yesterdays statistic from debian-devel-changes: 17x “New upstream release” with only 2 packages actualy fixing bugs! 5x “Initial Release“! Guys, that close before the release, use experimental, that is what it is for. And it gets autobuilded for almost all architectures (1 buildds (s390) currently down). Thanks for helping to get the release out in time. No Tags

17 October 2006

Steve McIntyre: BSP Marathon - Munich, 14 - 15 Oct 2006

The weekend of the 14th-15th October saw my third BSP in as many weekends, this time in Munich. Andreas Barth was in charge of the organisation, and the LiMux development team were kind enough to host us for the weekend at their offices in the centre of the city. Andi, Zobel and I headed into the office early on Saturday morning, ready to start hitting RC bugs. Others joined us during the morning, and we got to a total of 10 people working on fixing bugs. Personally I looked through many of the bugs listed on Andreas' page. It was heartening to see that a very large number of the RC bugs were already well in hand, with patches available and in lots of cases uploads already made. I spent some time looking into #389287, #392398, #389375 and #262440. I also helped out several other developers with their own bug fixes, giving out accounts on my wide range of machines at home so that they could debug on different architectures.

BSP We worked late into the evening, ordering in pizza and then later cooking in the offices. I moved onto some more debian-cd hacking later on, making real progress and getting almost to the point of having my multi-arch CDs working. As always, there was a lot of discussion about the general issues in Debian, especially the 4 GRs that were due to finish that evening. On Sunday morning, things started slightly later as we took breakfast at the office. There was more discussion of the GRs, and the results were generally well received by the group. We continued looking into the RC list; I investigated #389434, but struggled to make much progress. At lunchtime, we quickly(!) headed into the city to see the famous Glockenspiel at the city hall, and went for a quick tour of the historic city centre so that us non-locals could see something of the city outside of the office. We returned and picked up on the bug-killing for a couple of hours. Then the LiMux guys showed us some of their work, and gave us a demo of the project. More on that later... Unfortunately, I had to head back for my flight comparatively early this weekend so I couldn't stay around for very long after the demo. Despite the last-minute attempt by an S-Bahn ticket machine to delay my trip to the airport, I got back without incident and even landed early at Stansted. The Germans I met this weekend were very serious about getting work done, and their efforts are much appreciated. With more people helping to reduce the RC bug counts, we should have no problem releasing Etch in December. Let's keep up the good work...! As always, my meagre attempts at photography are online now.

14 October 2006

Martin Zobel-Helas: How DWN *could* be relaunched

I had a nice discussion recently how we could relaunch DWN. Idea was, that if we would get more contributors for times.debian.net, we could easyly produce a weekly summary out of that. But for that, we need more contributors. So if you think this is a good idea, and are good in writing, feel free to post possible submissions to debian-publicity@lists.debian.org. No Tags

19 September 2006

Jorge Salamero Sanz: Hello Debian Planet!

This is my first post in Debian Planet. Last sunday I was asigned an AM, zobel. He's a very helpful guy. It was a great birthday gift because I didn't expect to get an AM so fast, NM is know for being a long process. I've begun to work in the first steps of P&P questions already although I'm not going as fast I'd like because I've hitten by tons of TODO tasks just after finishing exams but I hope to get more involved in the Debian community and development quickly.

15 September 2006

Martin Zobel-Helas: First preparation mail sent

For the next upcoming stable update, which should happen around October, 16th, is just sent the first preparation mail. Procedure is as usual, intervene if you think, we do something completely wrong here. An up-to-date version of my mail can allways be found here. Next update on that mail will follow in about 10-15 days.

6 September 2006

Martin Zobel-Helas: Indian Summer in Germany

The best you can do on a tepidly summer evening like today? Drinking a glass of single malt scottish whisky while reading a good book and enjoying the sunset.

4 September 2006

Martin Zobel-Helas: Bug Squashing around the world - more about the BSP-Marathon

This blog should serve both as a reminder of the planned BSPs around the world the upcoming weekends and as a proposal for some tasks to tackle then. At this point there are two “real-life” BSPs planned for this weekend, 08th-10th September in Vienna (Austria) and Z rich (Switzerland) and another two BSPs planned for the weekend 15th-17th September in J lich (Germany) and San Cristoba (Venezula). If you would like to attend one of these parties, you can find additional links regarding these events here. First a few necessary words on coordination: #debian-bugs on irc.debian.org will be the main channel for overall coordination. Do not hesitate to ask there before tackling any task; there will certainly be people available that can advise against tackling problematic tasks or tasks already worked on, and give general advice. When working on specific bugs, please claim them or let a DD claim them for you. See also here for list of claims. Tasks that can not be expressed by a claim but are big enough to warrant a notice for others should be noted on http://wiki.debian.org/OngoingBSP or pages linked from there. There should be plenty of bugs for all levels of complexity, programming language or legal skills and time requirements. So if you never attended to a BSP before and want to help, now is the right time to start. The RC Bug Squashing HOWTO by Steve Langasek gives a good introduction and is probably a must-read for beginners. But don’t hesitate to ask questions in #debian-bugs, we will be eager to help you to do some work. :) Non-DDs can also easily contribute by creating patches and/or testing existing ones. Just send them to the related bug report, a DD can easily pick it up from there. See also the end of this mail for a list of useful links. Procedures:
During the BSPs we should use a 0-Day NMU policy again, that means uploads that fix RC bugs that are more than a week old can be uploaded directly. If you feel unsure about a patch and/or if the patch is rather invasive, please consider asking on #debian-bugs for review and/or giving the maintainer some time to react by uploading to the DELAYED queue. If you are unsure whether your package upload might break an ongoing transition, PLEASE speak up on #debian-release and ask for advice there. Help Etch forward: I personally will attend the BSP in J lich and hope to see many of you during that weekend there or on IRC.

3 September 2006

Martin F. Krafft: Never give up

Scott, the first thing I want to say in response to your post is that you are not alone. I did not know someone was attacked for wearing an Ubuntu shirt in Helsinki, but I did witness at least one "Fuck Ubuntu" incident, and it seemed that Ubuntu jokes and snaps at the new distro were very common. I find this utterly childish and stupid. I am sorry for everyone who was offended. But please don't blame or condemn everyone in Debian or the whole project for the actions of some of its members or followers. You've already linked to my thoughts on the Ubuntu-Debian situation, so I need not cover any of that anymore. I wouldn't want to either, because believe it or not, this article got me flamed by Ubuntu developers just way too many times, in personal mails as well as in forums. Instead, let's look at the now and then this time. I've heard a few developers express their unhappiness with Debian in the past year, much in the same way that you did. Not always was it related to Ubuntu, but quite often it was. There are newcomers to Debian who shake their head in disbelief how anyone can work in a project such as Debian, and there are the veterans among us who seem to concede that Debian has slipped away from their ideals and it's just not fun anymore. It's not hard for me to understand each of them. I've followed Debian for nearly a decade now and thus tracked how it changed over time. We are one of the largest free software projects, and size never comes without problems. So while the Debian project used to be an association of geeks enjoying their focus on technical excellence, the sheer growth of our project called for many other fields to be managed, and we did not always handle this increase in complexity very gracefully. After all, we are all just geeks who want to have fun, aren't we? As a result, several aspects of our project have been said to "stagnate", and parts (and parties) have diverged. As a volunteer developer, it's not always fun to run up against walls and find that your innovativeness is met with stubborness or simple silence. I say "not always" because I think it's really just a matter of perspective. Over the years, Debian has seriously affected my life, the way I look at things, the way I interact with people, and the way I do stuff. I am eternally grateful for much of that. But the learning process has not stopped. What Debian needs is a stronger grasp of the big picture. In joining all the other developers who are already doing excellent work in that direction, what better learning opportunity could there be to approach large-scale project management, away from academia and the corporate world. For me, this is a very interesting perspective of a fascinating project, one that directly relates to my current research endeavour. I was asked recently how we "control the anarchy", and the first thing I said was that "control" was not the right word. Debian is not about control, it's about the flow. If it's not going your way, you can swim against it, you can pull out, or you can try to find ways to change that flow, bottom-up rather than top-down. I think David's idea of a steering committee is an excellent one, and I'd be happy to dedicate time to such an effort. I wouldn't call it "steering" though, as that seems too active. Rather, I envision a group of people dedicated to keeping track of the big picture (obviously in close contact with the release team) to which developers can turn if they need advice. In the last few years, I've often asked myself why the heck I don't just give up, instead of continuously running up against problems that seemed hopeless. Even now, I sometimes think that I should have just pulled the plug, but my answer has always been no, and it looks like it'll remain that way. Why? Because we've come an incredibly long way, and that by itself provide for a lot of motivation. Mostly, however, I decided to hang in there because I tend to like challenges, even if at first I have no idea how to conquer them. When I then look at what some of the people are doing for the project, I come to realise that there are solutions, even if the road is a long one. You (Scott) strike me as a very innovative person, and not only because the problems you and I are looking at tend to overlap to a large degree. I strongly respect you for your work, and Canonical certainly deserves a tip of the hat for providing you with the environment to do so. Sometimes, I even envy you a little, simply because I haven't been able to get down to coding solutions as much as I would have liked to and you've beaten me to the punch on things like HCT or upstart -- even though my work in that area has been mostly vapourware, so there was no real punch to which you've beaten me... I think you'll know what I mean. Yet, scanning some of your older blog posts, I got the impression that you weren't always happy with the way you have to do things at Canonical. And still, you're enthusiasm for working on your projects is astounding; it wasn't hard to come to that conclusion just a week ago, even though we've only talked briefly in Cambridge. Have you asked yourself why that is? I'll go out on a limb and postulate it's because of your innovativeness, because of your urge to push technology further, to implement cool things, and to break free of the cruft that comes with 13 years of Debian and several decades of standards la POSIX and SysV. Debian is too conservative for you, and all the cruft weighs heavy. Ubuntu, on the other handy, is "fluffy" and not afraid to forge ahead, and you've been an active part of it from day one. As much as I hate to see you "with them" rather than with us, I think you've found your place. And so have I. I'm less about coding than I am about integration, and there's work to do. Debian is a massive project with an amazing track record of achievements to look at. And it has problems. Well, great! Let's attack them. Never give up. Another reason why I've stayed with Debian is because there are people who think alike. Three years ago, I would have been able to give you a long bullet lists of hopeless problems in Debian. If you ask me today, I would have problems arguing their hopelessness, for I've seen plenty of developers taking it up with these problems, and in the meritocratic way. Our release team is doing a fantastic job and I've never felt so positive about the promise we made with the next release. People like J rg, Zobel, Rapha l, the two Alex, Meike, Christoph, and the many others I'll leave out only in the interest of brevity (the list is longer and doesn't only span Germany and France) are doing great work, and that is truly motivating. And I ought to mention explicitly our leader, Anthony, who's been doing an excellent job so far. I hope he can keep it up. Also, take a look at our IRC channels. I would have to be lying if I'd say nothing has changed. And the same applies to mailing lists. We still have a reputation to deal with, but if you stop listening to what people say and actually take a look, I think we've come a long way. I'd even say it's become more fun to work on Debian again! I think we owe a lot of that to Debian Women. I am definitely proud to be a member of this community (with which I mean Debian as a whole, not just Debian Women). I think I could continue this blog post endlessly. Let's not. You (Scott) may not be a fellow DD any longer, but you remain a fellow D, and I hope we'll continue to let our cooperation prosper. Now if only you had told me that "getting upstart installable required changes to twelve different packages, including sysvinit itself" when you approached me with what sounded like a simple sponsorship request... I've started to have a go at the "herculian effort", step by step. Seems like an interesting experiment. NP: Eels / Daisies of the Galaxy (it's really hard to find a better band for a grey Sunday morning) Update: Maybe our reputation isn't all that bad, or Slashdot posts suddenly became all useful. A lot of insightful and interesting posts in the first batch of comments...

1 September 2006

Martin Zobel-Helas: Starting with Sarge r4 preparation early

After Sarge r3 is pushed out to the mirrors now, i thought it might be a good idea to start with the preparation of Sarge r4 early, thus i already started accepting packages into proposed-updates again.
Release of r4 is currently scheduled around October 16th, but that may vary a bit, depending on packages uploaded to proposed-updates and on the DSAs issued in the mean time. Happy hacking… :-)

29 August 2006

Martin Zobel-Helas: package list frozen

The package list for Sarge r3 has been frozen today, though we still wait for one package from one architecture to be uploaded. I hope it makes it before dinstall. Lets see….
FINALLY!

17 August 2006

Martin Zobel-Helas: Why m68k should not become release architecture for Etch

m68k is blocking the release for Debian Sarge r3 now for longer than a week. We are currently only waiting for one (essential) package from this arch: debian-installer. For some curious reasons this package did not build on any of the build-deamons and as porter machines are still locked down after compromise one can’t even do hand-builds. Wouter is currently doing this on one of his machines, but that might take a while… So one can still say what we said pre-sarge release: “It’s ready when it’s done”. Disclaimer: This is my personal opinion and reflects neither the opinion of the whole release team nor is consensus there.

8 August 2006

Martin Zobel-Helas: mostly done

The moderation queue of proposed-updates is now down to four packages, with one waiting to be accepted by ftpmaster. As soon as the Debian Installer is now build on the still missing architectures (alpha, arm and m68k), we should be ready to release Sarge r3 realy soon. Update: two packages are now waiting for ftpmasters, thanks to dannf, who’s first accept this was.

4 August 2006

Pascal Hakim: Teams.debian.net

One of the things I've been working on, on and off for the last few months is teams.debian.net. Along with a few others, we felt that there were not enough options for Debian-related mailing list hosting. While this may seem strange to some, a number of people at DebConf5 found the idea to be worthwhile. Most Debian-related lists which would not be considered for lists.debian.org could find hosting at teams.debian.net instead. The main purposes behind teams.debian.net are:
To request a new mailing list, simply follow the instructions on teams.debian.net Of course, like any free software project, there are still some things which are needed. The main one is currently the lack of a public web archive for lists which want it. I wanted to try to replace MHonArc with something that looked a little better and was more user-friendly, but I have yet to find something which I think would be an appropriate replacement. While some have suggested Lurker, I feel that is not very useable in a long term hosting environment, as it is harder to navigate around older entries. While this is acceptable in some places, it's definitely not in others. You can consider a "Dear Lazyweb" paragraph if you wish. Many thanks to Andreas Barth and Martin Zobel-Helas for their help in setting this up, providing machine space, and prodding me along when necessary.

2 August 2006

Martin Zobel-Helas: For those who wondered about proposed-updates

In collaborative work of Alexander Wirt, Marc Brockschmidt, Julien Danjou and me there is now a public list of packages which are in proposed-updates and await moderation currently. The backlog in that queue is currently decreasing drastically, thanks to AJ. Builds of the new D-I for Sarge r3 should start as soon as all needed packages are now spread to all mirrors. Update: Ooops, perhaps i should also add the link to that page.

20 July 2006

Amaya Rodrigo: In the news

Merc Molist interviewed me for El Pais, one of the biggest Spanish newspapers, which also happens to be my favourite one, in their weekly technology special, El CiberPais.

The interview, in Spanish, is here. Ugly pic of me wearing the Debian Women Tshirt in the printed version only.

I must say Merc made a great job out of a difficult subject, sexism in IT.

Update: Zobel provided me with a link to an Engrish version of it. Google 's Translation is not much better.


The ugly pic

Next.

Previous.