[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [seul-edu] CervanTeX needs a wiki, could seul help ?
On Sat, 21 Apr 2001, lp wrote:
> > Could be you so gentle of providing us with such a wiki?
> > I can't warrant that it'll be used, I'm just a member of CervanTeX,
> > an active member, but not president. So after the wiki is available
> > I'll show them and I think they'll use it, because it's much better
> > for the thing we're doing now, isn't it?
> I'd like to try to help with this, but do you need a wiki page
> or do you need help setting up a wiki on an existing server?
We had servers in several places, but since this a very new thing,
and the meetings are going on these days, so we need it now or
never( a year from now), the "factible" option is to add a wiki
page in SEUL and let us there to organize it, I'll be stuborn on how
to use it, and since they're very eager with new technologies,
most of them use Linux (partially or fully), TeX,... I think
it won't be any problem to adapt themselves to a wiki.
> If you need a wiki page (or pages) I think you are suggesting
> a kind of function that SEUL might want to consider ....
It's what I need, thinking better about the login, yeah it'll
be nice to have one, this login will be public within our
lists, so it'll be a not very restricted login password...
> Doug, if SEUL decides to support this kind of activity in the
> wiki, then this adds a whole new dimension to the intended use
> of the wiki that might be useful? Or what do you think?
I think a wiki is a very logical way to produce structured info.
Tipically email discussions have this structure:
<point name="p5" related-to name="p2"/>
<point name="p1"/> <!- yeah yeah, a point of issue i1 in issue 2->
<point name="p4" related-to name="p3" related-also-to name="p4"/>
..... issue i1 again with two new points: p8, p9
As you see the logical structure of the info is conditioned
by the "physical" media, this time is "email" sequence. The really
important thing here is the tree of issues and points :
<point name="p1" text="blah blah" author="e1">
<point name="p5" text="bleh gleh" author="e2"> <!- as you see this
a a related (sub)point>
This is not the perfect structure since a point may be included
in several issues, anyway, proceeding this way you get the
content in a very cool way. And you force people to order
and correlate their ideas. And you save reading time, if you
don't want to read things about issue "p2" you can skip.
Well this <issue> driven structure is just a "wiki", explained
in a xml-ish way.
> Instead of simply capturing useful information from the
> mailing list and organizing links to software, Manuel is
> suggesting that the wiki could be used for dialogues that
> are related to Linux and education, but that are somehow
> more appropriate for the wiki than the mailing list.
> The Portland Pattern Repository and Everything2 are examples
> of 'wikis' whose scope has evolved to be very broad.
> On another related wiki issue, this time regarding Jonathan's post,
> if there was a section in the wiki for details regarding Linux
> Conferences and InstallFests, then someone could open a new
> wiki page called [Linux World 2000], post a message to the
> mailing list announcing the event and then say "post a
> message on [Linux World 2000] regarding this event", or
> some such thing. All the other related dialogue could go
> on in the wiki. I personally don't mind the overhead of
> extra posts on conferences, etc., but maybe this is an
> alternative approach for messages that require a lot of
> follow-up that some might want to use.
> So, pending Doug's approval, I opened three new pages
> in the wiki just as an experiment: