Home Home
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Open Hardware Definition Goes 1.0!

February 11th, 2011 by

The Open Source Hardware Definition has reached a major milestone, hitting version 1.0 with this morning’s announcement by the Open Hardware Summit team.  This is remarkable news for all involved in the development of Open Source Hardware (OSHW), as this really exciting community had been growing by leaps and bounds in the last couple of years, but had no single, unified symbol that different development shops could rally under.

Now, with the Definition having reached 1.0, and a logo soon to be announced to stamp hardware and project websites, the hardware crowd will be able to rally under flags similar to Tux the penguin and Beastie the daemon — not to mention the Open Source Definition and the GPL.  As a Free/Open Source Software dude regularly cheerleading the Open Hardware crowd, I am impressed at how fast this young community came this far, as the 0.3 draft was circulated at the Open Hardware Summit last September in New York.

The Definition is not meant as a license, it rather mirrors the Open Source Definition that we are so familiar with — and indeed, a very energetic Bruce Perens was one of the opening speakers of the Summit last year, and has been actively commenting on the forums on the different drafts.  Similarly to the Open Source Definition, the Open hardware definition is an umbrella meant to cover a number of differing licenses, all requiring the “source” (in this case, unobfuscated designs) of the board to be made available with the hardware as a minimum precondition.

