Here’s my presentation on “People Management in a Collaborative Remote Work Context”. Sorry, Portuguese-only.

Update: You can also read the paper: Gestão de Pessoas no Contexto do Trabalho Colaborativo à Distância (yes, Portuguese-only too).


I am preparing PLIP #187 for review and further inclusion into Plone 3.1, after the official announcement of the PLIPs selected for inclusion.

For a start, I’ve created a buildout starting from optilude’s own, then added the related branches and extra products into the buildout config.

At this point, it should be possible to checkout the buildout, build it and run the tests, which currently gives me 3 failures for CMFPlone, two of them apparently unrelated and one related but which apparently did not happen at the time I’ve branched.

The next step is to update my CMFPlone and Marshall branches to trunk, and possibly getting rid of the PloneTestCase I had initially created.

FWIW, all this work was done as part of my Google Summer of Code 2007 project, and it is great to see it being accepted (erm, considered?) into a proper Plone release so quickly.

PS: I’ve created a tumblr account for myself, hopefully that will help channeling all the various posts, pictures, links, etc from the various sites I participate. If anyone else has tumblr accounts, please post a comment here. Discoverability is not very great with tumblr unfortunately.


Ok, I’m fed up. Here’s the first of a series of Pearls from the Plone Source. Call it The Plone WTF if you like.

Here goes, a loop that does nothing. Notice the ‘locking_info’ adapter is fetched outside the for loop:

for action in workflowActions:
    if action['category'] != ‘workflow’:
        continue

locking_info = queryMultiAdapter((context, request), name=’plone_lock_info’)

And then a few lines below, the same loop repeats, this time it is doing something. The ‘actionUrl’ variable is assigned inside the for loop:

if locking_info and locking_info.is_locked_for_current_user():
    return []

for action in workflowActions:
    if action['category'] != ‘workflow’:
        continue
    actionUrl = action['url']

Sad. I don’t think anyone is really reviewing this code….


Not much news over here. Spent most of the day renewing my passport (can’t believe 5 years go by that fast). Got home, and a great friend called me, lots of catching up.

When I got off the phone, I was chatting with my wife about the call. She met most of the Plone folks at the two conferences she attended with me. But she can’t remember everyone by name. So I searched for a picture of one of the guys we were talking about.

A few hits returned, I chose a picture from Flickr. She thought I was talking a different long-hair guy. I guess my description was really bad.

But the funny thing, and what prompted me to write this entry, was the stunning similarity between that picture, which I chose at random, and a certain comics character I just loved when I was young.

Long-hair guy, it’s been a long time since I saw you playing that little piano of yours live. New Orleans, 2005 if I recall. Was great to hear from you through my friend. I hope we can meet again soon.

And, I wonder if you love Beethoven too.


Since today seems to be about writing blog posts about blog software, I want to pass on some idea that’s been in the back of my mind for about a month.

I’ve installed Windows Live Writer and noticed that it is quite extensible. In fact, all of it’s extensibility features are documented on MSDN.

The really nice feature that got me hooked is the support for editing ‘inside the theme’ (for the lack of a better description). The way this works is, there’s a small contract between Windows Live Writer and the blog, where the blog can provide views that Windows Live Writer fetches for editing.

So a nice suggestion for those working with blog support for Plone: please implement Windows Live Writer’s Provider Customization API.

And then, there’s another great feature that Plone can exploit, but this one I would like to implement myself. Windows Live Writer supports Content Source Plugins, which basically allow you to pop up a form for some user interaction and then spit out some HTML to be inserted at cursor location in the blog entry.

Now, if you stop and think just for a second, we already have a concept of “Content Source” in Plone: Kupu’s Image and Link Libraries. It already has a well-defined XML format. It can be customized through the Plone UI. And to top it off there are examples of writing Content Source Plugins that read data from an XML source. It should be a piece of cake to implement a “Kupu drawer”-like Content Source Plugin for Windows Live Writer that reuses the data from Kupu.

