Search Results: "ag"

16 August 2008

Holger Levsen: Thanks to the videoteam!

So, DebConf8 is over (currently we have three machines left in the network, the video storage server, the video encoding server and my laptop...) and IMO it rocked! I really enjoyed being here, meeting many many known faces and getting to know quite some new ones and learning a bit here and there, even though I was mostly doing videoteam work :-)

And this should be the main message of this blog post: many many thanks to all the different members of the videoteam. You have been awesome! The camera operators, the sound and video mixers, the moderators (which strictly speaking are not part of the videoteam but nonetheless helped us very much), those of you who reviewed the videos, the debconf network admins, the localteam members who prepared the venue fantastically, those who prepaid for hardware (and Debian for paying in the end) and took it here, those who helped with the set up here, the hotel staff who generally were very helpful (for example they agreed to dig holes in their walls), the absent team members who helped via irc and very much Dami n Viano for his awesome work on pentabarf and Ben Hutchings for dvswitch and most of the debconf-video package.

Also I like to thank Amaya very much for bearing with me and for all the love and joy you give me! Te quiero!

Thank you all! Very very much.

(And now I'm curious who I forgot...)

I'm also really happy we got videoteam t-shirts this year and at the same time this is probably the biggest regret I have regarding the videoteam: We didn't have enough t-shirts for everyone who deserved one. But things can definitly be worse :-)

Recordings, as much as we have them, are being uploaded at the usual place. You can help us with post processing by adding comments about problems (non-obvious ones only, please. If a event is split into two files, thats an obvious problem), to our todo wikipage.

See you! Have fun!

Ondřej Čertík: I am switching from Mercurial to git

After a long night of debugging and while preparing, reviewing and pushing final patches before a SymPy release, I got this:

$ hg qpush
applying 1645.diff
Unable to read 1645.diff
** unknown exception encountered, details follow
** report bug details to http://www.selenic.com/mercurial/bts
** or mercurial@selenic.com
** Mercurial Distributed SCM (version 1.0.1)
Traceback (most recent call last):
File "/usr/bin/hg", line 20, in
mercurial.dispatch.run()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 20, in run
sys.exit(dispatch(sys.argv[1:]))
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 29, in dispatch
return _runcatch(u, args)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 45, in _runcatch
return _dispatch(ui, args)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 364, in _dispatch
ret = _runcommand(ui, options, cmd, d)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 417, in _runcommand
return checkargs()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 373, in checkargs
return cmdfunc()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 356, in
d = lambda: func(ui, repo, *args, **cmdoptions)
File "/var/lib/python-support/python2.5/hgext/mq.py", line 1942, in push
mergeq=mergeq)
File "/var/lib/python-support/python2.5/hgext/mq.py", line 833, in push
top = self.applied[-1].name
IndexError: list index out of range

I am using:

$ hg --version
Mercurial Distributed SCM (version 1.0.1)

Copyright (C) 2005-2008 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


And I just got pissed off and I am switching to git for good. I've been using mercurial every day since about November 2007, and I think I am quite proficient in it. But we were missing some features, like recording a patch by hunks (git add -p), so Kirill Smelkov (another SymPy developer) just implemented this to mercurial queues, it is now included in hg 1.0. But I am constantly beaten by stupid bugs, mercurial broke into pieces several times already (last time with hg bisect, before it with mercurial queues and file renaming), that just should not happen in a production version. Another problem is that hgweb is constantly using 100% of CPU on my server whenever someone clicks to see the contents of the README file. Again I can spend time debugging it, but I will just use git and if it works, I'll stay with it.

I started learning git recently and it is just better in every aspect. Bigger community, it has all the features that I was always missing in mercurial (like rebase, hunks recording, diff diff --color-words, better gitk). And it's superfast.

Unless I find some showstopper bugs in git too, I don't think I am coming back.

We'll have to create a live mercurial mirror of SymPy, so that people can continue using mercurial, but I'll myself just be using git. We wrote a simple translation table for anyone using mercurial to get started:

http://wiki.sympy.org/wiki/Git_hg_rosetta_stone

