<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
@ Jon & Bassel: I decided it would be better to let everyone know
now, so that we have more eyes on the project, and more awareness of
what's happening and what needs doing.<br>
To everyone ; welcome to the first steps in enabling anyone to be able
to join in on being a Librarian, to make methods of clipart management
that work or are easily changeable, and easily understandable
instructions for all users to accomplish various tasks.<br>
Right now, what I'm doing is looking at how OCAL is created using the <a
framework</a>. What is AIKI you ask? It makes the Library into a
database driven "moddable" website, using PHP, MySql(?) and a database.
I admit, I don't know much SQL language, but I'm finding the commands
and things that are making up the site very interesting. Please
understand that I am not a programmer, I'm an artist, a visual person,
but I have seen what AIKI can do, and I'm very excited by it. <br>
What I need from you guys is Use Cases for how you use OCAL. <br>
What have we got? What do we need?<br>
What should the completed website look like? <br>
<li>As an end user, how do you use OCAL? Please write and tell us
<li>As an Artist, what do you need for uploading your work? Or
self-promotion? How do you manage your own clipart on OCAL?<br>
<li>As a Librarian how do you go about your work? What tools do you
need? Even if they are obvious tools, break it down for us. I already
have a fair idea, but I'm not the be-all and end-all, and I certainly
don't have the only way of doing Librarian work. Are there better ways
we can do things? Are there things that we can do, which we aren't
<li>Give us pictures of what you would like your interface to look
like, and why you want them there. The more submissions we get, the
better idea of what we can make OCAL to be. I'm thinking of many
visuals. I'm not a fan of textual toggles, but we currently have them
and they work. How can we make them better?</li>
Please don't concern yourself with how things were done in the past, or
what's missing from then, but look towards what we can do now. Most of
the bugs from the Bugtracker days are irrelevant, and we need new
Have a look at <a
</a>to better understand what I'm doing.<br>
Join in if you can. We now have the opportunity to get some of these
issues sorted out. It may take awhile, it might take 8 or 9 months to
get to a reasonably finished OCAL. Hopefully it'll be quicker, however,
we are making some progress. One step at a time. Join in!<br>
On 23/06/2010 8:28 p.m., Jon Phillips wrote:
<pre wrap="">Great job on first pass at documentation!!! Keep them flowing and
letting the list know...
Our goal is to have an easier interface for most people to edit the site.
Also, bassel, can we add some form of versioning for changed on aiki
widgets? That would be killer...we need a way to allow for reverting
to past changes, esp. in this scenario of multiple editors.
On Tue, Jun 22, 2010 at 3:35 PM, chovynz <a class="moz-txt-link-rfc2396E" href="mailto:firstname.lastname@example.org"><email@example.com></a> wrote:
<pre wrap=""><a class="moz-txt-link-freetext" href="http://www.openclipart.org/wiki/Documenting_OCAL_development">http://www.openclipart.org/wiki/Documenting_OCAL_development</a>
this is a first run to understand how OCAL is being being built. Later on
I'll add how to do certain things.
@Jon : Please can we have the wiki upload directory as writable?
The upload directory (public) is not writable by the webserver."
We need it for images on the wiki.
Also the wiki spam filter needs some adjustment. It needs to allow <div>