SEDSAT-2 Meeting Transcript 20070204

From SEDSWiki

• Pradeep Nair: I'm not sure tho..
• Pradeep Nair: Aaron?
• Pradeep Nair: must be late night there..
• Kirk Kittell: 6:20 am in his time zone
• Pradeep Nair: oh..ok..
• Geoff: k I'm here
• Kirk Kittell: 5 people have turned in applications so far
• Pradeep Nair: in all?
• Kirk Kittell: Geoff and Pradeep, plus 3 new participants
• Pradeep Nair: ok..
• Geoff: Mike said that he'd be able to make it at 8am tho
• Kirk Kittell: and I have received email questions from 3 or 4 others
• Geoff: so he probably got held up or is sleeping in, dunno
• Pradeep Nair: Juan, Nirupam and David ( I think)..right?
• Kirk Kittell: Yuki Takahashi is the third
• Pradeep Nair: ok..
• Kirk Kittell: Japanese, but from CalTech
• Kirk Kittell: he is a friend of a friend
• Pradeep Nair: ok.
• Tom Nordheim: I'm trying to get my friend to apply for the project, the one that worked

with me on the other cubesat projecgt

• Kirk Kittell: Per Magnus?
• Geoff: cool
• Tom Nordheim: no this is someone else, but per magnus would definitely be an asset to this

project

• Tom Nordheim: he's not sure yet though
• Geoff: per magnus, cool name
• Geoff: heheh
• Kirk Kittell: ok
• Tom Nordheim: he hasn't startet his university education yet(he'll be starting here next year

probably) but is very knowledgable when it comes to embedded electronics/electronics in

general

• Pradeep Nair: ok..
• Kirk Kittell: it doesn't matter if he is univ-educated -- what students don't know, the mentors

can assist

• Kirk Kittell: ok
• Kirk Kittell: let's have a boring meeting
• Kirk Kittell: after today, we will assign a leader for each meeting -- in charge of making an

agenda and reminding the list during the week

• Pradeep Nair: makes sense..
• Tom Nordheim: sounds like a good idea
• Tom Nordheim: so what is the agenda for today?
• Kirk Kittell: I want to cover our "standards" for the project -- how to manage our

information

• Pradeep Nair: and present drawings and share it?
• Kirk Kittell: such as when to use ProtoForge and when to use the wiki
• Kirk Kittell: we should write this in a guide for new team members
• Kirk Kittell: do you guys have anything?
• Kirk Kittell: oh -- and we should get a topic for Prof. Murthy
• Pradeep Nair: Aaron was telling me about trying to do a video demo for Protoforge..
• Tom Nordheim: imaging would be a good one
• Kirk Kittell: Chris noted that the seds.org server can handle streaming video, Pradeep, if he

is interested in video

• Tom Nordheim: what kind of wavelengths we could look at, what kind of things we could

observe etc

• Kirk Kittell: can you write that in an email to Pradeep?
• Tom Nordheim: yes sure
• Tom Nordheim: I was going to give it a little more time, to come up with something more

specific

• Pradeep Nair: no, something like YouTube would be good..
• Kirk Kittell: sure you can take more time, Tom -- we probably don't need this until we have a

full team

• Aaron: Hey guys
• Pradeep Nair: Tom, i think you have Prof. Murthy's email id..
• Pradeep Nair: you can send it directly or send it through me ... no problems..
• Tom Nordheim: ok, I can email him directly then Hi Aaron
• Aaron: Still waking up here
• Pradeep Nair: Good morning, Aaron.
• Aaron: What's happening?
• Kirk Kittell: going to go over some standards here
• Kirk Kittell: where to do things and keep our information
• Kirk Kittell: just starting now, actually
• Aaron: Cool
• Kirk Kittell: did all of you understand what I meant by "design notes" on the wiki?
• Geoff: quick reminder?
• Kirk Kittell: for example, http://wiki.seds.org/index.php/SEDSAT-2_Power
• Kirk Kittell: previously all of the notes for your subsystems were added to a single page
• Kirk Kittell: -- the main subsystem page
• Pradeep Nair: ok..
• Kirk Kittell: I moved them to individual pages based on the day you create them -- like a lab

notebook