Community members are invited to spread the word by blogging, tweeting (#OSHW), endorsing the definition, contributing designs to the logo contest, and, of course, labeling their work as OSHW 1.0.

This is a very exciting moment for the open culture movement in general, as yet another field of knowledge comes organized in the copyleft / CC / Some Rights Reserved approach.

The Audience
F2 keeping an eye on Bruce Perens, who is keeping an eye on the keynote before his, at the New York Open Hardware Summit.

How to work with OBS via slow connections

February 9th, 2011 by

The openSUSE Build Service Books have a new chapter called HOWTOs. These will be written for asked questions, the first one existing is how to work best with OBS if you have limited bandwidth. There are multiple methods to avoid large downloads or even uploads of large files (like tar balls) and let just the server do the work…

LibreOffice 3.3.0 final available for openSUSE

February 9th, 2011 by

I’m happy to announce LibreOffice 3.3.0 final packages for openSUSE. They are available in the Build Service LibreOffice:Stable project. They are based on the libreoffice-3.3.0.4 release. Please, look for more details about the openSUSE LibreOffice build on the wiki page.

The openSUSE LO team hopes that you will be happy with this release. Though, any software contains bugs and we kindly ask you to report bugs. It will help us to fix them in the future releases.

False error during update

You might see some installation errors about missing extensions when updating from OpenOffice.org, for example:

ERROR: There is no such extension deployed: com.sun.reportdesigner

Please, ignore them. They are caused by a bug in the OOo packages and can’t be avoided easily. They does not affect the LibreOffice installation!

More known bugs

Other information and plans:

LO switched to a time based schedule and more frequent bug fix releases. The purpose is to keep quality and avoid infinite RC phase at the same time. The idea is that all serious blocker bugs can be found and fixed within few weeks. Then the application is ready for masses who want to enjoy new features and more complicated fixes. The history says that bugs in less typical scenarios are found weeks after the release. Such bugs will be fixed in pure bug fix releases and released few weeks after each other. It means that more conservative people should rather wait for the 3.x.1, 3.x.2, 3.x.3 releases. We hope that it will help all people to get faster what they want.

We are already working on LO-3.3.1 bugfix release. I have just published 3.3.1-rc1. The final 3.3.1 release should be available within 2 weeks.

AppMenu-GTK and Indicator-appmenu

February 7th, 2011 by

This is probably one of the most controversial features that has been subject of continuous work from the Ayatana Project. This two pieces of software work as one and allow to export GTK+ application menus through DBus, being the end result: application menus present on the gnome-panel and unity-panel.

This feature requires at least one patch on GTK stack. I’ve talked to Ubuntu devs regarding this patch, and it was told to me that GTK+ upstream had no interest on upstreaming this patch. I’m not the one to comment this move from upstream, but I find it at least interesting that QT has upstreamed an identical patch which includes the same functionality. Since they are competing products (one can replace other totally or partially), such actions only strengthen QT. Adding a bit of speculation and the latest statements from Shuttleworth regarding QT, I wonder if it is to be expecting some ‘wind of change’… who knows?!

For us at openSUSE what does matter is if we can Factor’ize this at least the Menu Proxy patch so we can offer Unity and Indicators at the original form and not crippled. I will request soon this changes to GNOME:Factory and we’ll see what people say, regardless of upstream positions.

This is on-development software, and has some itches, but for the most it works (GTK+ applications), I would expect some polishing in the future from upstream, either way, it’s another option.

Required Patches on GTK:
*  043_ubuntu_menu_proxy.patch
*  072_indicator_menu_update.patch (still figuring if this is actually required and the possible sidekicks of not having it there)

Notify-OSD in openSUSE 11.4

February 5th, 2011 by

My first contribution to openSUSE was Notify OSD, which is also a part of the Ayatana Project. On openSUSE version of Notify OSD, I’ve included a small patch made by Roman Sukochev which isn’t was upstreamed but declined on Ubuntu. This patch enabled skinning/theming of the Notification Bubble. Before submitting this package to GNOME:Apps, I’ve talked with Roman which confirmed that he would maintain the patch for upcoming versions of Notify OSD.

This patch handles the skinning of Notify OSD through a text file (~/.notify-osd). I’ve made available an application to configure Notify OSD. This application is known as notifyconf and is available currently on openSUSE:Contrib repositories.

The interface of notifyconf is very user friendly and intuitive. This two packages enable extra functionality not present currently in Ubuntu out of the box. I believe it is important to offer more possibilities to our users.

Installing Notify OSD is done through zypper for example “zypper install notify-osd”. For notifyconf the user is required to install the Contrib repository and install the package ‘notifyconf’ (depends on QT).

notifyconf

Notify OSD replaces the package ‘notification-daemon’ and can be used either in KDE or in GNOME (same for notifyconf). This is optional software for those who want a different desktop experience. I’m thankful to Vincent Untz, Dominique and Peter Linell for allowing this two applications to be a part of the openSUSE Desktop. Also a word of thanks to the Ayatana Project Team for making this software available.

Join us for the first virtual launch party openSUSE 11.4

February 3rd, 2011 by

Annoncing the first virtual launch party

Dear folk, we are organizing a special event for the openSUSE 11.4 launch, and you’re invited. Virtually all of you can participate, and increase the success of it. And spend a good time.

Too soon? Not really, we are in the process to organize also pre-release party, certainly for the RC1 and RC2 launch. So you can practice before the real event. Prepare your environment, and dress your avatars with decent clothes, and gadgets.

We will do our best to welcome you in english, french & greek.
If you want you can also anwser our short pool we are looking about help.

Where?

Geekos place bar in SL

On secondlife.com, go to area macedonia. at 183,213,21 coordinates
Or fire the search engine, and look after Geekos group, then join that group

When?

During 3 days March 9 10 & 11 2011
Party start at 16:00 UTC ( 8am SL time)

What?

Join our special place build for that event and let’s get

  • Dance party
  • Free drink
  • Goodies
  • Wall of pictures
  • 11.4 installations movies
  • open minded discussions
  • Experience exchange

Who?

tigerfoot on secondlife
Morgane Marquis on secondlife

Your guests would be myself (tigerfoot) & Morgane Marquis.
A team of excellent dj’s as Lillith from Australia, Esquievel from USA, Stefanos from France,
or our great Greeks neighbors

 

Why?

Hey not so long ago I was kicked by H!
Because it’s a place where people have also fun, and we want to talk with them about the freedom & openSUSE.
Did you never attempt to realize something that has not been made yet?
Just to have a lot of fun! The full explanation Here

How?

To access that 3D virtual world, you need a recent computer 1.5Ghz or +, and good internet access >3500/300bps, and a 3D enabled graphics cards like radeon HD4xxx or more, Nvidia Geforce >9600, Intel > i945 & Intel Extreme.

To be continued

In the next weeks, I will publish an more technical article about how to get 3D world viewer installed on your openSUSE. And we are just finishing the picture gallery about that project which should be online next week (due to FOSDEM) this week-end.

Stay tuned !

A simple clock indicator (indicator-datetime)

February 3rd, 2011 by

I’ve neglected this indicator since the first day because it drove me into package dependencies that aren’t used in openSUSE (we use YaST and not system-tools-backends and friends).

The documentation of Unity suggests that if no indicators are present, Unity will use the notifications from GNOME. This is very interes

ting, but from the debugging I’ve done from the Unity Panel, I’ve found it it scans the indicators directory and loads whatever it finds there. So it will eventually find something. One of the coolest features in Unity Indicators and the one I’m currently working on, is ‘appmenu-gtk’ which removes the menu from GTK+ applications and displays it on the unity-panel. This is interesting and the behavior is actually a bit different from OSX. The window buttons are also placed very close to this indicator.

If we have such feature enabled, I suppose the panel will always pick up at least one indicator which might endanger the fallback to GNOME notification area. I’ve tested this yet (unity isn’t launched properly yet), but if this happens, it will be wise to have the whole stack of indicators. This explains why I had to build also this clock indicator despite it’s wicked dependencies (liboost, not used on openSUSE).

This is how it looks and minimal functionality is already enabled, though configurations aren’t because I haven’t implemented the whole backend, a

nd if this indicators are to reach Factory (which depends mainly on the patching on GTK+ and GDK Pixbuf), there is the need to pass this packages through SUSE Security Team. If the indicators are only to live on GNOME:Ayatana, then we skip this process (running this package dependencies through SUSE Security Team).

Here’s how it looks the current stack of indicators (there’s a couple more packaged, but I’m not using them at the moment, ex: nm-applet patched, indicator-network and friends).

Within the next days, I will I will make a 1 click installer and run a BETA phase for the Indicators/GNOME2.

Special Thanks to Didier Roche, Jorge Castro and Ken VanDine from Ubuntu/Canonical which have been hyper helpful answering questions and helping me accomplishing and overcoming several issue. Also to Malcolm Lewis (Novell/openSUSE) for keeping up with Compiz and other fixes for the requirements of Unity, and in general to openSUSE GNOME Team for keeping up the motivation and giving some awesome pointers in several GNOME related matters. This work so far has only been possible due to the commitment of all this people.

Synapse – Semantic Launcher for GNOME

January 31st, 2011 by

Some time ago a openSUSE user mentioned to me if we had synapse available for openSUSE or what was required to have it around. I took a look into it and asked some advice in #opensuse-gnome regarding the availability of libzeitgeist which is one of the requirements to build this piece of software.

Some time ago Federico Quintero has posted a message on the opensuse-gnome mailing list regarding his work on the Zeitgeist stack. The rest of the dependencies for this package are provided by my work on the availability of Ubuntu’s software on openSUSE. From my work I took dee and libappindicator and builded a test package of synapse on home:ketheriel:ayatana. This package is here until I see this dependencies hit factory on time (libzeitgeist, dee and libappindicator). If anyone wants to test it out, go ahead.

I’m not sure of the functionality that should be present on this vala application, but for the time being I’ve disabled the Application Indicator on the build (needs hammering on the linking). I’ll take a closer look once I have some more free time. So far this should be working only for openSUSE Factory and openSUSE 11.4 milestones.

Synapse is a semantic file launcher (pretty much the same as hitting ALT+F2 on a GNOME session) with some crazy looks and a battalion of plugins. Once the dependencies are ok, I’ll maintain this package and push it to the GNOME:Apps repository.

Superficial notes on interpersonal relations

January 31st, 2011 by

1. Understanding ME

One of the fundamental demands to allow that interpersonal relations grow more richer, positive and mature is the necessity of understanding yourself and others. Each individual is the result of genetic and hereditary aspects, also from the network of situations that develop during his growth, influenced by family, friends, school, neighbors and other persons that are taken by reference by each one of us.

The ME in each individual is built in function of the image that he acquires from the world, in function of experience, of people and situations perceptioned, in short, from the perception one does from reality. The way that we see and evaluate the world and others, develops in functions of the socio-cultural context in which we live.

Each individual is unique and different from all the others, nevertheless, he has to live in society and interact with others, which will be different from himself.

2. Understanding the OTHERS

The first impression we take from someone we meet for the first time, is going to influence our future relation and it’s conditioned by:

* Psychological Factors;
* Previous experience;
* Expectations;
* Motivations;

If it’s positive, it will benefit the interpersonal relation, or if it’s negative, it will make the interpersonal relation harder.

Before someone which is unknown to us, or before someone from whom we only are aware of a few characteristics,  we have a tendency to create a global impression of that person, in short, we categorize her.

Through  categorization people are gathered into pre-determined social groups according with the characteristics we identify on them and in function of the signs we watch on them.

2.1 Social Group

Personal Group – collectivity to which I feel to bellong, as my family, my religion, my professional category, social class, etc.

External Grups – collectivities to which I don’t belong, as in other families, other religions, other professional categories, etc.

The personal groups create their own cultural components, which leads them to develop beliefs about the external groups. Usually we make a general idea about people, often forgetting important particular characteristics.

The base line is on knowing how we organize the various elements that we watch on the subject, in a single unique and coherent impression.

Categorization simplifies the knowledge that we have about someone else, which makes their behavior predictable and understandable. Nevertheless often we categorize others incorrectly, because there are not 2 equal individuals. It is necessary to confirm our categorization e and specially be open to confirmation or reformulation of our first impressions, otherwise we get:

1. Prejudice;
2. Stereotypes;

A prejudice is an attitude hostile or negative to a determined group based on malformed or incompleted generalizations. This generalizations are called stereotypes and mean to provide personal identical characteristics to any person from a group despite of their individual difference to the rest of the members of that group.

The negative consequences of prejudice and stereotypes is on incorrect generalizations that label people e do not allow that them are seen and treated as singular individuals with very own personal characteristics.

We might make evaluation mistakes and prejudice to assume that the individual is what it’s stereotype (race, creed, profession, genre) portraits as pattern.

Interpersonal competences allow us to deal effectively with interpersonal relations, to deal with other people in the proper way to the needs of everyone and to the demands of the situation. An harmonious interpersonal relation implies knowledge about yourself and about the others.

To practice interpersonal relations it means to understand the others as they present themselves, establishing an attitude of empathy, understanding them and respecting their individuality. People differ in the way of understanding, think, feel and act; those personal differences are inevitable.

It is up to each one of us to have the capacity of understanding, and the attitude of accepting the diversity e singularity of others. Without respect for the others, a good interpersonal relation won’t be possible, and it brings consequences to US and to the OTHERS, and eventually to the organization they represent.

—–

I’ve decided to organize this notes and make a blog post on Lizards as I believe that we as a community should promote this issues, as our sanity and future are heavily related to them. In the industry, many companies place a lot of money and efforts to promote trainings and this topics amongst their employees. We openSUSE, as a community should also do the same, as our target is actually people. Any member/contributor/enthusiast of openSUSE is in a way the public relations of openSUSE. Ignoring this fields and not making an investment on them might do us more harm than good on the long run.

As many are aware, I recently applied for the Board, this was one of the topics I was preparing to bring to the Community. My formation is on Marketing Management and not on Psychology or Sociology/Anthropology, and I believe there are people far more qualified than me in the community to develop this topic and maybe to try and deploy it on the field.

To understand this text and it’s goals is something that everyone of us needs to do, and maybe place a bit more of effort in our interpersonal relations with other members. I we can deploy more synergies in promoting the good side of people and not the bad side.

Dedicated to friend which isn’t no longer around, or maybe he is.

Nelson Marques

PS: Feel free to improve the text and correct what you believe that is wrong or make it more objective and better understandable. Feel free to share it.

Unity on openSUSE: UPDATE

January 30th, 2011 by

Unity works as a plugin for Compiz using the glib mainloop. Currently the development version of Compiz available in OBS X11:Compiz already provides this requirement (glib mainloop) as a plugin. This version and two git snapshots I’ve builded were crashing heavilly, so I’ve decided to take  a closer look into Ubuntu’s packages and build from their sources on my devel project. This has proven wise as their snapshots (2010-11-25) with their patches removed the crashes on compiz.

The patches applied include the new unity-window-decorator which works fine. Here’s a small screenshot of GNOME’s System Monitor using Unity’s window decorator (which relies on a patch on metacity to enable UX Shadows).

The theme for this screenshot is Ambiance (also from Ubuntu) with a changed color scheme. This shot was taken on M6 with the newest FireGL drivers from ATI. I’ve noticed some changes on the blur effects on this driver, but I really can’t develop much.

I haven’t seen crashes on individual components when I test them (ex: unity-panel-service and unity-window-decorator), which seems to be a good pointer.

Currently I’m working out in porting the Unity wrapper and some scripts from Ubuntu to the reality on openSUSE as many files seem to be distributed on the filesystem in very different places. Just to name an example… compiz on openSUSE currently stores it’s profiles and stuff on $HOME/.config/compiz-1, and Unity is searching those files on $HOME/.compiz-1, and as such, fails to find them. This is where I’m currently placing my efforts. This should fix soon the ‘unity’ wrapper.

To make this short… Compiz isn’t crashing anymore or seg faulting, and Unity is picking up the information required from different file locations on the file system. Once fixed, we should have a running Unity for BETA soon.

My very special thanks to Malcolm Lewis for making the integration of Unity with Compiz possible in a very nice way and for fixing many bugs that allowed us to successfully build this packages.

As soon as we have more developments, those will be posted.