changing the CTPUG wiki.
Neil Muller
probably better to discuss this on the list.
So, to summarise for those not at Saturday's meeting:
1) The current site is too heavy-weight for what we currently use the
site for. It's needlessly hard to navigate, and there's too much
boilerplate per page.
2) there was a lot of support for replacing plone with something
simpler, such as Trac.
2.1) running Trac has some advantages for the code-related projects
CTPUG has done.
Possible options include:
1) Reworking the current plone site to better suit our needs
2) Replacing plone
3) Moving python.org.za to some other site, and hosting a trac
instance there (which requires coordination with the gateng people and
the owner of the pyton.org.za domain)
4) Registering a ctpug domain, and just leave a pointer on python.org.za
--
Neil Muller
drnlm...@gmail.com
I've got a gmail account. Why haven't I become cool?
Roché Compaan
> After exchanging a few emails with with Roché Compaan, he suggested it
> probably better to discuss this on the list.
>
> So, to summarise for those not at Saturday's meeting:
>
> 1) The current site is too heavy-weight for what we currently use the
> site for. It's needlessly hard to navigate, and there's too much
> boilerplate per page.
This could easily be simplified. I just disabled the left and right hand
columns as an example. If the home page links directly to a PUGs Wiki, I
don't see how navigation can remain a problem.
If you make suggestions on how to simplify it or let us know what you
find difficult, we'll gladly help out.
> 2) there was a lot of support for replacing plone with something
> simpler, such as Trac.
> 2.1) running Trac has some advantages for the code-related projects
> CTPUG has done.
I'm against running Trac for PUG's web presence. It makes more sense for
a software project.
If you want to involve less technical people to help update the PUG
site, having a CMS is really helpful. At least it doesn't require users
to understand or like wikis to contribute.
>From my point of view, it seems to make more sense to host a trac site
for CTPUGs software projects.
--
Roché Compaan
Upfront Systems http://www.upfrontsystems.co.za
Louis Cordier
> 2) there was a lot of support for replacing plone with something
> simpler, such as Trac.
I am in favour of Trac and have written a few Trac plugins,
http://trac-hacks.org/, its very easy.
The Wiki markup is trivial and the templates realtively
easy to customize for your look and feel.
Regards, Louis.
--
Louis Cordier <lcor...@point45.com> cell: +27721472305
Adrianna Pinska
<ro...@upfrontsystems.co.za> wrote:
> If you want to involve less technical people to help update the PUG
> site, having a CMS is really helpful. At least it doesn't require users
> to understand or like wikis to contribute.
It does, however, require them to understand and like CMSes. A CMS is
no more intuitive or transparent than a wiki.
I don't think Trac is ideal either, but I think it may be easier to
use, and no worse a fit. We also have several members who are
familiar with running Trac, which is good for ensuring the ease of
future maintenance.
Regards,
Adrianna
--
~ Registered Linux User #334504 ~
"If ignorance is bliss, then knock the smile off my face."
Roché Compaan
> On Mon, Oct 26, 2009 at 1:53 PM, Roché Compaan
> <ro...@upfrontsystems.co.za> wrote:
>
> > If you want to involve less technical people to help update the PUG
> > site, having a CMS is really helpful. At least it doesn't require users
> > to understand or like wikis to contribute.
>
> It does, however, require them to understand and like CMSes. A CMS is
> no more intuitive or transparent than a wiki.
In my experience a wiki is significantly less intuitive for users for
the very simply reason that they have to learn some mini markup
language.
If a CMS offers users a wysiwyg editor, which Plone does, they have a
familiar interface that they come across in a range of word processors.
I haven't seen any significant gripe mentioned about Plone that can't be
easily solved. And if the argument against it is simply "we don't like
it because we don't use it", that's fine too.
> I don't think Trac is ideal either, but I think it may be easier to
> use, and no worse a fit. We also have several members who are
> familiar with running Trac, which is good for ensuring the ease of
> future maintenance.
It's easy for us to host Plone sites, support it and offer it as a
platform. We're not comfortable hosting anything else at this stage.
You are welcome to set this up and host it yourself.
Raoul Snyman
>> It does, however, require them to understand and like CMSes. A CMS is
>> no more intuitive or transparent than a wiki.
>
> In my experience a wiki is significantly less intuitive for users for
> the very simply reason that they have to learn some mini markup
> language.
>
> If a CMS offers users a wysiwyg editor, which Plone does, they have a
> familiar interface that they come across in a range of word processors.
Um, might I just mention that we're all developers, or prospective
developers, which means that CMS or Wiki syntax should be relatively
simple for us brainiacs.
Just saying...
--
Raoul Snyman
B.Tech Information Technology (Software Engineering)
E-Mail: raoul....@gmail.com
Web: http://www.saturnlaboratories.co.za/
Blog: http://blog.saturnlaboratories.co.za/
Mobile: 082 550 3754
Registered Linux User #333298 (http://counter.li.org)
Roché Compaan
> 2009/10/26 Roché Compaan <ro...@upfrontsystems.co.za>:
> >> It does, however, require them to understand and like CMSes. A CMS is
> >> no more intuitive or transparent than a wiki.
> >
> > In my experience a wiki is significantly less intuitive for users for
> > the very simply reason that they have to learn some mini markup
> > language.
> >
> > If a CMS offers users a wysiwyg editor, which Plone does, they have a
> > familiar interface that they come across in a range of word processors.
>
> Um, might I just mention that we're all developers, or prospective
> developers, which means that CMS or Wiki syntax should be relatively
> simple for us brainiacs.
There is a wiki on the Plone site, so I don't really see what the issue
is.
Plone or any other CMS just makes it convenient to upload other media
like files, images, etc.
David Fraser
For me it comes down to familiarity and the people most using a site being able to admin it. Whether that means CTPUG should run a separate site or not I think depends on how much other people are using python.org.za, and what for...
David