November 21, 2014

Choose to accentuate the positive

A number of folks have been talking about “choice” in open source recently.

See the classic post by Adam Jackson: Linux is not about choice and Will Woods followup: two fallacies as well as a google+ post by Greg Kroah-Hartman: here

I broadly agree with all of them, but I’d like to talk about a related thing here.

Folks are free to choose how to spend their time and energy, free to ask others to spend time or energy (which of course those people are free to ignore or decide not to do) and free to use whatever software they like. Thats all great.

I’d like to further posit that the most efficent way to get people to help you with your choices and spend their time and energy on making those choices happen is simple: “Strive to be positive”. If someone is working on software you dislike and don’t have any intention of using, move on, and instead work on what you DO intend to use or find agrees with your choices. Choosing to spend your time and energy knocking down people doing things (especially if you don’t agree with them) just makes you waste your energy on that and slows down the people you are flaming. I’d also posit that it makes your life full of negatives and much less enjoyable for both you and people you are flaming.

If you find you are in a discussion where you can’t find a way to be positive, it’s time to back away and go do something that is.

The first APAC Ambassadors FAD for annual budget planning
We have finished the first ever FAD for APAC Ambassadors for annual budget planning in Phnom Penh at the last weekend. As other participants like Sirko or Siddesh wrote some nice summary reports (day 0, 1 and 2), I would not like to repeat those more. Instead of those, I would like to tell you […]
PostBooks 4.7 packages available, xTupleCon 2014 award

I recently updated the PostBooks packages in Debian and Ubuntu to version 4.7. This is the version that was released in Ubuntu 14.10 (Utopic Unicorn) and is part of the upcoming Debian 8 (jessie) release.

Better prospects for Fedora and RHEL/CentOS/EPEL packages

As well as getting the packages ready, I've been in contact with xTuple helping them generalize their build system to make packaging easier. This has eliminated the need to patch the makefiles during the build. As well as making it easier to support the Debian/Ubuntu packages, this should make it far easier for somebody to create a spec file for RPM packaging too.

Debian wins a prize

While visiting xTupleCon 2014 in Norfolk, I was delighted to receive the Community Member of the Year award which I happily accepted not just for my own efforts but for the Debian Project as a whole.

Steve Hackbarth, Director of Product Development at xTuple, myself and the impressive Community Member of the Year trophy

This is a great example of the productive relationships that exist between Debian, upstream developers and the wider free software community and it is great to be part of a team that can synthesize the work from so many other developers into ready-to-run solutions on a 100% free software platform.

Receiving this award really made me think about all the effort that has gone into making it possible to apt-get install postbooks and all the people who have collectively done far more work than myself to make this possible:

Here is a screenshot of the xTuple web / JSCommunicator integration, it was one of the highlights of xTupleCon:

and gives a preview of the wide range of commercial opportunities that WebRTC is creating for software vendors to displace traditional telecommunications providers.

xTupleCon also gave me a great opportunity to see new features (like the xTuple / Drupal web shop integration) and hear about the success of consultants and their clients deploying xTuple/PostBooks in various scenarios. The product is extremely strong in meeting the needs of manufacturing and distribution and has gained a lot of traction in these industries in the US. Many of these features are equally applicable in other markets with a strong manufacturing industry such as Germany or the UK. However, it is also flexible enough to simply disable many of the specialized features and use it as a general purpose accounting solution for consulting and services businesses. This makes it a good option for many IT freelancers and support providers looking for a way to keep their business accounts in a genuinely open source solution with a strong SQL backend and a native Linux desktop interface.

Predictable Network Interface Names
Predictable Network Interface Names:

Even if quite “old”, one nice feature of systemd.

Inkscape Workshop Phnom Penh

I had yesterday the opportunity to give an Inkscape workshop at Development Innovations Cambodia in Phnom Penh. The participatns was only from several NGO’s, so called multiplicators and it turned out great. One day isnt that much time, to learn enough about Inkscape to use it in a professional way, but you can get at least the foundations to use it and learn more by yourself. But we had a lot of fun together and there was really some talented people amongst the 23 participants and the best two of them had already Fedora stickers on their laptop, so Open Source community in Cambodia begins to grow.

November 20, 2014

The State of the Cloud Working Group and Fedora 21 Cloud

As Fedora 21 approaches, let’s take a bit to examine the state of the Cloud Working Group (WG) — or, more importantly, the releases that are coming your way very soon! With Fedora 21 you’ll have two distinct Fedora “flavors” from the Cloud WG: ready to run images for public and private clouds, and Fedora 21 Atomic Host. And, to pique the buzzword crowd’s interest, here’s a spoiler – we’ll be talking about Docker.

Today the Cloud Working Group held / is holding a Atomic Test Day to take a look at the state of the Fedora 21 Atomic Host that’s brand new in Fedora 21. The Test Day went quite well, we found a number of bugs without anything exploding massively, and folks provided really excellent feedback.

First, let’s take a look at what you’re getting with Fedora 21. We have the base image, which isn’t entirely new. We’ve offered a cloud image suitable for deployment on EC2, OpenStack, etc. for a while now. It was a “first-class citizen” in Fedora 20, and (once again) it’s a major focus for the release effort.

The base image is a tailored set of packages that are specially targeted at the cloud environment. These images should be an excellent base for developing and deploying services and applications in private clouds like OpenStack and Apache CloudStack or an public IaaS environment like Amazon Web Services (AWS).

Atomic Base Image

What’s totally new in Fedora 21 is the Atomic Host Image. What’s this Atomic business, you may well ask?

In April, Project Atomic was unveiled as a community of practice to develop a platform for running Docker containers. This means having a tailored platform build from an existing operating system (e.g., Fedora), that allows “atomic” updates and has just the tools you need to run and orchestrate Docker containers. (It also should make a nifty platform for developing containers as well!)

The idea is that a lot of folks now want to build apps and services using containers, but they still use general purpose OSes for many existing applications. Also, the components we need to build the Docker host OS exist in Fedora (or CentOS, or RHEL), so there’s no reason to re-create the wheel in building the Docker host.

Atomic uses rpm-ostree to create the Fedora Atomic image, and then allows users or admins to use rpm-ostree for updates. An update is an “atomic” unit that can rolled back in the event there’s a bug or issue that impacts deployed applications. RPM is a great technology for packages, but it was only envisoned to go one way – forward. The beauty of rpm-ostree is that it lets you revert to a previous state of the host OS with a single command. It also offers some interesting additional features, like switching between trees for two different systems, but we’re not offering those kinds of updates/options yet.

The Atomic image will also feature Kubernetes and Cockpit for working with Docker. Cockpit is looking great, the team there has done a fantastic job of adding features and polish, and getting a stable version ready to ship with Fedora 21. We’ll be talking about Kubernetes much more in the future, and have some features on Cockpit on the Magazine soon. (Note that Cockpit is also available with Fedora 21 Server!)

Docker, Docker, Docker?

It bears mentioning that the Docker base image has been split out from the Cloud Working Group to the Base Working Group, though (obviously) we’ll still be making heavy use of it in cloud environments. A big kudos to the Base Working Group folks who’ve taken that on and are doing great work in getting it into shape for Fedora 21.

The big take-away on Docker, though, is that the Fedora 21 release will have an “official” Docker image. You can use the Fedora 21 Atomic base image with the F21 Docker image to test Docker features, or use Atomic to run Docker to test your containerized applications.

How do I do this? Just run sudo docker pull fedora:21 and you’ll get the latest Docker image for Fedora.

Where We’re At, Where We’re Going – Join Us!

As you can see, there’s a lot of exciting stuff going on in the Cloud territory. However, we still have a lot of work to do on testing, packaging, and developing documentation for best practices.

Have questions? Ask us on the cloud mailing list (cloud@lists.fedoraproject.org), or in #fedora-cloud on Freenode.

CONVOCAÇÃO: Reunião de Colaboradores do Projeto Fedora de Chapecó e Região
Bora fuçar no Fedora, pessoal!

CONVOCAÇÃO: Reunião de Colaboradores do Projeto Fedora
QUANDO: Sábado 29/Novembro, das 14h às 18h
ONDE: Lab B202 (Bloco B) da UNOESC Chapecó

Chamamos todos os atuais colaboradores do Projeto Fedora de Chapecó e região, bem como os interessados em se tornarem contribuidores deste grande projeto, para uma reunião de trabalho e habilitação de novos contribuidores, a se realizar no Lab B202 da UNOESC Chapecó, na tarde do sábado dia 29 de Novembro, a partir das 14h.

Se você já é colaborador e anda meio parado, venha encontrar seus colegas e receber uma nova dose de motivação! Se você tem vontade de participar de uma grande comunidade global de desenvolvimento de Software Livre, crescendo como pessoa e como profissional, venha aprender os primeiros passos conosco, e encontrar novos amigos!

A proposta de trabalho e estudo é a seguinte:
  • O que é, como se organiza e como funciona o Projeto Fedora;
  • Como instalar e utilizar o Sistema Operacional Fedora;
  • Como contribuir para o desenvolvimento do Fedora;
  • "Prática" com criação de contas no Fedora Account System, apresentação nas listas de emails dos grupos de trabalho de interesse dos presentes, canais de IRC onde a comunidade se encontra, etc.
O ambiente será informal e prático, como um grande trabalho em grupo. Venha aprender e fuçar no Projeto Fedora conosco!

Tragam seus laptops, pendrives (para criação de imagens Live de uso e instalação) e a vontade de realizar algo novo.
OPW Fedora Badges Intern… A Year Later!

I can’t believe that my internship started almost a year ago! I participated in the seventh session of the Outreach Program for Women working on Fedora Badges. Time has gone by so quickly! Since my internship ended in March I have continued to stay active on the Fedora Badges project, creating more badge designs and helping others design their own. To date I have designed or collaborated on 97 badge designs in the Fedora Badges system.

This past week I had the opportunity to visit my mentor Máirín Duffy at Red Hat’s Office in Westford, MA. I learned a lot about Fedora.Next and website design. I helped to gather and create content for a new website that will be serving up three flavors of Fedora downloads; Developer, Server and Cloud. I created illustrations, backgrounds and photographs. During my stay I also had the chance to meet my other mentor Ryan Lerch and see a few familiar faces from Flock.

The first project I worked on was an illustration of a computer to display screenshots of various features and interfaces. Drawing this was a lot of fun for me, being one of my first attempts at a more realistic style using Inkscape.

laptop

Fedora.Next for Developers will feature some cool packages, so Mo and I came up with creating a “gift package” illustration. Using the established logo for packages, I added on a sweet green bow!

giftpackage

Mo, Ryan and I brainstormed some ideas for backgrounds and we decided that I should work on creating a background composed of “Fedora.” I have experience with hand lettering so I had a LOT of fun with this project. Each “Fedora” was hand lettered by me with a pen/marker/nib on paper, scanned and then hand traced using Inkscape. Here you can see my hand drawn letters, details and the final product.

fedora_handlettering 3fedora_handlettering

Screen Shot 2014-11-20 at 12.18.15 PMScreen Shot 2014-11-20 at 12.19.05 PMScreen Shot 2014-11-20 at 12.56.55 PM

handlettering_fedora

Overall I had a great time meeting my mentors, Mo and Ryan, and using my skills to contribute some well needed graphics. I want to say thanks to them for patiently teaching me about web design and Fedora.Next, and for making my involvement easy and fun!

panda thank you_small


In praise of Linux Software Raid

It may interest some of you to know that we in Fedora Infrastructure use Linux Software Raid (mdraid) on all our servers local disks. Here’s a nice list of reasons why:

  • Portable: If a machine dies, the disks can actually be swapped into any Linux server and be brought up. If you have hardware raid, you need the same controller, by the same company, with the same firmware, which hopefully works the same way on the new different machine. Good luck with that.
  • Consistent: Since we use it everywhere we don’t need to worry about weird obscure binary only command lines from N raid vendors that we have to figure out each time we need to do anything with the raid.
  • Integrated: When a disk fails, we get email/nagios notification. With hardware raid you can get notification, but you have to setup weird binary only junk and hope that it all works, and hope it lets you know before it’s too late.
  • Great Performance: True it doesn’t have dedicated cache or cpu, but host cpus are so performant these days that mdraid just flies.
  • Easy to install: The Fedora/RHEL installer is well integrated to making software raid volumes.
  • Easy to discover: You can easily see how many disks a server has, if they are all ok and other info from the command line.
  • Hot: You can easily hot remove/add disks and migrate raid levels with no downtime. Hardware raid can sometimes do that with it’s binary only command line junk, but often you need to take the machine down into a ‘raid bios’ thing to do it.
  • Upgradable: To get new cool features, all you have to do is upgrade your kernel and userspace tools.
  • Completely open: Tons and tons of people use mdadm and the code is open. Most hardware raid vendors have something in the upstream Linux kernel, but it’s often behind their development or you need to install binary only tools to really maintain it.

In short, Linux software raid is awesome. :)

Standing desks

So around three months ago (yes, I must do a post on that too) I changed roles at Red Hat and moved from constantly travelling and being on customer sites to working from home. As a result I needed to setup a workspace that I could use day to day.

