It’s been a month since I migrated my desktop from openRC to systemd and I wanted to write down and share my experience about it.

Firstly, I would like to clarify that I didn’t migrated to systemd because I dislike openRC or have any issues with it. I just wanted to get my hands dirty with systemd and learn from the whole procedure. I still have openRC to some of my boxes.

Intro

When systemd first appeared in 2010 there was much noise in mailing lists. Like every new software that grows rapidly , everyone was worried about the  maturity of systemd.  Almost four years  later since its first appearance,  systemd it’s not an immature project any more. It is already embraced by some distributions( openSUSE, Fedora, Arch) and became their default init system.  Unlike other distributions Gentoo doesn’t enforce  users to have an init system by default and allows them to choose what to install.

A brief introductory for both projects.

openRC:  dependency-based init system that works with the system provided init program and is maintained by Gentoo and Debian developers.  openRC is not only used in Linux systems, but it is also compatible with FreeBSD and NetBSD.

Systemd:  system and service manager for Linux.  Systemd was developed as  a contemporary replacement for SysVinit and RC. Systemd obsoletes ConsoleKit  and welcomes systemd-logind! In addition, it has its own cron and  logging system.

Only these? No!  There are a lot more init systems to play with,  see the  comparison  of init systems  page into Gentoo’s wiki.

Migration

Migration didn’t take much time and it was an interesting process. Although,  systemd’s architecture[1][2] differs from the SysVinit,  systemd’s surface has a similar logic compared to openRC and the only thing to be done is matching  systemd tools with openRC ones.

Tools

Here is a list with useful utilities that helps to a smoother systemd  landing.

  • systemctl: Control the systemd system and services.
  • hostnamectl: Control hostname.
  • localectl: Configure system local and keyboard layout.
  • timedatectl: Set  time and date.
  • systemd-cgls : Show  cgroup contents.
  • systemadm:  Front-end for systemctl command.

Matching systemd services with openRC ones.

  • systemctl list-units —> rc-status (List running services status)
  • systemctl –failed  —> rc-status –crashed ( Check failed / crashed units/services)
  • systemctl  –all —> rc-update -v show ( Display all available units/services)
  • systemctl {start,stop,restart,status} xyz —> /etc/init.d/xyz {start,stop,restart,status} ( {start,stop,restart,status} units/services immediately)
  • systemctl {enable,disable} xyz —> rc-update {add,del} xyz ( add or delete  a service/unit)

Goodbye syslog-ng / rsyslog (?)

No! Systemd has its own  logging system called journal.  However, syslog-ng or rsyslog can still be used in conjunction with journal.

To  manage journal logging system, use journalctl command.

Performance

For all the performance freaks out there, systemd comes with a very neat tool. systemd-analyze which analyzes system’s boot performance .

This tool, also comes with a great feature,  systemd-analyze blame which  prints all running units ordered by the time they took to initialize.

In addition, systemd-analyze plot generates a plot detailing all services that have been started and the time they spent on initialization.

For the same purposes, systemd-bootchart can be used to speed up boot performance.

Conclusion

I find both of them great projects with a bright future.  I am not going to start comparing them . As we always say on Gentoo “It’s all about choice”(sic).  Use openRC, use systemd, use whatever ease your life.

That’s all folks.
Thanks for your time.

I am looking forward to your feedback.

Further reading:

soc-logo-300x200Last week Google announced all the accepted student proposals for Google Summer Of Code 2013… included mine !!
I will participate in this year’s GSoC with Gentoo Foundation. My proposal was about identity.gentoo.org (aka Gentoo Identity). Gentoo Identity will be an LDAP web interface written using Django, which is a Python web framework. That will allow Gentoo developers _and_ users to configure easily their attributes from Gentoo’s LDAP server. This project is based on a previous GSoC project(codename ‘Okupy’). The web application will be for general usage and not only for LDAP administrators and sysadmins. I am also going to rewrite perl_ldap script  in python and improve it.  Currently perl_ldap  script is the only way to edit attirbutes from Gentoo’s LDAP server.

