On Sat, Apr 23, 2011 at 6:48 AM, Alexandre Prokoudine
<alexandre.prokoudine@gmai...> wrote:
> On 4/23/11, Ronald Chmara wrote:
>> A CMS arguably makes it easier to get into website development for
>> people who don't have the "patience, passion and dedication" to use
>> fairly convoluted workflows to do something as simple as updating,
>> managing, and contributing web content.
> Why would you want people without patience, passion and dedication to
> be in charge of something you care about?

Because "patience, passion and dedication" means nothing when it comes
to fixing a typo, posting a random tutorial, uploading a tip, etc.

This is basically the wikipedia argument. Again.

If you only trust proven expert volunteers, that's all you're going to
get. It's slow. It doesn't work without lots of money.

Pity that wikipedia was such a failure, because they didn't demand
proven experts.

(Do I need a sarcasm tag?)

>> That being said, a CMS does not produce volunteers.... It merely
>> reduces the barriers a prospective volunteer has to cross in order to
>> become an active participant, so perhaps the conversation is not so
>> much about CMS vs. VCS vs. (whatever), but about reducing the barriers
>> to entry.
> Yes, but again -- we have noone to reduce them for.

Hi. I'd like to add a GIMP mirror, but the page on the topic is so
hosed that I cannot figure out how to do so. I have at least 10 years
of experience in apache, PHP, (blah blah blah) but I don't even know
how to *apply* to fix it, or who to talk to.

Yes, I'm just one person. How many of me have been shut out?

>> So, with that in mind, how many steps are required to fix a typo or
>> add content to the website, and can that amount of steps be reduced?
> With existing approach or with (possible) future static HTML + JavaScript? :)

I really don't care about the approach, but others might.

Others who can help.

> I think I'm utterly misunderstood -- I'm not against CMS. I'm fine
> with both static site and CMS. The question is whether we have someone
> who is willing to take full responsibility for availability of the CMS
> based website. With CMS the question is not _whether_ we'll be hacked,
> but _when_.

LOL, use a webserver, you'll be exploited..

With all tech, it's a question of "when". Some are more hardened than
others, but it's always "when".

> And when it happens, we shouldn't be running around like
> headless chickens, not knowing what to do. We need someone who will
> always be up to most recent security patches.

Or we need a team.

The concept of "someone" leads to failure, over time. Putting it into
the hands of one person creates a failure point.

> For Audacity we solved that by paying a community member who is
> experienced in that and can take care of issues. audacityteam.org was
> recently hacked, and he fixed that within half an hour.
> For Inkscape we are delegating that to OSUOSL whose team member is
> part of our community as well.
> For GIMP -- I don't think we have anybody right now to delegate it to.

This is why a team is needed. Folks check out. They come back. Or they
don't. Team leader roles change. As long as enough people are
involved, though, there is a team.

-Ronabop
_______________________________________________
Gimp-web mailing list
Gimp-web@list...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-web