On 3/6/07, Quim Gil <[EMAIL PROTECTED]> wrote:

On 3/6/07, Joachim <[EMAIL PROTECTED]> wrote:
> doesn't it seem odd to be
> discussing pages here, when the whole point of collaborative work
> environment like a wiki or CMS is that instead of discussing content we
can
> just update it?

Theory says you are right. In practice if we need to have some
feedback and quick we better come to this list.


Plone has a 'recent changes' page, no?
We need to get into the habit of checking it.
(I don't know where it is though...)

However if these
emails about wgo content are annoying we can move the work to the
wiki, yes.


That's just replicating the  problem with different tools.
A CMS should be up to the task of allowing discussion about the
collaborative work.

About "discussing content we can just update it?", I can discuss
content but in most cases nowadays I don't have the time or skills to
update it myself. This Windows page is a good example.


Make rough notes on the page. I can clean them up. Good collaborative
writing requires a fast iterative process, like on Wikipedia.
The About page is a good example  -- if I write something there now, half a
dozen people will pipe up and say 'That's not what Gnome is!'
So let those people write rough notes & ideas on that page NOW. Then I can
use that as raw material and make something nice :)

Also, why aren't bullet points working?

Because there is a "*" instead of a "<li>" in the HTML. I just copied &
pasted.


Can plone be set to handle wiki markup? It's inevitable that content will be
moved between plone and the wiki. We don't want to be fiddling with this
sort of thing every time.
(Though this raises the problem that our wiki uses nasty markup and not the
defacto MediaWiki standard...)
-- 
marketing-list mailing list
marketing-list@gnome.org
http://mail.gnome.org/mailman/listinfo/marketing-list

Reply via email to