Some major features are:

  • LDAP Authentication.
  • Editable LDAP attributes via web forms.
  • Information about Gentoo developers (full name, gpg key, location, team) in a list like a address book.
  • Additional information about other accounts based on the ACL.
  • Enable privileged users/groups(recruiters, devrel, infrastructure team) to add new accounts and edit their information based on their ACL.

For more information about Gentoo identity, check my full proposal.

The expected outcome is a fully functional and scalable LDAP web interface, where both users and developers will be able to edit their attributes easily.

Theo Chatzimichos from Gentoo Infrastructure team will be my mentor and my co-mentor will be Gentoo Infrastructure lead, Robin Johnson. Also Gentoo dev, Matthew Summers as  a previous GSoC mentor of Okupy will help us in the Django part. In addition Michał Górny will work in parallel in another GSoC project for Gentoo Identity. His project aims to built a complete OpenID provider on top of it, to provide a common authentication and identity exchange mechanism for all Gentoo sites.

I am going to post weekly reports about the status of the project with more technical details. To come in contact for feedback and questions please send your emails at identity[AT]gentoo[DOT]org.

Happy coding!

bugday gentoo

In a try to revive the Gentoo Bugday I wrote this article in order to give some guide lines and encourage both users and developers to join. I think it would be great to get this event back and collaborate. Of course everyone can open/close bugs silently but this type of event is a good way to close bugs, attract new developers/users and improve community relations.  There is no need to be a Gentoo expert.  So I will give you some information about the event.

About:

Bugday is a monthly online event that takes place every first Saturday of every month  in #gentoo-bugs in the Freenode network. Its goal is to have users and developers collaborate  to close/open bugs, update current packages and improve documentation.

Location:

Gentoo Bugday take place in our official IRC channel #gentoo-bugs @ Freenode.  You can talk about almost everything. Your ebuilds, version bumps, bugs that you will choose to fix, etc.. This is a 24h event, so don’t worry about the timezone difference.

Requirements:

  1. A Gentoo installation (real hardware) or in a Virtual Machine.
  2. IRC Client to join #gentoo-bugs , #gentoo-dev-help (ebuild help) and #gentoo-wiki (wiki help)
  3. Bugzilla account.
  4. Positive energy / Will to help.
  5. (bonus): Coffee ;)

Goals:

  1. Improve quality of Bugzilla
  2. Improve Wiki’s documentation.
  3. Improve community relations.
  4. Attract new developers and users.
  5. Promote Gentoo.

Tasks:

  1. Fix bugs (users/developers)
  2. Triage incoming bugs (users/developers) (Good to start!)
  3. Version bumps (users/developers) ( Good to start!)
  4. Improve wiki’s articles(users/developers) (Good to start!)
  5. Add new wiki’s articles(users/developers)
  6. Close old fixed bugs (developers-only)

A good way to start is to take a look at the ‘maintainer-needed‘ list . In addtion try picking up a bug from maintainer-wanted alias  at Bugzilla.

TIP: You should DOUBLE/TRIPLE check everything before submit a new bug/patch/ebuild.

TIP2: Please avoid 0day bump requests.

And do not forget every day is a bugday!!

Organize your schedule and join us every first Saturday of every month @ #gentoo-bugs.

Consider starting from today reading the following docs in order to help you.

Useful Docs:

  1. Gentoo Bugday
  2. Get Involved in Gentoo Linux
  3. How to contribute to Gentoo
  4. Gentoo Dev Manual
  5. Contributing Ebuilds
  6. Gentoo Bug Reporting Guide
  7. Beautiful bug reports
  8. Gentoo’s Bugzilla User’s Guide
  9. How to get meaningful backtraces in Gentoo
  10. The Basics of Autotools

When you work with Django and especially with static files or other template tags you realize that you have to include {% load staticfiles %} in all our template files. This violates the DRY principle because we have to repeat the {% load staticfiles %} template tag on each template file .

