Marketing-trac: #126: Create a wiki page for magazine covermount information
by Marketing Team
#126: Create a wiki page for magazine covermount information
----------------------+-----------------------------------------------------
Reporter: pfrields | Owner:
Type: task | Status: new
Priority: major | Milestone: F14a: Pre-alpha
Component: other | Severity: urgent
Keywords: |
----------------------+-----------------------------------------------------
We often get inquiries from magazines asking for permission to bundle one
or more Fedora discs with a future issue. This is a fairly routine
process as long as the disc is an unmodified copy of Fedora media (i.e. an
official release). Some interaction with Red Hat Legal is required to
send out an agreement to the magazine.
We can speed up that interaction and the overall process if we have a page
that tells magazines what they need to provide, and to whom, for a
covermount agreement. Generally we need the following information, sent
to the ''press(a)fp.o'' address:
* The name (d/b/a) and address of the company producing the magazine
* The exact disc(s) that are to be bundled
* Contact information for the person making the request
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/126>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 6 months
Marketing-trac: #125: SSSD F13 feature -- press blog entry
by Marketing Team
#125: SSSD F13 feature -- press blog entry
-----------------------------+----------------------------------------------
Reporter: pfrields | Owner: pfrields
Type: task | Status: new
Priority: major | Milestone: F14a: Pre-alpha
Component: Feature Stories | Severity: urgent
Keywords: meeting |
-----------------------------+----------------------------------------------
I had suggested this earlier to Robyn -- a press blog entry for Red Hat's
PR channel (http://press.redhat.com) that would synopsize and point to our
interview on the wiki. However, Robyn's pretty busy right now. Kara
Schiltz from Red Hat's PR department is willing to publish something next
week.
I'm going to pick this up and drive it forward, my way of helping this
week on something Marketing related!
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/125>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 6 months
Marketing-trac: #128: Press Release for FUDCon KL 2012
by Marketing Team
#128: Press Release for FUDCon KL 2012
--------------------+------------------------------
Reporter: izhar | Owner:
Type: task | Status: new
Priority: major | Milestone: Future releases
Component: FUDCon | Severity: urgent
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------------
Hi,
Could we have a press-release for FUDCon KL 2012 which is happening this
May?. We are planning to distribute it to local newspapers and news sites.
We are originally planning to produce our own but FPL said that marketing
might want to do and approve it.
In term of dateline, .. erm .. is 27th March too short?, or more than
enough?. The earlier the better of course
Thanks.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/128>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 6 months
Re: Documenting Features
by Jaroslav Reznik
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:
Hi Pete,
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[1] will be listed in a table roughly analogous to that
> used for Release Note Beats[2]. 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
> beat.
+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
> appropriate.
>
> 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,
ambassadors...
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.
Jaroslav
> [1]
> http://fedoraproject.org/wiki/Releases/19/FeatureList#Fedora_19_Accepted_Fea
> tures [2] http://fedoraproject.org/wiki/Category:Documentation_beats
11 years
F18 - huge drop in user numbers
by Jiri Eischmann
Hi,
frankly I'm not sure which mailing list I should write this to, but I
guess the marking one is the best fit.
I was really surprised (in the negative way) by the Fedora stats [1].
Repository connections in the first week dropped by 52 percent compared
to F17 and F17 was already low compared to releases before. F18 has
pretty bad reception, but such a huge drop is hard to believe.
The number of direct downloads is down by 7 percent.
Are these numbers still comparable or the way they're calculated has
changed? If not, it's a pretty bad trend.
The difference in drops between direct downloads and repository
connections is also interesting. It seems like a lot of users downloaded
F18, but never installed it, and connected to repositories which pretty
much correlates with my observation at linux portals, forums, mailing
lists. I've seen so many comments of users who said they didn't have
balls to install F18 on their hard drives with other systems and stayed
with F17 or switched to another distro.
Jiri
[1] http://fedoraproject.org/wiki/Statistics
11 years, 1 month
Fedora Project page on FB
by Jiri Eischmann
Hi,
we still don't have an official page on Facebook. I spoke with the guy
who owns the most popular Fedora page, he is a redhatter, but he doesn't
post news very frequently and doesn't seem to be willing to hand over
the page to someone else.
That's why I'd like to create a completely new official page that we
would build from the scratch. It will take more time to get a
significant number of followers, but I think it's the cleanest and
easiest way.
If there are no other plans already in the works or no one objects I'll
create the page and be maintaining it (I'll post there pretty much what
I post on G+) until some other volunteer steps into it.
Jiri
11 years, 1 month
Fwd: Fedora 18 Beijing Release Party Event Report
by Christopher Meng
I'll help promote Fedora as far as I can.
btw,anyone else in China of marketing team except me?
---------- 转发的消息 ----------
发件人:"Tommy He" <lovenemesis(a)fedoraproject.org>
日期:2013-1-31 PM5:58
主题:Fedora 18 Beijing Release Party Event Report
收件人: <ambassadors(a)lists.fedoraproject.org>
抄送:"Tao Zhao" <alick9188(a)gmail.com>, "Christopher Meng" <cickumqt(a)gmail.com>,
"Gerard Braad" <gbraad(a)fedoraproject.org>
Hi ambassadors,
I would like to share a few joyful moment after Fedora 18 Beijing
Release Party last weekend. It's the second Fedora themed event in
Beijing after the FAD 2011.
The event was hold in Information Technology Academy of Tsinghua
university. Six "Spherical Cow" related presentations were presented
by long-term project contributors, Red Hat engineers and open source
hackers from other communities. The topics cover i18n, cloud computing
and open source hardware. 50 Fedora 18 LiveDVD 64bit(40 GNOME 10 KDE)
were burned and distributed. Another 20 or so legacy Fedora DVDs were
spread for backward compatibility. Nearly 70 people have participated
the event. Feedback survey were sent to attendances via email. Result
can be expected in a week or so.
One thing worth to mention is that we had a preliminary agreement with
people from GNOME Chinese User Group to hold a Tech Seminar every
month. More specific details will be finalized after Chinese New Year
holiday.
Report in Chinese, also shared on via FedoraProject Weibo:
http://linuxtoy.org/archives/fedora-18-release-party-event-report.html
Event G+ (with more photos):
https://plus.google.com/events/activity/cpcjji4lbi1mllmk2s4nihcq6ug
Photo Booth on YouTube: http://youtu.be/tB1iD1SmQB8
After Event Survey: http://www.surveymonkey.com/s/RWYQZDV
This release party is initialized and organized by Ambassador Alick
Zhao, with assistance from Marketing Christopher Meng, Photographer
Tommy He and Mentor Gerard Braad.
Thanks,
Tommy
--
Take a Deep Breath out of Windows
https://fedoraproject.org/wiki/User:Lovenemesis
11 years, 1 month
People ask sometimes Why Fedora does not rolling distro? Sometimes think so too.
by Álvaro Castillo
Yeap, I'm ambassador and one of my task is to show Fedora's values between
other things. However, some people ask me about why Fedora does not a
rolling distro? It's too lazy have to upgrade system without any bugs each
6 month or 1 year month if you do not want lose Fedora security and
software updates.
I do not understand, Fuduntu is a very good laptop-based distro, based on
Fedora and comfortable for end-user such as Ubuntu, and It's a rolling
distro, you can get latest software without do a lot, and... when Fuduntu's
team releases a new version, you only do a yum upgrade to change a new
version without do a lot of and not suffer upgrade process. And Fedora has
got an testing group something like rawhide on Fedora.
Also, had known a people uses CentOS as desktop because does not like have
to upgrade your system each 6 month, do not like a possible bugs after
upgrade to Fedora new version or fix rpmnews... and would not like cross
your fingers to find a bug that could be break the system.
Why do you think about this? Fedora could be follow Fuduntu's steps? Or
it's no problem worry about some people wants?
Off: Please, I hope do not hurt with my "engrish" words because I'm trying
day-to-day improve my english, if you cannot understand, please let me know.
--
Álvaro Castillo
Fedora Project, EMEA ambassador
http://fedoraproject.org/wiki/User:Netsys
Linux user #547784
11 years, 1 month