I have just tagged, build and pushed a new fedocal update, 0.2.0, available as
With this update comes a number of improvements:
- Move to OpenID (and more specifically FAS-OpenID)
- Redesign of the home page (no more one calendar by default showing up as home
- A decent API, or at least more decent than the previous one
- Change in the ACL management with the creation of Calendar administrators
which have full rights on a specific calendar (based on FAS groups).
- Support full day meetings
- Support meetings over multiple days
- Support markdown syntax in the meeting description
- Easier access to edit/delete of the meetings you created / have rights on
And a number of bug fixes.
As every project, fedocal would be nothing without its contributors, so many
git shortlog -s -n -e:
56 Johan Cwiklinski <johan(a)x-tnd.be>
3 Haikel Guemar <hguemar(a)fedoraproject.org>
2 Ralph Bean <rbean(a)redhat.com>
1 Haikel Guemar <haikel.guemar(a)sysfera.com>
1 Lukas Brabec <lbrabec(a)redhat.com>
Feel free to have a look at it and report bugs/wishes at:
Hopefully 0.3.0 won't take that long to come out ! :)
Thanks for your attention,
OK, this bugzilla report has not gotten much action --
so lets try this list.
I would think that a common installation would involve two types of
btrfs subvolumes: a new subvolume for root ("/") and one or more
existing subvolumes for /home, etc. Anaconda can handle creation of new
subvolumes nicely and adds them to /etc/fstab. However, for existing
subvolumes, you need to specify "--useexisting" on the btrfs command
which specifies the mount point or anaconda crashes saying that the
subvolume already exists .. OK, that makes sense. But, if you then
specify --useexisting, anaconda proceeds BUT the mount point is NOT
added to /etc/fstab.
This problem has existed since Fedora 18 and is still true in Fedora 20
alpha. How about if someone fixes this, explains why it is not
necessary, or explains how to specify reuse of a btrfs mount point? Is
this too much to ask?
I do not like cross posting ... another copy of this message is posted
on the anaconda-devel-list.
This is a/the stand-alone replacement RPM for the glusterfs-ufo
subpackage and the fix for the broken deps in glusterfs in f20 and rawhide.
I personally would like to get this wrapped up so that glusterfs doesn't
have broken deps in f20 final.
I used Yubikey for some time (slot 1) for non-Fedora related stuff.
I just tried to use slot 2 for Fedora services, but whenever I try to use:
auth Failed: Unauthorized/Invalid OTP
What I did:
sudo fedora-burn-yubikey --slot=2 --username=msuchy
Commit? (y/n) [n]: y
Success! Your Yubikey ID is FOOBAR
I put that FOOBAR in "Yubikey prefix" on
I'm pressing the youbikey button for 4 seconds to get the OTP from slot2.
Can somebody help me diagnose what I'm doing incorrectly, please?
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
I'm new to these parts of the woods and hope that I can contribute to
the Fedora project in any way that I can.
I have used Fedora since FC6. For the last 5 years I've also used RHEL
in my line of work as a sysadmin and consultant.
I have made a bunch of rpms for work and for my personal projects and
would now like to use my skills to give back to the community.
To start learning how to do this the right way I'm starting of with a
fairly simple application.
Review request here: https://bugzilla.redhat.com/show_bug.cgi?id=1012391
This is my first package and I'm in need of a sponsor.