Lets give an example.

We have a base.html file which links some Javascript and CSS files from our static folder.

{% load staticfiles %}
<!DOCTYPE html>
<html>
    <head>
        <title>Webapp</title>
        <link rel="stylesheet" type="text/css" href="{% static "css/random-css.css" %}">
        <script type="text/javascript" src="{% static "js/random-javascript.js" %}"></script>
        {% block extra_js_top %}{% endblock %}
    </head>
...
</html>

Also we have index.html which extends base.html and in addition it loads some extra javascript.

{% extends "base.html" %}
{% load staticfiles %}
{% block extra_js_top %}
    <script type="text/javascript" src="{% static "js/extra-javascript.js" %}"></script>
{% endblock %}

As you can see I load again staticfiles in index.html. If I remove it, I will take this error. “TemplateSyntaxError at /, Invalid block tag ‘static’”. Unfortunately even if we extend base.html it will not inherit load template tag from the file and it will not load staticfiles to index.html that means it will not load our extra javascript file.
The truth is that there is a hack-y way to do that. After a small research I finally found a way to follow DRY principle and avoid repeating {% load staticfiles %} template tag in every template file.

Open one of the files that loads automatically from the beginning( settings.py, urls.py and models.py ). I will use settings.py.
So we add the following to settings.py:

from django import template
 
#django-staticfiles DRY principle
template.add_to_builtins('django.contrib.staticfiles.templatetags.staticfiles')

With that snippet of code we load statcifiles “globally” and we don’t have to load staticfiles for every template (not even in base.html) because it loads from the beginning.

PS: Sometimes on big projects this way maybe will not be so ‘correct’ or considered unconventional technique and complicate the developers.

I hope it will be useful.

Happy django-ing.

Further reading:

Nowadays I see lots of new blog posts about how to contribute in open source projects and I decided to write a blog post about how to contribute to Gentoo Linux and become a vital part of the project.gblend

My colleagues at university everytime we talk about Gentoo tell me that they cannot install Gentoo because it is too difficult for them or they are not ready to install it and configure it because they don’t have the experience and they finally give up.  Also some other colleagues tell me that they want to contribute to Gentoo and they don’t know how to start. Thats why I wrote this blogpost in order to give some guidelines for those who want to contribute.

In order to help and contribute in Gentoo you don’t have to know to code or to be a super duper Linux guru. Of course code/programming is the core of  open source projects but there are ways to contribute without knowing to code. Requirements are two things. A Gentoo installation and will to help.

Community

Gentoo like the rest FOSS Projects is based on volunteer efforts. The pylons of every FOSS project is its community. Without its community Gentoo wouldn’t exist. Even if someone doesn’t know to code, can contribute and learn from project’s community.

Forums:  Join our forums and help other users with their problem. It is a good opportunity also to learn more things about Gentoo.

Mailing Lists: Subscribe to our mailing lists and learn about the latest community and development news  of the project. Everyone can also help users to related mailing lists or discuss with Gentoo developers.

IRC: Join in our IRC channels. Help new users with their issues. Discuss with users and developers and express your opinion about the new features and the technical issues of the project. Make sure you will read our Code of Conduct first.

Planets: Follow our planet and watch some Gentoo-stuff blog posts from developers about Gentoo. There are interesting conversations (via comments) after the blog post between the users and the developers.

Promote: After you get some experience with the project promote your favourite distro( Gentoo of course ) writing blog posts and articles in forums and sites related to open source.  You can also spread the word in your local linux users group and at your university.

Participate in Events: Every month there are meetings from the most of the Gentoo project teams. The meetings take place at #gentoo-meetings. There is an ‘open floor’ at the end of the meeting where users can express their opinion.

Documentation

Gentoo has always been known for its wide variety and quality of documentation. It covers lots of aspect of Linux. Topics about desktop, software, security and most of them are not totally Gentoo based.  That’s the reason Gentoo documentation is successful and that’s why users from other Linux distributions using it. So you can be a part of this effort and improve the documentation.