• Tom Nordheim: I see
• Pradeep Nair: ok..
• Tom Nordheim: but we should mainly keep our notes on the blog right=?
• Kirk Kittell: this is what I want to discuss
• Aaron: So the wiki moves them automatically?
• Tom Nordheim: since we are still in such an early phase....or what?
• Kirk Kittell: I am experimenting with the information handling and want advice
• Tom Nordheim: hmm
• Kirk Kittell: wiki doesn't move them automatically -- a new page must be created
• Tom Nordheim: I think maybe we should keep the wiki up to date as well
• Aaron: Ok
• Pradeep Nair: there are also benefits of having one page on one topic..
• Pradeep Nair: depending on that person's seperation of it..
• Tom Nordheim: since it doesn't give a too good an impression if all the subsystems are

empty...

• Pradeep Nair: for eg..one page to do with thermal analysis...etc..
• Pradeep Nair: or you can do it both ways, but that would be easier, if the Wiki did it by

itself...

• Kirk Kittell: this is the problem... the blog is very easy for adding daily subsystem notes, but

it is a different application than the wiki or ProtoForge

• Kirk Kittell: so it will not be visited as frequently
• Kirk Kittell: and if we keep all of our design info on the wiki, we can search for it
• Kirk Kittell: I'll propose something, then tell me what you think --
• Kirk Kittell: -- esp. Aaron about the use of PF in all of this --
• Aaron: You could just do your entire design in Protoforge
• Pradeep Nair: ok.
• Aaron: that's what it is meant for
• Aaron: start with broad ideas at the higher levels
• Aaron: then work your way down to lower levels doing your researchh as you go
• Aaron: associating all of your thoughts and research about a particular requirement with

that requirement

• Aaron: so it is easy to find in one place
• Aaron: For example,

http://www.protoforge.org/requirements/index.php?pid=49&rid=10&

• Kirk Kittell: is there anywhere to keep notes and set up a page based on each subsystem?
• Kirk Kittell: it seems that PF is mostly a systems engineering tool, but I might not understand
• Aaron: You can keep notes in the discussion forum for a requirement
• Aaron: that requirement is owned by someone in a subsystem
• Aaron: pretty soon I'll add a "tagging" function
• Aaron: and a subsystem hierarchy
• Aaron: but I havn't got to that yet
• Kirk Kittell: that seems to be one of the things that is missing to me -- if I am the power

subsystem lead and want to record notes about research and design for that, I would want

my own page to do it

• Aaron: Oye, the new colors looked better late last night
• Aaron: lol
• Kirk Kittell: never looks good the morning after
• Kirk Kittell: Tom, Geoff, Pradeep?
• Geoff: lol
• Kirk Kittell: how would you organize all of this?
• Aaron: Great suggestion, OK, when I add the subsystem hierarchy I will makke sure to have

a notes section

