man, 16 11 2009 kl. 14:13 +0100, skrev Carlo de Falco:
> well, the current procedure looks a bit complicated and un-secure  
> (manually deleting the contents of the directories directly on the web- 
> server could lead to messy mistakes).

Agreed. I guess we could write some script that did all the necessary
work, such that you would only have to run something like

  install_html_files my_package_html.tar.gz

which would then make sure to setup the rights, etc.

> A great simplification could be obtained by upgrading all package  
> maintainers to "package admin" status so that they can take advantage  
> of the sorceforge web-based GUI tools, but I'm not sure we want to do  
> this...

Yeah, I've been thinking a bit about this. I guess we would like to have
a whole bunch of maintainers, meaning we would have many people with
'admin' status. I don't really have security concerns as I trust people
on this list, but the chance of somebody doing something wrong by
accident is just very high. So, I don't think we should take this route.

One option would be to have a team of administrators. When a maintainer
wants to release a package he/she would then contact this team (on this
list perhaps?) and tell them to upload the package and the html. The
downside to this approach is that a release depends on this team, but
that's why I would like to have more than one person on this team. The
current system, where things depend on me, is just terrible as I don't
have that much time.

Would such a setup be a good idea?

Søren



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to