Wiki:  Wiki is our fresh project. There are lots of ways to help here. Add new articles about the topics  you would like to see ( and have knowledge of them of course) and want to share it with the other Gentoo users. Improving and expanding wiki articles is a good way to help the project (avoid copy paste from other sources in the net). All users are encouraged to help, wiki is open for everyone. Use it responsibly because your posts will affect the Gentoo users who will try to follow your guide.

Translations: If English is not your native language translating wiki/documentation will be a very good way to help users that don’t know English and want to join to the community. Translations is a good way to contribute and expand the Gentoo community.

(bonus) Write article to your blog: If you find a configuration or a tool  or a new solution to a problem that saved your life at the Gentoo world. Don’t be afraid and share it with the other users.

Development ( Code )

As I said code is the core of any software project.  So if you have some knowledge with shell scripts and programming you are welcome to join the team. With small steps you can gain more experience with the project and contribute to it with your features and patches.

Bugs: Every FOSS project has its own bug tracking system, Gentoo as well has its own Bugzilla. There we report our issues. Build and run time failures , kernel problems ,  Gentoo tools issues,  stable requests.  You can also start contributing by confirming and reproducing bugs  and then try to offer solutions and fix the bugs( patches are welcome ). So feel free to  report new bugs to our Bugzilla. In addition there are requests to add or update(version bump*) ebuilds. Instead of requesting new ebuilds  and version bumps you can also write and  submit your ebuilds to our Bugzilla in order to be added to the Portage tree by a Gentoo developer.  Try picking up a bug from maintainer-wanted alias. If you need a review for your ebuild #gentoo-dev-help is the right place to do it.

* Please avoid 0day bump requests.

Arch Tester: An Arch Tester (a.k.a AT) is a trustworthy user capable of testing an application to determine its stability. Arch Testers should have a good understanding on how ebuilds works, bash scripting and should test lots of packages to their arch. You can become an AT at x86 and amd64 archs. Requirement is to have a stable Gentoo box. Your goal will be to test and install packages from the testing arch (~arch) and see if they are working in the stable arch. Then you can open a stabilization request to Bugzilla.

Sunrise Project: Sunrise is a starting point for gentoo users to contribute. The Sunrise team encourage users to write ebuilds and make sure that they follow Gentoo QA standards. Sunrise’s goal is to allow non-developers to maintain them. For questions you can ask at #gentoo-sunrise at Freenode.

Proxy-maintaining: The goal of this team is to maintain abandoned (orphaned) packages in order to prevent treecleaners from removing those packages.  Pick up some packages from the maintainer-needed list a begin to maintain it. For questions you can join #gentoo-dev-help.

Bugday: Bugday is an event which take place at #gentoo-bugs at Freenode every first weekend of every month. You can join and pick a bug and fix it. But have in mind that every day is a bugday so it doesn’t have to be a bugday to add your ebuild and fix bugs.

Advanced Community Projects: Portage, Gentoolkit Portage tools Kernel team, Infrastructure team, Security team and Hardened team. These projects are very special and important to the Gentoo so it is necessary to have a good level of knowledge in order to contribute to them. So if you have the skills join the party .  :)

Become a developer:  After you reach a good amount of contribution and you think you can be an active and vital member of the project you can start the process of becoming a developer. Talk to a Gentoo developer in order to mentor you and help you fill the ebuild and staff quiz and then the process of the recruiting will be completed with a live interview with a recruiter.

There are lots of  Gentoo project teams that need new members and help . Everyone can contribute to Gentoo either knowing to code or not. Every piece of help is useful for the project.

I think I covered the biggest part of the Gentoo and how to contribute to it . I’ll wait for your comments, if you think I missed something inform me. Fixes always welcome.

Start contributing from today.

Gentoo: If it moves, compile it ;)

