Archive for the ‘GNOME’ Category

Individuals contribute 20000 USD to make GNOME more secure and more privacy aware

Sunday, July 21st, 2013

rest

I’m so excited. I’ve just pushed the last update to the current Friends of GNOME banner. We received donations worth 20000 USD to make GNOME more secure and privacy aware. It’s so awesome to see so many individuals donating to make GNOME better for them and ultimately for all of us.

finished

We got 250 one-off payments and roughly 650 periodic payments from payment plans over the last 7 months. During that period, 52 payment plans were created with the average amount of 10 USD per month (the default setting). However, 51 plans were cancelled :-\ The one-off payments were worth 17600 USD and hence the average donation was about 70 USD.

Depending on how you do the math, the cost of taking the one-off donations was between 3.3% and 4.4%. I find that number surprisingly low, probably because I still can’t make sense out of PayPal’s fee structure. But there are probably some hidden fees that turn up once you actually want to do something with the money, i.e. have it wired somewhere.

A very big “Thank You” to all the donors who generously allow us to continue our mission to produce a Free Software desktop for everyone. You guys rock. Seriously.

The new GNOME board, which is already serving since the beginning of this month, will meet during GUADEC and probably call for bids some weeks later.

GNOME.Asia Summit 2013

Thursday, June 6th, 2013

This year’s GNOME.Asia Summit took place in Seoul, Korea. It’s my second GNOME.Asia Summit after the previous one in Hongkong and it’s again amazing to see how nice the local team put everything together.

SAM_1416

Initially I thought I’ll go to Seoul straight from LinuxTag which would have been quite stressful. Unfortunately, LinuxTag didn’t happen for GNOME :-\ We lacked people to run the booth and it’s insane to try to run the booth with only two or three people over four days. So I went more or less straight to Seoul. Via CDG. So far I didn’t like that airport because it is huge and transfers between terminals are very slow and the terminals themselves rather poor in terms of infrastructure (power, seats, WiFi, shops). But terminal 2E was surprisingly nice. It’s got designeresque chairs to sit in, lots of power sockets, free WiFi, some shops, water fountains, and it’s generally airy. So thumbs up for that.

SAM_1418

As for Seoul, things went surprisingly well. While i did organise this GNOME.Asia Summit to some extent I didn’t expect things to work out that nicely. The local team, which was pretty much unknown to me, was surprisingly big and they found a good venue and good sponsors.

GNOME Asia Summit

Lemote gave us a few laptops to give away *yay*. A raffle was organized and the best speaker got the biggest machine. I didn’t win in the raffle, but I got a machine as the best speaker. It’s a Lemote Loongson. I don’t know yet whether it is what I need. I have a very underspecced Lenovo ideapad which barely runs GNOME. Running anything that requires memory is really dreadful. Yes Firefox, looking at you. And some things like Gajim, an XMPP client, don’t even work because the machine starts to swap so heavily that every TCP connection times out. Again and again. I have to explore whether the Lemote laptop performs any better. It’s MIPS after all. And according to Wikipedia the CPU alone draws 15W.

SAM_1452

Anyway, the conference itself was good and I felt that it was bringing together people nicely. I hope that it relevant Korean businesses are happy, too. We will have to see though whether any measurable output has been generated.

The reactions to my talk about GNOME 3.8 were, as already mentioned, positive. To my surprise I have to say. I was still a bit tired and jetlagged, but from talking to people afterwards I know that I inspired some folks to take a closer look at GNOME. You can find my slides here.

CAM00344

I found a surprising large number of other talks interesting, too. Unfortunately, the aforementioned laptop died while taking notes so I can’t provided a nice summary. The most interesting thing I found was a talk about seafile. A Dropbox-like tool which sounds really good. But to be ready they have to fix some design problems like depending on a local webserver or not using established authentication and encryption protocols (think SSH).

SAM_5438

I’m happy for the GNOME.Asia. May it prosper in the future. I hope we can gain some more sponsors for future editions of the event and also for GNOME. As other people already stated: I’d like to thank the GNOME Foundation for sponsoring my attendance at the conference. I’d also like to thank the conference sponsors for their support, including NIPA, Lemote, LG, Google, Linux Pilot, ONOFFMIX and Bloter.net.

Sponsored by GNOME!

A journey to an updated Linux 18

Friday, May 3rd, 2013

Oh what joy this whole GNU/Linux thing brings. I took a few days off to upgrade my machines. I had the pleasure to update one laptop twice, i.e. from the Ubuntu 12.04 LTS to the current 13.04 and a desktop from Fedora 17 to Fedora 18.

The Laptop was almost easy. It took long time for the system to install packages. And there are stupid dialogues to confirm which block the whole process. Not very nice. I let it run for a couple of hours, everything went more less fine until I couldn’t log in anymore. LightDM saved my GNOME preference but there was no gnome-session left. So I went to the console and got myself ubuntu-gnome-desktop (arr. stupid wordpress doesn’t render apt:// links).

The second update from 12.10 to 13.04 took as long as the first, with nothing noteworthy happening. Interestingly though, it didn’t want to install the 13.04 unless being told to install a “development release”. Bollocks.

Anyway, Ubuntu’s GNOME runs almost nicely on my tiny laptop. GNOME-Shell is very slow when it comes to alt-tab. It takes three or four seconds to switch a window. Distraction free computing at its best.

The Fedora desktop is full bucket of joy. The FedUp utility keeps what it promises. It’s surprisingly refreshing. This time, the whole upgrade procedure worked flawlessly. No really! In 2013! I’m amazed. It only took a while for it to fetch everything but then a reboot straight into the upgrade system made the magic happen. Very cool.

Not so cool was the surprise of the machine not booting. Of course. Systemd hung somewhere in NFS related daemons and bailed out because they failed. The old GRUB menu entry booted a little further, just until sendmail, and enabled me to investigate.

Sendmail could not be brought up, because “-bd is not supported by sSMTP”. Right. I have sSMTP installed. And to make a long story short, something did place an init script in /etc/rc.d/init.d/. And that script failed now. NOW. After a couple of years. It was probably never used but got activated with the migration to systemd. Anyway, you might want to delete your stray init scripts and eventually get rid of the packages altogether.

Then GDM wouldn’t come up. Only flicker. It took me a while to find the relevant log files (thinking that everything was in the Journal by now…) but grepping for the usual “EE” and “WW” didn’t reveal much.

# grep -r -e EE -e WW /var/log/gdm/
/var/log/gdm/:5.log.1: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/gdm/:5.log.1:Initializing built-in extension MIT-SCREEN-SAVER
/var/log/gdm/:5.log.1:(WW) Falling back to old probe method for vesa
/var/log/gdm/:5.log.1:(WW) Falling back to old probe method for modesetting
/var/log/gdm/:5.log.1:(WW) Falling back to old probe method for fbdev
/var/log/gdm/:5.log: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/gdm/:5.log:Initializing built-in extension MIT-SCREEN-SAVER
/var/log/gdm/:5.log:(WW) Falling back to old probe method for vesa
/var/log/gdm/:5.log:(WW) Falling back to old probe method for modesetting
/var/log/gdm/:5.log:(WW) Falling back to old probe method for fbdev
/var/log/gdm/:1.log.2: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

But. There were also the logs for the “slaves”. They contained:

gdm-simple-slave[1030]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
gdm-launch-environment][1046]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
gdm-launch-environment][1046]: pam_unix(gdm-launch-environment:session): session closed for user gdm
gdm-simple-slave[1030]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0′ failed
gdm-simple-slave[1030]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0′ failed