One thing I’ve always wanted to try is a standing desk. I have back problems, and generally not the best posture, so I thought that would be one way to be able to deal with at least the later, and potentially even the former. The main problem, until recently, is that decent standing desks tend to be very expensive and I didn’t want to needlessly go and spent a lot of extra money for something that would be used for a week and never again. So I decided I would start with a cheap height adjustable desk, which I needed to get anyway due to my height, and then use it as a the basis of a standing desk and then hack it from there. The initial combo I decided on after a lot of looking was the IKEA Galant Height Adjustable Desk at £49 and the IKEA Lack Side table at £8 plus delivery. I figured at less than £100 including delivery if it was terrible I wasn’t wasting a lot of money!

As it turns out it’s been much better than I ever expected it to be. I initially setup the desk to the height I would want when sitting. At a height of six foot three inches I’m not the shortest of people so when sitting I prefer a higher than average desk. Sitting the Lack table on top of the desk by chance also ended up also giving me the perfect standing height. Bonus! A few quid for some foam gym mats plus a decent height adjustable monitor (the most expensive bit by far!) and I was done! Well mostly, I still haven’t decided on a decent keyboard yet.

So how does it look? Well a little bit weird to be honest. How does it work? Better than I ever expected as I find I can happily stand at the desk for a full eight hour working day without too much issue and I’ve even done longer (hello Fedora beta release candidates!!) and my back feels better than it has in a long time! I was also trying to decide on a decent but reasonably priced office chair to buy but now I’m not going to bother. Interestingly IKEA has also just launched the BEKANT sit/stand desk which is reasonably priced and has electric motors for raise/lower. It’s likely I’ll end up getting one of these one day but for the moment my IKEA hack is working pretty well.

Cheap IKEA Standing Desk

Is Amnesty giving spy victims a false sense of security?

Amnesty International is getting a lot of attention with the launch of a new tool to detect government and corporate spying on your computer.

I thought I would try it myself. I went to a computer running Microsoft Windows, an operating system that does not publish its source code for public scrutiny. I used the Chrome browser, users often express concern about Chrome sending data back to the vendor about the web sites the users look for.

Without even installing the app, I would expect the Amnesty web site to recognise that I was accessing the site from a combination of proprietary software. Instead, I found a different type of warning.

Beware of Amnesty?

Instead, the only warning I received was from Amnesty's own cookies:

Even before I install the app to find out if the government is monitoring me, Amnesty is keen to monitor my behaviour themselves.

While cookies are used widely, their presence on a site like Amnesty's only further desensitizes Internet users to the downside risks of tracking technologies. By using cookies, Amnesty is effectivley saying a little bit of tracking is justified for the greater good. Doesn't that sound eerily like the justification we often hear from governments too?

Is Amnesty part of the solution or part of the problem?

Amnesty is a well known and widely respected name when human rights are mentioned.

However, their advice that you can install an app onto a Windows computer or iPhone to detect spyware is like telling people that putting a seatbelt on a motorbike will eliminate the risk of death. It would be much more credible for Amnesty to tell people to start by avoiding cloud services altogether, browse the web with Tor and only use operating systems and software that come with fully published source code under a free license. Only when 100% of the software on your device is genuinely free and open source can independent experts exercise the freedom to study the code and detect and remove backdoors, spyware and security bugs.

It reminds me of the advice Kim Kardashian gave after the Fappening, telling people they can continue trusting companies like Facebook and Apple with their private data just as long as they check the privacy settings (reality check: privacy settings in cloud services are about as effective as a band-aid on a broken leg).

Write to Amnesty

Amnesty became famous for their letter writing campaigns.

Maybe now is the time for people to write to Amnesty themselves, thank them for their efforts and encourage them to take more comprehensive action.

Feel free to cut and paste some of the following potential ideas into an email to Amnesty:


I understand you may not be able to respond to every email personally but I would like to ask you to make a statement about these matters on your public web site or blog.

I understand it is Amnesty's core objective to end grave abuses of human rights. Electronic surveillence, due to its scale and pervasiveness, has become a grave abuse in itself and in a disturbing number of jurisdictions it is an enabler for other types of grave violations of human rights.

I'm concerned that your new app Detekt gives people a false sense of security and that your campaign needs to be more comprehensive to truly help people and humanity in the long term.

If Amnesty is serious about solving the problems of electronic surveillance by government, corporations and other bad actors, please consider some of the following:

  • Instead of displaying a cookie warning on Amnesty.org, display a warning to users who access the site from a computer running closed-source software and give them a link to download an open source web browser like Firefox.
  • Redirect all visitors to your web site to use the HTTPS encrypted version of the site.
  • Using spyware-free open source software such as the Linux operating system and LibreOffice for all Amnesty's own operations, making a public statement about your use of free open source software and mentioning this in the closing paragraph of all press releases relating to surveillance topics.
  • Encouraging Amnesty donors, members and supporters to choose similar software especially when engaging in any political activities.
  • Make a public statement that Amnesty will not use cloud services such as SalesForce or Facebook to store, manage or interact with data relating to members, donors or other supporters.
  • Encouraging the public to move away from centralized cloud services such as those provided by their smartphone or social networks and use de-centralized or federated services such as XMPP chat.

Given the immense threat posed by electronic surveillance, I'd also like to call on Amnesty to allocate at least 10% of annual revenue towards software projects releasing free and open source software that offers the public an alternative to the centralized cloud.


While publicity for electronic privacy is great, I hope Amnesty can go a step further and help people use trustworthy software from the ground up.

Workshop at Smallworld

I am still in Cambodia and after FAD I had on monday and tuesday an workshop about open source graphic tools at Smallworld Cambodia. It was great as always I like being there, its a nice place and its really nice to see how this young people organize to get an better education. The workshop was really good and there was really talented people amongst the particiants. I even managed to help one to install an Fedora on his laptop. The only thing bad was, that my tuesday morning started not so nice with being fetched in the elevator but I was still on time at the place.

So Fedora found again more friends in Cambodia, it might need time to get them to contributors but I have hope for it. At least they start using more and more free software and thats a good thing.

Fedora Cloud SIG update from 2014/11/19

Last week roshi mailed the new release criteria to the test list. Not much reply in that thread. He will bring this point again to the QA meeting on next Monday (2014-11-24). We also need more hands for testing the images. If you want to help please ping us in the #fedora-cloud channel on freenode.

Today is the Project Atomic testday. You can find more details about it here.

jzb will publish the magazine story on Fedora Cloud. It is ready and will be pushed very soon.

During the openfloor, dustymabe informed that he will be going to the Digital Ocean office and get some more information on how easily we can have released Fedora Cloud images there.

I have updated my worknotes so that anyone can run my small test suite. You will find more details in this link.

I will be working as FESCO liaison from the Fedora Cloud SIG, my first duty is to update the Governance page with the current team members.

On a side note, the third meeting of the CentOS Cloud SIG will happen at around 3pm today, meet us at #centos-devel. The log from the last meeting is already available.

Shooting yourself in the foot, part 53326: Mozilla
Step 1: with bad design decisions one after another (Australis is a shining example of that) slide yourself into irrelevance;
Step 2: when market share goes below some threshold, the main sponsor diminishes (or suspend?) payments;
Step 3: in retaliation, hurt the users by forcing om them a sub-par alternative as a default;
Step 4: profit bleed even more angry users and go even faster into irrelevance.

Brilliant strategy Mozilla!

Myself, I am still using Firefox for the time being, but that's exclusively due to Gecko.
targetcli on pre-Fedora 21

targetcli seemed to be a nice way to create an iSCSI target - which I needed - on Fedora 21.

I actually followed this guide which is quite nice. But there is one difference from targetcli on Fedora 18 and on Fedora 21:

On Fedora 21 the service which restores the LIO configuration is in a separate package (and called differently). python-rtslib - yes very intuitive - is the package called, which ships target.service (on Fedora 19 it was called targetd.service, and part of targetcli). This service is responsible for restoring the LIO configuration on boot.

Long story short: Use targetcli to configure LIO. And use The target service to save and restore this configuration on boot.

# Install targetcli
pkcon install targetcli

# Ensure to enable and start the relevant service
systemctl enable target.service
systemctl start target.service

# Ready to do the configuration
targetcli

# IMPORTANT: Save your configuration
targetctl save

In general a nice tool, I’d be happy to see a nicer documentation. But to be fair, there might be one which I haven’t found yet.

Vote now for Council, F21 final freeze, screenshots needed, Fedora Atomic, and Mozilla/Firefox ads

Fedora is a big project, and it’s hard to keep up with everything that goes on. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for November 19th, 2014:

Vote now in the first-ever Fedora Council elections!

The election for the two representative seats on the new Fedora Council is in progress! Fedora Magazine has email-based interviews with the five candidates to help you make an informed decision:

Voting is open to all Fedora Contributors, and closes promptly at 00:00 UTC on November 26th. That’s the afternoon or evening of the 25th in timezones to the west of the Prime Meridian, so don’t delay — read the interviews, and then vote now.

We’re frozen for F21 final

We are now in the “Final Freeze” for Fedora, the last polishing period before the release. This means that packages updates are only allowed via a special exception process, as we work to deliver a solid, stable release to our users on December 9th.

If you’re curious, you can read more on the wiki, or even better, as release candidates come out, help the Fedora Quality Assurance team take them through the validation process. You could be one of Fedora 20’s Heroes of QA!

Or if not, that’s cool — just a few more weeks and we’ll release what I’m confident will be the best Fedora yet.

Atomic Test Day

Speaking of testing… Fedora 21 will feature an experimental new cloud image called Fedora Atomic, based on the Project Atomic patterns. Tomorrow (Thursday — possibly today by the time you’re reading this!), the Fedora Cloud SIG is running a test day for Fedora 21 Atomic, looking specifically to get this into best possible shape for the release.

Screenshots needed!

Another easy way to help is to contribute to the Fedora 21 Screenshots Library. Everything is pretty well explained at the link — install the beta (or a release candidate), update it, and take some screenshots.

We’d particularly like screenshots that show new features in Fedora 21 and that have an interesting composition. We need screenshots of Fedora 21 Workstation as well as each spin (KDE, Xfce, LXDE, etc.).

(And if you can figure out a good way to take a screenshot of Fedora Cloud… awesome.)

Fedora and Mozilla advertising

In an effort to reduce funding reliance on search engine companies (check it out — after 10 years, they just switched their default search provider from Google to Yahoo), Mozilla just introduced a new thing into Firefox which they call “enhanced tiles“, and this includes paid advertisements by default. Compared to most web advertising, Mozilla is certainly making efforts to be minimal about data collection — read technical details, and Mozilla’s blog post about trust, transparency, and control in advertising.

Nonetheless, many Fedora users and contributors have expressed concerns about this, to varying degrees, in a long thread on the devel list. (As always with monster threads, there’s really no need at this point to add more unless you’ve definitely got something new and unique to say, but new insights and constructive discussion are always welcome.) This resulted in a few media reports suggesting that we’re going to drop Firefox. The concerns are real — privacy, the implication of endorsement by Fedora, and a dislike and distrust of advertising in general. It seems likely that we’ll need to work on new policies, not least so upstream project know what we expect — as ads seem to rule the world today, this won’t be the last such situation. But we’re a long way off from making any drastic moves. Instead, we’ll work as a community, including with our friends over at Mozilla, to figure out an approach we can collectively accept.

 


 

5tftw-large

November 19, 2014

Fedora Perú en Fesoli 2014

Llegue a las 9:20 de la mañana al Fesoli 2014, estaba programado para un minicurso o taller de 3 horas, había preparado material para el taller (maquina virtuales con fedora 32 y 64 bits) más no para una presentación, al ser recibidos por los organizadores una sorpresa para mí los tallares estaban tomados por unos cursos programados y no podían asignarme así que me asignaron un aula, al ingresar al aula estaba vacía, las demás charlas ya habían empezado y que tenían cada una regular número de participantes.
Antony Mogrovejo ya estaba a punto de iniciar su charla titulada “Como ser un puppetmaster” que por cierto me la perdi y que en ese momento había un buen número de participantes a la espera, entonces tuve que ir en busca del ambiente asignado para mi participación.
Quedaban como 10 minutos para la hora programada y empezaron a ingresar varios participantes, mientras tanto estaba configurando la resolución para el proyector y que el adaptador hdmi está muy sencible a movimientos asi que teniamos que hacerla con sumo cuidado.
Así que decidí hablar sobre fedora en el siguiente orden, ¿Qué es Fedora?, Fedora Spins, Novedades en la versión 21, La comunidad Fedora Perú, ¿Cómo aportar con Fedora?; las preguntas comúnes que siempre realizan los empiezan a conocer Linux ¿Por qué cambián demasiado rápido las versiones? ¿Por qué usaría fedora y otra distro? ¿Qué ventajas y desventajas presenta Fedora para un usuario final? ¿Puedo usar fedora como desarrollador? ¿En una red lan como puedo compartir ficheros usado Fedora? entre otras y con aportes de los participantes nos dimos cuenta que ya estabámos cerca a la final de la charla. A los chicos o chicas interesados en la distro y en pertenecer a la comunidad se les hizo la entrega de dvs, colgadores y adhesivos.
Después de la charla realizada con unos amigos fuimos a participar de otras ponencias que estaban muy interesantes.

