Las primeras dos fotos, donde lo agarramos de sorpresa y luego se hizo el loco:

Y la que salió bien, donde ya está posando cual modelo en propaganda de galletitas...
Las primeras dos fotos, donde lo agarramos de sorpresa y luego se hizo el loco:

Y la que salió bien, donde ya está posando cual modelo en propaganda de galletitas...
To go along with recent work to enable information sharing for bugs and branches, we are now enabling privacy for blueprints for beta testers. This means that blueprints now support some of the different information types that bugs and branches also support. For projects with a commercial subscription on Launchpad, this means blueprints can now be set to proprietary or embargoed. Project owners can also manage sharing for blueprints from their project’s sharing details page. For more on how sharing itself works, see Curtis’ blog post that announced that Information sharing is now in beta for everyone.
We have some minor fit-n-finish issues to complete, like nicer UI elements, and of those, we have one last known bug in progress — we know that blueprints don’t currently honor the sharing policy default when new blueprints are created. However, we thought it was worth getting this work to beta testers now to start getting feedback on this as we turn to finishing off the privacy work that is left to do.
Enjoy privacy for blueprints, beta testers! And please file bugs on any issues you find.
Read moreHewlett-Packard released two beta versions of its open source webOS on Friday: one for developers that runs on the Ubuntu Linux desktop, and one for the “OpenEmbedded” development environment, intended to help developers port webOS to new devices.
The August Edition, as the webOS team calls the latest release on the project website, consists of 45 open source webOS components and 450,000 lines of code. The two versions were released under the Apache 2.0 license, which is one of the most liberal and accepted in the open source community, the team said.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read moreThe OpenStack Board of Directors met this week and on the agenda was a somewhat surprising action item: Vote on whether or not to accept VMware – once thought to be a competitor to the project – into the increasingly popular who’s-who club of cloud computing.
VMware’s going to have to wait to see if they’ll join the party though.
The OpenStack Board met Tuesday evening but didn’t get around to considering VMware’s application. VMware may now have to wait for OpenStack’s next regularly scheduled board meeting, which is not until Oct. 19. There is a chance the board would reconvene in a special meeting before then, but there are no official plans to do so.
Some expect VMware to be a significant contributor to two areas of OpenStack, including virtual networking – which is being led by engineers from Nicira, which VMware bought – and integration of OpenStack with VMware’s Cloud Foundry platform as a service (PaaS) tool. The elephant in the room is whether VMware will work to further integrate its ESX hypervisor into the OpenStack project. Doing so could make it easier for VMware users to access non-VMware public clouds, undercutting the vCloud ecosystem that VMware has been developing.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read more
Luego de recibir algunos reclamos acerca de que nunca subí el video del casamiento (de ya hace casi cuatro años), me puse un poco las pilas y acá están.
No subí el .iso que dejó el fotógrafo (bah, el tipo me dejó un DVD, yo tengo guardada la imagen), sino que los partí y re-encodeé en theora para que sean más fácil de subir y/o elegir qué ver.
Entonces (haciendo click en cada foto)... el primer video es del casamiento por civil:
Ya el mismo día que la fiesta, primero fue la ceremonia:
La fiesta propiamente dicha está en tres partes... la picada y el baile inicial, la sesión de fotos, más baile y los juegos, y finalmente el brindis, algunos mensajes y ya las despedidas cuando se iban todos.

