Fedora Project's Robyn Bergeron: The Linux Desktop Is Almost Ready for Its Close-Up
By: Jack Germain
Full article:: http://www.linuxinsider.com/story/77499.html
"Open source in general, along with the enterprise market, continues to fare very well. If you asked me 10 years ago, I'd think it was an area that showed some interest. At this point it has become a business of some US$8 billion, and is a model that has proven itself. I don't see that slowing down any time soon."
"There are a number of reasons why open source has gotten good enough and has proven itself as a business model. More and more IT managers are aware of the benefits of open source. It's been an outreach and then proving that it really does work."
" In terms of the Fedora desktop, I think we offer quite a bit more choice to people. Think in terms of the number of desktop choices we offer. Consider that if somebody in the Fedora community wants to add to those choices, we are supportive of that interest. We will do that. We are not dictating from on high. We don't focus on "Thou shalt have" and "Thou shalt not have." We are definitely a distribution that is focused on freedom."
There has been a long break to publish the Fedora Weekly News(FWN). Fedora
experts, ambassadors, and contributors are playing an enthusiastic role for
the development of Fedora marketing, development, design, infrastructure,
documentation, and other. All of us are very strongly tied by our
dedication for Fedora.
Now, it is the responsibility of the FWN News team to explore all the
Fedora mainstream contribution to all contributors and news editor all over
the world. It is the honor of Fedora Weekly News team.
Please step forward to contribute at the FWN team and spread the news to
all. Your contribution can make a big difference for the community.
Releasing FWN Issue 297 on March 13, 2013
New bee is welcome to join in the team
For more information, please visit https://fedoraproject.org/wiki/FWN
I had taken a talk and covered following topics :
Getting started with Qt development
Contribution to Fedora
Introduction to Aeolus project
at *Jamia Millia Islamia College of Enginnering* , Delhi , India on
Saturday, March 9th , 2013.
My talk was one of the several talks under Jamia Dev Days 
The participants were mostly Btech students .
They were familiar with basic programming language practices mostly with
C/C++ and quite a few of them had a prior experiencing of using Linux.
In the first part of my talk I had covered the following topics :
What is Qt
How to start learning Qt
How to approach a GUI application using Qt
In the second part I mostly covered things like
What is Fedora
How to contribute
Where to ask for help and so on
In the last part of my talk I had given them information about :
My contribution to Aeolus project
How they could contribute to Aeolus project .
Thanks to JMI LUG  for their help in organizing this wonderful talk.
 Jamia Millia Islamia University : http://jmi.ac.in/
 JMI LUG : http://www.jmilug.org/cms/