1 OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA IMG_1407 IMG_1408 IMG_1409 IMG_1410 IMG_1411 IMG_1431 IMG_1434 IMG_1436 IMG_1447 OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA OLYMPUS DIGITAL CAMERA z22


Fedora on Guatemala CGSOL 2014
Daala Demo 6: Perceptual Vector Quantization (by J.M. Valin)

Jean-Marc has finished the sixth Daala demo page, this one about PVQ, the foundation of our encoding scheme in both Daala and Opus.

(I suppose this also means we've finally settled on what the acronym 'PVQ' stands for: Perceptual Vector Quantization. It's based on, and expanded from, an older technique called Pyramid Vector Quantization, and we'd kept using 'PVQ' for years even though our encoding space was actually spherical. I'd suggested we call it 'Pspherical Vector Quantization' with a silent P so that we could keep the acronym, and that name appears in some of my slide decks. Don't get confused, it's all the same thing!)

Upcoming Pulp Releases

2.5.0 <– A release candidate is available in Pulp’s beta repo in the 2.5 release stream.

2.6.0 <– Not yet built, but an alpha should be available soon.

Why is the release after 2.5.0 going to be 2.6.0 and not 2.5.1?
Since the version 2.4.0 release, Pulp is working to adhere to semantic versioning. Semantic versioning is important so that users can upgrade to a given version and have a correct expectation about what is in that new version ie: bugfix, features, or backwards incompatible changes. There are new features that are ready to be included in a release, so the next release planned will be 2.6.0.

Will 2.6.0 fix bugs that that exist in 2.5.0?
Yes. There are some new features but also a lot of bugfixes. One of the main bugs resolved is that 2.6.0 should work with RabbitMQ.

I integrate against Pulp (ie: HTTP API, plugin API), is it safe for me to upgrade from 2.5.0 -> 2.6.0?
Yes, any Pulp release that starts with a 2 should be backwards compatible from an API perspective. Sometimes there are good reasons (ie: security) that cause a X.Y release to be incompatible, but 2.5.0 -> 2.6.0 should be completely backwards compatible. 2.4.Z -> 2.5.Z should also be completely reverse compatible.

I develop or contribute to Pulp or Pulp plugins; how does this affect me?
You should do one thing. Go delete 2.5-dev from your fork and local checkouts of pulp, pulp_rpm, and pulp_puppet. We made sure nothing was lost when we deleted 2.5-dev, but you still need to delete your versions of those branches.

Send questions or thoughts to pulp-list; you can also discuss on #pulp on freenode

Availability of OpenLMI in Various Linux Distributions

A quick update on the availability of OpenLMI:

I have tested Fedora, RHEL, CentOS, and OEL servers using the LMI CLI running on a Fedora system – the cross platform access works.

Fedora

Fedora is the primary development platform for OpenLMI. OpenLMI support has been included in Fedora starting with Fedora 18. We strongly recommend using Fedora 20 or the upcoming Fedora 21 release when using Fedora with OpenLMI, as these include the latest versions of OpenLMI. Fedora includes all OpenLMI capabilities: the CIMOM, all Providers, the client tools and all client scripts.

Red Hat Enterprise Linux

RHEL 7 includes the OpenLMI CIMOM and Providers. RHEL 7 includes the client side infrastructure (LMIShell and the LMI CLI). Many of the client scripts are available through the EPEL repository.

CentOS

CentOS 7 includes the OpenLMI CIMOM and Providers. CentOS 7 includes the client side infrastructure (LMIShell and the LMI CLI). Many of the client scripts are available through the EPEL repository.

Oracle Enterprise Linux

OEL 7 includes the OpenLMI CIMOM and Providers.

SuSE

SLES 12 includes a subset of the OpenLMI Providers. SuSE uses the sfcb CIMOM instead of the OpenPegasus CIMOM used by default in the other distributions (both sfcb and OpenPegasus ship it all of these Linux distributions).

SLES 12 includes the following OpenLMI Providers:

  • openlmi-fan
  • openlmi-hardware
  • openlmi-journald
  • openlmi-logicalfile
  • openlmi-pcp
  • openlmi-powermanagement
  • openlmi-python-base
  • openlmi-python-providers
  • openlmi-realmd
  • openlmi-service
  • openlmi-software

The SLES 12 documentation notes that “Only reading of management information is supported for the ‘openlmi’ providers.”.

SLES 12 does not include the OpenLMI storage or network Providers; thus, you can not use OpenLMI to query or configure storage or networks on a SLES 12 system.

Debian

OpenLMI support is not currently available in Debian.

Ubuntu

OpenLMI support is not currently available in Ubuntu.


Run linaro aarch64 images with f21 virt-install + libvirt
Linaro generates some minimal openembedded based aarch64 disk images, which are useful for virt testing. There's simple instructions over here for running them with qemu on an x86 host. But with Fedora 21 packages, you can also these images with virt-install + libvirt + qemu.

Output looks like:
 Starting install...
Creating domain...                                          |    0 B  00:00   
Connected to domain linaro-aarch64
Escape character is ^]
[    0.000000] Linux version 3.17.0-1-linaro-vexpress64 (buildslave@x86-64-07) (gcc version 4.8.3 20140401 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) ) #1ubuntu1~ci+141022120835 SMP PREEMPT Wed Oct 22 12:09:19 UTC 20
[    0.000000] CPU: AArch64 Processor [411fd070] revision 0
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] Memory limited to 1024MB
...
Last login: Wed Nov 19 17:16:22 UTC 2014 on tty1
root@genericarmv8:~#
(Maybe you're wondering, what about fedora images? They are a bit different, since they expect to run with UEFI. I'll blog about that soon once I finish some testing)
Fedora Infrastructure Freeze for Fedora 21

Yesterday, Fedora Infrastructure went into “freeze”. This happens at the same time in the Fedora release cycle as the development freezes.

First, what is a ‘freeze’? We mark all our hosts (with ansible variables) as either freezing or non freezing. Hosts are assumed to freeze unless they specifically are marked non freezing. If a host is non freezing, there’s no change for it. We could update it’s configuration in puppet or ansible, reinstall it, apply updates, reboot it, whatever we normally would like to do with it. However, if the host is frozen, we have to follow a new process to make any changes on it: A patch or description of the change has to be mailed to the fedora infrastructure list and get two people to approve it that are in the sysadmin-main or releng groups.

Why do we do this? It’s to make sure that we don’t make any changes that could possibly impact the upcoming immanent release. For example, if we updated a compose machine and caused it to no longer be able to compose release candidates, the release might be delayed. Or we changed some configuration on the download servers that broke people’s ability to download and sync new releases or test composes. We want to make sure everything is very stable to build, compose, test and distribute the upcoming release.

Freezes have some other advantages as well, at least for me. They allow us to work on things we sometimes don’t have time for, like documentation, or testing new versions of things, or investigating how better to setup existing things, or staging setup, or logs that we don’t often get to read, the list goes on.

A response to Infoworld’s confusing article about Fedora

Working with the Fedora community is something I really enjoy in my spare time and I was baffled by a article I saw in Infoworld earlier last week. Here’s a link:

The article dives into the productization of Fedora 21 that hopes to deliver a better experience for workstation, server, and cloud users. The article suggests that Red Hat drove Fedora development and that the goals of Red Hat and Fedora are closely aligned.

That couldn’t be further from the truth.

I was heavily involved with the changes as a Fedora board member in 2013 and we had many lively discussions about which products should be offered, the use cases for each, and how development would proceed for each product. FESCo and the working groups trudged through the process and worked diligently to ensure that users and developers weren’t alienated by the process. It was impressive to see so many people from different countries, companies and skill levels come together and change the direction of the project into a more modern form.

Some of those board members, FESCo members, and working group members worked for Red Hat at the time. Based on the discussions, it was obvious to me that these community members wanted to make changes to improve the project based on their own personal desires. I never heard a mention of “Red Hat wants to do…” or “this doesn’t align with <red hat="Hat" product="product">…” during any part of the process. It was entirely community driven.

Some projects and products from Fedora eventually make it into the Red Hat product list (Red Hat Atomic is an example) but that usually involves Red Hat bringing a community effort under their umbrella and adding formal processes so they can offer it to their customers (and support it).

Fedora’s community is vibrant, independent, and welcoming. If anyone is ever confused by the actions of the community, there are many great ways to join the community and learn more.

The post A response to Infoworld’s confusing article about Fedora appeared first on major.io.

encoding module moved to a separate package
Fedora 21 Release Party Phnom Penh

As you are all aware that Phnom Penh is the first country who had kicked off F21 Release Party and it was the first for us to organize it.

Fedora 21 Release Party was fun and fruitful event, which we had our Ambassadors from another 4 countries such as gnokii, Danishka, Tuanta, Izhar and Siddhesh. There were about 40+ people attended the release party and enjoyed our talks on the following topics:

  1. Introduction to Fedora – Somvannda
  2. Fedora.Next – Tuanta
  3. Fedora Features – Botrey Nisa
  4. How to contribute to Fedora – gnokii

Before giving a talk, we had blown our Fedora 21 Cake with 21 candles by all the Ambassadors.

IMG_0217

IMG_0229

IMG_0234The cake was cut and shared to all the participants.

Each Ambassador gave a talk on the topics described above. And there many questions were asked as the following:

  1. How long does Fedora providing support?
  2. Will Fedora be on Mobile?
  3. How many release does Fedora do per year?
  4. How to be in a Translation team?
  5. Is there any technical skill needed to become a Fedora contributor?
  6. etc…

Reflecting to these questions, each Fedora Ambassador attended there were responded well to audiences, and as Fedora Ambassadors for Cambodia, Botrey nisa and somvannda will step another step to enlarge the Fedora community and get more contributors regarding our mission is to lead the advancement of open source and freedom.

After the talks, we had a group photos with all the Ambassadors and audiences, especially, Greta Greathouse who had helped us on moral, motivation and budget support to have our party gone smooth.

10733719_10205352153751224_9128108052074413462_oThen we had a great party afterward.


FAD APAC 2014

FAD APAC 2014, the first of its kind eneded already 3 days ago and I was not enabled to write an report until yet, as I am still in Phnom Penh and have each day a workload to do, with giving workshops, talks and meetings. But now its the time, Siddesh has already pushed out for each day ( day 0, 1 and 2) a nice summary, what things we have done. But here a short summary:

Day 1: this day, we started with me giving an overview as an outsider what I see are the problems of the APAC regions and then everybody had the opportunity to give us an inside view to his country. The rest of the day we spent with planning the budget for next year. I putted together with the help of other people an “asian event” page in our wiki, which we used to plan the budget. It was really a lot of work and the day ended really late, we stood in the DAI offices until past 7pm. So we was really late for dinner, which was definitely nice – to sad for me, to much fish and seafood.

Day 2: We used this day to finish the work on the event planning and then moved over to more problematic topics like production of swag. Thats a little bit more complicated here as I am used to in EMEA, but there is room for improvements, so we talked about the really needed swag, which should be easily accessible for the Ambassadors in the APAC region and how to produce it with good and acceptable prices, we also had to talk about how we deal with the reimbursements for some Ambassadors as transaction fees are to high, I think Siddesh explained it very well in one of his posts, the money value is here in a lot of countries another one, take Cambodia e.g. We came up with some ideas where we can improve but mainly they have to improve there organization how to deal with the costs.

I think this FAD was definitely progress for the APAC Ambassadors and we will see what it brings in the future. But we suceeded not only with the topics of FAD, we had also another thing. As I was here in February/March and gave some talks and awarded gifts for questions the session chair wanted to award some things to people who was Fedora Ambassadors. Why the was not visible as such ones, no Fedora shirt! There was several attempts to produce the same Fedora Ambassadors Shirts as we have in EMEA but it never progressed, but now its done. All the participants took home the shirts for the Ambassadors in their countries, with the list we have we already equipped 40% of the Ambassadors we have with an shirt. For the rest, well if we would know there size……. But look for the anouncement in the next APAC meeting.

We really have to say a BIG thank you for this really great support from Greta Greathouse from Development Innovations Cambodia, for hosting us, we enjoyed really being your guests.

Blogging again - two package updates
Let's see how regular in blogging I am this time around!

Kevin pushed Xfdesktop-4.10.3 update to rawhide and F21 yesterday (or was it Sunday?). I have built the update for Fedora 20 and have pushed the same. 

Leave some karma, please! :)


In the EPEL world, I have pushed gparted-0.19.1 as an update for EL-6. Although this is a major version update, this version fixes lots of serious bugs and the upstream devel opened a bug listing all the bugs fixed! So, I have submitted this update with karma threshold of 7. Hopefully, this will be tested thoroughly.


 

November 18, 2014

Booting Fedora 21 ARM with QEMU and U-Boot
Running Fedora ARM with qemu is a bit of a pain because you need to pull the kernel and initrd out of the disk image and manually pass them to qemu; you can't just point qemu at the disk image and expect it to boot. The latter is how x86 qemu handles it (via a bundles seabios build).

