Re: Marketing Minutes December 13, 2012

2012-12-15 Thread Allan Day
Karen Sandler ka...@gnome.org wrote:
...
 I don't think it's actually that hard to figure out what we need to do to
 improve the perception of GNOME and GNOME 3. There are lots of examples
 that run contrary to the negative discourse that has been circulating -
 you don't have to look far to find people who love GNOME 3, or to find
 developers and designers who are receptive to feedback or who are doing
 cool stuff.

 I love this - as I mentioned on a different thread, I'm working on putting
 together a series of interviews of GNOME users, starting with greggKH and
 Brett. Do you know of any other awesome folks we should feature?

I'm sure I could come up with a few names for you. I'll make some enquiries.

...
 Perhaps one thing we can do is put together a wish list of simple things
 we'd like to see done, sort of a GNOME love approach to marketing. That
 way when newcomers ask for things to do we have a whole list to choose
 from. We'd have to make it all things that are not very time sensitive,
 but even just listing articles or interviews we'd like to see written
 could be a good start.

I'd say that the key tasks look something like:

 * Ensuring that there's a steady stream of messages from the GNOME
social media channels
 * Regular posts on gnome.org
 * Monitoring of (and engagement with) blog comments, social media
sites and forums (we should have a list of sites we want to cover)
 * Semi-regular events (an announcement can be an event, so can the
completion of a new feature) - accompanied by press packs

Having a check list of what needs to be done every week (and perhaps
every month) could be a good start, perhaps with a way for people to
record when they've taken care of something. This would help
contributors get started and would also be a way for us to evaluate
our performance. It could also be a good basis for regular meetings
(less strategy, more tactics).