• Pradeep Nair: it makes sense now as to what Aaron is talking about..
• Aaron: who me?
• Tom Nordheim: I think there are advantages to mainly using protoforge for our own use
• Tom Nordheim: if you know what I mean...
• Pradeep Nair: but......(there're always buts) when people are working on the design...how can

you cross check etc..

• Aaron: cross check?
• Pradeep Nair: Protoforge will work well if we had a wise choice over the number of

requirements in each subsystem..

• Pradeep Nair: but no one can make that..
• Aaron: the number of requirements is not so important
• Aaron: some subsystems will have a lot of requirements and others will havee less
• Pradeep Nair: cross check as in....since sub-systems will depend on each other how will one

person find out about that part from other person..

• Aaron: it depends on the complexity of the system
• Aaron: yes Ii see
• Pradeep Nair: how will structure know from payload about how to place the payload....just as

an example..

• Aaron: the subsystems will need to look at other subsystem requirements
• Pradeep Nair: I don't see this happening even in the Wiki...
• Pradeep Nair: maybe it's too early..
• Aaron: well if structures calls out a requirement to be 10"x10"x10"
• Pradeep Nair: yes, and in some cases, these requirements will not be worded as the other

person would have..and hoped to find it there..

• Aaron: and associates a cad model of the structure
• Pradeep Nair: well, I'm not able to communicate very well, but i'm trying my best.
• Pradeep Nair: go on, aaron..
• Aaron: payload can see the reequirement and download the cad model to make sure they'll

fit

• Aaron: interfaces are always a big problem
• Pradeep Nair: is there a way to search requirements?
• Aaron: you need to know exactly where the holes line up, etc
• Pradeep Nair: well, sorta...yeah..
• Aaron: aha, um, nope there isn't
• Aaron: but there will be in a few hours
• Aaron: lol
• Pradeep Nair: so, I won't be sure...but a search of requirements doesn't make sense either..
• Aaron: make sense in what sense?
• Pradeep Nair: I mean it sounds silly..
• Pradeep Nair: searching requirements..and sub-requirements and sub-sub-requirements..and

all.

• Pradeep Nair: but it's sorta needed..especially when there'll be hell of a lot of requirements

that everyone has put up..

• Aaron: ok, well hopefully since the requirements are in a hierarchy it should be easy to find

what you're looking for just by starting at the top and working your way down the branches

to whatever leaf you're looking for

• Pradeep Nair: Kirk, how does the wiki overcome this?
• Aaron: I will add a search function (I've been meaning to do that)
• Kirk Kittell: the wiki overcomes nothing; it is a collection of different pages that you can

link together in any manner you want

• Kirk Kittell: not the same type of organization
• Tom Nordheim: well realistically wouldn't there be a team in charge of systems eng or

integration?

• Tom Nordheim: they would make a report I suppose? where the different requirements are

evaluated/listed

• Pradeep Nair: but even then, we should think about how he'll look into all this requirements

or documents..

• Amrut: hi Team.. sorry for being away
• Aaron: yes, in industry there is usually a team for systems engineering
• Amrut: i was bit busy with IAC07 Student Session
• Aaron: but this is a very wasteful practice
• Aaron: the expert engineers should be doing it as an after thought
• Pradeep Nair: which?
• Aaron: since it takes very little time when you know what you're doing
• Tom Nordheim: I can see the arguments for it at least
• Tom Nordheim: we are after all a very diverse group
• Tom Nordheim: maybe more so than most other engineering projects...
• Aaron: In a distributed project the systems engineering becomes very important so you

don't duplicate efforts

• Aaron: I think the best thing for you guys to do is to start designing from the top and work

your way down

• Aaron: Call out some high level requirements and agree that is what you want to do
• Aaron: then think about each requirement individually and see what kind of lower level

requirements you end up with Tom Nordheim: that brings me to something that I feel should be defined...... Tom Nordheim: and which I feel is very obvious when you look at the comments for the MFS Tom Nordheim: we need to know wich orbit we're aiming for

• Aaron: You need to decide on a path to take, narrow your focus, and work on that one part

for a while

• Aaron: You will have no control over your orbit
• Tom Nordheim: you can't really evaluate payloads/communication/power/adcs if we don't

have orbit paramtres

• Tom Nordheim: yes I know
• Aaron: You'll be lucky to get an orbit
• Tom Nordheim: that's not what I'm talking about
• Geoff: right! that reminds me
• Tom Nordheim: I mean where we want to be inserted
• Geoff: what orbit are we picking?
• Tom Nordheim: LEO, GEO etc
• Tom Nordheim: that's what I'm talking about!
• Kirk Kittell: see cubesat.org for their typical orbits
• Geoff: oh
• Aaron: Does the cubesat site talk about this?
• Geoff: *scrolls up*
• Tom Nordheim: LEO
• Kirk Kittell: at this point in the project, one of you needs to contact the CubeSat people and

register

• Kirk Kittell: a volunteer?
• Pradeep Nair: I'll go..
• Tom Nordheim: most cubesats are LEO....actually all of them probably
• Pradeep Nair: for volunteering and stuff I mean..
• Pradeep Nair: low earth orbits..?
• Tom Nordheim: yes
• Pradeep Nair: so, what can andcan't you do at LEO..
• Geoff: (9:03:01 AM) Aaron: You will have no control over your orbit

?

• Tom Nordheim: this affects communications for example
• Tom Nordheim: and it affects imaging, both in terms of resolution and angles
• Tom Nordheim: and power to some extent
• Pradeep Nair: I mean, what kind of payloads can we do at LEO...
• Tom Nordheim: I've basically been working with the assumption of an orbit of 600km-ish
• Kirk Kittell: Pradeep is going to register our team at cubesat.org -- he should ask what the

projected upcoming launches are

• Kirk Kittell: they have used different rockets, so no standard orbit (but I may be wrong)
• Kirk Kittell: ask Purvesh about that
• Pradeep Nair: things to do?
• Aaron: I think the orbit you get will depend on what the main payload of your launch is
• Aaron: the launch you get will just depend on if there's space for you and if you have a

working satellite

• Geoff: well, which orbit would be best for our goals if we want to keep a constant

alignment with the sun?

• Geoff: sun orbit?
• Tom Nordheim: sun-synchronous orbit
• Geoff: is that low enough for good pictures?
• Aaron: You may have a hard time getting a sun synchronous orbit though
• Geoff: how come?
• Aaron: You probably want to design for worst-case scenario
• Pradeep Nair: huh..so we have to worry about traffic too?
• Tom Nordheim: not many things are launched into that orbit you see...
• Geoff: how come?
• Tom Nordheim: and it's far higher than LEO
• Aaron: true
• Tom Nordheim: because it's an uncommon orbit
• Aaron: It'd be nice to get a lunar orbit, but not likely
• Geoff: uncommon to what degree? 1 launch per year if that? 20 launches per year?
• Tom Nordheim: and if we wanted constant exposure you could always lock your satellite in a

lagrangian point...but how likely is that...eh not very

• Geoff: why is that not likely?
• Tom Nordheim: because that's far way from the earth
• Tom Nordheim: like SOHO for example
• Tom Nordheim: http://en.wikipedia.org/wiki/Lagrangian_point
• Tom Nordheim: in a lagrangian point, your satellite is basically locked at a specific point by

different gravitational forces from the sun, other planets etc

• Tom Nordheim: the earth in this case I believe
• Kirk Kittell: what is the range of previous CubeSat launches? 600-900km?
• Tom Nordheim: yep
• Pradeep Nair: so, since many cubesats are in LEO, won't that be too congested for

launching another cubesat?

• Tom Nordheim: in what way?
• Aaron: Nah, there's plenty of space in LEO
• Kirk Kittell: space is big
• Tom Nordheim: hehe
• Pradeep Nair: but won't that also limit the sort of options we can try out...
• Kirk Kittell: yes
• Pradeep Nair: we might just be duplicating stuff..
• Aaron: "It's an awful waste of space"
• Tom Nordheim: depens on what we're doing
• Tom Nordheim: *depends
• Aaron: Part of engineering design is realizing what you can and can not do
• Tom Nordheim: a GEO orbit might be less practical for certain payloads
• Pradeep Nair: but is it practical for a cubesat?
• Pradeep Nair: I think we should think about that first..
• Aaron: GEO is 42000 km
• Tom Nordheim: ok:
• Pradeep Nair: sorry, my knowledge on orbits is very close to zero..
• Aaron: cubesats usually go to 600-900 km
• Tom Nordheim: temperatures are more extreme
• Tom Nordheim: way more radiation
• Tom Nordheim: and the cost of the launch ofc
• Tom Nordheim: both those abovementioned factors adds to cost/complexity as well
• Tom Nordheim: since we might need space grade/military grade components/rad hardened
• Geoff: GEO is more radiated?
• Aaron: GEO actually has less radiation I believe because it is above the van allen belts
• Aaron: it is the trapped protons in the van allen belts that really get you
• Tom Nordheim: ok sorry, my bad then
• Aaron: these are high energy particles from the sun that bounce back and forth between the

poles along the magnetic field lines of earth

• Tom Nordheim: but generally we wouldn't insert the satellite into a van allen belt...
• Aaron: the really high energy ones get down into the atmosphere and create the northern

lights

• Aaron: there is something called the South Atlantic Anomaly
• Aaron: it is a portion of the belts that comes very low
• Aaron: whenever space station goes through the SAA the electronics start seeing problems
• Tom Nordheim: but the space station has a pretty low orbit
• Pradeep Nair: how low can you go on, on LEO..
• Tom Nordheim: http://en.wikipedia.org/wiki/South_Atlantic_Anomaly
• Aaron: yeah, the space station is pretty low, that's why it does pretty well every where

else but sees trouble while passing over the South atlantic

• Aaron: almost any orbit you get for your cubesat will most likely go through the SAA
• Geoff: cool
• Aaron:
• Tom Nordheim: hmm that is something which we will certainly have to take into consideration

when designing our satellite

• Pradeep Nair: can you adjust orbit so that we go through the SAA when we're eclipsed...so

that it'll be a time when we don't work that much?

• Aaron: that would probably be hard to do
• Geoff: good idea
• Geoff: how so?
• Geoff: oh, we'd have to predict eclipses?
• Tom Nordheim: we have limited ways to adjust our orbit as well..
• Aaron: you won't have any control over your orbit, first of all
• Kirk Kittell: you probably won't adjust your orbit with a CubeSat --
• Tom Nordheim: extremely limited
• Kirk Kittell: your orbit is where the rocket drops you
• Pradeep Nair: can't we avoid the SAA..?
• Tom Nordheim: well theoretically we have discussed having microthrusters
• Aaron: and if you look at a ground track of a typical orbit
• Tom Nordheim: but it would not be enough probably
• Pradeep Nair: I mean by not going there at all..
• Aaron: over time you pretty much pass over every point in earth that is below the

inclination of your orbit

• Aaron: *on
• Kirk Kittell: you can not avoid anything in your orbit
• Aaron: Rad-hard parts are very expensive too
• Aaron: but there are other ways
• Kirk Kittell: it is just like putting a toy boat in a river -- it goes where the river goes
• Geoff: good analogy
• Aaron: You can have a monitor that keeps an eye on things
• Geoff: but yeah, what about thrusters?
• Aaron: and then resets it if there are problems
• Geoff: we haven't discounted that idea yet
• Tom Nordheim: I have looked into that very thing when we were thinking about an FPGA on our

last cubesat... how to recover from SEUs etc...

• Aaron: I think the cube is too small for a propulsion system
• Aaron: Cool tom what did you find out?
• Tom Nordheim: well that it could be done
• Geoff: ooh
• Tom Nordheim: at last as far as we could se
• Aaron:
• Tom Nordheim: but only if we had significant redundancy measures
• Aaron: I don't know too much about it actually, I'm mainly a software guy
• Tom Nordheim: FPGAs are very cool
• Aaron: but there are rad-hard FPGA's out there or you can use redundant self-checking

FPGAs to keep track of each other

• Pradeep Nair: ok, we've been discussing all day without getting any firm resolutions . we

started out with wiki etc..

• Tom Nordheim: we were aiming for the latter
• Tom Nordheim: since we were working with a limited budget
• Pradeep Nair: and are now talking about orbits..
• Pradeep Nair: any decisions?
• Pradeep Nair: what are we deciding to do about the wiki and protoforge?
• Aaron: I would recommend suggesting these types of things that we've been talking about

on protoforge

• Aaron: Say you think we need to be in a sun-synchronous orbit
• Aaron: suggest it as a requirement
• Aaron: then other's will discuss it on there and tell you that it is not likely
• Pradeep Nair: voting with multiple options would be better there and maybe after more people

come in..they might have a better suggestion..

• Aaron: if you make a good suggestion then other people will vote on it
• Aaron: yep, exactly Pradeep
• Aaron: and if you do it there other people will see what has gone on and not go down the

same dead-end paths that you will inevitably run into as you design your satellite

• Geoff: I think it'd be a better idea to offer up a selection of orbits rather than just one,

listing positives and negatives and reasoning for each, to let people choose which one, rather

than just yes or no

• Tom Nordheim: sounds good
• Geoff: we're more likely to get a final decision that way
• Aaron: making decisions will be the hardest part of all of this
• Kirk Kittell: Geoff: probably we will not get a choice of orbit
• Aaron: but you will need to do it
• Aaron: and you will learn as you go
• Kirk Kittell: there may only be one launch every year for CubeSats
• Aaron: but you won't learn anything if you can't start making decisions, somehow
• Tom Nordheim: http://www.eas.asu.edu/~holbert/eee460/spacerad.html
• Tom Nordheim: since we were dicsussing this
• Pradeep Nair: I just think we must decide before every meeting ends or atleast before the

next meeting begins...that's all...

• Geoff: one launch every year? :S crud
• Pradeep Nair: you can continue discussions..
• Kirk Kittell: ok, let's become organized here
• Kirk Kittell: several issues are in the meeting now --
• Pradeep Nair: Wiki/Protoforge, Orbits..
• Kirk Kittell: 1) use of protoforge and wiki, 2) orbits, 3) radiation
• Aaron: http://www.protoforge.org/requirements/Requirement.php?id=76&
• Kirk Kittell: let's come to a decision about (1)
• Pradeep Nair: We can use both...
• Kirk Kittell: let's take a five minute
• Kirk Kittell: break
• Pradeep Nair: protoforge = decision making ; wiki = documenting
• Tom Nordheim: I think I have to leave in like 15min
• Kirk Kittell: take a piece of paper, or use a computer notepad, and make a proposal for using