I love Python and I like that Mercurial is just a small C core and the rest is in Python, but for some reason, it still has the baby bugs, that should have been fixed years ago and why should we spend our time fixing and improving Mercurial, if other people have already done the job for us (and usually a better job than I could do) in git?

Another reason for switching is that in Debian, mercurial is not used for packages, while git is used a lot.

John Goerzen: I Want Something eBay Doesn't Have

I always have time to think while mowing the lawn. And today while mowing the lawn, I got the notion that it would be great fun to play Colossal Cave and other early text adventure games on a teletype. And, of course, since Linux has teletype support in its genes, if I played my cards right, I could probably get a login prompt to my workstation with the teletype, too.

Now, at this point, I am compelled to take a small diversion and explain just what a teletype is -- for those of you, like me, who are too young to remember them. (I will graciously omit comment on those of you too old to remember them!) Teletypes have been around since about the 1930s or so, but the ones I have in mind are the ones that were used to interact with computers in the 1960s and 1970s. Instead of a keyboard and monitor, you'd have a keyboard and printer. Believe it or not, surplus teletypes were the interface of choice for teletypes even in the later years because they were so much cheaper than video terminals.

So anyhow, back to the plot. Teletypes operated at speeds ranging from about 40bps to 110bps, but it seems that the most common protocol was Baudot-coded 50cps 5N2 serial format -- that is, 5 data bits, 2 stop bits. Amazingly, the serial UART in modern PCs is still capable of communicating with these devices (though it may take some circuitry to tweak the voltages), and at least one person has made it work with Linux.

So I zip on over to eBay to look for teletypes. What do I find? NOT A ONE! A few manuals, and apparently there is a GPS named the teletype. And some company that has something they think *might* be compatible with a teletype, but they don't know.

eBay has sorely let me down. An antique geeky item should be right up their alley, and zilch. They can sell everything from cars to advertisements on some guy's bald head, but not a teletype? C'mon!

So anyhow, I am afraid I will have to improvise. Perhaps I can find a dot-matrix printer with a serial port (or, I guess, a parallel port would do too) and an unbuffered printing mode. Then the trick would be getting keyboard input. Perhaps I could rig up a pty to do this, input from /dev/console, output to /dev/ttyS0. It would still be old, but not quite the real deal.

So if any of you have a working teletype you'd like to get rid of, do please let me know. I'll send you a photo of the printout of me getting lost in Colossal Cave.

Oh, and for those keeping track at home, I guess you can add this to the list of old technologies I'm interested in: Gopher, typewriters, teletypes... they're all alike, right?

Steve Kemp: Didn't I kill you already?