El fotógrafo también nos dejó un resumen del casamiento, algo cortito pero que muestra un poco de todo:
Y el postre son las fotos de la luna de miel:
Market research firm IDC says that data from a new survey shows that “open cloud is key for 72 percent of customers.”
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read moreRackspace one of the key founders of OpenStack, has finally switched to OpenStack.
These products will be provided to customers in limited amounts over a period of time to ensure a smooth ramp-up.
- Cloud Servers, powered by OpenStack – based on the latest OpenStack compute release, this solution is fast, reliable, scalable and is accessible via the new OpenStack API as well as via an easy-to-use, intuitive control panel. Limited availability sign-ups are open now and Rackspace will begin providing access on May 1.
- Cloud Control Panel – the new Control Panel was built from the ground up and with the customer in mind. It is simple, fast, intuitive and flexible. The new control panel also features multiple enhancements, including server tagging and multi-region capabilities.
The following products are in “early access”, as they are production workload ready but have limited support available, no service commitments and no billing.
- Cloud Databases, powered by OpenStack –gives customers API access to massively scalable, high availability MySQL database that is based on SAN storage for high performance and provides automated management of common database tasks.
- Cloud Monitoring –helps customers easily monitor their infrastructure and applications proactively, including OpenStack Clouds.
The following products are in “preview”, as we are currently inviting customers to test the early version of these products.
- Cloud Block Storage, powered by OpenStack – this new solution is designed to give customers highly elastic raw storage and a choice between a high performance (leveraging solid state disks) or a standard lower-cost block storage solution.
- Cloud Networks, powered by OpenStack – this solution is designed to allow customers to manage logically abstracted network services programmatically. Software-defined virtual networks provide flexibility and agility in addition to enhanced security via network isolation and port filtering.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read moreIs cloud storage really more power efficient?
There is, however, an often-touted benefit of using the cloud for data storage and that is power savings. Broadcasters are only now becoming aware of the importance of controlling power costs. Moving forward, technical managers can expect federal, state and local government bureaucrats to increasingly drive companies to use less electricity. One proposed way to reduce electrical costs is to move large-scale data storage off site to a server farm.
A huge server farm may be more efficient, have newer servers consuming less power and operate with lower costs than can a local production or broadcast house—right? Cloud storage providers may tell you so, but the real answer requires a bit of investigation.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read moreLaunchpad’s bug and branch privacy features are being replaced by information sharing that permits project maintainers to share kinds of information with people at the project level. No one needs to manage bug and branch subscriptions to ensure trusted users have access to confidential information.
Project maintainers and drivers can see the “Sharing” link on their project’s front page. The page lists every user and team that the project shares with. During the transition period of the beta, you might see many users with “Some” access to “Private Security” or “Private” user information. They have this access because they are subscribed to bugs and branches. Maintainers can unshare with users who do not need access to any confidential information, or just unshare a bug or branch with a user. Maintainers can share share with a team to give them full access to one or more kinds of confidential information.
I have prepared a video that demonstrates the features (my apologies for the flickering)
Projects with commercial subscriptions can also change bug and branch sharing policies to set the default information type of a bug or branch, and control what types they may be changed to. Maintainers can set policies that ensure that bugs and branches are proprietary, and only proprietary, to ensure confidential information is never disclosed.
I maintain many project which have a lot of private bugs and branches. The sharing page lists a lot of people, too many to read quickly. I know most work for my organisation, but I don’t even know everyone in my organisation. So I wrote a Launchpad API script that can be run by any project maintainer to share the project with a team, then unshare with the team members. The members still have access to the bugs and branches and their subscriptions still work, but they will lose access to my project when they leave the team. This arrangement makes it very easy to manage who has access to my projects. share-projects-with-team.py is run with the name of the team and a list of projects to share with it.
./share-projects-with-team.py my-team project1 project2
Read moreWhen it come to ARM Servers one thing that everyone agrees is that the new 64 bit architecture, introduced in ARMv8, will be a significant milestone for this market.
It seems that 14.04 LTS will be a big release for ARM Servers, as it is likely to be the first Long Term Support with ARMv8. However, the road to 14.04 starts now!
The first set of ARMv8 licensees are starting to be announced, so it is time to get Ubuntu ready for hardware bring up. What better place to start that with an ARMv8 kernel? and that is what Jeremy Kerr from Canonical has just published.
As he says: “Most of the components of the 64-bit ARM toolchain have been released, so I’ve put together some details on building a cross compiler for aarch64. At present, this is only binutils & compiler (ie, no libc), so is probably not useful for applications. However, I have a 64-bit ARM kernel building without any trouble.”
If you want to find out more about Jeremy’s work, see:
With the test kernel builds, we’re able to start low-level testing of ARMv8 hardware as soon as they become available. So, we are ready for ARMv8 hardware bring up, Are you?