...
 One possible way we could help with this would be
 to invite designers and developers to come and speak to the marketing
 crew as a part of regular meetings (I'd be happy to help organise that).
...
 We talked at this meeting about inviting designers and developers to our
 calls maybe on a monthly basis. If you wanted to help organize that it
 would be awesome!

My idea was to have the guest talk about what they have been working
on, and then answer questions from our marketing contributors. One of
the objectives would be to create opportunities for marketing
contributors to find stories to write about. Another would be to help
them establish contacts with the development community.

 What do others think? What can we do to grow the GNOME outreach effort?

 Our actual outreach efforts (mostly around OPW and GSoC) have been really
 successful, maybe we need to highlight that more too? I don't think we
 ever really did anything with the materials that were prepared at GUADEC
 even by the newcomers...

Sorry, outreach was the wrong word to use there. I should have said
marketing... I meant community outreach as community relations, not
new contributor programmes.

Allan
-- 
marketing-list mailing list
marketing-list@gnome.org
https://mail.gnome.org/mailman/listinfo/marketing-list


First time contributors : WAS Re: Marketing Minutes December 13, 2012

2012-12-15 Thread Andreas Nilsson

On 12/14/2012 07:21 PM, Dave Neary wrote:

Hi,

Sorry I couldn't attend - a sick son  bedtime meant that 8pm 
yesterday was rush hour in the Neary household.


On 12/14/2012 03:24 PM, Emily Gonyer wrote:

Sri: Theres a common wisdom that GNOME will throw out features and are
unfriendly. We've let others tell our story for us. As a result, most
of the press we receive is negative, focusing on GNOME 3's failures
and shortcomings.

Andreas: Whats the biggest drawback of this perception?


I would say that the biggest draw-back of this perception is that we 
are not growing as a developer community, because we're seen as a 
conservative project where code is as likely to be rejected as 
accepted once the work is done, it's not clear how to get pre-approval 
before developing something that it'll be accepted.
I can see this and it's something we can improve over time. Related to 
this (and sorry for hijacking the thread here), is that I think we 
currently do a very bad job at having a first time contributor experience.
We have https://www.gnome.org/get-involved/ but I feel it's currently 
pointing to a bunch of loose ends (especially Test and Code).
I was in #gnome-love the other day and someone joined and asked Hey! I 
want to start contributing to anything with code! How can I get 
started? and I was like Let me walk you through jhbuild hell The 
whole experience was extremely frustrating to me, I can't imagine how it 
was for this person.
I know Sri and Colin are looking at OSTree for some of this, but just 
having the jhbuild documentation sorted out would be a massive help. 
It's a mess right now.
Also clearer documentation on who to talk to, what to download, etc. 
would be a massive help.
Dave, since you have experience in this realm, any suggestions on what 
else we need to do to fix this?

- Andreas
--
marketing-list mailing list
marketing-list@gnome.org
https://mail.gnome.org/mailman/listinfo/marketing-list


Re: GNOME Quarterly Reports

2012-12-15 Thread Andre Klapper
On Sun, 2012-10-14 at 20:40 +0200, Andre Klapper wrote:
 As feedback is often slow (needs several times of nagging) I'd like to
 know if quarterly reports are still supported and wanted by the
 community, or if we should think of a better format (e.g. merging with
 news or journal activities).

No answers, so I guess there is no interest.

andre
-- 
Andre Klapper  |  ak...@gmx.net
http://blogs.gnome.org/aklapper/

-- 
marketing-list mailing list
marketing-list@gnome.org
https://mail.gnome.org/mailman/listinfo/marketing-list


Re: First time contributors : WAS Re: Marketing Minutes December 13, 2012

2012-12-15 Thread Sriram Ramkrishna
Yes, volunteer capture was one of the issues.  That's why one of the
projects was toe QA our website to make sure that we have a method of doing
volunteering capture.

I saw a similar issue in IRC where somebody came in and wanted to hack on
something and nobody answered him.  (I was reading from IRC history)  At
the very least we should maybe have our bot answer that question on
volunteering so they know where to go.

We even have that trouble here in this list.  I know I sent a couple of
people here and we weren't quite able to use them because of
disorganization.  In order to help with volunteering we kind of have to
know what help people need.

Anyways, good observation, Andreas!

sri


On Sat, Dec 15, 2012 at 5:57 AM, Andreas Nilsson li...@andreasn.se wrote:

 On 12/14/2012 07:21 PM, Dave Neary wrote:

 Hi,

 Sorry I couldn't attend - a sick son  bedtime meant that 8pm yesterday
 was rush hour in the Neary household.

 On 12/14/2012 03:24 PM, Emily Gonyer wrote:

 Sri: Theres a common wisdom that GNOME will throw out features and are
 unfriendly. We've let others tell our story for us. As a result, most
 of the press we receive is negative, focusing on GNOME 3's failures
 and shortcomings.

 Andreas: Whats the biggest drawback of this perception?


 I would say that the biggest draw-back of this perception is that we are
 not growing as a developer community, because we're seen as a conservative
 project where code is as likely to be rejected as accepted once the work is
 done, it's not clear how to get pre-approval before developing something
 that it'll be accepted.

 I can see this and it's something we can improve over time. Related to
 this (and sorry for hijacking the thread here), is that I think we
 currently do a very bad job at having a first time contributor experience.
 We have 
 https://www.gnome.org/get-**involved/https://www.gnome.org/get-involved/but 
 I feel it's currently pointing to a bunch of loose ends (especially
 Test and Code).
 I was in #gnome-love the other day and someone joined and asked Hey! I
 want to start contributing to anything with code! How can I get started?
 and I was like Let me walk you through jhbuild hell The whole
 experience was extremely frustrating to me, I can't imagine how it was for
 this person.
 I know Sri and Colin are looking at OSTree for some of this, but just
 having the jhbuild documentation sorted out would be a massive help. It's a
 mess right now.
 Also clearer documentation on who to talk to, what to download, etc. would
 be a massive help.
 Dave, since you have experience in this realm, any suggestions on what
 else we need to do to fix this?
 - Andreas
 --
 marketing-list mailing list
 marketing-list@gnome.org
 https://mail.gnome.org/**mailman/listinfo/marketing-**listhttps://mail.gnome.org/mailman/listinfo/marketing-list

-- 
marketing-list mailing list
marketing-list@gnome.org
https://mail.gnome.org/mailman/listinfo/marketing-list


GNOME infographics

2012-12-15 Thread Juanjo Marín


Hi there !


I've recently read about a post about how the Mozilla project did this year. It 
has a nice infographic work and I think we can do something similar for GNOME 
news in december.
Do we have data for doing a similar ?

https://blog.mozilla.org/blog/2012/12/14/mozilla-in-2012/


Some data by now:

* 2 major releases (GNOME 3.4 and 3.8)
* 4 big GNOME conferences (GUADEC, GNOME Asia, Boston Summit and Día GNOME)
* Presence in many FLOSS Conferences
* 9 hackfests (https://live.gnome.org/Hackfests/ Not sure if we must count all 
of them)


Other project, Libreoffice, always adds an Infographic picture in every 
release. I wonder if it is a good idea to do this in our releases.

http://blog.documentfoundation.org/2012/10/04/the-document-foundation-announces-libreoffice-3-6-2/


Cheers,

 -- Juanjo Marin

-- 
marketing-list mailing list
marketing-list@gnome.org
https://mail.gnome.org/mailman/listinfo/marketing-list