Keep Track of Team Computers

frc-4931 / 2014-Design

The files, issues, wiki pages, etc. for the design of our 2014 FIRST Robotics Competition robot

MIT License

1 stars 0 forks source link

Keep Track of Team Computers #73

Closed Polluxium closed 10 years ago

Polluxium commented 10 years ago

A list, or sign up sheet.

Zabot commented 10 years ago

Both classmates are now labeled.

randej commented 10 years ago

Also planning to get label maker so we can label all the club laptops. Right now I have Admin, Elec, and Mech (not sure what to do with #4).

Admin has Open Office, Dropbox, and that’s about it (I’ve uninstalled LabVIEW and CAD stuff to max drive space).
Elec has AutoCAD Electrical, Dropbox, Open Office, and LabVIEW (maybe?). Inventor would be nice if we have the room…
Mech has Autodesk Inventor, Dropbox, Open Office, and ?
Laptop #4 should be??

rhauch commented 10 years ago

Perhaps the fourth laptop should be for admin??

randej commented 10 years ago

Was thinking second Admin and/or programming: Eclipse, Git, LabVIEW, etc. Adam had the same thought. Since Admin really doesn't use much drive space, perhaps two identical admin/prog machines?

rhauch commented 10 years ago

Two identical sounds okay. We'll just will have to be careful about Git and GitHub, since it's very important to maintaining the author of the code. Any machine with programming may have to have separate accounts for each programmer.

agausmann commented 10 years ago

Yes, we should have a user for admin, and individual users for programmers.

On Mar 3, 2014, at 11:49 AM, Randall Hauch notifications@github.com wrote:

Two identical sounds okay. We'll just will have to be careful about Git and GitHub, since it's very important to maintaining the author of the code. Any machine with programming may have to have separate accounts for each programmer.

— Reply to this email directly or view it on GitHub.