Opened 2 months ago

Closed 2 months ago

#26714 closed defect (wontfix)

Read-restricted wiki

Reported by: atagar Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi Hiro, as discussed on irc I'd appreciate a wiki with read access restricted to tor-internal@ members. This is something we've discussed off and on for years, and could be useful for a few things...

  • GSoC and SoP student selection coordination.
  • Possibly replace some of TPI's need for an internal SVN server.
  • Maybe useful for our Council as well? Malicious relay detection? tor-security@ or network-team-security@ coordination?
  • Replacement for our tor-internal@ welcome email's membership list.

Weasel suggested ikiwiki and I'd be delighted to give that a try. I'm not picky at all about the solution, it would just be useful to have some place we can put semi-confidential stuff.

Bonus points if we can customize restrictions on a per-page basis so TPI can be extra restrictive for sensitive pages like finances. Not sure if they'll use it or not but nice to give them the option.

Child Tickets

Change History (2)

comment:1 Changed 2 months ago by weasel

I suggested that for a write-restricted, world readable wiki. I have no opinion or ideas on having something that is read restricted.

comment:2 Changed 2 months ago by atagar

Resolution: wontfix
Status: newclosed

Hi Hiro. Gave more thought to it this morning and think I'm gonna close this. I no longer organize gsoc so I don't have nearly as much use for one as I previously did. TPI also replied to say this wouldn't work as a replacement for any of their internal svn usage. As for the tor-internal@ membership list I'm leaning toward dropping it. Personally my preference would be for the membership to be public (and hence on trac) but I'd rather not have the headache of asking for consensus from ninety people.

We can always reopen this if we have a more compelling need for it in the future.

Note: See TracTickets for help on using tickets.