On physical arm hardware, the bit that typically handles fetching the kernel/initrd from disk is U-Boot. However there are no U-Boot builds shipped with qemu for us to take advantage of.

Well that's changed a bit now. I was talking to Gerd about this at KVM Forum last month, and after some tinkering he got a working U-Boot build for the Versatile Express board that qemu emulates.

Steps to use it:
  • Grab a Fedora 21 ARM image (I used the F21 beta 'Minimal' image from here)
  • Enable Gerd's upstream firmware repo
  • Install u-boot.git-arm (this just installs some binaries in /usr/share, doesn't mess with any host boot config)
To use it with libvirt, you can do:

sudo virt-install --name f21-arm-a9-uboot \
--ram 512 \
--arch armv7l --machine vexpress-a9 \
--os-variant fedora21 \
--boot kernel=/usr/share/u-boot.git/arm/vexpress-a9/u-boot \
--disk Fedora-Minimal-armhfp-21_Beta-1-sda.raw

For straight QEMU, you can do:

qemu-system-arm -machine vexpress-a9
-m 512 \
-nographic \
-kernel /usr/share/u-boot.git/arm/vexpress-a9/u-boot \
-sd Fedora-Minimal-armhfp-21_Beta-1-sda.raw
Server Working Group Weekly Meeting Minutes (2014-11-18)

<html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-type"/>
<style type="text/css">/* This is for the .html in the HTML2 writer */body { font-family: Helvetica, sans-serif; font-size:14px;}h1 { text-align: center;}a { color:navy; text-decoration: none; border-bottom:1px dotted navy;}a:hover { text-decoration:none; border-bottom: 0; color:#0000B9;}hr { border: 1px solid #ccc;}/* The (nick, time) item pairs, and other body text things. */.details { font-size: 12px; font-weight:bold;}/* The 'AGREED:', 'IDEA', etc, prefix to lines. */.itemtype { font-style: normal; /* un-italics it */ font-weight: bold;}/* Example: change single item types. Capitalized command name./* .TOPIC { color:navy; } *//* .AGREED { color:lime; } */</style>

</head><body>

#fedora-meeting-1: Server Working Group Weekly Meeting (2014-11-18)

Meeting started by sgallagh at 16:03:13 UTC(full logs).

Meeting summary

  1. roll call (sgallagh, 16:03:19)
  2. Agenda (sgallagh, 16:05:44)
    1. Agenda Item: Approval of the Final Criteria (sgallagh, 16:06:11)
    2. Agenda Item: Status check as we enter Final Freeze (sgallagh, 16:06:17)
    3. Agenda Item: Fedora 22 Planning – GUI (sgallagh, 16:06:26)
    4. Agenda Item: Fedora 22 Planning – Roles (sgallagh, 16:06:30)

  3. Approval of the Final Criteria (sgallagh, 16:08:26)
    1. https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html (sgallagh, 16:08:49)
    2. Adjusted text: “* Enrolled clients must be capable of authenticating against a valid user account using SSSD’s ‘ipa’ provider.” (sgallagh, 16:15:20)
    3. AGREED: Draft Criteria approved and will be submitted to QA for inclusion. (+5, 0, -0) (sgallagh, 16:19:30)

  4. Status check as we enter Final Freeze (sgallagh, 16:19:39)
    1. simo notes that there are several potential blocker issues in FreeIPA. (sgallagh, 16:33:11)
    2. ACTION: simo to propose blockers and freeze exceptions for FreeIPA issues (sgallagh, 16:33:26)
    3. Cockpit needs a branding update. We will propose it as a Freeze Exception and not a blocker. (sgallagh, 16:33:53)
    4. rolekit is good to go for F21 Final (sgallagh, 16:37:53)
    5. Branding issues for all of the products are still being sorted, but should be in their final phases now. (sgallagh, 16:38:25)
    6. Fedora Server brochure page looking good; remaining piece is in the Websites team’s hands. (sgallagh, 16:39:50)
    7. https://git.fedorahosted.org/cgit/fedora-web.git/tree/getfedora.org/data/content/server/index.html?h=getfedora (nirik, 16:41:30)

  5. Fedora 22 Planning – GUI (sgallagh, 16:43:16)
  6. Fedora 22 Planning – Roles (sgallagh, 16:57:25)
    1. Deferred until next week (sgallagh, 16:57:30)

  7. Open Floor (sgallagh, 16:57:36)

Meeting ended at 16:59:04 UTC(full logs).

Action items

  1. simo to propose blockers and freeze exceptions for FreeIPA issues

Action items, by person

  1. simo
    1. simo to propose blockers and freeze exceptions for FreeIPA issues

People present (lines said)

  1. sgallagh (91)
  2. simo (38)
  3. stefw (32)
  4. nirik (30)
  5. danofsatx-work (24)
  6. junland (17)
  7. mitr (15)
  8. zodbot (3)
  9. adamw (0)
  10. tuanta (0)
  11. davidstrauss (0)
  12. mizmo (0)

Generated by MeetBot 0.1.4.</body></html>

LISA’14 – Are We Making Linux Too Easy?

LISA’14, the Large Installation System Administration conference, was held in Seattle last week. I had the opportunity to give a talk on Server Management – if you are interested, the slides are available here.

One of the questions caught me completely off guard: “Aren’t you afraid that you are making system management too simple and that people won’t learn how to really manage Linux? They will just learn a few simple commands and not go any further. Today, they have to learn how Linux works and how to solve problems. OpenLMI will leave them unprepared.”

Wow… Where to start?

Thinking about this further, it could happen. In fact it will happen! Many people are looking for the quickest fix to a problem – a common way of working is to Google what you need, find something that looks like it should work, try a quick cut and paste, and move on.

OpenLMI is designed to support this. The LMI CLI is task oriented, simple, and easy to use. All you really need to use the LMI CLI is “LMI help”. The LMIShell scripts are designed to do useful work, to be easy to read, and to be modified for specific tasks.

If someone is simply looking for a way to perform a specific task, use it, and move on the the next problem, OpenLMI is a good way to go. You can use OpenLMI at a shallow level, even use it to avoid having to learn how Linux really works.

On the other hand, OpenLMI can also be used to ease into a deep knowledge of Linux: Start with the LMI CLI and use it to perform tasks. Move into LMIShell and start using and developing scripts. From there it is straightforward to develop custom automation tools. You have several ways to dive deeper into Linux administration, perhaps even developing custom OpenLMI Providers.

I would suggest that OpenLMI makes Linux more approachable. Some people will only use OpenLMI, and will never go deeper – if they can do what they need to do, this seems like a reasonable approach. Some people will use OpenLMI as a tool and and entry point to mastering Linux administration; this is great.

I don’t believe everyone needs to master Linux to use it. Consider the car analogy: All some people want to do is drive a car – automatic transmissions are perfect for them. Some people want to be able to do light repairs such as oil changes. Some want to rebuild engines and repair major subsystems of the car. And some people want to design the eight speed computer controlled automatic transmissions that are part of the integrated drive train of modern cars!

What do you think? Do we face a real risk of making Linux “too easy”, or should we try to make Linux more approachable?


Some feeds I like

ok, it’s day 18 of the post a blog every day challenge and I am stretching I know, but perhaps some of you will find these feeds/blogs as entertaining as I do:

  • popehat – http://www.popehat.com/feed – a blog done by some very articulate lawyers. I like how they manage to explain things so non legal eagles can understand. I also tend to agree with them on free speech issues and the like. Their posts are usually entertaining and enlightening.
  • bad astronomy – http://www.slate.com/blogs/bad_astronomy.fulltext.all.10.rss/ – Contrary to it’s name, this is GOOD astronomy. Lots of nice discussion about current events in astronomy and explaining how things work. It’s really quite fascinating.
  • Russel Corkers blog – http://etbe.coker.com.au/feed/ – In particular his ‘interesting links for the month’ have resulted in some great videos or things I would otherwise have missed.
  • Linux Weekly News – http://lwn.net/headlines/newrss – Not just weekly, but daily feed of happenings in the Linux world. If you aren’t a subscriber, go and subscribe now!
  • National Geographic Found Photos – http://natgeofound.tumblr.com/rss/ – A mix of photos from the National Geographic Society. Sometimes there’s some quite striking ones that come accross the feed. Many from long years past, black and white, color, everything.

There’s more, but I will leave it at those. Hope some folks find them interesting…

syslog-ng OSE 3.6.1 packages
Recently many people asked me in public and private about syslog-ng 3.6.1 packages. As usual, BalaBit does not provide official binary packages for syslog-ng Open Source Edition, only sources. Of course, this does not mean that packages are not available from third parties (often with the help of BalaBit employees). Here is the current state […]
Facebook At Work - new secret project of Facebook.
If you will be on work then you will test the new facebook with with your co-workers.
Over 8,348 facebook employees working now to test and develop the new facebook project.
Read more about this here.
Automation – a Security Imperative

So far we have established:

  • Security Guides are a good idea and exist in almost all organizations.
  • Security audits are good and widely used.
  • Security guides are often poorly written, subject to interpretation, and difficult to apply.
  • Security audits are expensive and not performed as often as they should be.

Hmmm…. Well, computers are good at following rules and measuring things. And if security guide rules are precise enough to be implemented and measured, they are very close to what you need to create a computer program.

The obvious next step is to create computer programs to implement security rules and perform computer audits!

In fact, this is what has been done for years. Numerous programs have been written for security, many security capabilities are built into operating systems, and scripts to configure systems are widely used.

However: security at the enterprise level is a big, complex undertaking.

You need a large investment in tracking threats as they emerge. It would be terribly convenient if there were a standard way to talk about threats – for example, the first 6 people who identify a new computer virus are going to call it different things, unless something is done to create a standard definition.

The vast majority of computer security issues are quickly fixed after they are identified. Decades of experience show that most computer intrusions can be prevented by applying existing patches. The question is what patches need to be applied to each specific system? This is a more complex question than it appears to be – few organizations automatically apply all patches to all systems. Instead, they test patches and carefully apply specific patches to specific systems.

The challenge is knowing which patches have been applied, which patches are available, and which patches are needed for each system. What is the risk addressed by each patch, what is the impact, and how relevant is the exposure?

Creating a useful set of security rules is a huge undertaking. If each organization is 90% common with other organizations and 10% unique, it is incredibly wasteful for each organization to build 100% of the security rules themselves.

And enterprise systems are complex. You need a workflow and extensible frameworks to be able to effectively secure, manage and monitor them.

All of these things call out for an industry wide initiative to build a standard foundation for automating security.


Spark performance talk at ApacheCon EU

I’ll be speaking later this afternoon at ApacheCon EU. The title of my talk is “Iteratively Improving Spark Application Performance.” The great thing about Apache Spark is that simple prototype applications are very easy to develop, and even a first attempt at realizing a new analysis will usually work well enough so that it’s not frustrating to evaluate it on real data. However, simple prototypes can often exhibit performance problems that aren’t obvious until you know where to look.

In this talk, we’ll introduce Spark’s execution model and discuss how to use Spark effectively. I’ll use a prototype implementation of my bike data analytics application as a running example and will present four general principles to keep in mind when writing efficient Spark applications, complete with detailed code explanations. My slides are available here as a PDF.

If you’re interested in more detail about the bike data analytics application, you can watch a brief video demo or watch a video of my talk about this application from Spark Summit earlier this year. Finally, I’ve published a blog post covering similar principles for improving Spark applications, which will be a useful reference whether or not you’re able to attend the talk.1

If you’re also at ApacheCon today, I hope to see you at 15:50 CET!


  1. The talk will feature visual explanations and other material that are not in that post, but the post has links to full code examples suitable for off-line experimentation.

FUELGILT 2014 conference and my activities
Last weekend i was fully involved in fuel conference. Lots of things i can share about the conference. Let me first start with my role in it.

1.  Representing Fedora @ conference.
2. My talk about "Why Globalization? world wide picture"
3. Celebrating 10 yrs of Lohit project and workshop on Lohit2.

1. Represented Fedora @ conference.

    We started planning for this event with Fedora Ambassador group well 2 months in advance and designed T-shirts for branding Fedora as a best platform for Language computing. This T-shirt was distributed to all active contributors to promote message Fedora perfect from language computing perspective. Most of them were available in conference wearing this T-shirt, it truly made people aware regarding yes Fedora takes care for language computing aspects and proud for same.


    I met number of people in conference and talked on how can Fedora help them. Specifically mentioned language team is very active in Fedora, most of the innovations happened first in Fedora including IBus, Harfbuzz and Updates regarding Fonts also gets in quickly in Fedora. Fedora i18n team weekly meets AT #fedora-meeting on Tuesday  06:00:00 to 07:00:00 UTC and discuss open issues.

    Analysed issues mentioned by ShivaKumar K.M  regarding corpus processing and requested Biraj Karmakar  to test Fedora 21 for Bengali and provide some report.

    Parag given talk on "How to create hunspell dictionary on Fedora". It was very well attended talk from audience. They learned practically on how to make hunspell dictionary from simple word-list and see it working. It increased there interest on hunspell dictionary. I talked with Omshivaprakash and he suggested it is possible to get some online tool for maintaining hunspell. This is the same thought we were thinking from last couple of months also discussed same with Libreoffice Caolan. Already some work has been done and soon will publish same.


    Parag also demonstrated wordxtr package avaialable in Fedora. He demonstrated it with html page and shown how quickly one can extract words with it.

    Wanted to distribute some Fedora stickers but somehow missed to collect some from Siddhesh before he moves to Phnom Penh, Cambodia for FAD.

    Discussed with Arky about how much language support Firefox OS does has and they also facing same issues which we were face some years back. In Fedora now we have nicely written criteria for language support. I mentioned him, link is here :)


    Event page for FUELGILT 2014 conference

    Overall i am happy with the presence of the Fedora in this conference. Will improve it further in upcoming conference around Language Technology.

    I would like to thanks here Rajesh, Chandrakant and Ankit for supporting activities around Fedora in this conference.

2. My talk about "Why Globalization? world wide picture"

    This was the first talk on second day. We got pleasing but unexpected rain that day. It delayed most of things. Since i was the first speaker most of the arrangements for speakers happened that time. Started talk around 10:15am.


    Its tricky subject to present. In this talk i targeted the users. Mentioned the importance of supporting not only major language of world but also as much as possible on platform. How it is important to preserve first languages of people. I have mentioned couple of important research that has been done to showcase how persons first language is very important. Also how first language can help for effective branding of products.

    Slides are available At slideshare Soon we will have youtube video for my talk.
   
3. Celebrating Lohit 10 yrs of Lohit project and workshop on Lohit2.

    This is moment i was waiting for long time. Though number of plans were there. We decided we will celebrate with cake in conference like FULEGILT where number of open source contributors and users get together.

    Cake arrived on time and we just thought lets start workshop by cutting it.
    Audience suggested Shilpa (present actively working on lohit2), Rahul Bhalerao (past maintainer of Lohit) and me to cut cake together.


    Later we had small presentation on Lohit 10 years. In this presentation Shilpa explained why Lohit project is important, What are the achievement of Lohit project in 10 years and what is plan for future through lohit2 project.

    Already big blog, will write one more to mention things happened in conference. Photo credits to Krishnababu and Bhushan :)
