Talk:2014-10-25 FCS Workshop

Notes from session

Two attendees incl. the lead

Anthony created a Hard drive 'Certificate of Assurance' for data wipe i.e. DBAN. This is stored in the Documents folder on the lead workstation. Printed out a few copies. We absolutely need to do this for certifying to certain donaters that their data will not be leaked.

We need SIGNAGE for the room, especially outside the door

We need some more & better tape: Scotch, Masking and Gaffer's tape. There are way too many cables along the floor to trip over. It's a hazard.

The Install Server Voltron is NO WHERE TO BE FOUND. How are we supposed to build systems using a CD/DVD every time? Really inefficient.

Generally the place was a mess. I spent 1/2 the time cleaning up misc. crap and organizing.

I could not get to the online hours spreadsheet http://calc.meshwith.me/fgseavolunteerhours it was just BLANK. I signed us in using the wire-bound folder and suggest the same for future sessions unless we can reliably get the online form to work.

Confirmed (1) server to be working, placed on the Outbound shelf for sale or grant. Another server (poweredge 1850) I configured/initialized the RAID1 logical drive but it would not boot from CD drive onboard, nor PXE thanks to the Voltron issue mentioned above. I would have tried the external CD drive but could not find the right USB cable.

I created Testing Hard drives page and found the cables needed to do so on LOOSE drives.

looks productive
The previous meeting we started to get inventory done. We also believed that things were a mess, and there was a computer that had a bad motherboard that I didnt' quite know what to do with for the last 4 meetings... I felt that getting the i nventory system working was more important.

I knew nothing about how to record hours, so we just did it in the event pages. if someone is there for the full event, they could mark that they had been there for their hours. It is good to know where the sign in form is, I believe that I didn't have access to it when someone tried to show me.

Logs of what happened in the meeting are appropriate for the actual event page, the happenings of an event is content.. talking about how to talk about stuff should probably go in the talk pages (imnsho)

We might want to create an event namespace, procedure: namespace fgsea namespace, (and then their associated talk namespace would be an odd number one above the other namespace)


 * proc: (everyone should be able to fix these, but alerts should go to people
 * event: (everyone should be able to edit this
 * fgsea: (staff and board should have access to this
 * dev:  (everyone should be able to make comments about their devices)
 * template: (for l33t haxor dudes, willing to test pages after they muck with it)

This way we can allow some people to edit procedures, but not events, and fgsea can be locked down for official bylaws and such. dev could be items, either sold or in our inventory, it could make importing and exporting our inventory easier...   I don't mind having everything be in the main namespace, and I don't mind people being able to edit a lot of things..