[SciPy-dev] RE: CVS Build Instructions
Travis N. Vaught
travis at scipy.org
Wed Feb 20 22:01:44 CST 2002
I completely agree. I think the 'edit' feature was a casualty of some
unrelated edition to the SciPy site dealing with menuing or something. The
behaviour should definitely be for an 'Owner' of a document (its creator) to
be able to edit--even after publication.
This should be fixed in the next generation of the site along with other
improvements and fixes. We will hopefully migrate to it later next week.
BTW if you have any other suggestions about the site, they are welcome.
Here are some thoughts that are being bandied about:
o Roundup bug-tracker instead of the currently ignored sourceforge tracker
o Better facility for community comments to docs and the site in
general--perhaps just the mailing lists
o get rid of duplicate functionality (Wikis are similar to comments (now
disabled) are similar to archived mailing lists--we should probably use one
for discussion (mailing lists) one for co-generated docs (Probably not wikis
but I'm not sure--could be some CMF document in users' folders)
I've posted this to the scipy-dev list to invite (gingerly worded) comments
about how the scipy.org site would ideally work.
> -----Original Message-----
> From: Fernando Perez [mailto:fperez at pizero.colorado.edu]
> Sent: Wednesday, February 20, 2002 12:46 PM
> To: Travis N. Vaught
> Subject: Re: CVS Build Instructions
> Hi Travis,
> a quick question/comment:
> > http://www.scipy.org/site_content/tutorials/user_folder_instructions
> seems to give no way of *editing* an existing document. For
> example if I now
> want to fix some typos in the CVS instructions doc, if I
> understand correctly
> the only option is to upload a full new one, delete the old and
> go through the
> editorial 'quarantine'. It seems a bit cumbersome both for you
> guys and for
> users, especially when one only wants to do minor editing.
> I wonder if it would be possible to add an 'edit' button that
> would open the
> document in a simple html text field, nothing fancy. I understand
> this creates
> a run around your editorial oversight, but I'd be willing to say
> that scipy is
> a small and focused enough group that abuse shouldn't be an
> issue, at least
> for quite a while.
> Just some thoughts, please correct me if any of my above
> assumptions are wrong
> or I missed something in the instructions.
> Best regards,
More information about the Scipy-dev