F21 Atomic Test Day && Test steps for Atomic Host
<! F21 Atomic Test Day && Test steps for Atomic Host>

Test Day on Thursday 11/20

The F21 test day for atomic is this Thursday, November 20th. If anyone can participate please do drop into #atomic on freenode as it will be great to have more people involved in helping build/test this new technology.

In anticipation of the test day I have put together some test notes for other people to follow in hopes that it will help smooth things along.

Booting with cloud-init

First step is to start an atomic host using any method/cloud provider you like. For me I decided to use openstack since I have Juno running on F21 here in my apartment. I used this user-data for the atomic host:

#cloud-config password: passw0rd chpasswd: { expire: False } ssh_pwauth: True runcmd: - [ sh, -c, 'echo -e "ROOT_SIZE=4G\nDATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup']

Note that the build of atomic I used for this testing resides here

Verifying docker-storage-setup

docker-storage-setup is a service that can be used to configure the storage configuration for docker in different ways on instance bringup. Notice in the user-data above that I decided to set config variables for docker-storage-setup. They basically mean that I want to resize my atomicos/root LV to 4G and I want to create an atomicos/docker-data LV and make it 10G in size.

To verify the storage was set up successfully, log in (as the fedora user) and become root (usind sudo su -). Now you can check if docker-storage-setup worked by checking the logs as well as looking at the output from lsblk:

# journalctl -o cat --unit docker-storage-setup.service CHANGED: partition=2 start=411648 old: size=12171264 end=12582912 new: size=41531232,end=41942880 Physical volume "/dev/vda2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Size of logical volume atomicos/root changed from 1.95 GiB (500 extents) to 4.00 GiB (1024 extents). Logical volume root successfully resized Rounding up size to full physical extent 24.00 MiB Logical volume "docker-meta" created Logical volume "docker-data" created # # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 20G 0 disk ├─vda1 252:1 0 200M 0 part /boot └─vda2 252:2 0 19.8G 0 part ├─atomicos-root 253:0 0 4G 0 lvm /sysroot ├─atomicos-docker--meta 253:1 0 24M 0 lvm └─atomicos-docker--data 253:2 0 10G 0 lvm

Verifying Docker Lifecycle

To verify Docker runs fine on the atomic host we will perform a simple run of the busybox docker image. This will contact the docker hub, pull down the image, and run /bin/true:

# docker run -it --rm busybox true && echo "PASS" || echo "FAIL" Unable to find image 'busybox' locally Pulling repository busybox e72ac664f4f0: Download complete 511136ea3c5a: Download complete df7546f9f060: Download complete e433a6c5b276: Download complete PASS

After the Docker daemon has started the LVs that were created by docker-storage-setup will be used by device mapper as shown in the lsblk output below:

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 20G 0 disk ├─vda1 252:1 0 200M 0 part /boot └─vda2 252:2 0 19.8G 0 part ├─atomicos-root 253:0 0 4G 0 lvm /sysroot ├─atomicos-docker--meta 253:1 0 24M 0 lvm │ └─docker-253:0-6298462-pool 253:3 0 10G 0 dm │ └─docker-253:0-6298462-base 253:4 0 10G 0 dm └─atomicos-docker--data 253:2 0 10G 0 lvm └─docker-253:0-6298462-pool 253:3 0 10G 0 dm └─docker-253:0-6298462-base 253:4 0 10G 0 dm

Atomic Host: Upgrade

Now on to an atomic upgrade. First let's check what commit we are currently at and store a file in /etc/file1 to save it for us:

# rpm-ostree status TIMESTAMP (UTC) ID OSNAME REFSPEC * 2014-11-12 22:28:04 1877f1fa64 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # ostree admin status * fedora-atomic-host 1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84.0 origin refspec: fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # cat /ostree/repo/refs/heads/ostree/0/1/0 1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84 # # cat /ostree/repo/refs/heads/ostree/0/1/0 > /etc/file1

Now run an upgrade to the latest atomic compose:

# rpm-ostree upgrade Updating from: fedora-atomic:fedora-atomic/f21/x86_64/docker-host 14 metadata, 19 content objects fetched; 33027 KiB transferred in 16 seconds Copying /etc changes: 26 modified, 4 removed, 39 added Transaction complete; bootconfig swap: yes deployment count change: 1) Updates prepared for next boot; run "systemctl reboot" to start a reboot

And do a bit of poking around right before we reboot:

# rpm-ostree status TIMESTAMP (UTC) ID OSNAME REFSPEC 2014-11-13 10:52:06 18e02c4166 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host * 2014-11-12 22:28:04 1877f1fa64 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # ostree admin status fedora-atomic-host 18e02c41666ef5f426bc43d01c4ce1b7ffc0611e993876cf332600e2ad8aa7c0.0 origin refspec: fedora-atomic:fedora-atomic/f21/x86_64/docker-host * fedora-atomic-host 1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84.0 origin refspec: fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # reboot

Note that the * in the above output indicates which tree is currently booted.

After reboot now the new tree should be booted. Let's check things out and make /etc/file2 with our new commit hash in it:

# rpm-ostree status TIMESTAMP (UTC) ID OSNAME REFSPEC * 2014-11-13 10:52:06 18e02c4166 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host 2014-11-12 22:28:04 1877f1fa64 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # ostree admin status * fedora-atomic-host 18e02c41666ef5f426bc43d01c4ce1b7ffc0611e993876cf332600e2ad8aa7c0.0 origin refspec: fedora-atomic:fedora-atomic/f21/x86_64/docker-host fedora-atomic-host 1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84.0 origin refspec: fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # cat /ostree/repo/refs/heads/ostree/1/1/0 18e02c41666ef5f426bc43d01c4ce1b7ffc0611e993876cf332600e2ad8aa7c0 # # cat /ostree/repo/refs/heads/ostree/1/1/0 > /etc/file2

As one final item let's boot up a docker container to make sure things still work there:

# docker run -it --rm busybox true && echo "PASS" || echo "FAIL" PASS

Atomic Host: Rollback

Atomic host provides the ability to revert to the previous working tree if things go awry with the new tree. Lets revert our upgrade now and make sure things still work:

# rpm-ostree rollback Moving '1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84.0' to be first deployment Transaction complete; bootconfig swap: yes deployment count change: 0) Sucessfully reset deployment order; run "systemctl reboot" to start a reboot # # rpm-ostree status TIMESTAMP (UTC) ID OSNAME REFSPEC 2014-11-12 22:28:04 1877f1fa64 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host * 2014-11-13 10:52:06 18e02c4166 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # reboot

After reboot:

# rpm-ostree status TIMESTAMP (UTC) ID OSNAME REFSPEC * 2014-11-12 22:28:04 1877f1fa64 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host 2014-11-13 10:52:06 18e02c4166 fedora-atomic-host fedora-atomic:fedora-atomic/f21/x86_64/docker-host # # cat /etc/file1 1877f1fa64be8bec8adcd43de6bd4b5c39849ec7842c07a6d4c2c2033651cd84 # cat /etc/file2 cat: /etc/file2: No such file or directory

Notice that /etc/file2 did not exist until after the upgrade so it did not persist during the rollback.

And the final item on the list is to make sure Docker still works:

# docker run -it --rm busybox true && echo "PASS" || echo "FAIL" PASS

Anddd Boom.. You have just put atomic through some paces.

Mozilla’s new ad feature

Edited to remove erroneous statements about what gets sent to Mozilla based on Matthew Miller’s comment below.

Mozilla’s release last week of in-browser ads has caused quite the discussion on the Fedora development mailing list. Firefox now will show sponsored “tiles” on the default home screen when a new or cleared profile is used. Although Mozilla claims to collect data in such a way that it’s not personally identifiable, there are reasons to be concerned. Sure, this can be disabled, but the default behavior is the only thing most users will experience.

The reactions on Fedora-devel spanned the gamut from indifference to insistence that Firefox be removed from the repository entirely. My own take (which was already represented on the mailing list, so I refrained from “me too”-ing) is that the right answer is to disable this feature in the Firefox build that ships in Fedora, effectively making it opt-in instead of opt-out. Mozilla has a history of being a good actor and I don’t begrudge them trying to make some money. However, I’d prefer that the user have to consciously enable such tracking.

Though I disapprove of the implementation, I find it hard to get very worked up about this. The Internet is awash in tracking. Google and Facebook probably know more about me than I do about myself. But that’s because I decided the value I get from those sites (well, not so much Facebook) is worth the data I give them. I respect the right of others to come to their own decision, which is why opt-in is preferred.

I appreciate the opinion of those who think the only appropriate response is to remove Firefox entirely, but I find that to be a wholly impractical solution. If Fedora wants casual desktop users (and I see no reason to not court that use case), having Firefox is and important part of a welcoming environment. A great deal of casual computing is done in the browser these days and Firefox is a well-known browser (even if some people call it “Foxfire”). Sure, there are other FLOSS browsers (including IceWeasel), but few of them work as well for casual users as Firefox and none of them have the familiarity and name recognition. Given the good Mozilla has done for free software over the years, this hardly seems like a bridge worth burning.

Fedora comes to University - Coimbatore Contribution Camp Report

At my University in Coimbatore, we run a tech{know}logy club, where we try to talk about interesting things in technology that normally isn’t covered in the classroom. We had a set of freshers join our club in August through the induction program. On Software Freedom Day in September, they were introduced to the idea of FOSS, open source communities and how it’s possible to contribute to them. When I went to Hanoi for our Ambassadors meeting, I decided to host a contribution camp in Uni sometime this year. Here’s the wikipage which has all the essential bits.

Background week

My friend Manjush and awesome (fresher) junior Sachin did a great job gathering a bunch of interested freshers and other students in our digital library for a half week before the camp took place. On the first day, they helped with installing Fedora (and other distributions of choice) onto the participants’ computers. They spent another day explaining what packages are and helping install the important ones. I showed up for the last two days and helped with Git and Jekyll.

Day One - Thursday

All of us agreed that the best way to motivate folks towards the camp was to screen a movie at our Auditorium. We were expecting 70, but were delighted to be able to host 180 students for Internet’s Own Boy: The Story of Aaron Swartz .

Movie Screening Poster, courtesy Anirudh Menon

For those initiated to the world of Free Software, the Startup Community, and DRM oriented arguments, the movie was a reminder of Swartz and the role he played in shaping part of our world. For the rest, they got to hear about terminologies, ideas and people they could later go and Google. Overall, the silence in the hall towards the end of the movie touched me. We invited everyone to join us for Day Two, and many did.

Day Two - Friday

We wanted to be less theoretic, so we structured our sessions that way. We expected 40 people, 45 showed up. I think if not for Google Club’s mindless discussion about landing jobs by marketing Google products, we would have had a larger attendance. Abhishek Ahuja started the day, speaking about FOSS in general - what it is, why bother, how it affects him. He followed it up with FOSS alternatives to popular software.