One of the sites that I no longer use, but have fond memories of is dotfiles.com. It had some pretty coarse catagories and allowed you to view other peoples configuration files. (I have no idea how the upload worked. Probably email submission I'd guess.) I know that my my own dotfiles have benefited from seeing other peoples snippets. Sadly it seems that the last upload to their site was back in 2006. With all the Web2.0 lust around it would seem to be a perfect candidate for reinvention. We need: Somebody competant could probably knock up a reasonable hack in a day or two. I guess we have some sites out there already like DZone snippets, snipplr, & swik, but none of those are exactly the same thing. Consider it my challenge to the world - just don't tempt me. I've got enough to do as it is. ObQuote: Hellboy

Michael Schultheiss: Happy 15th Birthday, Debian!

15 years ago today, Ian Murdock announced the Debian Linux Release. I've been involved in Debian since 2002 and am amazed at how the project has grown during my involvement, let alone its entire history. Here's to continued success for the Universal Operating System!

Russell Coker: Australian Business and IT Expo

I’ve just visited the Australian Business and IT Expo (ABITE) [1]. I haven’t been to such an event for a while, but Peter Baker sent a link for a free ticket to the LUV mailing list and I was a bit bored to I attended. The event was a poor shadow on previous events that I had attended. The exhibition space was shared with an event promoting recreational activities for retirees, and an event promoting wine and gourmet food. I’m not sure why the three events were in the room, maybe they figured that IT people and senior citizens both like gourmet food and wine. The amount of space used for the computer stands was small, and there was no great crowd of delegates - when they can’t get a good crowd for Saturday afternoon it’s a bad sign for the show. I have previously blogged about the idea of putting advertising on people’s butts [2]. One company had two women working on it’s stand with the company’s name on the back of their shorts. A representative of a company in the business of Internet advertising asked me how many hits I get on my blog, I told him 2,000 unique visitors a month (according to Webalizer) which seemed to impress him. Actually it’s about 2,000 unique visitors a day. I should rsync my Webalizer stats to my EeePC so I can give detailed answers to such questions. The IT event seemed mostly aimed at managers. There were some interesting products on display, one of which was a device from TabletPC.com.au which had quite good handwriting recognition (but the vocabulary seemed limited as it couldn’t recognise a swear-word I used as a test). Generally the event was fun (including the wine and cheese tasting) and I don’t regret going. If I had paid $10 for a ticket I probably would have been less happy with it. Updated to fix the spelling of “wine”. Not a “wind tasting”.

15 August 2008

Jos Parrella: DebConf 8 in Mar del Plata, Argentina

Me and Ail arrived at Buenos Aires on saturday. A member of the local team was waiting for people at Ezeiza, and we gave away our 2130 bus reservations in order to take a combi to Mar del Plata with Clint, four fellow german debianites and some venezuelans. The trip was quite long, around six hours IIRC. We arrived in the early morning, and slept past noon. I have no words to describe my particular experience with this year’s conference, but I do agree with our DPL: this has been the best DebConf I’ve ever attended. In general, the Annual Debian Conference is one of the most attractive events for me, since it provides us with the opportunity to share and define a little bit of the future of the universal operating system. I use, develop for and work with this operating system, so there’s the importance of this conference for me. That said, DebConf is a unique event. Some people that I know back in Venezuela are used to a different, more academic style of event, which features a tight schedule and no specific provision of group networking. They are not used to an event like DebConf, and when they attend it they feel they’ve lost their time in an event they don’t understand. And they ask for a participation certificate :) In that respect, besides the very interesting talks and events in the conference, DebConf offers an excellent opportunity for group development and general networking. On the other hand, both the local team and the venue have striked me in many good ways. I’m aware of LatAm limitations for some of the particularities of DebConf such as connectivity, provision for special food needs, special usage of the venue and general receptivity for a bunch of 24/7 geeks. The local team has made a huge effort putting this together in such a special and organized way. I don’t think the Venezuelan DC8 Bid would have made this much success in the same timeframe. Congratulations, Argentina! We will leave Mar del Plata on saturday (at 2200) and then we will spend some more days in Buenos Aires, particularly to attend Debian Day, where I’ll be giving a talk in spanish. Therefore, we’ll be writing a little more (in spanish) about Argentina later, since we loved our time in this country.

DebConf 8 video: Debian Wiki

We should coordinating to be able to release a "new" Wiki when Lenny is released. e.g :

1. Choose a License for the Wiki content. This topic has been discussed many times, but was never addressed (searching "wiki license site:lists.debian.org/debian-www" or in "/debian-legal", reveals lots of discussions !)

2. The layout could be refactored.
2.a. Create/adapt the moinmoin theme (CSS) to be more " la Debian" (either www.d.o, or pts, etc...).
2.b. Front page content : which links. The "new" front page is nicer, but the icons are meaning less. also it has too many entries... (compare http://wiki.debian.org/FrontPage?action=recall&rev=488 and current http://wiki.debian.org/FrontPage )
2.c. Front page Layout : Once we have decided the content, pick a layout (what do we want to emphasize : News ? Projects ? Download ? Support ? DDs ? Users ? Communities ? "Get Involved" ? )

3. Coordination : Make a planning until Lenny's release date.Full event details

DebConf 8 video: Best practises in team-maintaining packages

a) Situation

During the last few years team-maintaining groups of packages has become
more and more widespread in Debian; the exact number of packaging teams is
unknown, estimates vary between 42 and 893 -- reality is probably somewhere
in between. [0]

