Talk:Infrastructure

From GNC

A couple of follow-ups to our discussion yesterday (8/14):

• I changed the Navigation bar to reflect four of the sections in the Wiki. As we establish a more complete structure, I can adjust it accordingly
• Security and access - there's a number of things we can do to segment our users.
  • Allowing anyone to be able to see what's here is pretty much a given, since that's one of the objectives of the infrastructure.
  • Allowing anonymous users to edit pages probably doesn't make sense or add any value, so we require users to create a login ID.
  • We can set up user groups with different rights.
    • The rights structure and the software are not designed to segment by content - one group of pages can only be edited by one group of users. That's really more appropriate for something like managing a software project anyway.
  • We can limit the ability of new users to edit for a set period of time to allow us to verify the user.
  • We can also configure the site so that someone can't just create an ID, but an authorized user has to create ID's.
  • We can also create a set of users that has the ability to protect certain pages (and edit those pages). Protecting pages is not widely used, but could be used by, say, chairs of a group. Note that the ability to protect and edit is global, but presumably you wouldn't give that access to someone you didn't trust anyway.
• My suggestion would be to create a couple of user groups - say "general", "members" and "chairs", and decide as we go whether and how we want to provide differential rights. Anyone who creates an ID would be put into the general class, but we'd move GNC members into the member class.

Michael 08:32, 15 August 2007 (EDT)