Ahuja talking about an interesting GIMP plugin he once discovered Sachin went next, he provided a rather neat introduction to the popular GNU/Linux distributions and the history/community behind them. One interesting thing he did was talk about desktop environments - something people get to hear about often but don’t really understand. From what I could understand, the audience was confusing distributions and desktop environments.

Sachin presenting various desktop environments

I’m actually quite proud of those who attended - the sessions were held after class because we didn’t have much choice, and it’s tiring for freshers who have to wake up early for Yoga classes and walk all the way to our session hall. I didn’t want them to sit and listen to us in hunger, so I arranged for snacks with the money I had asked Tuan to allocate for this event. Anyway, after a quick break, we were back to the sessions.

I’ve seen Manjush try the most distributions, so we had him speak about his timeline of the various GNU/Linux distributions he tried. At least to me who’s spent enough time doing tech support for my peers with respect to installing distributions, it was an entertaining talk. He spoke about problems with installation, problems with lack of language support, problems with community, problems with bundled software, problems with licenses and every other kind of problem one can think of. I was proud when he said he eventually settled on Fedora since it gave him everything he wanted.

Manjush talking about his difficulties with distributions he previously used

I did the last session: Fedora A-Z Guide (partially due to time constraints). Now our University provides us with some hurdles: fresher’s don’t get to use laptops, lab usage is fairly restricted, and girls can’t hang out past 7.30pm (after which anything we want to do happens). So I tried to pick up the non-technical bunch of areas, or areas with less technical intensity, while making sure they have the opportunity to participate over their smartphone. I explained how Wikipedia is everyone’s encyclopaedia, and how they can host their own. Through this, I tried to excite them about the power of a collaborative community, and how they can start contributing with whatever existing skill they have. Some students seem to have gone back home and edited few Wikipedia pages as well :)

Yours truly running through the A-Z guide

Day Three - Monday

Come final day and we had a new set of faces. The attendance was 40. The demand seemed to be the Fedora A-Z guide, so I went over it once more, this time talking about fewer topics, but with more depth. For example, I showed them the badges project, traced a badge to the trac and showed them how the badges are designed and how they evolve. That seems to have gotten them pretty amused, because I met at least 3 people who said they’d like to contribute to badges.

Next up, I went over the hands-on bits from my FOSS 101 workshop at FOSSASIA Phnom Penh and SFD Hanoi. We had a brief look at Fedora and Mozilla’s contribute pages, OpenHatch and CodeTriage. I explained how we communicate - mailing lists, blogs, issue pages, IRC. I explained ettiquettes to follow when one is interacting with a community. It looked like a lot of people related with the usage of SMS lingo and hyper-exclamations (sigh, teens) - I got to see a lot of giggling and smiling around.

Good Procrastination and Bad Procrastination

After the usual snack break, it was time for my final presentation. When I asked a faculty for feedback on Day Two, he felt we were getting a little too technical for the freshers, and that we should do a funny/inspiring session. So I did one called “Good Nervous and Bad Nervous”, and it pretty much rocked :) I brought up lots of experiences from my personal life, what I learned from little things my friends in the Fedora and FOSS community taught me through their words and actions. I look forward to polish it and do the talk again sometime, or maybe even blog it.

So.. that’s the most of our camp, and we’re meeting again this evening to help people with any problems they have in getting started. I’ll be running a survey for the attendees later this week, and if the results seem interesting, I’ll share it.

Closing Notes & Thanks

  1. Although I’m excited about the enthusiasm everyone displayed, I wish the overall technical aptitude of the attendees was higher. I have another semester left here, I’ll try my best to fix that.
  2. I’ve started a reimbursement request on the apac trac (#161) for the food - I’ll upload bills and supply reports today.
  3. I’ve run out of swag now, so I need to figure out something before my Fedora Project workshops at IIT Madras in early Jan
  4. Thanks to: Manjush who kickstarted the sessions, the week prior to the camp. Sachin, our wizard first year who helped out pretty much everywhere. Proud of you! The University, for not making the permission process too much of a hassle to me. Everyone who attended, spoke or blogged.

November 17, 2014

Fedora 21 Atomic Test Day: this Thursday!

Instead of trying to come up with a clever play on “Atomic” for the headline and lede here, let’s just go with the facts. The facts: The Cloud Working Group is doing a test day for Fedora 21 Atomic on Thursday, November 20th. We think thinks are coming along nicely, but – hey – we need your help to put Fedora 21 Atomic through its paces.

More facts: We’re going to be in the #atomic channel on Freenode all day (give or take) and (as always) will be looking for questions to the cloud@lists.fedoraproject.org mailing list. Dusty Mabe has some great test steps for Project Atomic and we’ll be adding more before Thursday.

You can find the latest qcow2 image on Koji. Want to get a jump on things? We don’t mind! If Thursday doesn’t work for you, jump right on it and shoot us your results. Run your favorite Docker images, try out Kubernetes, give Cockpit a workout – the whole kit and caboodle.

Other questions about Fedora 21 Atomic or cloud? Find us in the #atomic and/or #fedora-cloud channels on Freenode, or hit us up at cloud@lists.fedoraproject.org.

Council Elections Interview with Pete Travis (randomuser)

This is a part of Fedora Council Elections interviews series. This is an important election, as two candidates will be selected as the Elected Representives, seats which carry full membership in our new top-level leadership and governance body.

Voting is open to all Fedora contributors. The elections starts on November 18th and closes promptly at 00:00 UTC on November 26th.

Please read the responses from all five candidates and make your choices carefully:

Feel free to ask questions of the candidates here or elsewhere!

Interview with Pete Travis (randomuser)

Pete Travis on bridge

What is your background in Fedora? What have you worked on and what are
you doing now?

I started contributing to Fedora late in 2011, after using it for a few releases. I was looking to expand my expertise in administering Linux systems, and after getting a lot of help from the Fedora community, I wanted to give something back. The Docs team welcomed me into their ranks; it seemed like a good pairing for the time I was spending researching, testing, and taking notes.

Contributions to Fedora Docs began with reading through the latest drafts and providing maintenance updates, something I still do regularly. I’ve since been elected for leadership of the Docs Project, wrangled the Release Notes for the last few releases, started drafting a couple new guides, and helped keep all the guides on track with the diverse changes in each Fedora release.

I spend a fair amount of time keeping up with the Fedora community; tracking various mailing lists, helping (or getting help) in #fedora, answering questions on Ask Fedora. It is a good way to identify gaps in documentation, clarify how the project works, and track the greater community’s perception of Fedora. A number people I’ve met in these areas have moved on to being productive contributors, and I’m happy to had a role in their beginnings with the project. Within Docs, we have a semi-formal mentorship  program that has been working out well, and I participate in the Join SIG to help folks get started in other groups.

In other areas, I try to help out where my efforts overlap with other teams and make an effort to keep track of happenings within the project. I’ll generally use a prerelease or rawhide on all my machines to catch both changes required for docs, and help test packages. I have some infra privileges that generally get used for docs ventures to help keep Fedora’s sysadmins’ valuable time free. I maintain a few packages, try to follow along with Fedora’s hugely talented application developers, and sporadically speak up in meetings or on mailing lists.

Categorically, I try to keep up with everything I can, and look for opportunities to contribute.

What is your vision for Fedora? Where should we be in five years?

Fedora’s strength lies in the openness of the community, the innovations we’ve made available, and the diversity of choices available to Fedora users. The side effect of such a broad number of choices is the
difficulty in finding the right solution for one or all users.

I want to see Fedora move in a direction where the user experience is streamlined and improved, without sacrificing the limitless potential available in the distribution. To some extent, Fedora’s default deliverable is perceived as the Project’s vision of the one true path, and the dedicated maintainers of alternatives to the default need more recognition and support.

I’ve encountered many small businesses with rather specific needs, and only costly, dubiously supported proprietary solutions to meet them. Small businesses and organizations might not have special requirements, and have use cases that could easily be accommodated by free software, but they aren’t aware of it. There is a lot of opportunity for Fedora (and open source based service providers) to make headway with general business use desktops outside the enterprise, and expand offerings that
cater to industry-specific niches.

In the future, above all things, the Fedora contributor base should grow. We should focus on nurturing new contributors and enabling them to develop and work towards common goals. We should view every user as a potential contributor, and provide opportunities for participation in as many contexts as we can guide them through. Where this will take us will depend on the interests and technology of the time, but if we as leaders can keep those conversations alive and productive, I’m convinced there will be a robust, viable result.

What does it mean for Fedora to be successful? What is “winning” for our project?

I’ll be specific here: We’ve won when Fedora stops being referred to as “Desktop RHEL” or “Red Hat’s Test Bed”. Success means demonstrating that a rapid release cycle can be a sustainable thing, and that
stability doesn’t equal stagnation. We’ve won when we’ve catalyzed the open source community towards effective communication between interdependent projects, and made it possible to effectively keep up
with the new stuff without sacrificing long term usability of the distribution itself.

In many contexts, Fedora is already successful, but there’s room for improvement in demonstrating that success.

What are the most pressing issues facing Fedora today? What should we do about them?

The Fedora development community is demonstrably the most active subset of the project. There’s new Products, a constant flow of new features and changes, and steady improvement of Fedora’s security posture. While the Project is inherently developer-oriented, the rapid pace of progress leaves ancillary groups such as Documentation, QA, Translations, or support volunteers struggling to keep up. Potential contributors trying to land a place in the project are faced with a constantly moving target.

This can be remedied with more effective recruitment practices and improved communication between development and outreach communities.

What are your interests and experience outside of Fedora? What of those things will help you in this role?

Interests, let’s see… I like creating things. I build furniture in the garage and brew beer in the kitchen. I have a plan for a home that’s seen iterative and sometimes drastic improvement. I like to take things apart and see how they work, then put them together improved; cars, electronics, code, stuff. Sometimes I like to pack a bag and hike for a few days.

Life has provided a lot of interesting experience along the way. I’ve drilled for oil, managed a B2B marketing department, built houses, provided corporate IT support, repaired automobiles, consulted for small business management, and administered a variety of computer infrastructure (in no particular order).

Besides the obvious places where I’m actively using and advocating open source software for my day job, I have always taken an active interest in learning how people and organizations leverage technology. The
things I’ve learned from experience are opportunities for Fedora to gain marketshare and mindshare.

Care to share a screenshot of your Fedora desktop?

Pete Travis'es desktop screenshot

Have you used Fedora in a cloud or server context?

I’ve done testing with Fedora Cloud when working on the draft Cloud Guide. For personal use, I have Fedora behind a relatively large fileserver, a load-balancing edge router, a handful of application servers, and a whole bunch of test VMs used when writing documentation for a variety of use cases. My little testbed gained Fedora Server with the domain controller role recently, and I’m really looking forward to
exploring its potential.

What did you do on your last vacation or weekend off?

I visited a local brewery. The master brewer visited with us for a while, and a jest about cloning American lagers got an interesting response: He was positive about the idea of other brewers trying to replicate his craft, and described an perspective about the open sharing of ideas that completely paralleled Fedora’s Foundations. It was surprising to find someone that had developed an analogue of familiar open source ideals completely outside of the software context. Naturally, I’ll be introducing him to the brewing software I package on the next visit

What do you want to achieve as member of council?

Enable collaboration, enable communication, and represent contributors. I’m excited to see how the active leadership model will develop, and looking forward to being a part of the process. Fedora is a community project; it is less about what I want to achieve and more about what *you* want the Council to help you achieve. So please, speak up!

How do you envision improving collaboration with downstream communities (ie: CentOS) ?

From what I’ve seen, there’s already a good relationship between the Centos and Fedora communities. The volume and quality of communication has increased recently, a trend that will probably continue. I don’t have a specific vision for the relationship – ultimately, the nuts and bolts of collaboration between the two will be determined by the contributors doing the work in whatever area.

In general, I’m in favor of working with them when there is mutual interest, contributors from each project keeping tabs on the other, and open communication. I follow the centos-docs team, for example; not because of any top-down directive, but because sometimes I can help them and sometimes they can provide some insight for me. I could see Fedora cloud instances running on CentOS hosts as an attractive option for organizations, and a viable opportunity for collaboration.

Anything else voters should know?

This is my dog, Skoda. She heard me talk about packaging for Fedora, and wanted to get involved.

Council Elections Interview with Langdon White (langdon)

This is a part of Fedora Council Elections interviews series. This is an important election, as two candidates will be selected as the Elected Representives, seats which carry full membership in our new top-level leadership and governance body.

Voting is open to all Fedora contributors. The elections starts on November 18th and closes promptly at 00:00 UTC on November 26th.

Please read the responses from all five candidates and make your choices carefully:

Feel free to ask questions of the candidates here or elsewhere!

Interview with Langdon White (langdon)

Langdon White

What is your background in Fedora? What have you worked on and what are you doing now?

I never really got involved with a distro until the past couple years. Even though I was a Linux user, I never thought I had much to contribute to a distro because I didn’t (and don’t ) know almost anything about the practical aspects of a distro. I know a lot about programming and software architecture but not the kinds that are used when building an OS. As of now, I have been using RHEL, Fedora, and CentOS pretty much exclusively for about 2.5 years. I help out on random content, representing developers, advocating to developers, and, generally, trying to agitate for how I think Fedora can be awesome.

What is your vision for Fedora? Where should we be in five years?

I want Fedora be the de facto developer desktop. Instead of wandering around a conference (including OSS-focused ones) and seeing mac after mac, I want to see those people using Linux. In the meantime, I want developers from any platform to prefer to deploy their applications to a Fedora flavor because the tools are the best and the community is the most welcoming.

What does it mean for Fedora to be successful? What is “winning” for our project?

As the computing environment changes to embrace “alternate computing devices”, I see an opportunity for Fedora to embrace the “content creators” using the same strategies as successful startups: start with one user persona, gather metrics, and react based on the data; rinse & repeat.

Winning means, putting our pre-conceived notions aside, understanding our users (and our future users) and delivering to them a rewarding experience. I also think it means, becoming the “distro of outreach” –
the distro that wants open source projects to be successful and encourages, enables, and supports them in doing so.

What are the most pressing issues facing Fedora today? What should we do about them?

The explosion and acceptance of open source software has been awesome for the world at large, but it has been tough for Linux distros in general and Fedora in particular because of the sheer volume of technologies and the rate of change. As a result, I think significant automation is the only way to successfully scale the distro.

I also believe that all the distros have become so good that without innovation within the distro itself (vs ensuring the quality and integration of upstream projects alone), we can’t differentiate how we are better.

What are your interests and experience outside of Fedora? What of those things will help you in this role?

I have spent significant personal and professional time engaged in Machine Learning and Artificial Intelligence which provides me some unique ideas on increased automation.

I have spent a long time as a professional developer, architect, and development manager in very high caliber and high pressure environments. However, most of that work has been in 3-tier/n-tier architectures (vs operating systems) which I think gives me a different perspective on how we can approach the design of the distro as it to becomes a part of a vast network of services.

I have spent most of my career, and a lot of my life, as a “fixer.” What does that mean? Well, in a lot of movies, its the guy who comes in and gets rid of the body(ies) when things go sideways . However, what it has meant for me has been, “hey, xyz project is failing, please fix.” As a result, I am very good at understanding problems (preferably quickly ), recognizing and collaborating on solutions, and then working with people to resolve them. I believe that this skill is really important for Fedora right now as we deal with a myriad of blockers to the “success criteria” I outlined above.

Finally, and perhaps most importantly, I believe. I believe in open source changing the world. I believe in Fedora (the software and the community) being in the enviable and unique position to deliver something new.

Care to share a screenshot of your Fedora desktop?

Sure, but it is really boring . Probably more interesting are the two desktops of approximately 12 firefox windows with ~20 tabs per window; two instances of thunderbird managing 4+ mailboxes; irc and IM clients, 3-5 terminal windows with 2-3 tabs per, and an instance of gedit mostly for clearing formatting on c/p and copies of content in case something crashes. But, that is harder to grab a screenshot of.

Langdon White's desktop screenshot Langdon White's desktop screenshot

Have you used Fedora in a cloud or server context?

Yes. However, I am mostly a developer, so I have pretty limited experience with running servers in production. That said, I have built and deployed a large number of applications on a large number of different OSs in the cloud and on premise. I just don’t normally manage them.

What did you do on your last vacation or weekend off?

Having kids means this doesn’t really occur anymore . That said, this coming weekend is a decent example of a non-working weekend. My oldest son is playing in a soccer (nee football) tournament so I will be driving 40 minutes away from home (each way) and attending at least 4 games on Saturday and Sunday. My daughter and younger son will be performing a couple of songs from their upcoming musical (The Music Man) at “South Boston Community Day” which I hope to be back from the tournament in time to see. My partner and I will try to attend a friend’s gallery opening on Saturday night. And all 5 of us will try to watch this week’s Pokemon and Teen Titans Go episodes together!

What do you want to achieve as member of council?

The two things that come to mind as concrete goals are:

  • Establishing a set of initiatives/objectives with concrete plans with a longer horizon than the next release.
  • Drive new participation by application developers in the Fedora community

Anything else voters should know?

Langdon White
Probably lots… But this is long enough already.

How do you envision improving collaboration with downstream communities (ie: CentOS)?

Personally, I try to talk to some of the leads of the CentOS project pretty regularly. I believe a lot of other community members do as well. I suspect there is less disconnect than one might expect between the various projects. However, I think it might be a great idea to try to enable some more formal collaboration especially given the upheaval in the industry and distros in general. Ideas off the top of my head: maybe a working session/series at the next Flock? Perhaps an online “summit” where any/all distros can get together for a series of proposed discussions?

Council Elections Interview with Haïkel Guémar (number80)

This is a part of Fedora Council Elections interviews series. This is an important election, as two candidates will be selected as the Elected Representives, seats which carry full membership in our new top-level leadership and governance body.

Voting is open to all Fedora contributors. The elections starts on November 18th and closes promptly at 00:00 UTC on November 26th.

Please read the responses from all five candidates and make your choices carefully:

Feel free to ask questions of the candidates here or elsewhere!

Interview with Haïkel Guémar (number80)

number80

What is your background in Fedora? What have you worked on and what are you doing now?

I started using Fedora around Fedora Core 2 and it has been since my main distro.

I’m a contributor for 8 years now, mostly as a package maintainer and ambassador. Recently, I’ve been involved in the Cloud WG and in the Fedora Board.

What is your vision for Fedora? Where should we be in five years?

Distributions ain’t the cool kid anymore, cloud and mobile computing have taken over the world, so it’s time that we also evolve.
In five years, I want Fedora and its ecosystem become a reference platform for developing/hosting applications.

More unlikely, I would like to see a Fedora-based distro for mobile (tablets, smartphones, etc.) – Fedora everywhere ! – but who knows :)

