Skip to main content

a silhouette of a person's head and shoulders, used as a default avatar

Integration of Karma Plugin with Twitter


This is my report for the last week and a half(1st june - 11th june).


Firstly, the integration of Karma plugin with Twitter has been accomplished. It fetches tweets of Connect users and those which are intended towards promoting openSUSE are rewarded with Karma points.


Then I also finished off the integration of Planet openSUSE. For all those users whose blog feeds are aggregated on Planet openSUSE and who actively post are rewarded with karma points, provided they have specified their blog in their profiles on Connect.


Karma pluigns now has the ability to update user score and keeps track of when it last updated so as to avoid duplicacy when it  again fetches user activities.


It also shows exactly how many bugs a user fixed, tweets and posts they had put up, for which they are being rewarded.

Now the problem that I am facing currently and on which I am going to work next is that tweeting and posting cannot be logically compared to bug fixing but can be compared to each other. So, there needs to be separate developer karma and marketing karma so that their is logical comparison of scores and appropriate badge distribution.

Also there are certain Connect users who haven't specified their blogs in their profile but their blog feeds are aggregated on openSUSE and openSUSE members who blog on Lizards blog also deserve to be rewarded.




a silhouette of a person's head and shoulders, used as a default avatar

Mercurial

Минимальная инфраструктура для работы с распределенной системой контроля версий Mercurial настраивается следующим образом.

Во-первых, нужно где-то разместить репозитории. Поскольку никаких других рекомендаций не поступало, по аналогии с cvs и svn будем класть все в /srv/hg/repos. Во-вторых, нужно обеспечить теперь доступ разным пользователям, которые счастливо существуют на компьютере и что-то там делают. Основная инструкция тут: http://mercurial.selenic.com/wiki/MultipleCommitters. Краткая инструкция: по аналогии с cvs и svn, создаем системную группу hg, системного пользователя hg, добавляем всех пользователей в группу hg.

Схема создания нового репозитория выглядит следующим образом:
cd repos/
mkdir test
chown -R hg:hg test
cd test/
hg init
chown -R hg:hg .hg
chmod -R g+w .hg
chmod g+s .hg .hg/store .hg/store/data

Mercurial >1.0 сам, о чудо, разбирается с правами доступа и делает так, чтобы все кому надо могли туда писать. Вообще говоря, данный подход (пулить всем вместе в один репозиторий) полностью противоречит идеологии hg.

В-третьих, никак не обойтись без веб-интерфейса. В /usr/share/doc/packages/mercurial живет пример под названием hgweb.cgi. Кладем его в /srv/hg/bin/hgweb.fcgi и меняем примерно следующим образом (чтобы через FastCGI работал):
#!/usr/bin/python

config = "/srv/hg/config"

from mercurial import demandimport; demandimport.enable()
from mercurial.hgweb import hgweb, wsgicgi
from flup.server import fcgi
application = hgweb(config)
fcgi.WSGIServer(application).run()

Конфигурация для lighttpd (обычно кладется куда-нибудь в /etc/lighttpd/vhosts.d/hgweb.conf):
fastcgi.server += (
        "/hg" => ((
                        "bin-path" => "/srv/hg/bin/hgweb.fcgi",
                        "socket" => socket_dir + "/hgweb.sock",
                        "max-procs" => 1,
                        "check-local" => "disable",
                        "fix-root-scriptname" => "enable",
        ))
)