And there was a hint given by systemd:

# systemctl status gdm --full
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
Active: active (running) since Fr 2013-05-03 12:22:04 CEST; 9s ago
Main PID: 1843 (gdm-binary)
CGroup: name=systemd:/system/gdm.service
└─1843 /usr/sbin/gdm-binary

Mai 03 12:22:07 bigbox gdm[1843]: gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.510350 seconds
Mai 03 12:22:07 bigbox gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.510350 seconds
Mai 03 12:22:07 bigbox gdm-simple-slave[1997]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Mai 03 12:22:08 bigbox gdm-simple-slave[1997]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Mai 03 12:22:08 bigbox gdm[1843]: gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.507905 seconds
Mai 03 12:22:08 bigbox gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.507905 seconds
Mai 03 12:22:08 bigbox gdm-binary[1843]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Mai 03 12:22:08 bigbox gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.509609 seconds
Mai 03 12:22:08 bigbox gdm[1843]: gdm-binary[1843]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Mai 03 12:22:08 bigbox gdm[1843]: gdm-binary[1843]: WARNING: GdmDisplay: display lasted 0.509609 seconds

Aha! There is the problem! But.. what is it? No indication whatsoever. Not even a tiny hint as to where to look next.

I decided to make baby steps and tried to bring up X on my own. My computer liked “X”. But it didn’t “startx”. That in turn revealed a missing library. libicule.so.48. But the current version is .49. Why on earth would something try to link against an old version? “yum distro-sync” proves me right that my packages are up to date. I thus set out to find the weird library causing me trouble. But there were many!


# ldd /lib64/libgailutil-3.so | grep not
libicule.so.48 => not found
libicuuc.so.48 => not found
libicudata.so.48 => not found

I thought I got rid of them by doing