Although the challenges for all teams are similar, there is a lack of
communication between those groups which leads to a situation where many
are "reinventing the wheel".

b) Objectives

- bring members of different packaging teams together
- get an overview of different work flows, tools, and challenges
- compile generally useful 'models of good practise'
- define possible areas for cooperation / tasks of mutual interest

c) Methods

Should the proposal for the BOF be accepted, a short questionnaire covering
"typical questions" for packaging teams will be prepared before Summer that
allows interested participants from packaging teams to prepare a short
overview of their team's situation and work flow.

This will allow the BOF to begin with short and structured presentations
dealing with common aspects of team packaging. From these presentations
common points of interest will be collected to form the "agenda" for the
next part of the BOF.

Ideally the session will conclude with a summary of "best practises,"
ideas for improving individual groups' work flows and ideas for
improved cooperation between teams. -- Findings will be made public in
the hope that they will be helpful to others.



[0]
http://wiki.debian.org/Teams lists 42 "Packaging teams";
http://krum.ethz.ch/ddc/teams-of-2007.txt has 218 entries;
http://alioth.debian.org/ talks about 789 "hosted projects", looking in
/home/groups on alioth shows 893 directories in general and 387 pkg-*
directories.
Full event details

DebConf 8 video: Best practises in team-maintaining packages

a) Situation

During the last few years team-maintaining groups of packages has become
more and more widespread in Debian; the exact number of packaging teams is
unknown, estimates vary between 42 and 893 -- reality is probably somewhere
in between. [0]

Although the challenges for all teams are similar, there is a lack of
communication between those groups which leads to a situation where many
are "reinventing the wheel".

b) Objectives

- bring members of different packaging teams together
- get an overview of different work flows, tools, and challenges
- compile generally useful 'models of good practise'
- define possible areas for cooperation / tasks of mutual interest

c) Methods

Should the proposal for the BOF be accepted, a short questionnaire covering
"typical questions" for packaging teams will be prepared before Summer that
allows interested participants from packaging teams to prepare a short
overview of their team's situation and work flow.

This will allow the BOF to begin with short and structured presentations
dealing with common aspects of team packaging. From these presentations
common points of interest will be collected to form the "agenda" for the
next part of the BOF.

Ideally the session will conclude with a summary of "best practises,"
ideas for improving individual groups' work flows and ideas for
improved cooperation between teams. -- Findings will be made public in
the hope that they will be helpful to others.



[0]
http://wiki.debian.org/Teams lists 42 "Packaging teams";
http://krum.ethz.ch/ddc/teams-of-2007.txt has 218 entries;
http://alioth.debian.org/ talks about 789 "hosted projects", looking in
/home/groups on alioth shows 893 directories in general and 387 pkg-*
directories.
Full event details

DebConf 8 video: i18n mini-sessions 2/4

Since Debconf 6, organizing a series of BOF dedicated to i18n-related topics has proven to be quite useful to all people working on i18n/l10n in the project.

Proposed topic: http://wiki.debian.org/i18n/TranslationDebs aka tdebs aka translation packages


Full event details

DebConf 8 video: i18n mini-sessions 2/4

Since Debconf 6, organizing a series of BOF dedicated to i18n-related topics has proven to be quite useful to all people working on i18n/l10n in the project.

Proposed topic: http://wiki.debian.org/i18n/TranslationDebs aka tdebs aka translation packages


Full event details

DebConf 8 video: i18n mini-sessions 2/4

Since Debconf 6, organizing a series of BOF dedicated to i18n-related topics has proven to be quite useful to all people working on i18n/l10n in the project.

Proposed topic: http://wiki.debian.org/i18n/TranslationDebs aka tdebs aka translation packages


Full event details

DebConf 8 video: i18n mini-sessions 2/4

Since Debconf 6, organizing a series of BOF dedicated to i18n-related topics has proven to be quite useful to all people working on i18n/l10n in the project.

Proposed topic: http://wiki.debian.org/i18n/TranslationDebs aka tdebs aka translation packages


Full event details

