olea is currently certified at Master level.

Name: Ismael Olea
Member since: 2000-10-24 16:45:00
Last Login: 2009-08-04 09:07:28

FOAF RDF Share This

Homepage: http://olea.org/diario/

Notes: Ismael has been a free software activist since 1994. He has coordinated the Spanish Linux Documentation Project TLDP-ES (known as LuCAS) since 1998 to 2005, is a founding member of the Spanish Linux users association Hispalinux and the local groups Indalinux and Linux Madrid and has deeply involved in the organization of the Hispalinux's congresses.

In his work career had been CTO of one of the very first commercial linux distributions in Spain, HispaFuentes Linux, and now manages their own consulting company, Planeta Olea SL, specialized on technology strategy and consultancy about free libre open source software, FLOSS, and the digital revolution.

He is member of the GNOME Foundation, the Foundation for a Free Information Infrastructure, the Instituto de Estudios Almerienses and is a visiting lecturer at the Instituto Superior de Estudios e Investigaciones Tecnolológicas, Caracas (Venezuela).

For long time is a passionate researcher on electronic publishing in almost all its facets and a supporter of applying the knowledge economy of FLOSS on the linguistic resources for the Spanish language. For the last years is performing an intense activity on the development of the SOOS concept, «Standard Organizational Operating System» in the framework of an open digital revolution. Had given dozens of talks in Spain, France and Latin America.

He is devoted to Our Father Genarín of León and tries to be sure everybody knows he comes from Almería (Spain).

Projects

Articles Posted by olea

Recent blog entries by olea

Syndication: RSS 2.0

31 Jan 2010 »

drobo-utils RPM's for Fedora

I've just released the first draft of the drobo-utils for Fedora (12). As usual there'll be available at my repository: drobo-utils.

If I get satisfied with it I could postulate it to Fedora/RPM-Fusion. Feedback would be grateful. <h4>About Drobo</h4>

The Drobo is supposed to be the 8th wonder in backup hardware. It does all the data integrity stuff automagically and only asks to be feeded with off the self SATA disks from time to time. Supposely as easy as your mother could manage it.

