Three links to sign up...
-- none of which work.
Desolé, temporarairement inaccessible
-- Nice broken header graphic, too.
Much ado about scripting, Linux & Eclipse: card subject to change
Three links to sign up...
-- none of which work.
Desolé, temporarairement inaccessible
-- Nice broken header graphic, too.
In: errata
Time to pay the bills. Thanks, Eric!
As always, the contents of this site are my own and don't necessarily represent IBM's positions, strategies or opinions. This post should not be construed as an endorsement of any of CodeGear's software, only of The Evil Mastermind and his minions.
The Eclipse Modeling Project stands poised on the precipice, ready to break the 50 committer mark, just in time for M4 the holidays.
Are you that 50th person? Send me your headshot and details, and I'll add you into the fold.
If you're already listed but your information is out of date (because you are now a committer for more than one project?) reopen bug 182613 with your updated info. If you've so far neglected to send me a photo, now's your chance!
And now... some musical encouragement:
The model is all inside your head
Ed said to me
The answer is easy if you
Take it logically
I’d like to help you in your struggle
For notoriety
There must be fifty ways
To be a Modeler
He said it’s really not my habit
To intrude
Furthermore, I hope my meaning
Won’t be lost or misconstrued
But I’ll repeat myself
At the risk of flak from Euge
There must be fifty ways
To be a Modeler
Fifty ways to be a Modeler
I can't believe I'm the first person to blog this, but it would appear that the nominations are open for the Eclipse Community Awards, to be announced of course on March 17 at EclipseCON 2008. Bjorn, Ian, what up? Anyway, here's some handy links:
In entertainment news, my two release engineering talks have been accepted, so it looks like
If you're curious what I do to convert insomnia into productivity for the Modeling project's component leads, come have a listen:
In: awards, eclipse, eclipsecon, marketing
Congrats, Rogers! Your new site fails to work even better than the previous one! That's quite an achievement!
I can't sign in, I can't go to 'Online Self Service', I can't recover my username or password, and I can't even register. It's as if your.rogers.com is completely broken, and that's a pretty impressive accomplishment! And it's not just in one browser, either - it's in Konqueror, Flock and Firefox, on two different machines (one ubuntu, the other debian). I'd check in Windows w/ IE, but let's be real. This isn't a browser issue.
Kudos, Rogers. Keep up the great work!
In: customer service, errata, rogers
The following is an experiment in B2P networking, and an attempt to implement a cross-province UUBP transfer. (Aside: I had considered a cross-country experiment too, eg., Toronto to Porland, but I'm not sure how to implement such an idea, especially given the ever-tighter security policies at the US-Canada border. Any suggestions?)
I'd also like to say upfront that this experiment should not be construed as an irresponsible attempt to encourage others to mix beer (or any form of alcohol, really) w/ software development. Drinking and coding can lead to serious problems. Please, B2P responsibly.
While I realize I'm deviating from the spec, I've decided to implement using a more MDD-based approach, in that the message I plan to send via UUBP will not be an actual beer, but rather a model of a beer, which can then be extrapolated and ingested (and later digested!) at the receiving end.
Raw materials can be acquired from your nearest Beer Store and your office's mail room.
Next, the message is encapsulated for security using the "gift envelope" technique, which I presume won't cause licensing headaches or adoption problems as this technique is already widely used in the public domain.
Now, a second layer of encapsulation is required to ensure the packet can be properly delivered to its intended audience. While there is no real protection of malicious packet sniffing, this at least ensures that the casual observer won't want to intercept the packet. The procedure is very similar to the above, and so will be lest as an exercise for the reader.
With the completed packet, it was time to attempt delivery. The UUBP spec says nothing about transport methods, so I'll first try a web-based approach:
Unfortunately, even with a 20" monitor, the packet is too large to be sent via the web:
After this initial setback, it was decided to try a more conventional delivery mechanism. This Canada Post node will be employed to transfer the completed packet to its destination.
Second Delivery Attempt: Success!
The UUBP packet is now in transit via the B2P network. With any luck, its recipient will receive it in a couple of days and take some shots, er, photos to complete Part 2.
UPDATE: See Part 2.
It's been a while since my last linkdump from the world of EMF, so here's a quick update, brought to you by Google Alerts:
Continuing from yesterday's thread...
| Option A | Option B | |
|---|---|---|
![]() Life without floss. |
![]() Life with FLOSS. |
In: eclipse, FLOSS, friendofeclipse, humour
Contact:: Nick Boldt:: Toronto + Halifax, Canada Productization, Containers & Operators:: Red Hat CodeReady Workspaces |
|
|