Further reading:

  1. Gentoo Handbook
  2. Gentoo Development Guide
  3. Gentoo Projects Listing
  4. Benefits of Gentoo
  5. Easy way to assist us  by Markos Chandras
  6. How to contribute to Gentoo
  7. Beautiful bug reports
  8. Sunrise Project ( lots of good tutorials inside )
  9. Always looking for Arch Testers by Agostino Sarubbo

After one month I think it was time to write my review about Gentoo miniconf. :-)

In 20 and 21 October I attended to the Gentoo Miniconf which was a part of the bootstrapping-awesome project, 4 conferences (openSUSE Conference/Gentoo Miniconf/LinuxDays/SUSE Labs)  where took place in the Technical Czech University at Prague.

Photo by Martin Stehno

Day 0: After our flight arrived in Prague’s airport – we went straight to the pre-conference welcome party in a cafe near the university where the conference took place. There we met the other greeks who arrived in the previous days and I had also the chance to meet a lot of Gentoo developers and talk with them.

Day 1: The first day started earlier in the morning. Me and Dimitris went to the venue before the conference started in order to prepare the room for the miniconf. The day started with Theo as host to welcome us. There were plenty of interesting presentations  that covered a lot of aspects of Gentoo, the Trustees/Council, Public Relations, The Gentoo KDE team, Gentoo Prefix, Security, Catalyst and Benchmarking. The highlight of the day was when Robin Johnson introduced the Infrastructure team and started a very interesting BoF which talked about the state of the Infra team, currently running web apps and the burning issue of the git migration. The first day ended with lots of beers in the big party of the conference in the center of the Prague next to the famous Charles Bridge.

Gentoo Developers group photo
Photo by Jorge Manuel B. S. Vicetto

 

Day 2:The second day was more relaxed. There were presentations about Gentoo@ IsoHunt, 3D and Linux graphics and Οpen/GnuPG .After the lunch break a Οpen/GnuPG key signing party began outside of the miniconf’s room.After the key signing party we continued with a workshop regarding Puppet also a presentation about how to use testing on Gentoo to improve QA and finally the last presentation ended with Markos and Tomáš talking about how to get involved into development of Gentoo. In the end Theo and Michal closed the session of the miniconf.

 

I really liked Prague especially the beers and the Czech cuisine.

Gentoo Miniconf was a great exp erience for me. I could write lot of pages about the miniconf because I was in the room the whole days and I saw all the presentations.

I had also the opportunity to get in touch and talk with lots of Gentoo developers and contributors from other FOSS projects. Thanks to Theo and Michal for organizing this awesome event.

More about the presentations and the videos of the miniconf  can be found  here.
Looking forward to the next Gentoo miniconf(why not a conference).

    Recently I booked my air tickets for Prague in order to attend to the first Gentoo Miniconf[1] and openSUSE Conference 2012[2]. The theme of the conference is Bootstrapping Awesome![3].  Four conferences ( openSUSE Conference 2012 , Gentoo Miniconf(the first) , LinuxDays and  the 14th SUSE Labs conference) will be held into one location. The conferences will be held in Prague( Czech Republic ) at the Czech Technical University during October 20- 23.
In addition the organizing commitee of Gentoo miniconf needed volunteers for  some “fresh” graphics and videos for the miniconf,  so I decided to create a promo video for the Gentoo miniconf. I hope you like it:)

You can also see the event pages for Facebook[4] and Google+[5].

For more informations you can visit the follow links.

[1] http://miniconf.gentoo.org

[2] http://conference.opensuse.org/

[3] http://bootstrapping-awesome.org/

[4] https://www.facebook.com/events/309722462450480/

[5] https://plus.google.com/u/0/events/c0fn547i01b94gae3v9tkn2umqc/101184229781272153227

Gentoo has always been known for its wide variety of documentation. It covers lots of sections about desktop, software, security and most of them are not totally Gentoo based(configuration files). That’s the reason Gentoo documentation is successfull and that’s why users from other Linux distributions using it.

