Re: Marketing Materials in git

[Nelson Marques <07721 ipam pt>]

On Tue, 2010-02-09 at 16:27 +0100, Dave Neary wrote:
> Hi,
>
> Joe 'Zonker' Brockmeier wrote:
> > More pain on our side, less pain on the side of the contributors who
> > aren't developer tool friendly.
>
> Yes and no... one more account to create, or moderation request to wait
> for - one more bottleneck to get through before you're productive. For
> reference, see how long it has taken some of the members of the
> marketing team to go from volunteering to help maintain the web pages to
> actually getting access to the resources (in one case, there's still a
> request in a queue somewhere awaiting an SSH key).
>
> > You outlined 6 steps that a new
> > contributor would go through in order to participate.
>
> Well, really the 6 steps contains 2 really important ones - getting git
> & getting the marketing resources. As I said, it's a cheat sheet - the
> other commands you only need from time to time, and the git problem is
> memorising everything.

 Those using a POSIX compliant system like Linux or *BSD would probably
manage to run a local depot and a simple crontab script to update it
every X minutes if needed.

  Eventually there are also GNOME/GTK clients for git which would cut
much of the command line pressure for some people.

  And eventually, we could make a proposal of a GNOME project to the
developers list to create a more robust GUI git client, which would not
only serve us, but the entire community and we could integrate it easily
with GNOME and make a part of it.

  I would recon that most people see Marketing as a sales force, which
is actually not correct. Marketing goes far beyond that idea. When
people are sick, they go to the doctors. When an organization is sick,
they turn to Marketing, which is actually a set of tools and processes
that allow you diagnose and treat the "illness". 

  Just as a curiosity, how would GNOME developers see a Marketing
Developing Plan for a new application? Would they be cool enough to
follow a roadmap and a script or would just they see it as an attack of
the bureaucrats ?

  Nelson

> > Some may be that
> > motivated, others are likely to quietly decide that another project
> > might be better suited to their free time.
>
> So be it.
>
> As I say
> here:http://blogs.gnome.org/bolsh/2009/04/08/copyright-assignment-and-other-barriers-to-entry/
>
> some barriers to entry are desirable. Others aren't.
>
> In general, I would say that for any task where the commandline isn't
> otherwise necessary, avoid the command line. So a natural graphic way to
> get git and download & update files from git is probably useful, but
> there's no inherent reason why we'd need Alfresco.
>
> We could also use the Ubuntu One cloud, or DropBox... obviously, I
> prefer we don't, because they're proprietary software, but at least
> there the "hard to use" argument is less evident.
>
> > Not disagreeing that wiki attachments are sub-optimal, but I'm not
> > sure git is any better for sharing something like an OpenOffice.org
> > document.
>
> Sharing a document is probably best done as a wiki page, or in Google
> Docs or Zoho. Sharing the actual .odt doesn't make any sense to me, any
> more than it made sense to me back in the day, when project specs were
> sent as .doc attachments by email.
>
> If documents need regular revision, then you need something which allows
> collaborative editing & has version control. A wiki, a BaseCamp
> writeboard, or Google Docs (or an equivalent), or (if it ever gets
> released) the rumored web-hosted OOo would all fit the bill.
>
> Cheers,
> Dave.
>
> -- 
> Dave Neary
> GNOME Foundation member
> dneary gnome org
> -- 
> marketing-list mailing list
> marketing-list gnome org
> http://mail.gnome.org/mailman/listinfo/marketing-list