Traducción del artículo sobre actualizaciones

Este trabajo se inició en la lista de correos MDKTrans.

Sin embargo, por problemas "técnicos" (como mails que llegan tarde provocando que varios colaboradores traduzcan lo mismo), Diego sugirió utilizar el foro para la traducción de artículos como este.

El artículo en cuestión es este: http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/

En dicho artículo se distinguen varias partes:

• - Caroline Casual-User
• - Pamela Packager
• - Connie Community
• - Nancy Ninja
• - Where you stand depends on where you sit
• - Bonus
• - About this blog post

Cada colaborador puede tomar una parte (de hecho, creo que ya han atacado a Caroline Casual-User por lo menos, dos traductores).

Sin embargo, considero que la parte "Where you stand depends on where you sit" podría dividirse por ser la más larga:

----------------Parte 1----------------

This is something my colleague Adam Young
told me this morning. It kind of resonates for me here – “Where you
stand depends on where you sit.” I think at some level in the various
discussions about Fedora updates, Caroline, Pamela, Connie, and Nancy
are making assumptions and taking away completely interpretations of the
same idea, and communication is breaking down, because they come from
such different positions. Computing I think is really the world of the
abstract, and because so many things like, ‘packages,’ ‘updates,’
‘repositories’, ‘environments’, don’t really have real-world objects
bound to them, folks end up using the same words to describe completely
different things a lot.

----------------Parte 1----------------

----------------Parte 2----------------

Pamela wants updates to be constant throughout a release, no holds
barred – she wants the latest Gimp and she wants it yesterday. Caroline
just wants her computer to work – “please don’t change a thing – it
worked yesterday – if it breaks before my presentation I’m screwed!” Can
both their needs be met? I think so! But it’s easy to completely miss
where interests and needs can both be met when the language is so easily
interpreted to mean the problem is untenable. Let me give you an
example of how I think both Pamela’s and Caroline’s needs could be met
here:

----------------Parte 2----------------

----------------Parte 3----------------

Here, if Caroline runs stable (as she should be with a default
install of Fedora), she might notice an update to the core system once a
month or so, maybe occasional additional security or critical bugfix
updates now and then. Not two hours’ worth of updates on a fresh F13
that took 15 minutes to install a month after release…. ahem. Pamela
wants her newest Gimp and she wants it now – well, she’s got options.
She can hook her system up to testing, and if the Gimp she so craves is
not there, she can enable rawhide real quick to grab it, or look for a
koper that’s got the latest and greatest Gimp – maybe a pre-release
development version.

“Well, wait a minute!” you cry. “Once-a-month updates???” No, not
exactly. Let’s zoom in a bit on that stable package graph, okay?

----------------Parte 3----------------

----------------Parte 4----------------

Why should update policies for the kernel, dbus, firefox, inkscape,
xorg-x11-server, and cowsay be the same? Does that make sense? If an
update breaks my graphics, I can’t use anything. If an update breaks
cowsay, well… my clever MOTD is a little less clever but it shouldn’t
break other apps. So why not bundle critical stuff that’ll really hurt
our users in a huge way – the basics like networking, graphical display,
hardware support, i18n input methods, sound – and put much more
stringent guidelines on them than apps like figlet, xbiff, or xbill? If
an application is relatively self-contained and can really only break
itself – is it so necessary to be as strict about updates to it within a
stable release?

----------------Parte 4----------------

----------------Parte 5----------------

I thought this game was the bee’s knees when I was a junior in high school. Take that, The Man!

Then we have a base platform that’s a bit more stable, letting
Caroline live without fear, all without stifling
gotta-have-the-latest-apps hunger of folks like Pamela. Hmmm. Stable
base platform. That might make life easier for 3rd party developers such
as Boxee, Amazon, and Adobe to provide support for Fedora, no?

----------------Parte 5----------------

Por mi parte, me he dedicado a traducir las imágenes:

http://img229.imageshack.us/img229/5158/actualizacionesatravsde.jpg

http://img808.imageshack.us/img808/9751/actualizacionesdeversin.jpg

http://img443.imageshack.us/img443/1540/actualiazacionespkgkitd.jpg

http://img215.imageshack.us/img215/2361/actualizacionespkgkitan.jpg

http://img823.imageshack.us/img823/9663/actualizacionesusuario1.jpg

http://img204.imageshack.us/img204/2138/actualizacionesusuario2.jpg

http://img137.imageshack.us/img137/4608/actualizacionesusuario3.jpg

http://img140.imageshack.us/img140/1735/actualizacionesusuario4.jpg

http://img530.imageshack.us/img530/5448/logohb.gif

Así que, les pido tanto a los que ya tomaron una parte como a los que desean tomar otras, que por favor, lo notifique con un breve comentario en este hilo.

Una vez que esté todo traducido y revisado, armaremos un semi-clon del artículo original con imágenes y todo en Blogdrake.

Saludos.

tavillo1980