What does it mean for Fedora to be successful? What is “winning” for our project?

As a project, I measure our success in our capacity to influence the world around us.
Though, it’s an interesting metric, I don’t care about how much end-users we have, I care about the vitality of our community, of our ecosystem (ie: our downstream communities).

To measure our success, we’ll need having metrics and analyze them so we could improve ourselves as a project.
Thanks to fedmsg/datanommer/datagrepper, we can watch the whole project pulsing in realtime. We should leverage these data to monitor the project health.

We win when:

  • Fedora is a first-choice platform to develop applications, host services
  • Fedora influences the direction of GNU/Linux
  • our contributors have fun

What are the most pressing issues facing Fedora today? What should we do about them?

Many pain points, among them:

  • recruiting new members, not only because we’re understaffed in some areas but also to bring new people with a fresh perspective.
  • lack of common vision: in the current context, we need to build a common vision to define where we’re headed.
  • More coordination & communication: Fedora has grown big, it has become difficult to set a direction, and many impediments are kept hidden to most of us so we can’t even try to solve them.

What are your interests and experience outside of Fedora? What of those things will help you in this role?

On the professional side, I’m a software engineer like most of us, though I have a degree in electronics.
I’m an activist (diversity, equality of rights, etc.), I was also an elected staff representative but that’s another story.
From my personal experience, I learnt the value of teamwork, the value of ethics and to stand to what you believe is right.

I’m also involved in (too) many technical user groups, organizing a lot of events.

Care to share a screenshot of your Fedora desktop?

Nothing exciting, I use vanilla GNOME Shell and I spend most of the time working in local/remote shells.
I appreciate that GNOME let me work without too much distraction.

Haïkel Guémar's desktop screenshot

Have you used Fedora in a cloud or server context?

As a stakeholder in Fedora Cloud, I use our images in a daily basis be it on a cloud (OpenStack, AWS, etc.) or as a virtualized guests for testing purposes.
All my bare metal machines (personal servers included) are on F21.

I believe in dogfooding, I *do* use Fedora at work since 2009 (development workstation, server, SaaS applications, etc.), and it has proven rock-solid.
This is my own experience, and to mitigate that, in the technology adoption lifecycle, I’m probably somewhere between early adopters and innovators.
As a council member, I want Fedora to be suitable up to early majority, and cooperate with our downstreams to provide something suitable for the majority folks.

Technology adoption lifecycle

Anything else voters should know?

I currently work for Red Hat as maintainer for RDO (Red Hat Distribution of OpenStack which is based on Fedora) since few months.
My commitment to Fedora has no link with my past/current/future employer, and I intend to keep that way.

As a board member, I did my best to hear my fellow contributors and voicing their concerns to the board.
I admit that I was a bit clumsy in doing so, but this was all in good faith and I’m improving myself on that matter.
My email box is always open to any fedora contributors, I’ll listen whatever you want to talk privately.

What did you do on your last vacation or weekend off?

I haven’t taken any vacations for a while.

What do you want to achieve as member of council?

  1. bring more diversity: gender, ethnicity, age, background, etc.
    I want to make more people from diverse backgrounds willing and comfortable to contribute to Fedora.
  2. Identify bottlenecks and pain points and activelXy work to fix them
  3. More Fun !!
    Most of us are volunteers, so it should be fun to participate in Fedora to keep the project sustainable.
  4. More collaboration with our downstream communities and fellow distributions
    With Fedora.Next and its 3 flagship products, Fedora embraced its mission as a platform. We need to make it easier using Fedora as a foundation for third-party products (including spins).

How do you envision improving collaboration with downstream communities (ie: CentOS)?

Since CentOS and Red Hat have joined together, we have an unique opportunity to work more closely
with CentOS to collaborate.
We need to share our infrastructure and make it easier to contribute to both projects. We need to build
a consolidated ecosystem while keeping our own identities.

More generally, we need to open up to downstream communities and help them fit the fedora ecosystem.

Council Elections Interview with Michael Scherer (misc)

This is a part of Fedora Council Elections interviews series. This is an important election, as two candidates will be selected as the Elected Representives, seats which carry full membership in our new top-level leadership and governance body.

Voting is open to all Fedora contributors. The elections starts on November 18th and closes promptly at 00:00 UTC on November 26th.

Please read the responses from all five candidates and make your choices carefully:

Feel free to ask questions of the candidates here or elsewhere!

Interview with Michael Scherer (misc)

What is your background in Fedora? What have you worked on and what are you doing now?

My background is rather classic. I started as a user of the distribution while contributing to others projects, mostly because I wanted to play with SELinux and some java stuff which was not integrated by the distribution I was using at the time. As I was helping during free software events in Paris and France, I was already well connected to the local Fedora community, having done joint booths and this kind of things along the years. Then I started to report bugs and to help with testing on stable releases. As I had a packager background, I later decided to make reviews and do a few packages, sponsoring a few people. I also served for 1 year on the board. Now, I am more busy so I stopped being as active as before, but basically do the same things.

What is your vision for Fedora? Where should we be in five years?

IT is a domain that move too fast for me to have any kind of credibility on a 5 years time frame. Yet, if I had a magic wand, I would use it to have Fedora becoming the obvious operating system for a free software hacker, either directly or with downstream. And to me, this include offering a modern and secure desktop, robust and pushing free software movement as a whole. But that’s not very original, as that’s what we already aiming and already have.

Another part of the vision also take in account what I consider as threat to the community. I think that others distributions are not a threat, far from it, so we should not compete against them but collaborate more. Having people part of 2 communities, going to different events, or others ways would be beneficial. After all, the ideas of the council was championed by Christophe Wickert after discussing with Mageia folks, and Debian use fedmsg due to a presentation of Aurelien Bompart while a debian hacker was present in the assistance during Distro Recipes. The systemd project also show that inter distributions collaboration is possible and helpful.

However and to go back on the topic of threat and challenges, I see Apple and the rise of numerous SaaS companies ( Google to name one ) to be more worrying because they push ideologies that are detrimental to us and the free software movement in the long run. For example, the centralization of services in the end of a single provider who broke interoperability several time and who keep code for himself, or the use of patents to stifle innovations, etc. That’s all philosophical positions that have very practical repercussions to us and free software as a whole, and where we should do something.

So while pondering about this, I think that we should not compete only on the technical side, but also put a huge focus on external communication to have a consistent and compelling story. For example, the keynote of Matthew Garrett during Guadec this year, where he spoke about privacy and the desktop, was inspiring. In turn, this requires making Fedora more welcoming for non technical contributions to attract people that can help us achieve this goal.

So maybe Fedora Workstation could be one of the incarnation of this vision, a system that respect users privacy and take it seriously, which is easier to do as we do not have a clear conflict of interests, unlike the aforementioned companies. The same goes for Fedora server, which I hope would help more people to host their own infrastructure, instead of moving everything at the same place. Doing this on the technical level is a good first step, but we also need to take in account the non technical aspect, and for that, we need to have a more diverse community and work on the communication side.

What does it mean for Fedora to be successful? What is “winning” for our project?

Fedora by itself is a project based of openness and community, so one of the definition of winning for Fedora would to have others people following the lead of the project and reuse and enhance the ideas and principles. As we push for the mantra of upstream first in Fedora, having a vibrant and diverse community of users and contributors is winning for us and for upstream. In practice, both objectives are quite fuzzy, especially since we do not all have the same priority nor the same vision on how to achieve our shared goals. So I guess winning for Fedora would be to make progress, despite and thanks to the difference in community. The Fedora.next change is a step in the right direction, permitting to each work-groups to have different deliverable, tailored to their specific goals and visions.

