Here it is the first release of Thinkfan,
a simple and lightweight fan control program, for Fedora. As a thinkpad
user so it's obvious what my interest is, but developer assures now can
manage other computers fan too.

It's not trivial to build Bitcoin in Fedora since it uses Elliptic Curve
Digital Signature Algorithm (ECDSA) «a cryptographic algorithm used by
Bitcoin to ensure that funds can only be spent by their rightful
owners», a feature of OpenSSL which has been restricted in
Fedora due to patents concerns.

To circumvent this obstacle package includes pristine sources of
OpenSSL from upstream and builds it for the sole needs of bitcoin
compilation and static linking.

Notes about this release:

This is supposed to be fully operational; if you find a
disarrangement please report through comments below.

Support of UPNP is deactivated for a while. I'll fix this as
soon I get miniupnpc decently bundled.

Some love is pending to make rpmlint happy.

It, sadly, doesn't build with Mock. The cause is some of the juggling
for compiling the upstream OpenSSL. I'll try some workaround for it.

If you rebuild de src.rpm in your system you must remove the
openssl-devel package to avoid conflicts.

If I got satisfied about the final results I probably postulate it to RPM Fusion, since the patents concerns
restricts it in Fedora. If someone is interested on taking the
responsability of maintain it I'll be very happy to let it.

I'm not used to SparkleShare so I'm not sure if all dependencies are
well tuned. I've activated the support of libnotify
and smartirc4net.
The first is working but I don't really know how it uses it and if it's
really working. Integration with
Nautilus is available too.

The package quality is a bit under Fedora requirements but it's, but the
application seems to me mature enough to add it to Fedora. I encourage you
to contribute it. In the middle, please report here any defect you
detect.

The thing is syncing right now. Evolution is supposed to be
able to access the local repo which is very nice to check the
repo althought I plan to use for one direction sync only. If
interested, OfflineIMAP is supposed to do double direction syncs
smothly.

Some caveats:

I'm having random OfflineIMAP crashes so
I'm doing the first full sync calling it manually inside a while true
bash line, but as far as I read seems to be a mature program with
specific support for Gmail IMAP server.

If you wish secured access take care to
set up the ssl variable
to yes for each
repository since setting port
to 993 is not enough.

For next steps I'm considering to switch definitively to the Google
2-step verification and to set up a duplicated cloud backup using
Amazon S3 or similar. I'm open for other suggestions :-)

It's really good news JRC is taking OSS into account
seriously, and the mixing/linking code practices are a good thing to
teach to use. Good for JRC.

OTOH, I would expected an explicit adhesion and promotion of OSS
licensing in all own developments, at least an strong recomendation for
all suitable cases. An being a research center, in my view would be
recomendable to promote the more openest licencing schemes (BSD like)
for the best transfering of coded knowledge to the society. Not so good
for JRC.

I've just released the first draft of the drobo-utils for Fedora
(12). As usual there'll be available at my repository: drobo-utils.

If I get satisfied with it I could postulate it to
Fedora/RPM-Fusion. Feedback would be grateful.

About Drobo

The Drobo is
supposed to be the 8th wonder in backup hardware. It does all the data
integrity stuff automagically and only asks to be feeded with off the
self SATA disks from time to time. Supposely as easy as your mother could
manage it.

For your curiosity, my backup system is composed with Drobo and the
desktop application back-in-time
(which puts rsync under the hood). Time will say if this is as easy and secure as a soho user (that's me)
needs.