We are pleased to announce our new openSUSE Weekly News.
Archive for January, 2011
We will have a service outage (expected are 30 minutes) this Thursday morning between 09:00 and 10:00 CET.
The software search on software.opensuse.org might also be affected during that time.
In 2009, a set of trademark guidelines were created to help define how the community and beyond could use the openSUSE logo and related trademarks in their own products and services.Â Along with this, Novell granted powers to the openSUSE Board to be the guardians of the openSUSE trademarks.Â This included ensuring that proper usage followed the guidelines as well as giving the Board the ability to review special use cases
It also helped those who wanted written permission from the Board authorizing the use of trademarks on their products and services.Â Formal requests for such permissions were sent to firstname.lastname@example.org, and Novell would forward the request to the Board for review.
As you know, trademark protection is important because it represents the identity of an organization.Â Trademark usage also provides an important tool for the community that wishes to promote openSUSE.Â The use of the trademarks makes it easier to share and spread openSUSE works.Â Of course, regulating the appropriate usage of the trademarks is also a necessary evil to prevent abuse.
As with anything in life, time gives perspective.Â There has been sufficient time since the implementation of the first guidelines to observe real use cases where the guidelines were either effective or ineffective.Â And for the Board, this includes identifying a more responsive workflow to addressing requests for authorization of usage, as we, and others, recognize the current process as being perfectible.
The Board, along with others in the community, would like to begin a review of the current state of our trademark guidelines and identify where it can be strengthened and be more effective.Â To this end, our first step is to open an openFATE Feature request for comments.Â We invite the community and beyond to review the current guidelines and offer their input on language and past use case experiences.
While we would like comments submitted on openFATE, if you prefer, you can post your comments here or send your thoughts directly to email@example.com.
A specific timeline for completion of this process has not been determined yet, but it is the intention of the Board to move forward on this topic in order to help the community at large move forward on their own projects.
Accessibility has become an important selling point in getting computing solutions into many organizations. Organizations are faced with legislations and regulations that require their environments be accessible and they take it into account when looking for a solution that fits their needs. For government organizations, software that doesn’t live up to certain accessibility standards is simply not an option.
Let’s just be frank here. While the openSUSE community cares about accessibility as much as anyone else does in FOSS, we haven’t done that well in delivering the best accessible solution. There are various people who look at the situation in their own corners and try to make the best of it. Andrew Wafaa highlighted some of the challenges in two recent articles.
Meanwhile openSUSE presents a very unique advantage that hasn’t been leveraged yet. With DBUS, the GNOME and KDE communities have worked together to leverage GNOME’s long-standing applications to work well on KDE. As openSUSE is a major distribution that provides support equally to GNOME and KDE, we have a distinct opportunity to provide the best integration of KDE and GNOME with accessibility. Thus offering prospective users and organizations a real choice on a distro that is known for its stability and support.
Since the openSUSE Conference in Nuremberg in October, the openSUSE community has been extremely active. New projects announced there have had progress, others have emerged. One example of the latter would be Project Tumbleweed, aiming to create a rolling-release repository for openSUSE. Going in the opposite direction is Project Evergreen – the Evergreen developers want to provide longer-term support for older openSUSE releases for a core set of packages. And there is the new Virtualization:Cloud project, where a team got together to create a cloud software repository. Finally, we can’t forget to mention the new GNOME:Atayana project, bringing Unity to openSUSE! And those are new just since our last conference! (more…)