figure out what we want/need
ASK: could we put together a survey asking everybody what extra expertise would be helpful?
find people who might be a match
trust but verify
Not sure what the current system is here (though the Wiki does mention one). Evaluating a number of tools that might be a good fit.
get them up and running
My onboarding was a little unguided
This could be a test of an employee… self-starting is a nice trait but if we want to try measuring that we should do it deliberately.
/Users/null/Desktop/IMG_8152.jpg
In the more general case here are some of the things that I had some question marks on.
idea: maybe hire freelancers with some tricky little task and recruit ones that impress us
idea: a contest where the winner gets their name engraved into the satellite
idea: pretty badass to have a live image of the Earth from one of our satellite’s as the homepage background
Would like to setup a better password manager
Meldium was in the same YC batch as we were. $1 million in funding (which doesn’t seem like a lot to me but still)
providers: (Meldium, Last Pass Enterprise, Okta)
Comparisions
comments on producthunt
comments on HackerNews
Actually I don’t really know anyone, their history, or their realm of experience/expertise.
ASK: is a centralized contact info/bio/expertise page something that'd be valuable to create?
Not well acquainted with IRC. Managed to get account but still have to learn.
Putting together a list of features that people want in their communication tool would be interesting.
I got access to Atlassian but it was a little… non-intuitive (at least compared to tools like Trello or )
Training definitely required.
the process is a little unclear. for instance I ran into a problem on one of the repos where the code wouldn't build. Not sure where to put this. Like the obc-server instructions fail because there's no wscript file in one of the libraries (which itself is a seperate repo, or needs to be)
Wiki shares the problem that plagues all wikis. Stuff is outdated but it’s not clear what.
Tests stay up to date because they break if the code does. Documentation needs to do the same thing.
Strikingly was a website in our YC-batch.
ASK: do we have a designer onboard? if not, objections to mocking up a page there?
This was drawn from the drawn from our Google Doc.
If a site isn’t supported you can still track and share the password. You just can’t automatically login and take advantage of other features.
99Designs
Amazon AWS
Amazon AWS Billing Account
Apple Developer
ardusat@gmail.com
Atlassian Account
ebay
Facebook
FedEx
GitHub Chef Deployment User
github CI user
godaddy dns account
heroku
Loggly
MailChimp
my.atlassian.com
NanoSatisfi Youtube
oDesk
Send Grid
Skype for NanoSatisfi
Sqwiggle
taskrabbit
Twitter
UPS
UserVoice
USPS
Vagrant Cloud
AdStage
Afternic
Apple Account
Codebender
Double Telepresence Robot
Forumatic
Google App Admin
Greenhopper Account
Kickstarter
MS BizSpark
myDlink Services
Newegg
Opscode Hosted Chef
SparkFun
vpn4all
admin @ acc (ardusatCommandCenter)
Business Cards
ESRI
Kubi
LEMOBC
space track
Tracking Toolkit
CI server (dev.nanosatisfi.com)
Comcast Edge Router (new office)
DCS-2332L
DS9 File Server (deep space nine)
ground station bootstrap account
irc
jenkins@dev.nanosatisfi.com
JohnLeguizamo(5GHz) network
Mac Mini (1 of 2 - Main Room)
Mac Mini (2 of 2 - Conference Room)
Mac Mini (sf-intr-mini) (3 of 3) Integration Room
Nanosatisfi
nanosatisfi wifi
Nanosatisfi_guest
Nanosatisfi_private
netgear wireless router admin
Office Subversion Server (10.1.10.217)
sonic.net router