Add last couple posts

This commit is contained in:
R. Tyler Croy 2011-12-23 13:26:41 -08:00
parent 0868aa3b0d
commit aa00c9c1e2
2 changed files with 125 additions and 0 deletions

View File

@ -0,0 +1,58 @@
---
layout: post
title: I will be speaking at FOSDEM
tags:
- jenkins
- fosdem
- puppet
- conference
---
This upcoming February I will be making the trip to the bitterly cold
cobblestoned streets of Brussels, Belgium for [FOSDEM
2012](http://fosdem.org/2012/), one of the most fantastic open source
conferences of the entire year.
I've been to FOSDEM once before, but as a timid young lad who barely spoke to
anybody. I distinctly recall walking down a hallway past [Theo de Raadt](https://en.wikipedia.org/wiki/Theo_de_Raadt)
thinking "ZOMG IT'S THEO" then in the most sauve fashion, I turned around and
walked back down the hallway in the opposite direction making sure I got a good look at Theo.
What a damn nerd.
This year will be something special in that I will be speaking in the
[Configuration Management Devroom](http://fosdem.puppetlabs.com/) on the
subject: "*Open Source Infrastructure - Running the Jenkins project with Puppet and
more*.
If you're not familiar with the structure of FOSDEM, there are a two main
tracks which are held in amphitheaters which can hold hundreds of people at a
time. The only one of these I remember from my last visit was watching a talk
by [Alan Cox](https://en.wikipedia.org/wiki/Alan_Cox), to give you an idea of
the scale of those sessions.
Concurrent to the main tracks there are a number of topic-oriented "devrooms"
where developers of common interests (Mono, MySQL, Open source virtualization,
etc) congregate for talks, panels, etc.
My talk is structured as a hybrid technical/case study talk, the abstract of
which is below:
> In early 2011 the Jenkins project became the Jenkins project, leaving behind an
> organically grown but Oracle (formerly Sun) operated infrastructure. An open
> source project with thousands of users had to grow an infrastructure
> practically overnight, initially doing things "the wrong way" by hand crafting
> machines. That was until a costly mistake forced us to reconsider and migrate
> to managing our infrastructure with Puppet from a publicly available shared Git
> repository.
>
> Besides Puppet, the Jenkins project also uses a number of other tools to help
> manage access control on GitHub, parts of JIRA, etc, all carrying on the very
> transparent and welcoming tradition the project prides itself on.
>
> In this talk I will discuss the ups and downs of switching an established
> infrastructure to Puppet, all within the public eye and with volunteer time and
> energy.
If you're in Europe next February, I highly recommend making the pilgramage to
FOSDEM, and be sure to come up and say "hi!" I promise I don't bite.

View File

@ -0,0 +1,67 @@
---
layout: post
title: Identi.ca is dead to me
tags:
- opinion
- identica
- microblogging
- twitter
---
There was a time when I was a big fan and user of open source microblogging
site [Identi.ca](http://identi.ca). I regret ot inform you that this time has
passed and I can no longer in good conscience support the platform.
Identi.ca has always had issues, to be expected of an open source web property,
there are bound to some rough edges running around. Things took a turn for hte
worse when the team decided to [perform a major
upgrade](http://status.net/2011/09/15/upgrading-identi-ca-and-other-statusnet-cloud-sites-to-1-0-0rc1)
which took the site offline for an entire weekend. The major upgrade in
mid-September introduced a number of issues:
* Entirely new UI which improved things in some areas (more AJAX) but
introduced whole new UX flows, heavily padded rounded UI elements and new
hiding places for elements (Groups) that I used to use heavily (why the
christ would you put the Groups that I **admin** behind three clicks and not
have them in the stupid sidebar? Idiocy).
* Took the XMPP bot offline for interacting with Identi.ca. This was often the
*only* way I interacted with the site!
* [Data integrity
issues](http://status.net/2011/10/28/big-loss-of-data-on-identi-ca)
* A [number](http://status.net/2011/12/20/identi-ca-down-update-not-any-more)
of [stability
issues](http://status.net/2011/12/02/unscheduled-downtime-for-identi-ca) and
[bugs](http://status.net/2011/11/05/overview-of-technical-problems-with-identi-ca)
I would go on, but my mouth is already foaming at an unhealthy rate so I better
stop before I get kicked out of this coffee shop.
Anyways, it is of my opinion that the folks behind made a classic blunder: the
major re-write (joining Netscape 5, Perl 6, Python 3, and numerous other
over-promising projects that falter in the "real world"). Eschewing the
evolutionary approach to a project means large changes in data structure or
user experience can and will be made before anybody has seen them operate with
"real world" data and users.
I'm not sure where this leaves me with regards to using Identi.ca, I want to
like the site so badly but every tiem I've tried to use it in the past three
months I end up terribly frustrated.
----
*Extra bonus rant:* If you ever try to use the mobile site, you'll have a taste
of how silly Identi.ca can be sometimes. If the site doesn't detect that your
browser is mobile (which happens on every device for me), then you have to load
the full non-mobile home page, at the bottom of which is a "Switch to mobile
desktop layout" link. The link doesn't have an href, it uses **fucking
JavaScript**, clicking this link will reload the page with a special
mobile cookie set. There is no `m.identi.ca` site at all.
To use Identi.ca from a mobile browser: your browser must run JavaScripts, you
must load the full non-mobile document, click that link, set the cookie then
hope that your browser keeps that cookie around forever.
Uh oh, my mouth is foaming up again, better stop here.