for f in /lib64/*.so; do ldd $f | (grep -q “not found” && echo $f); done | xargs yum remove -y

but that didn’t help. The ldd resolves symbols recursively but I really want to know the symbols needed by the library itself, not its dependencies. Readelf comes to mind. And after chasing a few libraries manually, I was tired so I came up with

for lib in $(cat /tmp/libs); do echo $lib; for l in $(readelf -d /lib64/$lib | grep NEEDED | cut -d[ -f2 | cut -d] -f1); do echo $lib: $l; done; done | less

which showed nicely which library the culprit was.

It was /lib64/libharfbuzz.so.0 from harfbuzz-0.9.13-1.fc20.x86_64. Where does this package come from, you may ask. So did I. I didn’t know how to make yum tell me, but I found out that it belonged to the F17 texlive repository.

Interestingly enough, yum check told me that there was a problem but couldn’t handle it. The solution, very similar to the command above, but with an important difference:

yum --disablerepo texlive distro-sync

Hope this will be useful to someone in the future. Chances are quite good.

GNOME.Asia 2013 is now Calling for Papers

Wednesday, March 6th, 2013

A shameless copy from over there:

GNOME.Asia 2013 is calling for papers. GNOME.Asia Summit is Asia’s GNOME user and developer conference, spreading the knowledge of GNOME across Asia. The conference will be held in NIPA Business Center, Sangam-dong Seoul, Korea on May 24 -25, 2013. The conference follows the release of GNOME 3.8, helping to bring new desktop paradigms that facilitate user interaction in the computing world. It will be a great place to celebrate and explore the many new features and enhancements to the ground breaking GNOME 3 release and to help make GNOME as successful as possible.

Call for Papers

Submit a Talk!

Important Information

The deadlines:

  • Submission: March 8th, 2013
  • Notification of Acceptance: March 15th, 2013

Conference:

  • Conference Date: May 24th – 25th , 2013
  • Venue: Nuritkum Square – Business tower(3F, 4F), Sangam-dong 1605, Mapo-gu, Seoul, Korea

Main Topics

Possible topics include, but are not limited to

    1. How to Promote/Contribute to GNOME in Asia
      • GNOME Marketing
      • Promotion of Free and Open Source Software
      • How to run a Local GNOME User Group
      • Asia Success Stories/Local GNOME Projects
      • GNOME and Education
      • GNOME Outreach Program for Women
      • Google Summer of Code
    2. Hacking GNOME
      • Lastest Development in GNOME
      • GNOME 3 & GNOME 3 Usability
      • GNOME Human Interface Engineering (Icons and Graphic Design)
      • Bugsquadding in GNOME
      • GNOME Accessibility
      • GNOME 3 Coding How-to
    3. Adapting GNOME to New Types of Devices
      • Develop GNOME on mobile device, like smart phone, tablet PC
      • Develop GNOME on embedded system or open source hardware
      • On-going Projects, Success Stories
      • Find FOSS Friendly Hardware Manufacturers
    4. Localization & Internationalization
      • Translation
      • Input Methods
      • Fonts
    5. Other topics

Any topics related to free and open source which are not listed above is still welcome.

Lightning talks

A five-minutes presentation to demonstrate your work or promote an interesting topic. Reservation and on-site application are both accepted.

A standard session at GNOME.Asia 2013 will be scheduled as 45 mins (35 mins talk + 10 mins Q&A). Please take into consideration any time you will need for preparation. The session could be a technical talk, panel discussion, or BOF.

If you’d like to share your knowledge and experience at GNOME.Asia 2013, please fill in the form at http://2013.gnome.asia/cfp before March 8th, 2013. Please provide a short abstract about your proposal (under 150 words). Include your name, biographical information, a photo suitable for the web, a title, and a description of your presentation . The reviewing team will evaluate the entries based on the submitted abstracts and available time in the schedule. You will be contacted before March 15th, 2013 on whether your submission has been accepted or not.

All interested contributors are highly encouraged to send in their talks. Please help us to spread the invitation to other potential participants. Even you do not plan to be a speaker, please consider joining GNOME.Asia 2013. This is going to be a great event!

GNOME @ FOSDEM 2013

Tuesday, February 5th, 2013

Phew, I’m excited about FOSDEM and also exhausted. We had a nice GNOME presence with a lovely booth, many helpers and nice shirts. Thanks to everyone involved who made it such a success.

Our current T-shirt was designed last minute by Andreas, printed last second by an awesome printing shop, and I like it very much. Especially the girly shirts have a nice colour. The shirt accompanies our current Friends of GNOME campaign about Privacy and Security.

In case you haven’t heard: GNOME is raising money to make GNOME more privacy aware, i.e. to allow to you to use your computer anonymously or leave as few traces behind as possible. Also security is a vital part, so maybe the money will be spent on enabling the chat to transfer files encryptedly or better OpenPGP integration into GNOME. If you want to support these goals, consider becoming a Friend of GNOME. Also, if you only want one of those shirts, become a Friend of GNOME, because at a certain level, you will be eligible to get hold of one of those t-shirts :-)

Unfortunately, our donation process depends heavily on Paypal and is quite US centric. That’s not very nice, the majority of donations does not come from the US. In fact, many donations come from Europe.

Anyway, I couldn’t attend a single talk at FOSDEM, because I was so busy with the booth and with maintaining relationships with friends from other Free Software projects, i.e. OpenSuSE. They had, again, a very nice presence and “The Old Toad”, a nice German beer, which is really needed since the Belgian beer is barely drinkable ;-)

As for the GNOME night out, the GNOME Beer Event, it was seriously crowded. While we occupied the upper floor of a bar the last year, we had two floors this year. We did advertise it. Well enough it seems. We went through the building we had our booth in and taped loads of paper onto the walls and pillars. Not only beer event ads but also posters about GNOME Outreach program for Women or the fact that we had T-Shirts on sale.

Our stand was probably the second most beautiful after the OpenSuSE one. Our T-Shirts were aligned up nicely and we sold quite a few of them. Preliminary statistics suggest that we managed to convince people to buy something between 100 and 150 t-shirts. Next time we better try to provide more girly shirts in larger sizes as they ran out quickly. The KDE folks did have many girly shirts but overall their booth didn’t seem to be as well run as the other years.

While the booth generally went well, our interaction story with the people isn’t great. So far, we have a demo machine in the middle of the table which makes it really hard to do stuff together or to show off things, because you can’t really look at what the person is doing neither can you easily show stuff. So maybe putting the machine on either edge of the table would help.

I’m looking very forward to next year’s FOSDEM, hoping that we will have, again, a great set of people willing to spend their time standing there for GNOME.

Now reachable again on my GNOME alias

Tuesday, January 8th, 2013

Public service announcement: If you tried to contact me via email on my @gnome.org alias within the last three weeks, the email eventually bounced and didn’t get through. Now things should be back to normal.

I just realised that I wasn’t able to receive mail due to some fuckups on my side. I was told that sending email to me was a bit difficult but only from people I know where using a deprecated address that I stopped using a while ago. So I replied that they should update their addressbook instead of complaining. But I then I was told that sending to my gnome.org address was also difficult. I didn’t really realise that I was not receiving mail since December 18th! Well, I did think that I got way less email than usual, but I blamed the festive season…

What did finally happen? Easy: The @gnome.org alias was set up to forward to my deprecated address and eventually the domain expired. I didn’t know that I had the alias set up to my deprecated address and no-one told me that all of a sudden all the mail was bouncing.

Anyway, now things should be operational again. Except that I have to re-register with all the mailinglists that I was probably thrown off of due to the bounces.

Talking at FOSS.in 2012, Bangalore, India

Friday, December 28th, 2012

As reported, FOSS.in took place this year, in Bangalore, India. I was fortunate enough to be invited again to this leading Free Software event in India, if not Asia.

Queueing people trying to get in to FOSS.in

The event hosted many very good people and it was a real pleasure to be surrounded by smart folks that love Free Software. It’s a real honour to be invited and speak on the same stage as these people. And it’s an honour to be able to talk about Free Software in a so called developing country and try to form the next generation of Free Software hackers.

There were many talks and I think I will follow up with a separate post about that.

My first talk went really well I think (others do seem to think so, too). The audience seemed to be genuinely interested and I enjoyed being on stage. At some stage, I need to revamp my slides though. I usually go with TeXed slides, but for the GNOME ones, I keep using LibreOffice. One of the minor problems is, that I want to play videos from within the presentation. I can do that (more or less) with LibreOffice and PDF can also do it. But this is not working with my version of Evince :-\

Anyway, thanks to hasgeek.tv, we have recordings of FOSS.in (Day1, Day2, Day3)! And here is my first talk live on tape:

The second talk was a surprise for me, because I was told just a few hours in advance that I need to give another one. Apparently someone couldn’t come and the slot needed to be filled. I jumped in and did my show. I was still a bit hung over from the night before, but it went off well. Except for the fact that my laptop went off the presenter desk. It’s a bit shaky still, so if you happen to have a spare machine that’s decent enough, let me know. Anyway, I have to say, that I dislike the fact that I was told just a few hours in advance that I had to give another talk. But I appreciated being the one that is considered to entertain the people the most. Also very interesting was that I sat on a panel that Lenny moderated. I remember well when Lenny was asked to do that for the first time last year in Japan. He does it well and again, I felt very honoured to be invited to sit next to all those important people, eventually being considered being one of them. However, it appears that there no videos yet.

As for the rest of the trip, we went to Sri Lanka and did a round trip there. An interesting country indeed. Very developed. Not as affordable as expected but still very good value for us whities.

Panorama from Sigiriya Rock

I hope that the FOSS.in team manages to pull it off again next year. I really believe that the event impacts the development of Free Software in the region. And without such an event, great opportunities are lost.

As usual, thanks to FOSS.in and the GNOME Foundation for supporting me to go there.

Updating Bylaws of the GNOME Foundation

Sunday, September 9th, 2012

The GNOME Foundation Bylaws are currently in an ugly PDF which you can see here or from our website here.

I’ve just sent a mail to foundation-list asking for feedback on our proposed changes.

I want to explain the changes we made to hopefully clear some points up that might arise. So let’s walk through the diff, hunk by hunk.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -1,10 +1,60 @@
+.. comment:
 
+        You can compile this document using Python's docutils like this:
+        
+                rst2latex --documentclass=scrartcl --documentoptions=a4paper,10pt,bigheading   --no-section-numbering bylaws-simple.rst > bylaws.tex
+          
+        Then you'll get a .tex file which you can compile using pdflatex. You probably need to have a couple of packages installed.
+        If it complains about a missing .sty file, you can install it using yum:
+        
+                yum install -y 'tex(pdfcomment.sty)'
+
+
+
+        The HTML version compiles similarly:
+        
+                rst2html --no-section-numbering --stylesheet=bylaws.css bylaws-simple.rst > bylaws.html
+
+
+.. role:: raw-html(raw)
+        :format: html
+
+.. role:: raw-latex(raw)
+        :format: latex
+
+.. role:: comment
+.. role:: huge
+.. role:: uppercase
+.. role:: hugeuppercase (huge)
+
+
+.. To turn off the comment function, uncomment (remove the first two leading dots and the white space) the following
+
+.. :raw-latex:`\renewcommand{\DUrolecomment}[1]{}`
+
+.. this sets the title
+
+        =============================
+        Bylaws of GNOME Foundation
+        =============================
+
+.. contents::
+
+        
+-----------------------
+
+.. for some weird reason, the order of the classes is important. Maybe fix it anyway, by patching \maketitle
 .. class:: centered
         
         :hugeuppercase:`Bylaws of GNOME Foundation`
         :raw-latex:`}\\% There's weird behaviour in docutils, i.e. every paragraph would get centered on its own`
         Initially Adopted on March 16, 2001.
         As Amended on April 5, 2002.
+        As Amended on November 11, 2005.
+        As Amended on October 22, 2007.
+        As Amended on [October 30, 2012.]
+        
+
 

So this is just some commentary to enable you to make a nice looking document from that .rst file.

Well, the filename in the comment will most likely be different. But that’s a very minor change. And the date indicated in square brackets is preliminary. So that will be replaced with a proper date once it’s set.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -12,7 +62,7 @@
 ==================================================================
 
 
-The name of the Corporation shall be Gnome Foundation (the "**Corporation**"), a California
+The name of the Corporation shall be GNOME Foundation (the "**Corporation**"), a California
 Nonprofit Public Benefit Corporation.
 
 

Since we use GNOME all over the place, we should not propagate “Gnome” any further.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -107,15 +164,17 @@
 Other Classes of Membership 
 -----------------------------------------
 
-. The Board may, from time to time, establish another class or classes of members, with or
+The Board may, from time to time, establish another class or classes of members, with or
 without voting rights. The privileges, rights and duties of such other class or classes of members
 shall be as provided by the Board, subject to the terms of the Bylaws, as amended from time to time.
 The Board may thereby confer some or all of the rights of the members upon any person or persons.
-If such person or persons do not have the right to vote for either: (i) the election of a Director or
-Directors, on a disposition of all or substantially all of the assets of this corporation, on a merger, on
-a dissolution or (ii) the selection of delegates who possess any such voting rights or (iii) changes to
-the corporation's Articles of Incorporation or Bylaws, such person shall not be a member within the
-meaning of Section 5056 of the Nonprofit Corporation Law of the State of California.
+If such person or persons do not have the right to vote for either:
+
+1. the election of a Director or Directors, on a disposition of all or substantially all of the assets of this corporation, on a merger, on a dissolution or
+
+2. the selection of delegates who possess any such voting rights or
+
+3. changes to the corporation's Articles of Incorporation or Bylaws, such person shall not be a member within the meaning of Section 5056 of the Nonprofit Corporation Law of the State of California.
 
 
 

The first change is just a whitespace.

The other changes should just be a conversion of the format. That is, the list is now a proper list as opposed to the inline notation.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -141,7 +198,7 @@
 Admission and Removal 
 -----------------------------------------
 
-Admission or removal from membership shall be by the vote of a majority of the number of
+Admission or removal from membership shall be by the vote of a majority of the 
 Directors then in office.
 

This is meant to be a minor language cleanup. I was confused of the double speak with the “number of”.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -171,20 +226,18 @@
         that the member no longer meets the qualification requirements for membership in the
         Corporation.
 
-
 #.      **Removal or Suspension**.  Membership shall terminate upon the determination of the Board
-        or Membership Committee after a hearing duly held in accordance with this Section 6(c), that
+        or Membership Committee after a hearing duly held in accordance with this Section 6.7.3, that
         the member has failed in a material respect to observe the rules of conduct promulgated from
         time to time by the Board and applicable to members, or otherwise has failed in some
         material respect to merit continued membership privileges in the Corporation. In the event of
         a removal or suspension of a member, the following procedures shall be implemented:
 
-        a)      A notice shall be sent by prepaid, first-class, certified or registered mail to the most recent
-                address of the member as shown on the Corporation's records, setting forth the removal or
-                suspension and the reason therefore. Such notice shall be sent at least fifteen (15) days
+        a)      A notice shall be sent by electronic mail and prepaid, first-class, certified or registered mail to the most recent
+                address of the member, if known to the Corporation, setting forth the removal or
+                suspension and the relevant reason. Such notice shall be sent at least fifteen (15) days
                 before the proposed effective date of the removal or suspension.
 
-
         #)      The member being expelled or suspended shall be given an opportunity to be heard, either
                 orally or in writing, at a hearing to be held no fewer than five (5) days before the removal.
                 The hearing shall be held by the Board or Membership Committee. Any such hearing may

The section 6(c) is wrongly referenced.

We first require an email to be sent. On top, we clarify the requrement of a snail mail to the point that we have to sent a regular mail if we do know the address. So far, we do not really collect address data (well, the travel committee does and the Friends of GNOME programme generates address data, too). And I don’t think we want to. Hence we specify that we need to know the address in first place.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -192,10 +245,9 @@
                 participants in the hearing can hear one another. The notice to the member of his or her
                 proposed removal or suspension shall state that such member is entitled, upon request, to
                 such hearing, shall state that a date, time and place of hearing will be established upon receipt
-                of request therefor, and shall state, that in the absence of such request, the effective date of
+                of such a request, and shall state, that in the absence of such request, the effective date of
                 the proposed suspension or removal.
 
-            
         #)      Following the hearing, the Board, or Membership committee, as the case may be, shall
                 decide whether the member should in fact be expelled, suspended, or sanctioned in some
                 other way. The decision of the Board or Membership Committee, as the case may be, shall

The “therefor” was quite confusing to me, so I got rid of it everywhere. There will be more changes with either a “therefore” or a “therefor”.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -199,11 +251,10 @@
         #)      Following the hearing, the Board, or Membership committee, as the case may be, shall
                 decide whether the member should in fact be expelled, suspended, or sanctioned in some
                 other way. The decision of the Board or Membership Committee, as the case may be, shall
-                be final.
-
+                be final, subject to any challenge brought pursuant to this section.
 
-        #)      Any action challenging a removal or suspension of membership, including any claim
-                alleging defective notice, must be commenced within one year after the date of the removal
+        #)      A member may bring an action challenging a removal or suspension of membership, including any claim
+                alleging defective notice, within one year after the date of the removal
                 or suspension.
 
 

I pushed for that change, because it was contradictory to me, that the decision shall be final but can then be challenged. By now, I understand the spirit and the reasoning very well, but nonetheless, I wanted to make it simpler for others (and potentially for me, in a few month) to read. The bylaws simply want to enable someone to claim a defective notice. And it makes perfect sense to me in such a serious cirumstance as a removal. So all the change wants to achieve is to clarify that the decision shall be final, only if there is no defective notice to be claimed.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -252,13 +301,11 @@
 of the Corporation.
 
 
-
-Annual Meetings and Election of Directors
+Annual Meetings
 -----------------------------------------
 
-The annual meetings of members of the Corporation shall be held on the second Saturday
-in November of each year at 10:00 a.m., or at any other time and place determined by the resolution
-of the Board. Directors shall be elected and other proper business may be transacted at the annual
+The annual meetings of members of the Corporation shall be held at any time and place determined by the resolution
+of the Board. Directors may be elected and other proper business may be transacted at the annual
 meeting of members.
 
 

This biggie simply reflects our currect way of working. I actually like the idea of a fixed annual meeting mentioned in the bylaws, but well, reality shows us that what we really do is to meet each year at GUADEC.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -269,7 +315,9 @@
 Special meetings of members, for any lawful purpose, may be called at any time by the
 President or by the Board. Furthermore, special meetings of the members for any lawful purpose
 may be called by, upon request in writing by at least ten percent of the membership, or at least five
-percent of the membership in accordancw with Article XVI, stating the business to be transacted at
+percent of the membership in accordance with
+Article XVI,
+stating the business to be transacted at
 the special meeting, mailed to the principal office of the Corporation, or delivered to the chairman of
 the Board, the President, the Vice President or Secretary. It shall be the duty of the President to
 cause notice to be given, within seven (7) days from receipt of such a request, to be held no more

Accordance was a typo in the original

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -280,12 +328,9 @@
 Notice of Meetings 
 -----------------------------------------
 
-A notice of each annual meeting, written ballot for election of Directors or otherwise, if
-any, and special meeting shall be given by the President or, in case of his or her failure or refusal, by
+A notice of each annual meeting, and special meeting shall be given by the President or, in case of his or her failure or refusal, by
 any other officer or any Director; shall specify the place, time, day and hour of the meeting or the
-date on which the ballot shall be returned, if applicable; in the case of an annual meeting at which
-Directors shall be elected, shall specify the names of all those who are candidates for election of
-Directors at the time the notice is given, and in the case of special meetings, the nature of the
+date on which the ballot shall be returned, if applicable; and in the case of special meetings, the nature of the
 business to be transacted thereat. Such notice shall be given in writing to every member of the
 Corporation who, on the record date for notice of the meeting, is entitled to vote thereat. Such notice
 shall be given either personally or by sending a copy thereof by first-class mail or by telephone

The president was supposed to send the ballots for elections. But we don’t do that anymore. And I do think it makes sense to not require the president to do it. Currently, it is tighly coupled with the rest of the elections, effectively requiring the president to do the elections.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -297,6 +342,13 @@
 all other meetings.
 
 
+Election of Directors
+-----------------------------------------
+
+Directors may be elected at the annual meeting as described herein or otherwise by eletronic mail and electronic voting. Notice of such electronic mail or electronic voting shall be given by the President or
+by anyone duly appointed with the authority to do so by the Directors in accordance with Section 8.3.
+Such notice shall be sent promptly to the membership at least thirty (30) days prior to the last day on which votes may be submitted.
+
 
 Adjourned Meetings 
 -----------------------------------------

And to clarify, that we do our elections via electronic voting (as opposed to the AGM). It might actually be beneficial to the AGM if the directors were elected there, but then again, that would reduce the people being able to vote drastically. But maybe that’s something for the future, i.e. find a mix between e-voting and voting at the AGM.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -341,6 +393,14 @@
 
 
 
+
+
+Quorum for Referenda  
+-----------------------------------------
+
+Any member of the Corporation may propose a referendum. Such request for a referendum must be endorsed by 10\% of the Membership. The overall referendum process shall be conducted by the Membership and Elections Committee, as authorized by the Directors pursuant to Article IX.
+
+
 Record Date 
 -----------------------------------------
 

This is a change just reflects our way of working with referenda since at least 2004. I don’t know the origin and it’d be interesting to know where it came from. In fact, I was hesitating to make that change, but we lived with that rule for so long now, it should be written down then.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -438,7 +499,7 @@
 
 2.      A Director shall be a Member.
 
-3.      The initial number of Directors shall be eleven (11).
+3.      The number of Directors on [October 31, 2012] is seven (7).
 
 4.      No organization, corporation or similar entity, or any affiliate thereof, shall hold, directly or
         indirectly, more than 40\% of the Board seats, regardless of election results. In the event that

As per a referendum, we reduced the number of directors. I’m not really in favour of changing the spirit of the bylaws at this point. But it’s not very intrusive and hopefully removes potential confusion for people reading the bylaws and who wonder why we have 7 and not 11 directors.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -458,7 +519,7 @@
 Election and Term of Office of Directors 
 -----------------------------------------
 
-1.      Each of the directors shall hold office for one (1) year.
+1.      Each of the directors shall hold office for one (1) year, or a period of up to two (2) years as determined by the Board and announced prior to an election being called.
 
 2.      Directors shall be elected by the membership in accordance with the rules set forth on

http://foundation.gnome.org/electionrules.html.

This is another change to the bylaws from a referendum in 2007.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -495,19 +556,18 @@
 3.      **Removals**. A Director may be removed for cause. In the event such removal, the following
         procedures shall be implemented:
 
-        a)      A notice shall be sent by mail by prepaid, first-class, certified or registered mail to the
-                most recent address of the member as shown on the Corporation's records, setting forth the
-                removal and the reason therefore. Such notice shall be sent at least seven (7) days before the
+        a)      A notice shall be sent by electronic mail and by prepaid, first-class, certified or registered mail to the
+                most recent address of the member, if known by the Corporation, setting forth the
+                removal and the relevant reason. Such notice shall be sent at least seven (7) days before the
                 proposed effective date of the removal.
 
         #)      The Director being removed shall be given an opportunity to be heard, either orally or in
                 writing, at a hearing to be held no fewer than five (5) days before the removal. The hearing
                 shall be held by the Board. The notice to the Director of his or her proposed removal shall
                 state that such member is entitled, upon request, to such hearing, shall state that a date, time
-                and place of hearing will be established upon receipt of request therefor, and shall state, that
+                and place of hearing will be established upon receipt of such a request, and shall state, that
                 in the absence of such request, the effective date of the proposed removal.
 
-
         #)      Following the hearing, the Board shall decide whether the Director should in fact be
                 expelled, suspended, or sanctioned in some other way. The decision of the Board shall be
                 final.

Again, email and snail mail, if possible.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -547,11 +606,11 @@
 executive office of the Corporation. Special meetings of the Board shall be held at any place within
 or outside the State of California that has been designated in the notice of the meeting or, if not
 stated in the notice, or if there is no notice, at the principal executive office of the Corporation.
-Notwithstanding the above provisions of this Section 5, a regular or special meeting of the Board
+Notwithstanding the above provisions of this Section  8.5, a regular or special meeting of the Board
 may be held at any place consented to in writing by all the Board members, either before or after the
 meeting. If consents are given, they shall be filed with the minutes of the meeting. Any meeting,
 regular or special, may be held by conference telephone or similar communication equipment, so
-long as all Directors participating in the meeting can hear one another, and all such Directors shall be
+long as all Directors participating in the meeting can communicate with one another, and all such Directors shall be
 deemed to be present in person at such meeting.
 
 

The first change is purely cosmetic.

The second change is about hearing one another. While I do think it is import to actually hear, some people simply cannot. Apparently for US legal reasons, those kind of provisions need to be adapted for the impaired. It has also a benefit of allowing things like IRC meetings.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -578,7 +638,7 @@
         a)      **Manner of giving**. Notice of the time and place of special meetings shall be given to each
                 Director by one of the following methods:
                 
-                i. by personal delivery or written notice;
+                i. by personal delivery;
                 #. by first-class mail, postage prepaid;
                 #. by telephone communication, including a voice
                    messaging system or other system or technology designed to record and communicate

The written notice is redundant information, as there is snail mail mentioned (and email FWIW).

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -623,6 +683,10 @@
 any action taken is approved by at least a majority of the required quorum for that meeting.
 
 
+.. _Section Adjournment: `Adjournment`_
+.. _Article Directors: `Directors`_
+
+
 Waiver of Notice 
 -----------------------------------------
 

This is a technicality for the current reStructuredText parser :-\ The problem is, that there are more than one headings with the same name.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -682,7 +744,7 @@
 Directors as such shall not receive any compensation for their services, but by resolution of
 the Board, expenses of attendance, if any, may be allowed for attendance at regular or special
 meetings of the Board; but nothing herein contained shall be construed to preclude any Director
-from serving the Corporation in any other capacity and receiving compensation therefor.
+from serving the Corporation in any other capacity and receiving compensation for this. 

Another therefor removed.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -697,7 +759,7 @@
 -----------------------------------------
 
 The Board, by resolution adopted by a majority of the Directors then in office, provided a
-quorum is present, may create one or more committees, to serve at the pleasure of the Board.
+quorum is present, may create or remove one or more committees, to serve at the pleasure of the Board.
 Appointments to committees of the Board shall be by majority vote of the Directors then in office.
 The Board may appoint one or more alternate members of any such committee, who may replace
 any absent member at any meeting of the committee.

This is just a clarification as serving “at the pleasure of the board” apparently means to not serve anymore if the board does not want to. But to make it more explicit, we incorporate “remove”.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -777,6 +839,10 @@
 
 
 
+.. The following incoming anchor needs to be defined because reST doesn't like the section and the subsection being named Officers
+
+.. _sec\:officers:
+
 Officers 
 ==================================================================
 

Again, a technical change for reST.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -796,14 +863,20 @@
 Election and Term of Office 
 -----------------------------------------
 
-The officers of the Corporation, except such officers as may be appointed in accordance with
-the provisions of Section 3 or Section 5 of this Article X, shall be chosen annually by the Board, and
-each shall hold his or her office until he or she shall resign or shall be removed or otherwise
+
+The officers of the Corporation, except such officers as may be appointed in accordance
+with the provisions of Section 10.3 or Section 10.5 of this Article X, shall be chosen
+annually by the Board, and each shall hold his or her office until he or she shall resign
+or shall be removed or otherwise
 disqualified to serve, or his or her successor shall be elected and qualified, subject to the rights, if
 any, of an officer under any contract of employment. New offices may be created and filled at any
 meeting of the Board. Each officer shall hold office until that officer's successor shall have been
 duly elected and shall have qualified.
 
+.. _Section Subordinate Officers: `Subordinate Officers`_
+.. _Section Vacancies: `sec\:vacancies`_
+.. _Article Officers: `sec\:officers`_
+
 
 Subordinate Officers 
 -----------------------------------------

Just cosmetic and technical changes to include the section number.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -821,16 +893,16 @@
 1.      **Removal**. Any officer, other than the President, may be removed with or without cause. In
         the event such removal, the following procedures shall be implemented:
         
-        a)      A notice shall be sent by mail by prepaid, first-class, certified or registered mail to the
-                most recent address of the officer as shown on the Corporation's records, setting forth the
-                removal and the reason therefore. Such notice shall be sent at least seven (7) days before the
+        a)      A notice shall be sent by electronic mail and by prepaid, first-class, certified or registered mail to the
+                most recent address of the officer if known by the Corporation, setting forth the
+                removal and the relevant reason. Such notice shall be sent at least seven (7) days before the
                 proposed effective date of the removal.
 
         #)      The officer being removed shall be given an opportunity to be heard, either orally or in
                 writing, at a hearing to be held no fewer than five (5) days before the removal. The hearing
                 shall be held by the Board. The notice to the Officer of his or her proposed removal shall
                 state that such member is entitled, upon request, to such hearing, shall state that a date, time
-                and place of hearing will be established upon receipt of request therefor, and shall state, that
+                and place of hearing will be established upon receipt of such a request, and shall state, that
                 in the absence of such request, the effective date of the proposed removal.
 
         #)      Following the hearing, the Board shall decide whether the Officer should in fact be

Again a therefor, email and snail mail issue.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -845,7 +916,9 @@
         it effective. Any resignation shall be without prejudice to the rights, if any, of the
         Corporation under any contract to which the officer is a party.
 
+.. Again, this reference needs to be explicitely given because there is another "Vacancies" section.
 
+.. _sec\:vacancies:
 
 Vacancies 
 -----------------------------------------

Technical.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 14:16:50.849271582 +0300
@@ -864,8 +937,12 @@
 President 
 -----------------------------------------
 
-The President shall be the chief executive officer of the Corporation and shall in general
-supervise and control all of the business and affairs of the Corporation. The President may sign,
+The President shall act as the chief executive officer of the Corporation
+if no chief executive officer or executive director has been appointed by
+the Board and shall in general supervise and control all of the business
+and affairs of the Corporation. The President shall also act as the
+Chairman if none has been appointed.
+The President may sign,
 with the secretary or any other proper officer of the Corporation authorized by the Board, any deeds,
 mortgages, bonds, contracts or other instruments that the Board of Directors has authorized to be
 executed, except in cases where the signing and execution thereof shall be specially designated by

We do have our own, paid, CEO. I do like the fact though, that we intend the President to be the CEO. It makes a great deal of sense to me to have these kind of priviledges attached to the President. It is also nice, though, to be able to appoint that position. To then fill the role of the President with something, we make it the chairman.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -943,7 +1016,8 @@
 Definitions 
 -----------------------------------------
 
-For the purpose of this Article I:
+
+For the purpose of this Article XI:
 
 1.      "agent" means any person who is or was a Director, officer, employee, committee member
         or other agent of the Corporation; or is or was serving at the request of the Corporation as a

The original probably meant to reference Article XI, not I. Article I is the name of the Corporation. That wouldn’t make much sense.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -977,7 +1053,7 @@
 Actions Brought by Persons Other than the Corporation 
 ---------------------------------------------------------
 
-Subject to the required findings to be made pursuant to Section 5 below, the Corporation
+Subject to the required findings to be made pursuant to Section 11.5 below, the Corporation
 shall indemnify any person who was or is a party, or is threatened to be made a party, to any
 proceeding, other than an action brought by, or on behalf of, the Corporation, or by an officer,
 Director or person granted related status by the Attorney General, or by the Attorney General on the

Cosmetic.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -1051,8 +1130,9 @@
 Limitations 
 -----------------------------------------
 
-No indemnification or advance shall be made under this Article XI, except as provided in
-Section 2 or 5(b) above, in. any circumstance when it appears:
+
+No indemnification or advance shall be made under this Article XI,
+except as provided in Section 11.2 or 11.5.2 above, in any circumstance when it appears:
 
 1.      That the indemnification or advance would be inconsistent with a provision of the Articles
         of Incorporation, a resolution of the Board or an agreement in effect at the time of the accrual

Cosmetic.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -1099,9 +1179,10 @@
 Fiduciaries of Corporate Employee Benefit Plan 
 -------------------------------------------------
 
-This Article XI does not apply to any proceeding against any trustee, investment manager or
+This Article XI
+does not apply to any proceeding against any trustee, investment manager or
 other fiduciary of an employee benefit plan in that person's capacity as such, even though that person
-may also be an agent of the Corporation as defined in Section la of this Article XI. Nothing
+may also be an agent of the Corporation as defined in Section 11.1.1 of this Article XI. Nothing
 contained in this Article XI shall limit any right to indemnification to which such a trustee,
 investment manager or other fiduciary may be entitled by contract or otherwise, which shall be
 enforceable to the extent permitted by applicable law.

Section “la” (lower case L, a) doesn’t make much sense. That must have been a typo.

--- bylaws-2002.rst	2012-08-25 14:04:42.243447405 +0300
+++ bylaws-2012.rst	2012-08-31 03:28:50.518455409 +0300
@@ -1224,20 +1308,20 @@
 Amendments 
 ==================================================================
 
-Bylaws may be adopted, amended or repealed by the membership. In the event of such
-adoption, amendment or repeal, the following procedures shall be implemented:
 
-1.      Any proposal relating to the adoption, amendment or repeal of the Bylaws shall be posted
-        on http://foundation.gnome.org by the Board for a period of twenty one (21) days;
+Any member can propose the adoption, amendment or repealing of the Bylaws.
+In the event of such a proposal, the following procedures shall be implemented:
+
+1.      The members shall be provided with the reasonable means to comment upon and/or object
+        to any such proposal for twenty one (21) days
 
-2.      The members shall be provided with the reasonable means to comment upon and/or object
-        to any such proposal;
+#.	The proposal shall be sent to the membership and shall be posted on http://foundation.gnome.org by the Board
 
-3.      In the event that five percent or more of the members objects to the proposal, a special
+#.      In the event that five percent or more of the members object to the proposal, a special
         meeting of the members shall be convened in accordance with the provisions of Article VII,
-        and the proposal shall be voted upon;
+        and the proposal shall be voted upon
 
-4.      In the event that five percent or more of the members do not object to the proposal, then
+#.      In the event that five percent or more of the members do not object to the proposal, then
         the proposal shall be adopted by the Board to the extent permitted by CNPBCL Section
         5150(a).

The main change here is to make explicit that any member can propose a change. Any member means any member. Including those who cannot vote or do not have any other rights. They may not necessarily vote on the proposed amendments, but they may propose some.

I was thinking long about this, actually. As a security person, my thinking was that we should rather be protective against people proposing changes to the bylaws, because more or less external people could propose amendments and that’s rather expensive in terms of organisational costs. And we don’t necessarily want some malicious member to create a lot of costs. But then I thought that with a rather easy way of changing the bylaws, we can easily fix this issue if if indeed arises. And then I thought that it is way better to not prematurely optimise, but rather enjoy that kind of freedom we have. Let’s hope it lasts long :)

You can have a look at the full new bylaws here as HTML or rendered as PDF

GUADEC 2012 in A Corunha

Wednesday, August 15th, 2012


As so many people did, I attended GUADEC in A Conrunha *yay*. Overall, the conference was well organised. The local team was really committed and helped us a lot with all our matters. Little details like providing fruits, some sweets and chocolate for the hacking areas made everything just nice.

They also were very careful about keeping the news updated and the GUADEC website interesting. So they published interviews, photos and announcements regularly so one had an incentive to browse the website often. Very well and smartly done.

While I didn’t attend that many talks, I do think that the first keynote stood out. Jake Appelbaum gave a really inspiring talk about Tor and GNOME. He explained Tor and why it is important to provide anonymous internet access not only for wrongdoers but more so for regular people! For example, he mentioned that he had to use Tor on the venue because the WiFi would block SSH. So to get uncensored access to the network, he would use Tor. Another example was to not tell Google where you are. You authenticate with your credentials, but not from your IP, so you only share your location if you really want to. He had very clear proposals for GNOME and hope to be able to share the list soon. I, personally, would like to see us communicate very clearly, why we spy on our website users using Piwik.

The second keynote was a bit annoying, as she was referring to “open source” all the time although she really meant Free Software. Anyway, at the end of the day, I think her message was that other people exist that want a Free society and that we should not feel alone.

Between the talks, one could have a great time talking to people, especially during lunch. For not talking so much, the WiFi worked pretty well all the time. Quite amazing actually. I am also amazed by the effort people put in to things for GNOME. The locals did, i.e. put some GNOME feet stickers on the ground or hung a daily sheet on the wall to indicate today’s timetable. Daniel created an awesome Yearbook for the GSoC and OPW students and Andreas created an annual report. Thanks for working so hard on cool GNOME things!

It also happened that we had our first in person board meeting and I was very excited about that. We were quite productive during the rather long meeting. But afterwards I was quite exhausted. I guess it was the same for everyone involved. I am also quite happy to see two strong proposals for a GUADEC next year. It will be great.

Also thanks to the GNOME Foundation for sponsoring my travel to this year’s GUADEC!

I realised again, though, that I don’t like the Madrid airport and Iberia all too much. It’s a huge airport with no clear way indications, too few benches and power, and annoyingly loud and pointless passenger announcements. But well, it seems to be the cheapest in Spain…

Another huge round of “thank-yous” must be given to the i18n team. It is just incredible how they manage to cater for so many languages in usually close to no time. I have met many people at conferences or exhibitions that mentioned that if there was a success story to GNOME, it would be the translations. And the very fact that we get mails and bugreports in non english languages shows the success of the team, namely giving a very native feel to the users. To show our appreciation, we went for dinner and had a very good evening with discussions, food and wine. Again: Thanks!

PS: Here the whishlist:

Empathy should support OTR and it should be enabled by default (like adium)
I heard this so many times, I nearly stopped asking for feedback at all!
ZRTP/SRTP/TLS for all VoIP services (forward secrecy and strong crypto)
Tor controller extension for gnome-shell – why settle for only having
Vidalia?
What if we could contextually launch applications anonymously? A 'Launch
Torified' context for applications (perhaps with torsocks?)-
 NAT? Who cares? How about 'single-click file sharing over hidden services?
 Decentralized instant messaging – resist traffic analysis (Federated
XMPP HS? For extra fun add decentralized and anonymous offline message
queuing.)
 network-manager improvements:
Ability to configure wireless networks before connecting to them
VPN 'automatically connect' checkbox should work and no traffic should
leak before the VPN comes up.
 VPN connections must fail closed.	
Ability to override DNS settings for all connections.
macchanger support in network-manager
Random MAC addresses per connection or per if-up
Ability to use a Tor DNS resolver on unpriviliged port
Normal modem support
Full Tor support in NetworkManager
Think of it as a free VPN
Full Guest mode in Gnome/GDM that uses Tor by default for all network
traffic – don't just refuse to write data to the disk, refuse to write
information to the bare network too

Interview for gnome.org

Friday, August 3rd, 2012

I was interviewed recently for GNOME.org and while you can read the interview over there, I felt like copying it over here. So enjoy the questions and the answers

Why is open source/free software important to you?

I believe that Free Software makes the world a better place. Also, as I am a bit of a computer security person, it is absolutely crucial to be able to see how the software in question works and be able to eventually fix issues (or have someone to fix them).

How/when/why did you become involved in GNOME?

I was using GNOME ever since and started to follow it more and more until I came greatly involved as a Summer of Code student.

Why did you run for the GNOME Foundation Board?

I am sticking around GNOME for about 5 years now and while I enjoy being in the community I do wanted to progress within GNOME and take new responsibilities.

What do you hope to accomplish during your term on the board?

I hope to push the revamp of the bylaws and enable people to work together more effectively.

Do you think GNOME is heading in the right direction? Why or why not?

I think GNOME is doing well so far, but it must not rest (decadence anyone?). We have very smart people in our community and we should enable them to get awesome stuff for GNOME and the Free Software world done.

Have you attended GUADEC in the past? If so, when/where?

My first GUADEC was the one in Birmingham in 2007.

What are you looking forward to most at GUADEC?

To see friends again and having nice discussions.

Any other thoughts on GUADEC and/or GNOME?

GNOME is a great community and GUADEC is a good place to get in touch. Sometimes though, it might not be comfortable for newcomers to chime in. I still remember myself being too shy to talk to some great GNOME people. So while I recommend to young GNOMErs to not be shy, maybe a “This is GNOME” introductory session for new GNOME people might be a good idea.