Что писать в /srv/hg/config подсказывают в hg help hgweb:
[paths]
/ = /srv/hg/repos/*
/home/user = /home/user/hg/**

Последняя строчка для того, чтобы пользователям было не обидно, там они хранят свои личные репозитории. Вот только . Поля "Description" и "Contact" настраиваются в .hg/hgrc персонально для каждого репозитория. Кроме того, теперь через http возможно анонимное клонирование.
a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

LibreOffice CorelDraw Import filter - text support hatches out

Uff, it is done!!!

We started to work on the text support inside libcdr already before the Libre Graphics Meeting in Vienna. We worked hard during the talks and the long evenings after having eaten some portions of Wienerschnitzl.

Now we are proud to announce that we managed to release yesterday libcdr-0.0.8 with "basic initial primitive [u]ncomplete" (further BIPU) text support. At the moment, we are supporting only a couple of parameters as a font face and font size and we are able to detect the encoding and produce a corresponding utf-8 string. Far from being perfect, it is nonetheless a milestone, because in the FOSS world, there was no support for CorelDraw text before.

We know that you prefer to look at nice pictures instead of reading bad text. So, this gives your heart's desires.

A simple document with text in CorelDraw 7:

fancytext_cdr7.cdr in CorelDraw 7

The same document opened in a build of LibreOffice from yesterday:

fancytext_cdr7.cdr in CorelDraw 7

At the moment, libcdr is able to convert text in CorelDraw documents from versions 7 to 16. Nonetheless, we know already roughly how to read it in files of lower versions and we will add the support for next release. In the same way, we will extend our support of other text properties, like font colour, transparency, effects, paragraph alignments, character positions, etc.

How can I test it? All this goodness will be part of LibreOffice 3.6.0 release. You will be able to test the text support in the 3.6.0 beta2 pre-release. For the brave, any of the daily builds that are built from a code checkout after June 11th also include libcdr-0.0.8 and thus the text support in CorelDraw files.

As usual, this is a free and open source software project and, as such, it delights in developers that want to help. So, if you feel the itch, patches can be sent to libreoffice-dev mailing list. And, do not forget to find a way to join the #libreoffice-dev channel at irc.freenode.net in order to meet other developers. We can promis you that you will feel at home in the LibreOffice community.

the avatar of KDE at openSUSE

a silhouette of a person's head and shoulders, used as a default avatar

Συμμετοχη στο 2ο openSUSE Collaboration Summer Camp 2012


Ζεσταθήκατε;

Ήρθε η ώρα να κανονίσετε τις καλοκαιρινές σας εξορμήσεις!

Το 2ο openSUSE Collaboration Summer Camp πλησιάζει και φέτος στο γνωστό μέρος (ξενοδοχείο Grand Platon στην παραλία Κατερίνης) στις 20-22 Ιουλίου 2012!

Όπως και πέρσι θα μαζευτούμε όλοι μαζί και θα συνδυάσουμε μπάνια και μπύρες στην πισίνα με παρουσιάσεις και workshops (μην ξεχάσετε να φέρετε τα laptop σας!)

Η εκδήλωση δεν αφορά σε καμία περίπωση μόνο χρήστες του openSUSE!

Σκοπός είναι η συνεργασία μεταξύ ανθρώπων που απολαμβάνουν να προσφέρουν στο Ε.Λ/Λ.Α.Κ και η γνωριμία με τους διάφορους τρόπους που μπορούν να το κάνουν.

Σας περιμένουμε όλους ανεξαιρέτως από τη διανομή σας, για να συζητήσουμε, να ανταλλάξουμε απόψεις και φυσικά περιμένουμε και τις δικές σας ομιλίες ή/και workshops πάνω στα θέματα που σας ενδιαφέρουν!

Όπως και πέρσι θα υπάρχει ποικιλία θεμάτων που θα παρουσιαστούν, τα οποία θα ανταποκρίνονται σε όλους, ακόμα και στους πιο νέους και όχι και τόσο έμπειρους χρήστες.

Όλοι μπορούν να συμμετέχουν ενεργά, να παρακολουθήσουν τις παρουσιάσεις και να πραγματοποιήσουν workshops!

Τι πρέπει να γνωρίζετε:
1.[CfP] Η υποβολή ομιλιών/workshops έχει ανοίξει και περιμένουμε και τις δικές σας προτάσεις!
Το μόνο που χρειάζεται να κάνετε είναι να συμπληρώστε τη φόρμα: http://www.os-el.gr/content/submit-talk-collaboration-summer-camp-2012

2. Για δήλωση συμμετοχής & κρατήσεις δωματίων (καλό είναι να το κάνετε εγκαίρως για να μας βοηθήσετε να κρατήσουμε τα διαθέσιμα δωμάτια που θα χρειαστούν στο ξενοδοχείο) στείλτε τα στοιχεία σας στο reservations@os-el.gr

(Για κράτηση δωματίου απαιτείται η καταβολή του 50% του κόστους – περισσότερες πληροφορίες για την κατάθεση θα σας δοθούν μέσω email).

Το κόστος για τα δωμάτια είναι (συμπεριλαμβάνεται πρωινό & βραδινό):

* Μονόκλινο – 35 ευρώ/βραδιά

* Δίκλινο – 45 ευρώ/βραδιά

* Τρίκλινο – 60 ευρώ/βραδιά

3. Έχετε άλλες ερωτήσεις ή απορίες;

    * Περισσότερες πληροφορίες μπορείτε να βρείτε στη σελίδα http://www.os-el.gr/summercamp

    * Για οποιαδήποτε ερώτηση, επικοινωνήστε μαζί μας μέσω email: summercamp@os-el.gr

Διότι αγαπάμε αυτό που κάνουμε & περνάμε ωραία συνεισφέροντας στο ΕΛ/ΛΑΚ ακόμα και το καλοκαίρι!

ΣΑΣ ΠΕΡΙΜΕΝΟΥΜΕ ΟΛΟΥΣ ΕΚΕΙ!

a silhouette of a person's head and shoulders, used as a default avatar

Dear All.

Dear All.

In the light of the recent hack of the Linkedin server and advisement from fellow colleagues within IT security, my account has been closed. This is not the first time a big organization has implemented poor security policies, many times due to it relating to costs. Well, their costs might be lower, but the cost of having your personal information being spread across the net without your consent, is much higher of a cost to YOU than it will ever be to them. 

Moreover, I have checked and my account password was one of the ones that was hacked. I am sure I will not even receive an apology from Linkedin, especially since I was not a paying customer. Imagine if I was? Then the hackers would have my credit card info also. 

We need to voice our opinions about these issues before they happen, since after it is too late. So, join the many of us conscious people and close your account too, since yours may also be breached. 

It is better to be safe, than sorry!!

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

a silhouette of a person's head and shoulders, used as a default avatar

Goolge Summer of Code 2012 – Ambassador/Event plugin for openSUSE Connect – Event#3

Event #3 (25/05-06/06)

What did i do

This period of time was the continuity of the last one (ok i suffered from fever for 3 days). So the hacking is on and new features are already added. As i promised on my last post , i had to add some new useful features in the Event Calendar Plugin (while creating a new event). So i added some new fields which are useful for the ambassadors and also requested from users. These fields are :

Material ,Arrival,Departure ,Booth ,Travel,Talks [1] .

Adding these fields means that ambassadors can add more information while creating a new event. But what is going on when an ambassador or a new user wish to add extra info on these fields? In openSUSE Connect you can make comments as a general instance in a page , but by default you cannot make comments into fields. Μore detailed i made annotations for the ElggObject ($event) and then printed their value (annotation value is a comment for a example). [2] . In order to make the comments visible during “View Event” i created new fields (Material Comment,Arrival Comment, Departure Comment , Booth Comment , Travel Cmment , Talks Comment) where the annotation from the user are available [3].

Problems and Solutions

During this period i faced problems with annotation. Elgg only allows annotating ElggObject but not metadata (our fields are metadata of the object $event) . I made a lot of tries and tried many thoughts so as to reach my goal. Creating a new Object would be a disaster and with no sense. So annotating the $event and add the annotations as a new StdClass was the solution in the problem [4].

What i am going to do

This period of time i will add a map locator for the each event. Furthermore i will  find out if other fields are requested from users and try to add them to event calendar plugin.