DebConf 8 video: Bugs in large packages

Full event details

DebConf 8 video: Debian and Ubuntu

This keynote reports on the current state of collaboration between Debian and Ubuntu, reports back on progress made since previous DebConf's, and looks forward to new opportunities for collaboration and development.

Debian's derivatives are a powerful part of the Debian family. They bring Debian technology and, usually, Debian values to a broader audience than Debian itself will reach. At the moment, Ubuntu is the derivative with the largest reach, bringing millions of new users to GNU/Linux and Debian specifically. Ubuntu has shifted the commercial Linux landscape from one focused on RPM-based distributions to one where DEB-based distributions have much greater commercial and consumer acceptance. In this keynote, the leader of the Ubuntu project will discuss the state of current collaboration between Debian and Ubuntu developers, articulate the roadmap of Ubuntu in the coming years, and explore ways in which Ubuntu's work can improve the state of Debian.

The talk will cover:

* Current areas of collaboration
* Toolchain, Java, Python, Debian Installer,
* OpenOffice, X.org
* GNOME and KDE
* Security
* Roadmaps and transitions

* Challenges and obstacles to collaboration
* Cultural and organisational differences
* Divergent goals and priorities
* Release management and coordination

* Frameworks for collaboration
* Patch management and submission processes
* Package review, merging and delta management
* Version control interchange
* Leadership meetings and dialogue
* Bug coordination and collaboration
* Translation coordination and management

Ubuntu is only one of many derivatives - and others are achieving tremendous success in their own ways, too. The eeePC ships a derivative of Debian, and Debian is at the heart of many excellent free software solutions. The goal of this talk will be to celebrate some of those achievements and also to look for ways to make the "family" feel more cohesive. In short, to ensure that innovation which happens in derivatives has a natural pathway back to Debian. If the leaders of other derivatives are present at DebConf, this would also be an opportunity to seek comment from them, perhaps in the form of a panel for Q&A at the end of the keynote.
Full event details

DebConf 8 video: Debian Edu 100% in main

This talk will briefly explain what Debian Edu is, how we develop our distribution, how we differ from Debian, how we work on bridging the gaps that still exist and what our plans for the future are.

In July 2007 the Debian Edu project released its third release, codename "Skolelinux 3.0 Terra". Debian Edu is probably the most widely known and most widely used Custom Debian Distribution - at least if you follow the official criteria for a CDD, which we aim to finally fulfill 100% for Lenny: all packages are taken unmodified from Debian main.

This talk will explain the development process of Debian Edu and the various differences to a default Debian install. An overview of the planned features for Lenny will be given as well as a list of current showstoppers will be presented. To explain to the audience, what challenges have been overcome since Debian Edu was started, the history of how 100% inclusion in Debian was achieved, will also be explained. (Debian Edu used to be a seperate distribution! Now we have become a part of Debian!)

Using wiki.debian.org to write a fine manual will be explained briefly too: our documentation is written in a wiki, then exported as docbook and translated using .po files, then transfered back into docbook, to generate html and PDFs versions, which are made available in the debian-edu-doc package, which is installed on a webserver again.

In the end, releasing with Lenny will not be the end of the process of becoming part of Debian. Currently it looks like we might release with Lenny, but then do point releases on our own. Whether this is a sensible strategy or if there are others, will (hopefully) become clearer in future. Until & after the talk - it's a long and winding road!Full event details

DebConf 8 video: Custom Debian Distributions

One goal of Custom Debian Distributions is to form a group of Debian
developers who care for a specific set of packages that are used in
the day to day work of a certain user group. The fact that Debian has
grown to the largest pool of ready to install packages on the net has
led to the side effect that it is hard to maintain for
beginners. A Custom Debian Distribution adds some substructure
to the currently flat pool of 15000+X packages without a real
structure. These substructures are intended to put a focus on
special user interest. These substructures are not oriented on
technical matters like Debian installer team, porting teams or teams
that are focussing to implement programming language policies.

