Program Track B

I want to discuss the following items during the talk.

1. Having A problem to solve - a demonstration of my application in use.
2. Choosing a license.
3. Why Python?
4. Why PyQt?
5. Collaborating with others, using launchpad for code hosting and bug tracking.
6. Packaging the app so that you get feedback. Debian packaging and the use of a PPA.
7. Translating into other languages - the GNU gettext tools. Porquoi?
8. the future for the application - can we make money from this?

With less than 10% of IPv4 address space remaining, it is extremely urgent that all organizations adopt IPv6 – the next generation of IP technology – before time runs out and the global Internet community is fragmented.

Some Linux IT professionals have been slow to adopt IPv6, and have yet to fully understand the benefits and ease of the deployment. With fewer resources on the Web regarding IPv6 and Linux, it is important for attendees to learn why IPv6 is necessary.

In this session, John Curran, President and CEO of the American Registry for Internet Numbers (ARIN), will discuss how attendees need to prepare for IPv4 depletion challenges, key considerations for IPv6 adoption, and the benefits of early IPv6 adoption. The session will provide attendees with the information and tools needed to ease their technical and business concerns of adopting IPv6.

John will also focus on open-source software implementations of IPv6 and how to make the transition as seamless as possible. He will highlight educational resources available to help Linux IT professionals to better understand and communicate the value of IPv6 to their organizations.

ARIN is the nonprofit corporation that manages the distribution of Internet number resources, including IPv4 and IPv6 addresses and Autonomous System Numbers (ASNs), to Canada, many Caribbean and North Atlantic islands, and the United States.

Color Management has long been perceived as a niche area, of interest mainly to professional graphic designers and the like, however it has come to be important to a much wider audience. At the same time it is also becoming more and more accessible to much larger groups of people. What used to be reserved for high-end service bureaus and professional publishers has now come to be usable in areas such as 1 hour prints at a local drugstore, web sharing and emailing of family photos, and output of graphics and photos on home printers.

This talk will first focus on color management in general, and many of the different types of end users who can benefit from it. Photographers, digital painters, illustrators, website creators, graphic designers and different home users can all gain in many different ways from adopting at least a bit of a color managed workflow. Aside from the obvious graphics professionals, potential users include anyone who might email a photo from a cell phone to their home computer, or who might edit a website on an OS that might be different from that used by some people viewing it. Also developers themselves can benefit from adding at least minimal color management support to projects they work on.

After the general information of color management and who might benefit from it, the focus will then move on to the history and current state of color management in Open Source software. In just the last few years large advancements have been made, with GIMP and Inkscape among those joining the projects supporting color management and a color managed workflow. Tools including Argyll CMS, LProf, xicc and others will be covered.

Specific examples and cases will then be drilled down to, with a focus on illustration and SVG. The speaker's experience in adding color management to Inkscape will be leveraged to show concrete examples for workflows before and after color management. Issues such as printing output, spot colors, CMYK printing, mobile devices, and integration with raster paint programs will be covered.

Finally, pending improvements in Open Source software will be highlighted with an eye to inspiring both end users and developers. End users can look forward to the improvements to come, and can help ensure their individual needs will be covered. Developers can see that adding color management to their project is not difficult to start, and can lead to even wider acceptance of their software and of color management itself.

OpenSolaris attacks the four problem areas in an unique manner. Through the remainder of the paper we will examine each of the 4 problems areas declared above. We will look over the historical problems consumers of Operating Systems face and detail how OpenSolaris solves those problems with examples.

1.) CPU/MEM access layer

Kernel = Solaris Kernel
Virtualization = VirtualBox, Xen, Containers, LDOMs

2.) File System/Disk/Storage layer

File System = Zettabyte File System
Universal Storage Framework = COMSTAR

3.) Runtime layer

System Services = Service Management Facility
Fault Management = Fault Management Architectures
Process Diagnostics = Dynamic Tracing
Network Virtualization = Crossbow

4.) User Access layer

User Administration = Java Panels
Windowing Environment = GNOME/compiz
User Applications = Mozilla/OpenOffice/MySQL
Developer = GNU/Netbeans/AMP stack/SourceJuicer
Network Installation = Automated Installer/Distro-Contructor
Software Management = Image Packaging System
Security = Role Based Access, audit, file fingerprint, Least Privilege, Privacy Levels

Vim is the most commonly used text editor in Linux. It is a extremely powerful and flexible editor. This talk introduces people to many of the more advanced features that they might be unaware of including:

* Multiple windows
* Commands for searching through *multiple* source files.
* Diff mode
* Commands for locating files when you only know a partial name.

So, you've heard of BSD but haven't tried it yet. Or perhaps you used it years ago and are wondering what has since changed in the BSD world. This talk will introduce the BSD family of operating systems. We'll start with a brief comparison of the BSD projects and a description of the BSD release engineering process. We'll then cover the main differences between BSD and Linux from an administrative and end-user point of view. This will be followed by an overview of some features which aren't available on non-BSD systems.

Written in ruby, PoolParty provides a nice domain specific language for describing a repeatable, declarative cloud computing infrastructure. Mainly focusing on amazon's EC2 offering, the presentation will cover basic concepts of cloud computing, how PoolParty works and how you can get into the clouds in one command.

Writing a technical document is hard. Reading a poorly written technical document is harder, and probably more painful than writing one. It takes a lot of work to create a clear, accurate, engaging piece of technical writing. Thus, in order to make life a little easier for all parties involved, I am going to share with you the 7 Rules that I follow when creating a piece of technical documentation.

The 7 Rules are:

1. Dry sucks
2. Before you start, be clear about what you want your reader to do after you end
3. Write to a well formed outline, always
4. Avoid ambiguous pronouns
5. clarity = illustrations + words
6. When dealing with concepts... logical illustration and example
7. Embrace revision

This session will provide the very basics of trademark law along with recommendation for best and minimum practices. Common misconceptions about trademark law will be debunked and community interests in trademarks will be contrasted with corporate ones.