Microblogging
by Paul W. Frields
We currently have a microblogging capability through HootSuite/Ping.fm
that connects to Identi.ca, which in turn feeds Twitter. We started
using HootSuite because it offered the ability to share access to the
@fedora feed without sharing a passphrase, which would be non-optimal
from a security standpoint.
However, according to the HS site, we will no longer be able to share
team access to the feed. They are moving to a pay-to-play model for
any team functions. This was a risk we assumed in using HS, but
mitigating it is very simple, as we knew going in.
Therefore, I'm going to distribute the passphrase for the Identi.ca
@fedora account (to which the Twitter account is hooked) via GPG
encrypted email to the team members listed on the wiki:
https://fedoraproject.org/wiki/Status_and_microblogging_SOP
If I can't find a GPG key for you, I won't be able to distribute to
you via this email, but you can get in touch so we can remedy that.
(I'll have to require some sort of verification in that case, like a
key signature by someone trusted.)
If anyone has better ideas, please let me know.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
13 years, 3 months
Re: Microblogging
by Jan Wildeboer
Take a look at brdcst.it, does what you want, is AGPLv3 and I am one of the
devs ;-)
Jan
----- Original Message -----
From: marketing-bounces(a)lists.fedoraproject.org
<marketing-bounces(a)lists.fedoraproject.org>
To: Fedora Marketing Team <marketing(a)lists.fedoraproject.org>
Sent: Tue Dec 14 11:05:21 2010
Subject: Microblogging
We currently have a microblogging capability through HootSuite/Ping.fm
that connects to Identi.ca, which in turn feeds Twitter. We started
using HootSuite because it offered the ability to share access to the
@fedora feed without sharing a passphrase, which would be non-optimal
from a security standpoint.
However, according to the HS site, we will no longer be able to share
team access to the feed. They are moving to a pay-to-play model for
any team functions. This was a risk we assumed in using HS, but
mitigating it is very simple, as we knew going in.
Therefore, I'm going to distribute the passphrase for the Identi.ca
@fedora account (to which the Twitter account is hooked) via GPG
encrypted email to the team members listed on the wiki:
https://fedoraproject.org/wiki/Status_and_microblogging_SOP
If I can't find a GPG key for you, I won't be able to distribute to
you via this email, but you can get in touch so we can remedy that.
(I'll have to require some sort of verification in that case, like a
key signature by someone trusted.)
If anyone has better ideas, please let me know.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
--
marketing mailing list
marketing(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/marketing
13 years, 3 months
[In the news] Jackass IT: Stunts, idiocy, and hero hacks
by Heherson Pagcaliwagan
Hi *,
http://infoworld.com/print/145932
"Jackass IT stunt No. 1: Route city services through a laptop
Ever wonder whether you could route an entire city network through a
laptop running Fedora? Take a seat. Or better yet, leave the chair for
your laptop. You'll need to balance it somewhere to keep city services
up and operational through a two-day snowstorm.
.
.
After a feverish half-hour configuring the switch and setting up
802.1q trunking and routing on a Dell Latitude running Fedora Linux,
the city network was back up and running, with all traffic routing
through a single interface on the laptop balanced on a chair in the
data center."
13 years, 3 months
[in the news] Red Hat Fedora 14 Review
by Kara Schiltz
Fedora 14 rated 4/5 in the following review...
Computing.co.uk
12.13.10
Red Hat Fedora 14 Review
By Dave Bailey
Fedora 14 <http://fedoraproject.org/get-fedora> – codenamed Laughlin –
is the latest version of the open source operating system from Red Hat
and was launched in late October.
Fedora will be tempting for desktop and laptop users. The 686MB download
is a Live-CD, which means that you can run the operating system from a
CD in the disk drive, without it needing to be physically installed.
[clip]
For mobile road warriors, or firms with users unfazed by using Linux
OSes, Fedora 14 is a good option, especially if it is dual-booted with
Windows, because Fedora is free.
Wired and Wi-Fi connectivity, Bluetooth, NTFS support SD cards, USB
flash drives, and onboard cameras all worked seamlessly, demonstrating
good usability for both laptops and desktops.
Full post:
http://www.computing.co.uk/ctg/review/1931152/red-hat-fedora-14-review
13 years, 3 months
[In the news] IT Lure Distro Hoppin`: Fedora 14
by Rahul Sundaram
Hi
http://www.itlure.com/2010/12/distro-hoppin-fedora-14.html
"While some users may be turned off by the lack of easy-to-reach proprietary
drivers/codecs and the barren default software selection, most will
appreciate the true qualities of this distro:
* its focus on developing the community and trying to keep everyone
active and contributing in some way or another;
* giving users access to the latest and greatest apps in the open source
world;
* its commitment to freedom.
Surely, as always, there is room for improvement, but I found Laughlin to be
the most stable and solid version of Fedora I've tried in years. "
Rahul
13 years, 3 months
"The Big Reveal" debunked
by Mel Chua
Saw this on
http://www.neary-consulting.com/index.php/2010/12/08/curing-shy-developer...,
via the teachingopensource.org mailing list, and thought it would be
interesting for the team:
However, another phenomenon is fighting against this desire for openness.
It is not uncommon for companies to want to keep their plans secret, so
as to have a Big Reveal announcement effect at a major trade show. This
can lead companies to ask their engineers to work internally on
significant features for fear that the big surprise will be ruined
otherwise. The alternative seems to be to announce a project when you
start, rather than when you have something to show – but this can result
in a long wait before products get to market, and impatience and bad
press from the mainstream press.
I would argue that having engineers talk about design decisions &
implementation details of significant features in a mailing list will
not result in significant attention outside of your community – and when
the press release and announcement comes, the community who knew it was
coming will feel better about having been in on the secret from the
beginning, rather than feeling worse because they have to deal with a
big code drop which no one person can review.
13 years, 3 months
FWN Reader Survey: final copy
by Pascal Calarco
Thanks to everyone who offered suggestions for the FWN reader survey!
I've made some changes, which can be previewed at:
https://fedoraproject.org/w/uploads/6/67/FWN-survey-20101207.pdf
Mel, I'll take you up on the offer to purchase responses for this with
the Community credit card, so that I can open this on Thursday for
responses. Contact me off list and I will send you the
username/password for the Limeservice account I have set up. They take
PayPal and Visa. Alternatively, I can pay with PayPal and submit for
reimbursement to that same PayPal account, if that is easier. Thanks!
- pascal
13 years, 3 months
FWN reader survey
by Pascal Calarco
News, Marketing and Logistics Teams --
In order to gather some more feedback so that FWN on Fedora Insight can
be as user-driven as possible, I've mocked up a Limesurvey to gather
feedback for Fedora Weekly News and uploaded this to the wiki at:
https://fedoraproject.org/wiki/File:FWN-draft-survey-20101203.pdf
I would welcome your feedback between now and next Wednesday, when I
would like to include the survey with the next issue of FWN.
The survey is currently ten questions. The purpose of the survey is to
gather:
1) background on the readership of FWN
2) which beats are most and least useful, and if readers miss any
currently dormant beats
3) what new features readers would like to see with FWN
I am thinking we'll be safe to purchase 500 responses for US$35. I
think we would be wildly successful if we got that many responses. We
could also go with 250 responses, for $13 less, but the incremental cost
seems minimal between 250 and 500 responses.
Any feedback is very welcome -- thanks!
- pascal
13 years, 3 months