Have you ever wondered what is all the fuss about ARM Servers? Yes? good , good.
Have you ever wish you had some crazy Zooming UI presentation that told you all about it? what.. no!? Well though.. because now you have one
If you haven’t heard of Prezi, it is a new way to generate more dynamic presentations. I will give you a few tips:
Without further ado, I give you ARM Server on a Prezi:
url: http://prezi.com/_zwqpnowk8cv/arm-server/
For the last year, Launchpad has been doing schema patches using a process we call ‘FDT’, short for Fast Down Time. We have applied 60 such patches, typically taking between 60 and 90 seconds each time, at 1000UTC, our scheduled daily 5 minute downtime window for DB patching.
Recently, we eliminated Slony from our environment, which has dropped the overhead of schema patches to ~6 seconds, and this gives us <10 second downtimes to apply schema patches. We’re taking advantage of this to add two new downtime windows at 0200 UTC and 1800 UTC. All three windows will be for 10 seconds. Hopefully you will never notice that we’re doing schema patches. But if Launchpad is offline for a few seconds at one of these times, you’ll know why – we’re busy rolling out a schema change to bring a new feature to life.
Read more
Hace algunas horas se dieron a conocer las charlas que estarían en la PyCon Argentina 2012.
Llamó la atención que no apareció entre las aprobadas el nombre de un orador muy conocido en la comunidad. ¿Por qué? No lo sé, yo no participé en la selección de charlas.
Debo decir que voté algunas charlas, pero luego no pude seguir con eso, y al final no participé en ninguna reunión... la verdad es que este año no tuve el tiempo como para ponerme con ese tema.
Otra gente sí lo tuvo, o no lo tuvo pero igual lo dedicó. Y votaron muchas charlas. Y se reunieron muchas veces. Y discutieron razones para que las distintas charlas estén o no estén. Y eligieron algunas. Y dejaron de elegir otras.
Estoy seguro que a algunas de las que dijeron "NO" estaban buenas, de verdad. Pero no hay espacio para todo, y las razones por las cuales se aprueban algunas charlas o se dejan de aprobar son complejas. No entran en un comentario. Habría que transcribir horas de charlas (sé que se juntaron por IRC y por videoconferencia) para encontrar las verdaderas razones.
El tema es que algunas personas luego empezaron a hacer bardo por twitter sobre las decisiones tomadas. Y no es lo correcto. Porque no conocen el trasfondo de las decisiones. Porque mientras otros invertían tiempo propio en hacer que la PyCon tenga la mejor calidad posible de charlas, ellos estaban haciendo otra cosa.
Entonces, mi mensaje es: el espacio para laburar en la selección de charlas estaba abierto a todos, pero no lo aprovechaste. Si no quisiste invertir de tu tiempo ahí, dale la derecha a los que sí lo quisieron, y lo invirtieron.
O sea, si querés participar, participá. Y si no, no rompas las pelotas.
Google will be launching 1 Gbps (1000 Mbps) Internet connection in Kansas City, US.
This will be a huge jump from the current average speed of 5.8 Mbps in the US. Just hope this spreads to other places soon.
In India the average speed is 0.9 Mbps. Now when will this come to India ?
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read more
Finalmente viendo películas como corresponde... veremos si podemos mantener el ritmo durante el resto del año, :), y recuperar terreno perdido (estoy viendo películas que anoté hace dos años y medio!). Por otro lado, estuve revisando las pelis que tengo pendiente de ver... y están buenísimas! Me dan ganas de ponerme más seguido...
Bueno, las que ví:
Algunas nuevas anotaciones para el futuro:
Finalmente, el resumen según cuando las anoté:
(24-Sep-2008) 15 6
(21-Ene-2009) 18 18 12 1 1
(09-May-2009) 13 11 10 5
(15-Oct-2009) 17 16 15 14
(01-Mar-2010) 18 18 18 18 16
(12-Sep-2010) 19 18 18 18 18
(14-Dic-2010) 13 13 13 13 12
(13-Abr-2011) 23 23 23 23
(09-Ago-2011) 12 12 11
(06-Ene-2012) 21 21
(27-Jul-2012) 15
Total: 113 123 121 125 117
In my previous entry, I argued that Ubuntu is possibly the best development environment to write connected android apps, thanks to Juju. Although using WordPress was possibly not a great example
I still think that this idea has legs! Hence, I have decided to build an example project.
The example will mainly be a simple and plan ToDo list app for Android, that gets its items from a back-end MySQL server.
So here is my list of things to get done for this example project:
And as there is no time like the present, here is the first bullet point!
Accessing a Juju Local Environment from the Android Emulator
As I was working on my wordpress charm, the easiest thing for me to do was to access the local webserver set-up for the blog. I first installed the Android SDK, which turned out to be pretty easy to do by just following the instructions posted at http://developer.android.com/sdk/index.html . Apart of the sdk tools that download you the emulator, build tools and so on.. you can also choose to use Eclipse as your IDE. If you do this, you can then install an Android plug-in that is *very very* complete. Having had previous experience with Eclipse, I choose this root and unless you feel very strongly against it, I recommend that you do the same.
Once I had the SDK installed, I run the 2.2 emulator (because that happens to be the version in the spare Android phone that I plan to use later on) and open the local IP address of the WordPress service. That just worked fine.
Then I decided to create a sample android project and tried some code to do the same. I found that the following method within the main activity of the project was able to ping and then open in a browser window the wordpress app:
private String hostip = "192.168.122.137";
...
public void pingme(View view) {
TextView info = (TextView) findViewById(R.id.mytext);
WebView mweb = (WebView) findViewById(R.id.webView1);
InetAddress in = null;
Log.w("PING","trying to reach" + hostip);
info.setText("trying to reach" + hostip);
in = InetAddress.getByName(hostip);
if (in.isReachable(5000)) {
info.append("\nHost found");
Log.w("FOUND",in.getCanonicalHostName());
} else {
info.append("\nHost found");
}
mweb.getSettings().setJavaScriptEnabled(true);
mweb.loadUrl("http://"+hostip);
}
So in a nutshell, the first bullet point (and the easiest) of my list is completed!
El otro día llevamos a Felu a ver La Vuelta al Mundo en un Violín, una obra muy muy interesante. De su sitio:
La vuelta al mundo en un violín es un espectáculo musical didáctico en el cual se presenta música de diversos compositores en forma amena y con participación del público. La gran mayoría de los adultos supone (y está comprobado por diversos estudios e investigaciones recientes) que el introducir a un niño en el mundo de la música clásica no sólo es importante per se sino que también funciona como estímulo para potenciar su rendimiento en otras áreas de su vida cotidiana, tanto en el orden intelectual como en el emocional. La sensibilidad para disfrutar del arte musical es común a todos los niños. Por tal razón lo más importante de este evento es el contacto del público con la música: intencionalmente la escenografía es sobria, y no se utilizan muñecos o payasos, comunes en espectáculos para niños.
Y es así, con "sólo" una orquesta de cuerdas en escena (muchos violines, violas, violonchelos, un contrabajo...), el espectáculo es divertidísimo gracias a diversas actuaciones de las cuales no voy a contar nada para que disfruten todo cuando la vayan a ver.
Felipe, obviamente, volvió enganchadísimo. Y como el tiene una guitarrita, se me ocurrió armarle un arco casero para que la use como violín. Como la guitarra es demasiado grande para él, también se le ocurrió (a él solito) usarla como violonchelo, como pueden ver en la foto...
(hagan click en la foto para ver el video)
Project maintainers can now see all the private bugs in their project. While Launchpad tried to ensure the proper people could see private bugs in the past, the old subscription mechanism was brittle. Users could unsubscribe themselves and lose access, or retarget a bug to another projects which does not update bug subscriptions. The Purple squad migrated project configurations to project sharing so that all private information was shared with project maintainers. Project sharing ensures that confidential information is disclosed to the proper people.
If you are a project maintainer, you might be surprised to find old private bugs that you have never seen before. This happened to me. Some ancient private bugs were in the “New” listing of bugs, other were buried in search results. You can search for just private bugs to review all private bugs.
We reverted the information type terminology changes introduced a few months ago.
While the jargon-laden terms helped the small number of people who work with confidential information, the people who report bugs were confused. The most common reason for unwanted disclosure is that people enter confidential information, and cannot see how to make it private. Sometimes a user may not notice the mistake until a few minutes later. We also revised the descriptions of the information types to help new users quickly select the correct information type.
Read moreYou can now hide your own bug and question comments. If you want to hide a comment made in error, you can use the “Hide comment” action.
You can see it, and even unhide it if you choose. The project’s maintainer or the trusted people delegated to work with private information can still see your comment.
This allows you, or the people the project shares private information with, to hide just the comments that contain personal information. The bug does not need to be made private if the comment can be hidden. Project maintainers can also hide comments because they contain spam or abuse.
Read more
Cloud computing is more than just a new set of technologies businesses can utilize — it is a new way of thinking about technology. As a result, businesses are being challenged to transform every single practice and policy they are using to govern how IT systems are managed and deployed. This IT/business evolution spotlights the need for a more business-minded executive to oversee the dynamic issues introduced by the cloud. The time of the chief cloud officer (CCO) is upon us. Someone who will advise and manage a company’s approach to the cloud (community, hybrid, private, public) and who will maximize the opportunities it offers in a variety of lines of business, while mitigating the complexities or concerns introduced.
If cloud computing plays a significant role in your business or you expect it to in the near future, consider these 10 critical job functions, which a CCO could handle for your organization.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.
Read more
Latest Official Posts
Featured Blogs
People
You can't take the sky from me
Alex Chiang
allenap
Amit Kucheria
Andrew Glen-Young
Ara Pulido
Barry Warsaw
Bazaar team
Bitácora de Vuelo
Bjoern Michaelsen
Björn Tillenius
Blogging in the Wind
Brad Figg
Brad Marshall
Brian Fromme
Canonical Blog
Canonical Design Blog
Canonical ISD
Canonical Marketing Team Blog
cat /dev/ursula
cat /dev/ursula
Certifiably (Brendan Donegan's Ubuntu Blog)
Chad Miller
Chris Halse Rogers
Chris Johnston
Christian Reis
Code Singer: Gary Poster's blog
Corey Goldberg
Daniel Holbach's blog
Danilo Segan
Darryl Weaver
David Henningsson
David Murphy
David Murphy
David Owen
David Planella
Distributed Teams
Gavin Panella
Graham Binns
Guilherme Salgado
Gustavo Niemeyer
How Bazaar
Iain Lane
Illruminations
Inert Ramblings
James Tait
James Westby
Jamie Strandboge
jedimike's adventures in typing
Jeremy Kerr
Joey Stanford
John Pugh
Jono Bacon
Jorge Castro
Julian Edwards
Julien Funk
JussiP
Ken VanDine
Keng-Yu Lin
kevin gunn
KyleN Ubuntu
KyleN Ubuntu
Landscape Blog
Launchpad Blog
Launchpad Blog
Lee Jones
Louis Bouchard
Manuel de la Pena
Marcin Juszkiewicz
Mark Shuttleworth
Martin Albisetti's blog
Martin Pitt
Matt Fischer
Michael Hall's Blog
Michael Hudson
Michael Terry
Multi-touch on Ubuntu
Not Lucky All The Time, But Smart Everyday…
Olli's random thoughts and impressions
person@CANONICAL-DESK
person@CANONICAL-DESK
Pixoul Photography
Prakash Advani
racarr's blog
racarrs blog!
RedVoodoo.org
Ricardo Salveti
Rick Harding
Robert Ancell
Robert Ayres
Ryan Finnie
S3hh
Scott Sweeny
Sean Feole
Shang Wu
Shuduo
Sidnei da Silva
sil2100//vx web-page
Smackerel of Opinion
Something driven development
Stéphane Graber
Steve George
Steve Langasek
Stuart Bishop
Stuart Metcalfe
Subcritical
Ted Gould
The Dowdberrys
The Orange Notebook
The Quality Hour
The Raving Rick
Timo Jyrinki
tvoss@work
Ubuntu App Developer Blog
Ubuntu Kernel Team Blog
Ubuntu One Blog
Ubuntu Server Team
Ubuntu Server Team
Ubuntu Server Team Blog
utlemming
utlemming's blog
Victor Palau's Blog
Wanderings of a Kernel Engineer
ZhengPeng Hou
~apw
Canonical Voices© 2010 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.