So, that was it. Hopefully someone will take those ideas to the next level and implement something soon. Unfortunately I’m a little busy with graduation and all that at the moment, so I can only provide ideas. But maybe next year. :)


Plone is an extremely popular high-end open source content management system. This year’s Plone Conference is currently underway in Naples, Italy. CMSWire.com is providing ongoing coverage of the event on its blog.

It is really important to have live coverage (or even coverage at all) of conferences like this. I’ve attended several conferences in the past, and it’s a shame that much of what was talked about or announced at those conferences has never reached anyone outside the conference audience.

read more | digg story


On his Strategy Letter VI article, Joel writes about something that many people are starting to realize: that the current Web 2.0 is not much better than Smart (or even Dumb!) Terminal days, when you had to care about memory constraints and there were no standards for interop between applications, or even UI guidelines.

Then after a short history lesson, he speculates that people should stop worrying about the size of their JavaScript and that eventually JavaScript would be compiled to native code a new portable language will appear that can be compiled to JavaScript (did someone tell him about GWT at all?).

What’s going to happen? The winners are going to do what worked at Bell Labs in 1978: build a programming language, like C, that’s portable and efficient. It should compile down to “native” code (native code being JavaScript and DOMs) with different backends for different target platforms, where the compiler writers obsess about performance so you don’t have to. It’ll have all the same performance as native JavaScript with full access to the DOM in a consistent fashion, and it’ll compile down to IE native and Firefox native portably and automatically. And, yes, it’ll go into your CSS and muck around with it in some frightening but provably-correct way so you never have to think about CSS incompatibilities ever again. Ever. Oh joyous day that will be.

Well, after Paul Graham said that Microsoft is Dead, the only thing I can think of is that Joel has started to believe Paul’s lie, and stopped paying attention to what comes out of Microsoft.

Everyone that is paying attention to Silverlight and has not been blinded by the anti-Microsoft FUD, something that even the Linux Foundation executive director condemns, will realize where Microsoft is heading with the introduction of the DLR, specially if you make the connection between Joel’s post and Managed JScript. I really hope that people will soon take their tinfoil hats off and start paying more attention to what’s coming out of Microsoft, specially since there is an option in Mono, which is a completely open implementation of .NET, and now with Moonlight a JavaScript compiler  will be soon hitting your beloved Linux Desktop anytime now.

And listen, Joel. We don’t need no new stinking portable language that can compile to JavaScript. If we get to write code in our own lovely favorite language, be it Python or even Ruby, being able to access the dreaded DOM and to top it off compile it to native machine code, what could be better than that?

In other news, if you just consider the approach of making JavaScript faster instead of compiling it, you might want to keep an eye on Mozilla’s Tamarin Project. Mum’s the word that some exciting news will be coming out of that in the near future.


Enfold Systems  and the Texas Learning and Computation Center will be sponsoring a one-day event at the University of Houston in November.

What: Ploneability Higher Ed
Ploneability Higher Ed is a one-day conference for college and university Web content managers, developers and site administrators to connect and share success stories involving Plone, the open-source content management system. Agenda, registration and more information at: http://ploneability.eventbrite.com/
When: Thursday, November 8, 2007 (all day)
Where: University of Houston
4800 Calhoun Road
Houston, Texas 77004   United States

 

If you’re interested in Plone, and involved in Education, you can’t miss this one.

There will be another two events, on the day before and after.

Wednesday, Nov. 7
Joel Burton of Plone Bootcamps will hold a training session on the UH campus. Course information and registration will be available soon on the Plone Bootcamps Web site.
Friday, Nov. 9
Christian Vinten-Johansen and Mike Halm of Penn State will hold a meeting at Rice University to discuss collaboration on higher ed Plone products. Seating is limited. For information, please e-mail Christian at [email protected].
 

Make sure you register soon, there are only 146 tickets available right now. Registration is FREE!



Follow

Get every new post delivered to your Inbox.