Agora Octave

[Jordi Gutiérrez Hermoso]

On 25 June 2010 18:28, Fotios Kasolis <address@hidden> wrote:

> So here we are! I made a function "publish()" with reasonably close
> interface to matlabs publish().

Btw, I've started working on Agora Octave, where hopefully functions
like this can soon be easily shared. There's almost nothing there yet,
but release early release often, right?

    http://bitbucket.org/jordigh/agora

Already I'm looking for some sort of website design. Would you be
willing to do some sort of design for it? You don't have to write any
CSS or anything like that; I can do all the code. I would just like
mockups of what you think a pretty design for it, and I can implement
it with CSS and icons and that sort of thing.

Ideally, the design would also use the same overall scheme as
Octave-forge and the Octave homepage itself, perhaps same colour
scheme, for example, so that visually the unity of the three locations
can be made explicit.

Structurewise, more or less what should go in Agora Octave is this:

    1) Users can upload bundles of code.

    2) Bundles clearly indicate which free license they are using. I'm
       thinking that it's reasonable to restrict allowable licenses to
       GPL-compatibility. This is not a stringent requirement, and it
       would simplify distribution with Octave. For the moment I'm
       considering that this might be relaxed and any license approved
       by the OSI or FSF should be ok.

    3) Additionally, there's a place to post quick snippets. They'll
       be under a default free license that the user indicates in
       their preferences. Usually only single bits of code go in
       there. Responding with more snippets will be facilitated.

    4) I'm thinking that optionally, I can setup bundles to also
       create an hg repo if the uploader requests it, or existing hg
       repos can be imported.

    5) When viewing a user's bundle, the bundle as a whole can be
       ranked and commented upon by logged in users. The contents of
       the bundle can also be browsed from the web without needing to
       download the whole bundle.

    6) Logging in is required only to contribute to the site with
       code, comments, ranking code. Everything else is public to
       anyone.

    7) Users are encouraged but not required to provide real names.

    8) Bundles that are somehow deemed to be of high quality can
       easily be pushed to Octave-forge (i.e. they've been "forged",
       tempered, tested and tried).

    9) A user's landing page will indicate which bundles and snippets
       this user has uploaded as well as whatever personal information
       the user would like to provide.

I'm thinking most of this is fairly uncontroversial. And mostly still
a pipe dream. I know, I know, I'm getting around to showing the code
for this. ;-)

So, can you help me with a pretty design layout?