wiki and PF

• Tom Nordheim: I agree with pradeep
• Kirk Kittell: ok, we will still finish before 15 min
• Kirk Kittell: take 5 min still to organize your ideas
• Kirk Kittell: I am starting the time now...
• Aaron: sounds good
• Kirk Kittell: 1 min
• Kirk Kittell: (4 remaining)
• Kirk Kittell: 2.5 min remaining
• Geoff: overall, how many launches per year are there, that transport cubesats?
• Kirk Kittell: see cubesat.org
• Kirk Kittell: not many
• Geoff: oh
• Kirk Kittell: http://cubesat.atl.calpoly.edu/pages/missions.php
• Kirk Kittell: basically, they take whatever launch provider will give them a good deal
• Kirk Kittell: 1 min remaining
• Pradeep Nair: ok...I've sent the mail reg. registration to CubeSat community...
• Kirk Kittell: ok
• Kirk Kittell: time is complete
• Pradeep Nair: the team members were optional..so I didn't mention them..
• Kirk Kittell: who wants to suggest a proposal first
• Geoff: I don't see anything about average number of launches that carry cubesats on 8

cubesat.org

• Geoff: oh
• Pradeep Nair: (Please go through mail...I've given 48 hrs time to respond..)
• Pradeep Nair: Use both. protoforge = decision making ; wiki = documenting
• Pradeep Nair: as in documenting before loading it on the website..
• Tom Nordheim: use protoforge for internal documentation, wiki for more "Public" stuff
• Tom Nordheim: like documentation as praddep said
• Tom Nordheim: *pradeep
• Pradeep Nair: Geoff?
• Aaron: Use protoforge as the War room , where very involved members make decisions

Use wiki for more publicly visible information and well refined documentation

• Geoff: so there's no definit number to the # of launches then
• Kirk Kittell: no
• Geoff: sounds fine with me
• Kirk Kittell: that is why Aaron said you'll be lucky to get a launch
• Kirk Kittell: do you have any suggestions?
• Geoff: I believed we were already doing just that
• Geoff: I see what you mean
• Kirk Kittell: ok, the summary seems to be this:
• Pradeep Nair: we have to use Protoforge more .... as a "war room"..
• Geoff: is there a calendar of schedules flights anywhere?
• Kirk Kittell: protoforgeecision making, esp. important internal decisions about design,

requirements, etc.

• Kirk Kittell: (why is that a smiley face?)
• Kirk Kittell: wiki: where we write things -- documents, notes, ideas
• Kirk Kittell: is this right? wrong?
• Pradeep Nair: (no space between : and d...)
• Pradeep Nair:
• Pradeep Nair: see?
• Tom Nordheim: yes
• Pradeep Nair: yep, Kirk..we can carry that..as voted in the meeting notes..
• Geoff: pf and wiki are fine, with the war room/doc thing
• Tom Nordheim: so we are all agreed on that?
• Pradeep Nair: ay..
• Aaron: yes, keep in mind though what a war room is
• Aaron: a place to suggest ideas, discuss them, and decide on them
• Geoff: I guess we could just settle on LEO, but I was hoping for something... less

ordinary, would be the easiest way to put it

• Tom Nordheim: we could for the moment design with LEO in mind(since we need some

paramtres to do anything at all)

• Tom Nordheim: and if some rare opportunity presents itself, then we could always seize it...
• Pradeep Nair: guys, can we wrap this up faster?
• Tom Nordheim: depending on where we are in the design process(how far)
• Pradeep Nair: put all ideas on which orbit you think will be good with pros and cons....and let

the team decide..maybe on Protoforge..

• Kirk Kittell: ok, here are some tasks from this meeting --
• Pradeep Nair: and send an email about it..
• Geoff: how much adjustment would a change in orbit affect?
• Tom Nordheim: a lot
• Kirk Kittell: Geoff: research the number of launches and possible upcoming launches (you may

need to email cubesat)

• Pradeep Nair: and send a link to us too?
• Pradeep Nair: after the research..
• Kirk Kittell: Tom: take some of your payload discussion above and make it into a plan for Prof

Murthy to teach us how to choose a system

• Tom Nordheim: will do
• Kirk Kittell: Pradeep: can you write up a policy about using wiki and PF together?
• Pradeep Nair: will try..
• Geoff: sure
• Kirk Kittell: maybe it is just a few lines, but we will introduce it to the team as our defined

method of working

• Kirk Kittell: and we will teach the new people (as we teach ourselves )
• Geoff: hehe
• Tom Nordheim: next meeting...
• Tom Nordheim: same time?
• Geoff: same bat channel, sure
• Geoff:
• Kirk Kittell: let's ask Lavina about the next time
• Kirk Kittell: we will just set the date
• Geoff: we've settled on 1300 gmt then?
• Kirk Kittell: yeah -- I changed my mind -- set the time
• Geoff: oh, right
• Kirk Kittell: but ask her if it is OK
• Pradeep Nair: we can send a mail to the list too..
• Kirk Kittell: who will be the next meeting leader?
• Kirk Kittell: volunteer?
• Geoff: yea
• Pradeep Nair: some don't seem to be aware..
• Pradeep Nair: will take care of this meeting...next meeting..
• Geoff: yup
• Pradeep Nair: I'm not sure about attending it...so can't...
• Geoff: http://hardware.slashdot.org/article.pl?sid=07/02/04/0643223&from=rss

from the no-part-of-that-title-is-not-freaking-sweet dept. hehe

• Kirk Kittell: ok -- Pradeep, you are responsible for creating an agenda and reminding the

group

• Kirk Kittell: you may need to ask each of the members if they have items for the agenda
• Pradeep Nair: eh, Kirk...I volunteered for this meeting..
• Geoff: unrelated sorry, just thought you all might like that
• Pradeep Nair: I'm not sure of attending the next..
• Kirk Kittell: next meeting, we need a volunteer for next meeting
• Tom Nordheim: I can do it...
• Kirk Kittell: ok, Pradeep, you can post the notes and transcript for this meeting
• Pradeep Nair: can we declare the meeting closed? Tom, for the next meeting...
• Kirk Kittell: http://wiki.seds.org/index.php/Template:SEDSAT-2_To_Do -- for now I am

using this as a to-do list (until someone makes a better way)

• Aaron: I've got to go, had fun, start posting some ideas as requirements and email me or

chat me with any questions you have, see you next time

• Pradeep Nair: it's a good way..like it already..
• Aaron: bye
• Geoff:
• Kirk Kittell: Geoff, do you have a minute
• Kirk Kittell: or anyone, really
• Kirk Kittell: just wanted to ask for advice about the blog
• Tom Nordheim: ok
• Kirk Kittell: how to use the blog?
• Geoff:
• Kirk Kittell: is it just a public outreach interface?
• Geoff: well, personally I'm not a fan of blogging
• Geoff: thus my lack of enthusiasm for using it
• Tom Nordheim: I feel it's good for just putting my thoughts out there
• Geoff: for what audience though Tom?
• Tom Nordheim: what we've been using it for already in other words
• Geoff: because the mailing list does just as well, I find
• Tom Nordheim: you don't really need an audience...
• Tom Nordheim: I find it useful for my own sake as well
• Tom Nordheim: a place to gather my thoughts
• Tom Nordheim: /dieas
• Tom Nordheim: /ideas
• Geoff: i suppose
• Kirk Kittell: I have a lingering feeling that it will be good for sponsors and potential team

members

• Kirk Kittell: the email list doesn't touch them, and the wiki seems too... esoteric or internal
• Tom Nordheim: it gives a realistic representation of the dynamics of our group/team
• Pradeep Nair: wiki seems like encyclopedia..
• Pradeep Nair: too much info..
• Geoff: I suppose
• Pradeep Nair: ok....this much will come in the chat transcripts..I have to leave now..sorry....
• Geoff: I just never know who my audience is, even for a blog
• Kirk Kittell: that is the hard part, Geoff, that's why I don't like to blog
• Kirk Kittell: (and I hate blog as a verb)
• Tom Nordheim: ok I have to leave now too, blog=yay
• Geoff: I mean, am I writing out my thoughts to myself, and letting others read them -- or

am I wring them with the audience in mind, talking to them?

• Tom Nordheim: see you guys later
• Kirk Kittell: later, Tom