durusmail: quixote-users: Sandbox
Sandbox
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-18
2005-03-19
2005-03-28
2005-03-29
Sandbox
Shalabh Chaturvedi
2005-03-29
On Mar 28, 2005, at 2:47 PM, mso@oz.net wrote:

> Shalabh:
>> I created a public svn repository on cafepy.com port 13690. A Quixote
>> web interface is at:
>>
>> http://www.cafepy.com/quixote_extras/
>>
>> To check out the entire tree use:
>>
>> svn checkout svn://cafepy.com:13690/
>
> Cool.  I tried it out and it works fine.  Thanks, Shalabh.  Shall we
> bless
> it as the official repository?

Sure! If people find the service inadequate, we can always move to a
different repository.

>
>> Right now it has unrestricted write for everyone (I'm feeling brave at
>> the moment) but I'm wondering if that's a good idea. I'm not sure what
>> else would be convenient.
>
> We'll want to advertise our wares (not warez) to the public once we
> have
> some, so it would be best to implement write access now.  How about
> giving
> accounts to ppl on request who are known to be reputable on
> quixote-users,
> or who can convince Shalabh they are responsible.  There will only be
> 5-10
> ppl initially so it shouldn't be overwhelming.

This sounds like a good idea. I'll turn off anonymous write soon. Apart
from security issues, anonymous write also doesn't keep history about
who checked stuff in. Please send me an email if you want write access
- I will create an svn login for you, with a simple password.

> I wrote up a README.  Does it sound all right?
>
> ===
> This is a public Subversion repository for contributed Quixote material
> hosted
> at cafepy.com port 13960.  To checkout the entire directory do:
>     svn checkout svn://cafepy.com:13690/ qxtras
> A read-only web interface is at http://www.cafepy.com/quixote_extras/ .
> The Subversion manual is at http://svnbook.red-bean.com/ .
>
> To upload material, create your own directory ("svn mkdir my_name") and
> save it there.  Include a README file explaining what each
> file/subdirectory
> is, its status (well tested?  API stable?), copyright/licence info, and
> how to
> contact you.  Please also include a CHANGES file(s); this is very
> helpful for
> users.

For a lot of itty-bitty files though, comments in the file are
generally sufficient. Also documentation may already be on the wiki or
elsewhere. I'd like to keep this with as few restrictions as possible
to encourage participation.

I added a feature to the web interface - you can now set the svn
properties 'description' and 'info_url'. These will show up in the web
interface and may be used to provide a one-line description and info
link to another page which describes the file in detail.

> There are also a few site-wide directories:
>
>     imports/quixote/Quixote-2.0a5
>         Unmodified copy of Quixote for use in derived implementations
>         ("svn cp ...").
>
> All contributed software must be Open Source (GPL, BSD, MIT, etc; see
> http://opensource.org/).  Documentation/multimedia must be under a
> Creative
> Commons license (http://creativecommons.org/) or the OPL
> (http://opencontent.org/openpub/).  A sample MIT license is at
> http://opensource.org/licenses/mit-license.php .
> ===

Hmm, I think this is generally understood, and would like to keep it
out of the readme. If we do find people checking in restrictive
licensed code, then we'll complain. Code could also be public domain,
like any recipe type snippet should be.

Also, I'll add at the bottom:
No warranties of any kind - use repository at own risk!

And of course, links to the main quixote sites.

Cheers!
Shalabh


reply