PyCon DC 2004
A surprising number of Macintosh laptops were spotted at this conference. But then I remembered that there was a surprising number of Macintoshes at last year's conference too. Bob Ippolito gave a talk called "60 Minutes with MacPython". I haven't had a Mac since I sold my Classic in 1993 to get a machine that could run Linux, I'll spare you a clueless interpretation and refer you to the session paper and SubEthaEdit notes. Bob has some warnings about which Python to use for OS X 10.2 vs 10.3, the dreaded resource fork and more. MacPython also has libraries for Cocoa, the NeXT framework that was ported to the Mac. Bob says Cocoa is a good API; it's been around for 15 years. wxPython works on the Mac but it doesn't put the widgets in quite the correct place.
One thing I didn't realize until after the conference (when my friend Brian Dorsey pointed it out) is that many of those Mac laptops were running SubEthaEdit. SubEthaEdit is a distributed text editor; you may prefer to think of it like a multiplayer game, CVS on steroids or a real-time wiki. All the SubEthaEdit programs running in wireless range of one another get together and state which files they have open. Anybody can update anybody's document simultaneously in real time. The background color of the text shows who edited what portion. When done in a lecture hall (for instance, a talk at a Python conference), the result is the best of everybody's notes all in one. This is the next generation of notetaking and will no doubt be a staple at future Python conferences.
Some of these Mac addicts went to dinner together on the first day of the conference and started thinking, "Why don't we write an open-source equivalent to SubEthaEdit in Python?" The result is Fuse, which is partially working. The developers' mailing list stalled March 30, but a couple people checked in April 11 to say they're still working on it.
Success has its drawbacks, and the biggest one is that we may outgrow GWU next year if attendance approaches 500. The organizers are shopping for a venue that can handle a thousand people, so we won't have to move again after a couple years. We may be too late for next year because conferences normally book 18 months in advance. If we do stay at GWU one more year, we'll have to cap attendance at its capacity. Priorities for a new location include:
proximity to public transportation, low-cost accommodations and a city to hang out in
facilities that include catering, network equipment and the like at a cost comparable to GWU
accessibility for off-hours activities, like BOFs
a place to hold the sprints before or after the conference
There are arguments both for and against remaining in DC. "lac" writes in the wiki that we can't assume that the number who attend because it's in DC are more than the number who don't attend because it's in DC. We just don't know. The West Coast has OSCON, but OSCON attracts a different clientele due to its higher price and different focus. There's a possibility of two regional conferences down the road, PyCon East and PyCon West. Is that better for the community or worse? Europe already is hosting its own conferences (EuroPython and Python UK), and maybe Asia will too.
Steve Holden has said he's willing to chair one more conference but he wants to retire after that. He's hoping to train a vice-chair next year who can take over the reigns the following year. PyCon cannot remain dependent on one person or it won't succeed long term.
Steve's greatest regret is that 50-100 people marked the volunteer box on the registration, but there was no mechanism in place to alert them when they were needed, so that manpower was lost.
There's discussion about whether to have the sprints before or after the conference, or both. The argument for after is the talks will draw new people to the same-topic sprints, and the sprinters already will know one another and maybe have decided their tasks so they can start running. The argument for before is that people will be burned out after the conference.
Open Space definitely needs better organization. Open Space, Lightning Talks and BOFs need to be planned into the schedule. Perhaps the first day's topics should be set before the conference to avoid losing that day. Also, what's the difference between an Open Space and a BOF anyway?
The brightest note is that Steve writes, "It's amazing how many people say that PyCon is the best conference they have [ever] attended, even people who are quite experienced conference-goers."
Oh and Steve, if you do step down from the chairman role, you'll still be there with your British understatement zingers, won't you?
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- LiveCode Ltd.'s LiveCode
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide