Minutes of SRCF executive meeting, 11th May 2014
The meeting was held on Friday 11th May 2014, between 7:30pm and 10pm, at The Castle, Castle St, Cambridge.
- Tejas Guruswamy (Chair, Sysadmin,
- Daniel Richman (Secretary, Sysadmin,
- Lev Livnev (Junior Treasurer,
- Alec Wright (Publicity Officer, Sysadmin,
- Charles Board (Co-opted,
- Malcolm Scott (Sysadmin,
- Andrew Cooper (Sysadmin,
Apologies for Absence:
- Michael Hsu (Sysadmin,
- Souradip Mookerjee (New sysadmin,
- Daniel Thomas (Sysadmin,
Review of minutes of previous meetings
- Two 4TB disks are on order: Ian Abel (
iga20) bought one; the SRCF bought the other (Lev has reimbursed Malcolm for it).
- The old disks are of little use; they may as well be spares for the machines that still use them.
- To summarise, three of the four 4TB disks were personal donations; one from each of Dominic Benson, Andrew Cooper and Ian Abel. Action (Tejas): Thank them again.
Executive meeting of 17th Jan 2014
- CUER: we didn’t give them a VM, we gave them more disk quota on pip.
- Removal from mailing list: case closed; Andy and Tejas processed both the outstanding requests and a year or two of backlog.
- News server: still pending
- Reminder (sysadmins): Change the shared mailbox password on the 1st Oct each year.
- The Hack day was a success; but we need another one (after exams; before may week). Action (Daniel): Doodle poll the sysadmins.
Executive meeting of 11th Oct 2013
- We still haven’t told users.
- People are liable to ignore warnings now (exams) and over the summer. We could break websites advertised at the societies fair, but we really don’t want to wait until after it.
- Action (Malcolm): Using the web logs or otherwise, figure out which higher-traffic sites are liable to break.
- Action (Tejas): Tell users that we’re going to deprecate
srcf.ucam.orgon the 1st July…
- …then we’ll actually do it a month later (after warning people again).
- We will have to explicitly book a back up room.
- Proposed dates are the Thurs & Fri before May Week (12th & 13th). Avoiding clashes is infeasible, so we should just go ahead and organise it.
- We’re planning to acquire Pimms from Trinity Hall, and Pizza from Perfect Pizza.
- Having a Key Signing Party at the Garden Party was proposed.
- Action (Charles): Investigate booking with Trinity Hall.
Bank mandate forms, etc.
- The relevant forms were signed by the Chair and Junior Treasurer.
- They need to be signed by the Senior Treasurer; Lev will visit Bob soon.
SSL certificate renewal
- … has been done by Malcolm, as has the reimbursement of its cost.
Cancellation of expired accounts
- We’ve almost run out of people to ask at the UCS; they have all told us to use LDAP…
- LDAP: Only about a dozen people will be a problem. We’ll have to maintain a whitelist of people and how long they are staying / how long the exception lasts.
- The UCS don’t seem to see this as a big issue(?).
- Proposed new membership policy:
- You can join, and become a user if you’re a current university member.
- We cancel your account (remove user-ship; keep membership) if we can no longer contact you. If you change your SRCF email address to a non-cam one, this will mean you keep your account / user status after you leave (an intended consequence).
- Practically, this would be implemented by us (only) cancelling people when we get bounces to emails sent to the maintenance lists. It would require development of some bounce handling.
- If we later have to change our mind we’re going to annoy people.
- … Action (Malcolm): Talk to Bob (since Lev needs to talk to him in person anyway); be open about our plans and see what he thinks.
- The UCS is being renamed (to the UIS), and is getting new management. Their policy is liable to change soon.
- Interim decision
- Whatever we decided to do in the future, users to which emails bounce will be cancelled.
- …so we can start doing this now, not least because receiving such bounces is annoying.
- Sysadmins aren’t obliged to act on bounces if they can’t be bothered.
- Sysadmins that decide to cancel in response to a bounce should forward the relevant bounce to the shared mailbox, along with a note.
Possible stash order
- People are keen for T-shirts.
- Last time payments was a bit messy; we should be more organised and demand money in advance.
- Keep it simple: logo and black t shirts.
- Action (Alec): Investigate, possibly using PANDIS, acquiring a new logo and/or re-branding. If it fits on the current website / is within the existing colour scheme, that would be easier, but an overhaul could be possible.
- Action (Alec): (having done the above) figure out what should be on the stash.
- We have two new servers.
- They officially belong to Frank Stajano.
- In practice one belongs to us; we would like something in writing documenting this on the wiki.
- Malcolm has summarised the state of affairs as we see it in an email to to Frank, who replied to say “yes, that’s correct”.
- The new servers are substantially better than pip.
- The current plan: the box owned by us becomes pip (via moving pip’s hard-drives into it), and the old pip hardware is added the XenServer pool.
- This gives us a backup plan if pip breaks: move the disks back.
- The rack is now full, but:
- this doesn’t need to be a problem,
- we can remove Tyan boxes from the XenServer pool without issue.
- The other one is being set up as a security playground: currently, it only has a bare XenServer install.
Any other business
executive@has spiked in spam; we’re on a really awful list.
- She’s on Maternity leave and has been over quota for ages.
- The cause is a 500MB logfile.
- Action (Sysadmins):
SIGHUPher server and tell her what we’ve done.
- We have hefty sysadmin inconsistencies; the following do not match:
executivegroup accounts on pip
- the list on the website
- minutes from meetings / committee ratification of new sysadmins
- Action (Executive): Consolidate passwords (internet banking, PayPal, etc.) and then (using something equivalent to symmetric encryption) store them in one location, to make it easier to hand over to new treasurers.
- Thank all those that have donated 4TB disks for pip.
- Tell users that we’re going to deprecate
srcf.ucam.orgon the 1st July.
- Resolve inconsistencies in various sysadmin lists.
- Using the web logs or otherwise, figure out which higher-traffic sites are liable to be broken by the
- Talk to Bob about user cancellation; be open about our plans and see what he thinks.
- Doodle poll the sysadmins; organise a new hack day.
- Investigate bookings at Trinity Hall for the Garden Party.
- Investigate, possibly using PANDIS, acquiring a new logo and/or re-branding.
- (having done the above) figure out what should be on the stash.
ez232’s large log file,
SIGHUPher server and tell her what we’ve done.
- Change the shared mailbox password on the 1st Oct each year.
- Consolidate passwords (internet banking, PayPal, etc.) and then (using something equivalent to symmetric encryption) store them in one location, to make it easier to hand over to new treasurers.