Except from the documentation where is on the main site of Gentoo(Handbook,Guides)[0], Gentoo now has and an official wiki.

On November of 2011 the official Gentoo Wiki launched[1]. Gentoo Wiki Project team maintain the wiki and with users contribution, improve/edit articles and add much more. Also there is  the unofficial Gentoo wiki[2] which has hundreds of articles that covers wide range of Gentoo. After the launch of the official Gentoo wiki, unofficial Gentoo wiki announced that plans to continue running alongside the official Gentoo Wiki.

Although the official Gentoo Wiki is relatively new on the web, it has a sufficient number of articles. The Gentoo wiki project in order to urge users contribute on Gentoo and  improve wiki, organize the first Summer Of Documentation(SoD)[3]. SoD has already began on 15th of June and it will last until 23rd of September. The goal is the improvement of  the current articles of wiki and the enrichment with new articles(at least 500) . Everyone can join on this effort. You don’t have to be a Gentoo developer or to have programming knowledge.

If you don’t know how to start, there is a list of requested articles[4] that should be added. You can also add new articles that are not in the list.

The way to come in contact with the Gentoo Wiki Project is via IRC on #gentoo-wiki at Freenode or you can email them at wiki@gentoo.org.

[0]  http://www.gentoo.org/doc/en/

[1] https://wiki.gentoo.org/

[2] http://en.gentoo-wiki.com

[3]  https://wiki.gentoo.org/wiki/Gentoo_Wiki:Summer_of_Documentation/2012

[4]  https://wiki.gentoo.org/wiki/Gentoo_Wiki:Requested_Articles

Φέτος σαν SerLUG αναλάβαμε την διοργάνωση της FOSSCOMM 2012 πράγμα που μας χαροποίησε πολύ. Έτσι μετά από μια διαδρομή αρκετών μηνών και αρκετού τρεξίματος έφτασαν οι μέρες. Έτσι η FOSSCOMM 2012 έλαβε χώρο στο ΤΕΙ ΣΕΡΡΩΝ 12 και 13 Μαΐου.

Παρασκευή [11/5/2012] – Welcome Party!

Απο την ανακοίνωση των ημερομηνιών της FOSSCOMM είχαμε ενημερώσει πως θα υπάρχει και ένα welcome party την προηγούμενη μέρα της FOSSCOMM. Πράγμα που έγινε. Έτσι μετά τις ετοιμασίες που είχαμε στο ΤΕΙ οργανωτική και εθελοντές, πήγαμε στα ξενοδοχεία στα οποία βρίσκονταν ο κόσμος που ήρθε για τη FOSSCOMM προκειμένου να μαζευτούμε και να πάμε όλοι στην μπυραρία που θα γινόταν το welcome party.  Η προσέλευση του κόσμου ήταν ικανοποιητική καθώς γεμίσαμε όλο το μαγαζί :-) . Συναντήσαμε κόσμο που μιλούσαμε καθημερινά online, συζητήσαμε για ποικίλα θέματα και φυσικά ήπιαμε μπύρες!! Έτσι το βράδυ πέρασε ευχάριστα μέσα σε ένα ζεστό κλίμα με αρκετή συζήτηση.

Σάββατο [12/5/2012]