Nitesh Narayan Lal
Plivo invites you for a off campus recruitment drive on 8th March,
2013 at Kalyani Government Engineering College (West Bengal).
Interested candidates can take a print out of this post and visit the
venue (written below).
Position: Dev-Ops Engineer
Salary: 5 - 6 LPA.
Note: Salary and position will not be a constraint for the deserving candidate
Plivo provides easy and feature rich APIs for businesses to develop
powerful voice and messaging applications.
Plivo has been part of Y Combinator (US biggest incubator), and The
Morpheus (TM) (Indian Incubator). Plivo is funded by same investors
like Google, Facebook and Skype.
Plivo is headquarted in San Francisco, United States with an office in
Plivo is a small team, and are looking for people who can make a big
impact. They are all about startup work culture.
Kalyani Government Engineering College,
Kalyani, Nadia, West Bengal, India-741235.
College website: http://www.kgec.edu.in
Google Map Location: http://bit.ly/visitkgec
Biswajit Pain: +91-9434608413
Thanks and Regards,
Core Team Member,
PS: You may also apply online for open position in Plivo. Please
On Tuesday 29 of January 2013 17:29:47 pete wrote:
> Hey guys,
> I've been reading the Feature discussions on devel@ today, and an idea
> came to mind. A process for documenting accepted Features would help
> prevent major changes from slipping through the cracks. Here's what I
> came up with so far; I think we can hammer it into something useful:
thanks for kicking this off - I've been overflooded with all features coming and
I did not have time to start it (actually I had time, but mentally ;-).
At FUDCon we had a long discussion how the feature process should look like
and the result is - we would like to do the real proper planning and tracking
of features (so it will be Planning process, not feature process - even we
could find some other name?) and split it from marketing side - so only a
subset of these proposals will be featured (and thus it's the word "feature").
> Accepted Features will be listed in a table roughly analogous to that
> used for Release Note Beats. The table would have columns for the
> Feature name, a docs volunteer, and developer contact, as well as others
> reflecting the Feature documenting workflow.
Believe me - maintaining even FeatureList is a big pita - but speaking about
tracking of development and splitting marketing - this could be done on the
main FeatureList - I'm definitely open to any suggestions from documentation
team how to enhance FeaturesList to work for you - as we really want all
planning/tracking to happen in one place (and definitely not anything that's
out of sync often etc.).
One idea is to try to use some other tool than plain wiki - that's not very
suitable for this task (but with more parsing scripts...). But at least
there's huge resistance to Trac at least in FESCo ;-)
> A set of guidelines for the docs volunteer covering a feature will come
> along with the table. The set of tasks to be juggled might include:
> - Establishing an appropriate developer point of contact to aid in
> documentation. Note that this isn't always the feature owner.
But mostly it is Feature owner (but anyone willing to help could be added to
Owner section as "Developer contact").
> - Ensuring the content of the Feature is understandable by a
> hypothetical average user.
This is something I'm not sure based on the split we want - as we really need
technical details for planning features and that users/press part should be
processed differently (and aim on the user).
> - Working up a basic guide to implementing the feature, if applicable.
> - Creating an entry for the Feature in the appropriate Release Notes
+1, again - more features = more data for RN
> - Checking existing guides for impact caused by the new Feature, filing
> bugs as needed, and assisting the guide owners in updating as
> A defined process like this will help split up the workload caused by
> feature churn and cut redundant efforts by providing new information for
> multiple published works. Your thoughts?
It's a good idea to have a good source for multiple published works in the way
- FeatureList for tracking (RNs, docs) etc -> pick up spotlight Features (we'd
like to Feature) -> Announcements are for free, leaflet for media is for free,
Btw. I understand that we can never split the feature process completely, and
there will be always people using the internal planning/tracking process for
articles etc. - we are open project and we will never hide any kind of
information. But FreeBSD kernel is a good example how it works :)
I'm CC'in marketing team for feedback.
> tures  http://fedoraproject.org/wiki/Category:Documentation_beats
Mabuhay Everyone!!! I am Eleazer Caramancion from the Philippines. Y'all
can call me "Amatz" for short. I was very interested in learning more about
Linux and thought of joining in this amazing community. I am a system
administrator supervisor but find my job alil dull with the routine stuff
we do everyday. I am actually taking Linux class on my dayoffs and find it
very liberating and exciting.
I am grasping on how things work in your comminuty thats why i kept on
visiting the fedora site last month every so often. I joined the Fedora
Marketing because I know its another skill of mine I wanted to explore and
I know I can deliver. I am into photography but just an amateur and still
learning techniques. Some of my friends see my work as amazing photos. I
like engaging myself to different projects and learning new stuff. I also
have a creative side when it comes to designs and creating event programs.
I hope I have shared alil bit of me and I hope I'll be able to contribute
alot for this community. Have a nice week everyone!
My name is Thom Ables, I live on the west coast of the United States (GMT -8:00). My FAS username is tables, my IRC nick is tra and I can be found on Twitter @eightseventysix. I learned about the Fedora marketing team while perusing the wiki/homepage, looking for a way to help out with the Project. I originally applied for the Free Media group, but I haven't heard back yet...
I haven't spearheaded a marketing project before, but my professional background is varied and I've been involved in "outreach campaigns" with a couple US/Canadian based companies. Though my professional marketing experience is limited, from the outside looking in, I feel like I may have some talents to bring to the table.
It sounds cliché, but I really do consider myself fairly confident, outgoing and very easy to talk to. I spent a few years as a self employed photographer so creative self promotion and marketing is are not completely foreign concepts to me. I've been a Linux user for a few years...starting with Mint and finally finding my way to Fedora. I am a staunch believer in the freedom of information and knowledge and enjoy seeing peoples face light up when I tell them that there is an alternative to the "other OSs". Privacy rights are very important to me and given half a chance, I will speak endlessly to anyone who will listen about the benefits of being aware of ones surroundings on the internet.
It comes down to this: I think I have the personality and the creativity to help out, however big or small the role may be. I'm not exactly sure where the needs lie, or if I will even be a good fit at this point. With a little direction...I'd like to find out.
Hi all! (and sorry for post to sooo many lists)
As we already have a final schedule (for a three weeks now) and we're
getting closer to release windmills - I'd like to make the schedule
easy to use for everyone (and that means for me too), to be sure
it makes sense etc. And inform you about recent changes I did to schedule
,plans but also I'm going to ask you for a little assistance.
These are a few changes/or requests for your feedback:
1. from F19, schedule moved to FPGM neutral site , you can get
there from standard wiki schedule page.
Over the time, schedule got messy, some teams are even not aware what
a specific milestone means, why it's there, many times it's historical
relict and even collective memory does not work to remember what's
the reason to have it in schedule. On the other hand, I don't want
to remove anything people still relies on, based on my "common sense".
So please, take a look and let me know (some people already contacted
me and I work it in asap).
3. links in schedule
Thanks to Robyn, with her great TJ foo skillz, I'm now able to link
milestones in schedule to wiki and SOPs. Fedora QA asked for that,
I'll try to match as many as possible by myself but if you want to
link specific event to specific url, let me know.
4. future of scheduling, for F20+
For F19, we used a different way to schedule, based on the scope
of submitted features. It worked quite well from developers POV but
we completely forgot other teams and made the scheduling of theirs
tasks harder. I created a FESCo ticket , please take a look
(and comment it if you have ideas!). Also we would like to start
F20 as early as possible so the submission period should start
at F19 branch date (or shortly after) to let people propose the
ideas in advance.
5. new TJ3
And the main goal of the move, cleanups and so on is to jump on TJ3
board - I have initial port done, but a lot of changes are needed
and I'd like to start with TJ3 based schedule from a clean old one.
Btw. with any question, ping me, report ideas to schedule Trac 
and you know ;-)