Re: GNOME weekly roundup (was Re: community managers)



Maybe it would be simpler to just do a Google+ Hangout?

--lucasr

On 15 November 2012 06:34, Sriram Ramkrishna <sri ramkrishna me> wrote:



On Wed, Nov 14, 2012 at 9:52 PM, Karen Sandler <karen gnome org> wrote:

On Wed, November 14, 2012 7:58 am, alex diavatis wrote:
On Wed, Nov 14, 2012 at 2:54 PM, alex diavatis
<alexis diavatis gmail com>wrote:

Hello,

Why don't you try an YouTube channel. A weekly 5' show kinda like:

I love the idea of maybe doing a weekly audio recording of this week in
GNOME. I could potentially do this as an interview with a different key
person each week, if it's not too long. Perhaps a half hour each time? I'm
wary of video as I think that will take a lot of work...


slightly off topic:
The youtube channel idea seemed pretty good but it was hard to manage.
Mostly because I had a hard time figuring out how to tag posts for GNOME.
Maybe I'm missing something there.  Design guys are always throwing up video
on their thoughts.  A missing opportunity IMHO.


Do others think this is a good idea? Alex, would you want to help with it?


It depends.  I would set it up almost like an RSS feed postcast.  That would
make it more automatic and something people can subscribe to.

sri


karen


This week in Gnome...[ie new features]
We cannot support this because .. [ie theming API]
In Gnome 3.. [discuss/explain some features and how to use desktop]
In Gnome 3.. [tech news]

It will take only two hours for each person to do this, and you can
rotate
This week, Allan, next week Seif, week after next Sri and so on.

YouTube is by far the most popular media to promote a product, plus you
will have a more "personal"
connection with people.


Oops that was going to previous thread [reddit IAMA GNOME
developer/designer] sooorry :)
- alex


- alex


On Wed, Nov 14, 2012 at 2:35 PM, Seif Lotfy <seif lotfy com> wrote:


Hello,
First I love the idea of a community team. KDE already has such a team
with a good mission (http://ev.kde.org/workinggroups/cwg.php).I think
studying their history and experience would be beneficial to the
community
team.

After discussing this Lydia from KDE, it looks more like a "Public
Relations" team more than a "Community Management" team. Both do have
some
common tasks. I think a Community team should encompass a PR team.

Agreed. We have a problem communicating our vision internally and
externally.
Internally it seems like not all of us are on the same page, e.g:
"theming will damage our brand". Or systemd dependencies etc. Do all
"high
profile" GNOME contributors agree on this?

Before communicating to the outside world that "XYZ" is a fact we need
to
at least agree on it internally. Taking the liberties with ones own
modules
without general consensus inside the community leads to friction and
arguments. This is something that a community team should work on,
make
people inside the community get along, reduce friction.

As a community team another mission would be working on communication
between devs, on mailing lists and bugs. Damage caused by snarky,
arrogant
or dismissive remarks should be controlled and positive communication
efforts have to promoted and praised.

Just my 2 cents
Cheers
Seif

On Wed, Nov 14, 2012 at 12:38 PM, Dave Neary <dneary gnome org> wrote:

Hi,


On 11/13/2012 06:53 PM, Sriram Ramkrishna wrote:

As a project, we are having trouble communicating our vision because
everything gets lost in a sea of vitriol due to past actions or
perceived actions.  For instance, removing fallback is seen as yet
again
the GNOME project is removing a feature instead of an act of
maintenance
and sustainability.


I think that as a project, we have had trouble communicating our
vision,
because as a project we are not sure what it is. There is a part of
the
project that has a very clear idea of their vision, but that vision
has
either not been clearly expressed, or what has been expressed has not
got
clear support from the community of contributors in the project. For
instance, the insistence that theming will damage our brand, or that
Cinnamon is not GNOME 3, has led to missed opportunities for the
GNOME
project, and has not got grass roots support among the GNOME
community
(and
I'm not talking about users here, I'm talking about contributors -
developers, translators, user group co-ordinators, and marketers).


 After all, GNOME design doesn't have any authority but is able to
convince maintainers that doing their approach is best for their
application.


I disagree with your analogy.


 I'm envisioning a team of 10 volunteers.  10 volunteers who start
out
as
community managers and then hopefully will be interested in doing
other
things within the project.

I currently have four as of right now.  Need to recruit six more!


Sounds like a plan, and we certainly need to do something to stop the
rot.


Cheers,
Dave.

--
Dave Neary, Lyon, France
Email: dneary gnome org
Jabber: nearyd gmail com
--
marketing-list mailing list
marketing-list gnome org

https://mail.gnome.org/**mailman/listinfo/marketing-**list<https://mail.gnome.org/mailman/listinfo/marketing-list>



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



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



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



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




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]