[Hosting] gforge Monitoring files broken?

[Ed Hill]

On Fri, 2003-09-05 at 13:32, Joseph Tate wrote:
> On "My Page" it says "You can monitor files by visiting a project's 
> 'Summary Page' and clicking on the check box in the files section.".  I 
> haven't found such a check box.  Either on the summary page or on the 
> Files page.  Do there have to be files there first before this checkbox 
> appears?

<wiseguy>
  Yeah, its hard to monitor stuff that doesn't yet exist.  ;-)
</wiseguy>


Seriously though, we can look into that.  The GForge source (see the
contents of forge.trilug.org:/local/gforge) is actually pretty legible
so its not too tough to figure out what the code really can/can't do and
even modify it.

And this brings up another, really important, issue!  I'm mostly
ignorant of how members get accounts on TriLUG machines.  If someone
wants to help out with the GForge maintenance then theres sort-of two
"levels" of permissions:

  1) GForge "admin privs" through the web interface

  2) root (eg. sudo) on the server

The former will let you do a lot of little things on the web site and is
really pretty much harmless from a security point of view (though that
individual could delete projects, etc.).  The latter is needed to do any
real "heavy liftng" like the setup new of new projects, adding mailing
lists, etc.

So how are we going to handle letting people help with and learn about
GForge?  Some of them should probably earn the ability to become sudoers
but how is that decided?

Tanner?  Jeremy P?  Can you guys please give some direction here?

Ed


-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://www.trilug.org/pipermail/hosting/attachments/20030905/3c386082/attachment.bin