Πρώτη μέρα της FOSSCOMM, οι προεγγραφές ξεκίνησαν από νωρίς όπως και το στήσιμο των booth. Έτσι μετά απο ένα σύντομο καλωσόρισμα απο την οργανωτική επιτροπή όλοι πήραν τις θέσεις και ξεκίνησαν οι παρουσιάσεις στα 2 αμφιθέατρα και τα workshops. Η πρώτη μέρα ήταν αφιερωμένη κυρίως στις κοινότητες. Η μέρα κύλισε ομαλά και γεμάτη θετική ενέργεια. Καθ’όλη την διάρκεια των παρουσιάσεων υπήρχε αρκετός κόσμος και στο φουαγέ στο οποίο υπήρχαν τα booth. Το μεσημέρι στο διάλειμμα βγήκαμε την ομαδική φωτογραφία μας και στην συνέχεια η ομάδα του Πανεπιστημίου Πατρών ξεκίνησε το Capture The Flag το οποίο είχε μεγάλη συμμετοχή απο ομάδες οι οποίες διαγωνίστηκαν σε challenges τα οποία κάλυπταν μεγάλο κομμάτι της ασφάλειας . Το βραδάκι συναντηθήκαμε πάλι όπως χθες στα ξενοδοχεία μόνο που αυτήν την φορά πήγαμε για σουβλάκια ! Έτσι το βράδυ έκλεισε πολύ όμορφα.

Κυριακή [13/5/2012]

Δεύτερη μέρα του συνεδρίου. Η δεύτερη μέρα ήτα πιο χαλαρή από την προηγούμενη και δεν υπήρχε το ίδιο άγχος. Η μέρα ήταν κυρίως αφιερωμένη στο Web και στο development γενικότερα.Η ομάδα του Mozilla είχε τις περισσότερες παρουσιάσεις οι οποίες κάλυπταν μεγάλο φάσμα στο πώς να συνεισφέρει κάποιος στη Mozilla. Καθώς επίσης υπήρχαν παρουσιάσεις για την ασφάλεια και κυρίως σε πιό τεχνικά θέματα. Το Capture the flag συνέχισε κανονικά  και ανέδειξε και νικητή στο τέλος του συνεδρίου. Τέλος κλείσαμε με ένα Round Table – Feedback time στο οποίο ακούσαμε τι άρεσε και τι δεν άρεσε καθώς και τι περιμένει ο κόσμος να δει στην επόμενη FOSSCOMM όπως και για τις προσδοκίες του για το μέλλον για τέτοιου είδους γεγονότα. Το συμπέρασμα του round table ήταν οτι ο κόσμος θέλει να δει κάτι παραπάνω απο παρουσιάσεις κοινοτήτων αλλα παρουσιάσεις σε πιο τεχνικό επίπεδο.

Έτσι η FOSSCOMM 2012 έριξε την αυλαία.

Συμπέρασμα

Όλες οι παρουσίασεις ήταν εξαιρετικές. Αυτό που μ’άρεσε περισσότερο όμως ήταν οτι συναντήθηκα με φίλους ήπιαμε μπύρες μαζί και τα είπαμε αλλά και οτι γνώρισα καινούριο κόσμο και ανταλλάξαμε απόψεις. Ένα από τα πράγματα που δεν μάρεσε ήταν ότι δεν είδα στη FOSSCOMM πολύ κόσμο της τοπικής κοινωνίας και κυρίως φοιτητές των τμημάτων της Πληροφορικής και Γεωπληροφορικής έτσι ένιωσα πως υπάρχει λίγο αδιαφορία σε ένα μεγάλο ποσοστό των φοιτητών. Επίσης μικροπροβλήματα υπήρχαν σίγουρα στην πορεία και κατα την διάρκεια της FOSSCOMM τα οποία σαν οργανωτική προσπαθήσαμε να λύσουμε. Ας κρατήσουμε τα καλά όμως. Το τριήμερο αυτό πιστεύω πως κύλισε όμορφα με πολύ ενδιαφέρουσες παρουσιάσεις και workshops. Ελπίζω όλοι να έμειναν ευχαριστημένοι και φυσικά να πέρασαν καλά!!!

Ευχαριστώ όλους όσους ήρθαν, μας στήριξαν και μας έδωσαν feedback όλο αυτό τον καιρό.

Καλή FOSSCOMM 2013, λοιπόν!! :-)

———————————

Χρήσιμα Links

1) Επισκόπηση FOSSCOMM 2012

2) Αρχείο Παρουσιάσεων FOSSCOMM 2012

3) Φωτογραφίες FOSSCOMM 2012