Otherwise, I guess having the magic wand I spoke in the previous question and using it as described would be a win. ( I however do not think we should pursue research in free software magic for now ).

What are the most pressing issues facing Fedora today? What should we do about them?

From a high level point of view, I think we have a lack of balance when it come to contributions. I perceive a huge implicit emphasis on being a packager, and this skew the demographics of the community and the resulting products. I tend to think that a good product requires input and work of a wide range of people from documentation, designers, QA, translators to name a few. And to fix that, I think the council is a first good step in the right direction. Another proposal would be to overhaul FESCO to be more diverse. For example, having formal representatives of i18n, QA or rel-eng as in the readiness meetings was a idea that was discussed around, and this could send the clear signal that those groups are important. But that’s just a discussion we had in the past, and we should first agree that there is something to improve before improving it.

On a more lower level view, I consider the FPC to be currently in crisis due to the lack of volunteers. In turn, this result in the burnout of the existing members, and this in turn become a bottleneck, resulting then in issues in packages due to lack of guidelines, and lot of bureaucracy. Being a reviewer, I am all for
having more guidelines and guidance to ensure the quality of the distribution, but the current process do not seems to be optimal. I do not have a easy fix for that, and I am just seeing the consequences without being involved, so the issue is likely more complex. I would first discuss around with people to gather their points of views, find the pain points and proposes ideas to solve them in a way that gather some consensus.

Another concern I hear from time to time is that rel-engineering is critically understaffed. While all parts of all free software projects are understaffed ( since we have always have more ideas of what to do than time to do them, not counting bugs), rel-eng seems to be blocked on various things due to the lack of people. However, I know that work to fix this is underway since a few months, from Ralph working on getting a staging setup of koji to help testing things to Dennis having started meetings around rel-eng to scale himself. I also put big hopes on having vagrant in the distribution, as we will likely soon be able to leverage it to ease testing by the community on the infra side.

What are your interests and experience outside of Fedora? What of those things will help you in this role?

My experience are the one of a sysadmin, which is my day job, and a developer, who was my previous day job. I do not really think this will help me so much for the council except the fact it give me street creds in the community due to its technical nature. I was also part of the founding members of the fork of a distribution, having contributed to set it up from 0, both on the infrastructure level and on the governance level. And the fact that the distribution still run fine despite my departure for personal problems show that we did the right choice to sustain it in the long term I am also interested in the security and privacy realms, for professional and personal reasons.

I do not think my others interests are important or relevant enough to disclose in the context of this interview.

Care to share a screenshot of your Fedora desktop?

I would rather not, I consider that what appear on my screen is private for me, so I want to keep it this way.

Have you used Fedora in a cloud or server context?

I use it as a server in a regular datacenter, hosting various personal things ( VPN, XMPP server, etc ), and I do use it to build static websites at work. I guess that count as cloud context, as the installation is fully automated at a various cloud providers and various hosting issues forced me to redeploy on a regular basis ( ie, ephemeral instances ). I appreciate to have the latest software to be present for me to use.

What did you do on your last vacation or weekend off?

My last vacation were in North America and I was visiting North Carolina to see a friend of mine. I could speak of my last weekends, but they were all exceptionally filled with free software events since my return from my travels and not representative of what I usually do.

What do you want to achieve as member of council?

I want to make sure the council is properly started and running fine. The first years of any new organization are usually a bit rough, as we discover various problem that are unplanned, and I want to be here to help. As the others questions already touched, I already went to this exercise once, so I guess I can at least help to avoid some pitfalls that I already faced. However, i also think I will be able to help, wether I am eleected or not, so I see the questions to be a bit misleading.

Anything else voters should know?

For the sake of transparency and disclosure, I am currently being employed by Red Hat as a system administrator in the OSAS team, who is in charge of helping communities be successful. However, being part of the board ( fedora or anything ) never was something asked by my employer, even if I am quite sure the experience I got while doing this for several community did help me to get my current job. So while I am employed by Fedora’s primary sponsor, and while I have a lot of insider ( and outsider ) contacts, I am also just a volunteer for this and try to keep in mind the interest of the external community. I still think it would be beneficial to get a more diverse set of sponsors around the project, but this interview is long enough without me adding more on the topic :)

How do you envision improving collaboration with downstream communities (ie: CentOS) ?

Besides EPEL ( who is a obvious answer on how we can collaborate with Centos ), and coming from a infrastructure background, I tend to see infrastructure based solution and collaboration in priority, so mostly sharing the software and making them easier to reuse. There is lots of possible interaction, like having some integration with fedmsg ( as Debian did ). Another potential ideas would be around SCL, as that’s a topic that often come when I talk to people about Fedora and Centos so having them as a joint project ( Fedora taking care of the innovation around it, and Centos being a downstream serving them ) would be a idea. Another potential area for collaboration would be having joint events, specially in the context of Fedora Server.

For non Centos downstreams, getting their feedback in a more official way would be a good start. While we have spins and remix, I do not think we often take in account their needs when deciding something. There is however a case to be made of avoiding fragmentation and pushing everybody to be under the Fedora umbrella in order to share the load and make the project more resilient.

Another often ignored part of downstream is for software that we develop as part of Fedora, who are not that often reused outside of it. Various infrastructures projects come to mind, and finding why they are not not compelling or reused would be beneficial.

Council Elections Interview with Rex Dieter (rdieter)

This is a part of Fedora Council Elections interviews series. This is an important election, as two candidates will be selected as the Elected Representives, seats which carry full membership in our new top-level leadership and governance body.

Voting is open to all Fedora contributors. The elections starts on November 18th and closes promptly at 00:00 UTC on November 26th.

Please read the responses from all five candidates and make your choices carefully:

Feel free to ask questions of the candidates here or elsewhere!

Interview with Rex Dieter (rdieter)

brno-rdieter

What is your background in Fedora? What have you worked on and what are you doing now?

I’m a long-time fedora contributor, packaging mostly. I have served on the Project Board (several times), FESCo, and Packaging Committee. Currently I’m an active member of the KDE SIG and generally try to help out anywhere I can, particularly by mentoring/sponsoring new contributors.

What does it mean for Fedora to be successful? What is “winning” for our project?

For me, it’s simple. Success means Fedora continuing to grow into a thriving, even more active community. Winning means continuing to be an ideal incubator for our vision of free culture and collaboration.

What are the most pressing issues facing Fedora today? What should we do about them?

I think it important to continue to empower those doing the hard work within the project, and to tear down barriers that get in the way of getting that valuable work done.

What are your interests and experience outside of Fedora? What of those things will help you in this role?

I work as system administrator in the Mathematics department at the University of Nebraska Lincoln. I also contribute occasionally to other (upstream) projects, including KDE and xdg-utils. I believe my experience in administration/deployment and upstream development give me some valuable and unique perspectives.

Care to share a screenshot of your Fedora desktop?

 

rdieter-screenie

Have you used Fedora in a cloud or server context?

I currently use Fedora to power several web-based application servers (as part of my dayjob).

Anything else voters should know?

 

I’m an avid baseball fan, go Cubs and Astros (an odd pairing of favorite teams, I admit, but there you have it).

EVENTO DE SOFTWARE LIBRE EN SISE: SEDE SURCO
Estimados amigos, como estan? nuevamente escribiendo en este blogs para avisarles que en la primera semana de diciembre se realizara un evento de software libre en la sede de sise de surco. Para esto contaremos con la participacion de la comunidad de Blender, Ubuntu, Fedora (como siempre la comunidad ayudando en todos los eventos y participando todos unidos...).
Esperamos contar con su participacion. En algunos dias se daran mas detalles del evento y pagina web respectiva para las inscripciones, pues habran talleres de aprendizaje en los laboratorios de la sede.

Comentarios y palabras claves en Go

Como todo lenguaje de programación Go posee palabras claves o reservadas y varias formas de comentar muy similar a como se hace en C

Comentarios.

Comenzando con la parte de comentarios, Go tiene dos formas de definir comentarios, la primera es la que utiliza dos slash (//) para hacer comentarios de una línea, por ejemplo:

// Esto es un comentario en Go de una línea

También se tiene la opción de múltiples línea, aunque también se puede usar para una sola línea comenzando con /* y terminando con */.

/* Esto es un comentario
de múltiples líneas */

Palabras claves

Go posee unas 25 palabras claves que no puede ser usada para ningún otro identificador incluyendo: nombre de variables, constantes, funciones, paquetes, de lo contrario el compilador arrojará un error al momento de compilar el archivo o el proyecto, las 25 palabras reservadas son las siguientes:

break

case

chan

const

continue

default

else

fallthrough

for

func

go

goto

if

import

interface

map

package

range

return

select

struct

switch

type

var

defer

Day 2: Fedora APAC Budget Planning FAD: Little Things

We reserved the second day for all of the little things, most importantly swag. Sirko passed around samples of swag that EMEA made, notably stickers, pins and buttons and also some balloons as examples of things we could do.

The main problem however was bulk production and distribution of the swag. Unlike EMEA, APAC was not one big region with few export controls. APAC was a lot more divided and given strict customs policies of some countries, we would have to produce a lot of swag locally, thus increasing cost of production. We have to figure out the cheapest way to do this and ambassadors agreed to get quotes by about January for production as well as shipping.

One of the most important problems from the budgeting viewpoints for APAC however was the charges for transactions that ambassadors had to pay for each reimbursement. The current charges are much too high for APAC at about 4.4% of the transaction amount. For example, for a $100 reimbursement, the ambassador tends to lose about $4, which is a significant amount of money in most APAC countries. In terms of McDonalds meals, one can have two McChicken meals in India with $5.

The other problem with Paypal was that all countries in the APAC region could not accept Paypal. Because of this, one would either have to use something like Western Union to transfer money, which is again riddled with steep charges.

Various approaches were discussed, from getting Paypal to waive those charges, to passing on the charges to Fedora somehow, to associating the APAC credit card with a US based Western Union account. We still need to discuss this with the Fedora leadership.

The other action item was to make an inventory of all material we had in APAC, i.e. banners, tablecloth, etc. so that we know what kind of material is available for conferences around. This would also help us plan production of any such material in future.

Finally, everyone seemed to like the idea of having smaller focussed contributor/user meetups like I had proposed for India and Izhar suggested making a brand name for such meetups so that everyone could standardize on them. I suggested Fedora Contributor Meetup and Fedora User Meetup. Tuan will bring this up at the FAMSCo meeting.

We ended the day with dinner at a restaurant at the Mekong riverfront. Greta joined us for this one and we had a great time. Somvannda and Nisa took us to the night market after that to buy stuff and we then headed back, but not before having another round of snacks and drinks at a local place near our hotel. I had a 4AM start but it was past midnight by the time we were done. Almost everyone stayed up chatting about various things till it was time for me to go.

This was my first trip to the East and perhaps one of the more interesting trips in recent times. We are geographically and politically divided but it was interesting to see that a lot of the problems we had were common and solutions to them could be quite common too. This is hopefully a beginning to an even closer association with ambassadors in APAC to bring Free and Open Source Software closer to people in the region through the Fedora project.

I have taken a few pictures, which I will hopefully be able to process and upload before the end of the week.

Day 1: Fedora APAC Budget Planning FAD: An Eventful Day

Prior to the FAD, Sirko made a table of events to fill in events happening in APAC that we thought we ought to ensure a Fedora presence for by allocating a budget for one or more people to travel to the event. Most of us sent out a communication to our respective smaller communities and got the table populated further. Sirko had already covered most of the bigger events, but there were additions to the list.

We went through the list of events, with one or more people arguing for or against representing an event. We agreed to discuss swag production and other issues on Sunday. This turned out to be a fairly exciting affair, with emotions sometimes running high over some events. It was great to see though, because it meant that people were really involved. My pet event was not really a single one, it was a group of small ($20-$50) events I plan for us to do in India over the whole financial year. These would be user and contributor meetups with a specific focus, similar to the Security FAD and Test Days we had earlier this year. The proposal did not get any opposition since we have enough contributors in India to pull this off. Now I only hope we get such a budget and we are indeed able to pull off such events and that they are successful.

Other than that it seemed odd that there weren’t a lot of large events in India that Fedora could focus on. I think we will have to look at this a bit deeper in the coming year to see if there are events we may have missed. Maybe smaller events just tend to be more productive due to which such meetups seem to be cropping up more frequently. Or maybe nobody wants to step up to do bigger events. I don’t know.

We ended the day at a local restaurant that Somvannda took us to. We had a great meal of various seafood dishes that I thoroughly enjoyed. Of course, I have yet to come across cuisine that I have not liked, so me enjoying Cambodian food was not surprising. Heck, I even enjoyed British food (which apparently is considered bland) when I was in Cambridge in July, even the blood sausages and haggis!

It turned out to be a very productive day and I was happy that we managed to finish discussing the entire set of events in that one day. The next day we would discuss a lot of the little things that seemingly make a big difference.