There are some similarities to Debian-i18n which also has the pure
goal to serve the needs of certain end user groups with the difference
that the users are grouped not according to their field of work but
according to their language. In fact it makes even sense to create
CDDs for languages that require certain technical means to optimally
support the language regarding direction of writing, special fonts
etc. It is known that some countries in Asia builded Debian
derivatives for this purpose but in principle it is not necessary to
derive - the better solution is to make Debian more flexible by
starting a CDD effort inside Debian.

The talks will give some examples from the success of CDDs like
Debian-Edu and Debian-Med. One very important outcome of the CDD
effort is the ongoing reunification of Linex - the Debian derived
distribution that is used in all schools in Extremadura - with
Debian-Edu. This step means that Debian gets a very large
implementation in all schools of Extremadura while on the other hand
the effort of development for the people who invented Linex will be
reduced. Debian featuring Debian-Edu now has a very good chance to
become a really good international school distribution because it has
roots in five countries (Norway, Spain, France, Germany and Japan) and
might become attractive for many more.

The success stories of CDDs would not have been possible outside
Debian and thus leaving the path to build Zillions of Debian
derivatives that reach a very small user base and working together
inside Debian is the main idea of the talk. To make this idea more
attractive in the second part of the talk a description of tools that
were developed in the CDD effort will be presented. Especially the
newly developed web tools that give a good overview about the
packages that are useful for a certain field of work and the QA tools
that enable the CDD team members to easily get an overview about
packages that need some action. So if people are not yet convinced
that a CDD for their purpose makes sense we will catch them by the
tools they might get for free if they follow the proposed strategy.
Full event details

DebConf 8 video: Healthy CDDs

The Debian-Med CDD was started in January 2002 and has evolved a lot
since this time. Debian now becomes the distribution of choice for
people who are working in the field of medicine. On the one hand this
can be obtained from the increase of pure numbers of packages in the
field of medicine.

On the other hand - which is even more interesting for general Debian
development - a group was formed that has developed a certain way of
cooperation which might serve as an example for other teams. Debian
knows a lot of technical teams focussing onto technical issues
(pkg-perl, pkg-python, d-i, etc.). An important part of the project is
to involve people who call themselves "pure users" or "non-developers"
(whatever this might mean) as it is done at a certain amount by the
i18n and Debian Edu team.

So this talk is not about boring the audience by mentioning medical
Free Software - it exists at a certain amount out there as other
specific software does as well - but rather how to attract people to a
topic where FLOSS is not common but should. It will give examples for
our way to advertise Free Software in medicine which is heavily
dominated by proprietary software, which tools we developed inside the
CDD framework to be always up to date with our web pages that are
intended to attract users to Debian and last but not least the lessons
we have learned in the project that might be of high interest for
other CDDs (or potential CDDs). Examples are given for project
management, attracting people by working techniques and making sure
that medical software finds a good home in Debian.
Full event details

DebConf 8 video: I18n mini-session 1/4

Since Debconf 6, organizing a series of BOF dedicated to i18n-related topics has proven to be quite useful to all people working on i18n/l10n in the project.

Traditionnally, session 1 is an open talk/round table meant to enlighten the topics to be discussed in other meetings (as well as more informal work sessions during the conference).

Session 1 would be "opening session" as well as the first "work session"

churro: status of server

Services on churro:
(listed on http://i18n.debian.net/wiki)

- l10n material collection: status by nekral
what does it cover (unstable/testing, po-debconf/po/?)
what is using it?

- Pootle. define admins
bubulle: explain what's currently and what's in production
D-I: direct commits to SVN. Missing projects
Debconf: interaction with debian-l10n SVN, need for tools to
grab l10n from SVN. Integrate in po2debconf?

- DDTP: grisu gives status
what about PO export/import
bubulle about PO import to Pootle and perf problems
ddtss: nekral?

- tracking robots: status by nekral

- compendia: status by bubulle

- stats and graphics: status by nekral
Organize this? (pointers on main l10n page?)
Move stats pages to churro?

Server administration and hosting: status by faw
- server admin ML: use d-l-devel?
- move to i18n.debian.org: blockers?
Full event details

Next.

Previous.