khard ownCloud Contacts for mutt

I use ownCloud to store my contacts and calendar, but until recently this has not been very useful when using mutt. My memory is not very good, and email address are hard; so I would have to either pull out my phone or open a web browser and find a contact. The setup was less than ideal.

Then I remember that vdirsyncer, the back-end for khal a tool I use for the caldav data also supported carddav downloads. I went to the documentation and found that vdirsyncer was pointing people to a tool called khard for use with the carddav data. So I configured vdirsyncer to download my contacts and went off to get khard working.

[storage my_contacts_local]
# A storage references actual data on a remote server or on the local disk.
# Similar to repositories in OfflineIMAP.
type = filesystem
path = ~/.contacts/
fileext = .vcf

[storage my_contacts_remote]
type = carddav
url = https://my.owncloud.url/remote.php/carddav/
#username =
#password =

A pip install (--user) later and it was ready to use. Like khal since the data is already on the computer the configuration as simple as pointing it to the contacts.

path = ~/.contacts/contacts/
editor = /usr/bin/emacsclient
default_country = USA

All that was left at that point was to tell mutt what my query_command was and I had my contacts list available from within mutt.

set query_command= "khard mutt --search '%s'"

That second F

I have been using Fedora for a long time, what started out as the simple usage of an operation system turned into a passion for a great community. I have always thought that the 4 Fs of Fedora where a catchy yet honest representation of the project, but recently the 2nd F has had a whole new meaning to me.

In January my wife and I had our third child who was born with several medical problems. I made a passing comment to someone about it in IRC and I have been blown away by the amount of support I have received since that time. Someone once told me that users are great but making users contributors is what strengthens the Fedora Project. If Fedora had all the users in the world, but no new contributors where being added everything would fall apart.

That idea is obvious and true, but now more than ever I see how important the idea of friends are to the community. Over the years I have made many friends in the Fedora community and that has only strengthened my passion for Fedora. When you receive so much support from people who you only talk to online, in a time of need, it is an amazing thing. People I do not normally talk to regularly reached out to me to offer support or sometimes just to talk. I think that the amount of support I have from members of the Fedora community may have been better than what I had from people I deal with in person on a daily basis.

This post is not to talk about my issues, my son is doing better, it is to highlight all of the amazing people we have working on Fedora every day. Fedora is made up of a wonderful community of smart and helpful people. While I think that freedom, features, and being first are all valuable attributes for Fedora to aim for, to me the friendship is the most important.

Fedora Docs FAD

The Fedora Docs team recently held a Fedora Activity Day (FAD) and I think it was a big success. Late last year the team was talking about how to make it easier for new people to contribute to Docs, and after a lot of great discussion it was decided that we should get together to find a solution. Since the team is spread out all over the global we had two meeting locations linked by video conference. One group was located at Red Hat's headquarters in Raleigh, North Carolina and the other was in Brno, Czech Republic, with a few others (like me) joined in from home to as well.

As the date of the FAD approached more tasks where added to the list, and while we initially wanted to talk about new contributors, several other tasks also got completed. Over the course of three days we worked of the following tasks.

  • A mentoring program
  • Videos for new contributors
  • The Documentation Guide
  • Docs Office Hours
  • The new publican site
  • Plans for handling Docs in the world


In order to help people get started in working on Fedora documentation the team has committed to several tasks. Firstly we are going to revive the mentorship process, this means that when someone shows interest in helping work on documentation someone from the Docs team is going to work with them to make sure they have the tools and skills needed to get things done. While we have always try and help people as a group, assigning new members a single point of contact will help people to fell more comfortable asking questions start out strong. Along with the mentoring we have started to allocate time each week for members of the team to be available on IRC to answer questions. Starting this week we have office hours set for Thursdays from 1800-1900 UTC and Sundays between 1500-1600 UTC.

Docs Website

With the migration to Publican 4, we are also working on refreshing The new site is built using RPMs for each guide and will allow the team to refresh documents quicker and easier. Over the course of the FAD Jared, Pete, and Nick did a lot of work to get that new infrastructure working.


Several people worked on improvements to guides during the course of the FAD as well. The Documentation Guide received a lot of attention, adding information from the style guide along with numerous other updates.

In order to make sure we keep up with the changes happening around Fedora, the group has decided to send a representative from Docs to each Working Groups meetings. Jared will be working with the Cloud group, Pete with the Workstation group, and I will be working with the Server group. Additionally, we have added a section to the release notes to highlight the changes in each product.


I was very happy with the outcome of this FAD, and hope that it will revitalize the Documentation team. The action items we have for work should help the team to stay focused on what needs to be done, and that should allow us to create better documentation for Fedora as we go forward. Thanks to Red Hat for providing space for the FAD, and to everyone who participated.

Day One Notes
Day Two Notes
Day Three Notes