For your curiosity, my backup system is composed with Drobo and the desktop application back-in-time (which puts rsync under the hood). Time will say if this is as easy and secure as a soho user (that's me) needs.

Syndicated 2010-01-31 23:33:00 from Ismael Olea

29 Jan 2010 »

Mi dictamen sobre el iPad

Oh sí, yo también puedo escribir sobre el iPad. Y para más inri me autocito (y re-cito) de la lista de comunidad de ASOLIF:

De todas maneras, niños míos, la palabra aquí es «dynabook».

Lleva años inventado y sólo Esteban Curreles es quien lo trae al mercado. Para bien y para mal.

Para los applefanboys: http://rinzewind.org/archives/<wbr />2010/01/27/guia-visual-para-<wbr />entender-el-dia-de-hoy-por-lo-<wbr />menos/

Y para los escépticos: http://es.wikisource.org/wiki/<wbr />La_zorra_y_las_uvas_(Esopo) Los demás, a estudiar, que merece la pena.

Y me quedo tan ancho.

Syndicated 2010-01-29 06:21:00 from Ismael Olea

28 Jan 2010 »

Un dictamen sobre el proyecto de licencia pública de marca

Un buen amigo me pidió realimentación para el proyecto de licencia pública de marca que promueve el gobierno de Brasil. De ahí que hiciera algunas disquisiciones al respecto y he aquí algunos resultados. Creo que su lectura será sugestiva al menos. <h4>El análisis SOOS</h4>

He repasado los contenidos de http://www.softwarepublico.<wbr />gov.br y he comprendido que la mayoría de mis conclusiones actuales no encajan en el proyecto de la «licencia pública de marca». Mis indagaciones están concebidas para tratar de identificar y resolver «las ineficiencias del software». En ese sentido hemos trabajado mucho en desarrollar un, llamémosle, punto de vista «SOOS». La aplicación de un «análisis SOOS» genera mucha información sobre los problemas del software y apunta a nuevas líneas de trabajo para resolverlos[1] [2] [3].

Es muy interesante descubrir muchos puntos de encuentro entre ambas iniciativas, LPM y SOOS. Por activa o por pasiva aparecen nuevos problemas que realmente siempre han estado ahí. Y un caso muy interesante es el problema que generan las marcas al mundo del software en general y al FLOSS en particular. Me ha alegrado mucho saber que en Brasil se ha decidido trabajar en ello.

El principal problema que generan las marcas, desde el punto de vista SOOS, es que son una terrible, y en la práctica infranqueable, barrera contra la convergencia. ¿A qué convergencias me refiero? En realidad todas las posibles, puesto que a más convergencia, más productividad, en el sentido de la ley de metcalfe. Como es sabido, la práctica en el mundo del software —ambos abierto y privativo— es la de la más absoluta divergencia/forking/<wbr />fragmentación. Me atrevo a decir que en una enorme cantidad de los casos la divergencia se infiere a partir del principio de mercadotecnia de la diferenciación, del que el concepto marca es el epítome.

En este dictamen mi problema es que no veo que el proyecto de «licencia pública de marca» sea capaz de minimizar las divergencias del software. Desde mi punto de vista eso se explica porque hay una relación 1:1 marca:producto. <h4>Al márgen del análisis SOOS</h4>

Por otro lado hago el esfuerzo de olvidar todo el análisis SOOS que realmente tanto me apasiona y mi impresión es que realmente la iniciativa LPM puede proponer una solución legal reutilizable para un problema que no es el más llamativo pero sí claramente recurrente. Está al orden del día saber la mayoría de las organizaciones de desarrollo de software abierto importantes han necesitado escribir sus propios reglamentos y licencias para la creación, uso y explotación de sus propias marcas:

En este sentido parece razonable hacer un esfuerzo de formulación y crear un esquema legal claro, manejable y realista que pueda ser reconocido y adoptado por cualquiera de estas organizaciones, incluso sustituyendo sus actuales reglamentos, y sobre todo capaz de ser adoptado por nuevos actores.

Directa o indirectamente es una ventaja clara para reducir los costes de adopción del software. Para mi corazoncito SOOS es una pequeña decepción porque no sirve claramente para maximizar los efectos de red de metcalfe. <h4>Antecedentes: las asociaciones para estándares abiertos</h4>

Me permito llamar la atención de que éste problema de marcas no es nuevo o exclusivo del mundo del software abierto. Existe exactamente el mismo en el mundo de los «estándares»[4]  y, como decimos en España, para ejemplo un botón: el Objet Management Group.

Probablemente haya mucha más información que pueda estudiarse en Consortium Info y el propio Andy Updegrove pueda ser un gran experto con quien contar.

<h4>Conclusión SOOS</h4>

La iniciativa LPM nos es interesante en tanto que llama la atención del problema real de la ineficiencia del software. Pero a priori no vemos cómo puede servir para la rotunda transformación del sector que tan urgente nos parece. <h4>Conclusión no SOOS
</h4>

Dado que hasta ahora yo no he tenido ocasión de estudiar este tema no puedo aportar ni validar cuáles deben ser los requisitos que deba cumplir una licencia pública de marca, o una recomendación legal equivalente, pero sí me atrevo a sugerir algunas acciones:

  1. recopilar las soluciones legales creadas hasta ahora por los colectivos más importantes de creación de software abierto y de estándares;
  2. caracterizar las condiciones de licenciamiento, y en ese sentido el trabajo de Ken Kretchmer para identificar las condiciones para ser abierto es extremadamente inspirador;
  3. replicar la práctica de Creative Commons de crear un esquema legal abstracto, que en este caso imagino debe contemplar tanto la licencia en sí como alguna clase de reglamento que la acompañe, capaz de ser traspuesto a los sistemas legales de cada país, a menos que se demuestre la certeza de que hay suficiente compatibilidad legal internacional;
  4. considerar que tal vez sea necesario replicar el sistema CC de varios grados de licenciamiento diferentes para responder a diferentes realidades; en la práctica ocurre exactamente igual con el licenciamiento de software en el sistema combinado GPL/LGPL/BSD;
  5. validar la propuesta a través de socios comprometidos, idealmente aquellos que pertenecen al primer punto de esta lista;
  6. idealmente, mantener un comité de expertos que puedan evaluar la compatibilidad de los esquemas de licenciamiento de terceros con el esquema del punto 2 y la licencia del punto 3.

Syndicated 2010-01-28 16:16:00 from Ismael Olea

18 Jan 2010 »

LinuxTag CfP ends January 29th

LinuxTag logo

Hey: all of you interested on presenting articles at LinuxTag should be in a hurry. The call for papers finishs Jan 29. Go!

Syndicated 2010-01-18 16:19:00 from Ismael Olea

16 Jan 2010 »

Be your own eID provider

One of my particular interests is to explore the requirements of digital personal sovereign and it's implementation with libre software. I've done some thought about this in the past (what I call the «SOOS Desktop») and I'm implementing little by little on my own server. For me, this is an amazing research line deserving a lot of attention both the formal academic and the technical development side. But everything is still to be made.

One of the pieces needed, getting particular importance from some time to now, it's the authentication services. The most trivial protocol to choose today is OpenID.

I've been using phpMyID as my OpenID provider for some time to now, but some consumers complaint about it. I suppose it's because it doesn't implement OpenID v2. After some research I've found the suggestion to use SimpleID. The list of OpenID provider software, I think all the items are OSS, was helpful too. Seems there are very powerful alternatives for «enterprise» servers. In my case I've prefered a low requirement system so I finally chose SimpleID.

When installing software my usual practice is to install it packaged. It's the easiest way to manage  what software is installed, where and to have it integrated with the rest of the operating system... hopefully. So I have made a  SimpleID RPM package for CentOS 5. The present form doesn't accomplish all the Fedora Packaging Guidelines but I think is fine enough for serious sysadms. I plan to maintain it through Olea.org RPM's repo. <h4>Seting up your OpenID identity</h4>

After installing SimpleID you should configure the webserver name at /var/www/simpleid/www/config.inc and restart Apache.

For each identity you should fill a username.identity file at /var/www/simpleid/identities/. Take care username here should be the user name you want to log against SimpleID and have nothing to do with your identity details. For creating your password hash you can use md5sum:

echo -n "mypassword" | md5sum

An interesting feature is you can create your own Extensible Resource Identifiers (XRI) and add them to your user identity file. I hope to play a bit with this soon.

When ready, log into SimpleID, the default URI I set in my package is http://localhost/simpleid. Now go to the «My Profile» tab, where you can gather all the HTML links tags you should add to the webpage you want to be your OpenID URI. In my case it is in http://ismael.olea.org, which seems to me a meaningful URI. You only need the copy generated code to the HEAD section of the chosen HTML document. It's a flexible way to really decide how your OpenID URI should look like.

When ready you'll can login using your brand new OpenID URI. Enjoy.

Another SimpleID nice feature is the «My Site» tab. When login into your account you'll can track the OpenID consumers you are logged and remove them if needed.

I'm waiting for new SimpleID releases!

Syndicated 2010-01-16 04:38:00 from Ismael Olea

145 older entries...

 

olea certified others as follows:

  • olea certified juantomas as Master
  • olea certified miguel as Master
  • olea certified Barbwired as Journeyer
  • olea certified olea as Master
  • olea certified rodrigo as Master
  • olea certified jwz as Master
  • olea certified lxhispano as Master
  • olea certified federico as Master
  • olea certified chema as Master
  • olea certified dcm as Master
  • olea certified cuenca as Master
  • olea certified alvaro as Journeyer
  • olea certified rms as Apprentice
  • olea certified esr as Apprentice
  • olea certified jfs as Journeyer
  • olea certified julio as Master
  • olea certified gwolf as Journeyer
  • olea certified Ankh as Master
  • olea certified martin as Master
  • olea certified jgb as Master
  • olea certified villate as Journeyer
  • olea certified xose as Journeyer
  • olea certified jjamor as Master
  • olea certified gerardo as Master
  • olea certified davefx as Journeyer
  • olea certified godoy as Master
  • olea certified mancha as Master
  • olea certified gregorrothfuss as Journeyer
  • olea certified danguer as Journeyer
  • olea certified macana as Journeyer
  • olea certified acero as Journeyer
  • olea certified jotajota as Apprentice
  • olea certified syvic as Apprentice
  • olea certified tanis as Journeyer
  • olea certified Jordi as Journeyer
  • olea certified afernandes as Journeyer
  • olea certified mooch as Master
  • olea certified alejandro as Apprentice
  • olea certified Camille as Journeyer
  • olea certified Jujo as Apprentice
  • olea certified garnacho as Master
  • olea certified skymix as Journeyer
  • olea certified lgs as Journeyer
  • olea certified natfriedman as Master
  • olea certified marcelo as Master
  • olea certified alvherre as Master
  • olea certified connolly as Master
  • olea certified ndw as Master
  • olea certified Aspuru as Master
  • olea certified alo as Master
  • olea certified tacvbo as Journeyer
  • olea certified dsandras as Master
  • olea certified jemarch as Apprentice
  • olea certified ettore as Master

Others have certified olea as follows:

  • olea certified olea as Master
  • jacobo certified olea as Journeyer
  • rodrigo certified olea as Master
  • lxhispano certified olea as Master
  • juantomas certified olea as Master
  • davefx certified olea as Master
  • monk certified olea as Master
  • julio certified olea as Master
  • jjamor certified olea as Master
  • gerardo certified olea as Master
  • pau certified olea as Journeyer
  • alo certified olea as Journeyer
  • alvaro certified olea as Journeyer
  • gwolf certified olea as Master
  • fxn certified olea as Journeyer
  • jfs certified olea as Journeyer
  • danguer certified olea as Master
  • kiwnix certified olea as Master
  • macana certified olea as Master
  • afernandes certified olea as Master
  • acero certified olea as Journeyer
  • gregorrothfuss certified olea as Master
  • tanis certified olea as Master
  • syvic certified olea as Apprentice
  • jotajota certified olea as Master
  • kilmo certified olea as Journeyer
  • xose certified olea as Journeyer
  • Barbwired certified olea as Journeyer
  • carlosgc certified olea as Master
  • alejandro certified olea as Journeyer
  • jarashi certified olea as Journeyer
  • alexm certified olea as Master
  • patux certified olea as Master
  • gpoo certified olea as Journeyer
  • alvherre certified olea as Master
  • Sandino certified olea as Journeyer
  • jmauricio certified olea as Master
  • zordor certified olea as Master
  • kclayton certified olea as Master
  • tacvbo certified olea as Journeyer
  • KBrown certified olea as Journeyer

[ Certification disabled because you're not logged in. ]

New Advogato Features

FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!

X
Share this page