Posible project

w3nlb at amsat.org w3nlb at amsat.org
Fri Aug 10 16:08:19 UTC 2007


Hi All,

I agree.  Documentation is needed.

Greg thinks this will just be a shim.

Greg:
Could you please provide copies of your previous correspondence with 
this client and an example of a "shim" that we could use as a pattern 
for this effort?  A pointer into LDD 4th would suffice if an example 
is presented there.

Robert:
Could you please send me a short CV and let me know what your 
strengths are, what language(s) you prefer, etc., and any comments 
you think relevant.  And a general assessment of your productivity 
would be of interest... 10 lines/day, 100, 1000, 10000???  How much 
time could you expect to devote to the project per week?

The next step should be to define the scope of effort and determine 
whether additional resources are required.  Since Greg has an idea of 
the type of driver required, perhaps he could provide a reasonable 
effort of the time/effort required to write same.

I should contact the client, picking up that conversation where Greg 
left off.  I'd like to get our preliminaries out of the way so I can 
make that contact by Monday 20 August.

What about source code management?  There has been some chaos in the 
kernel tree over this particular subject.  What is the current 
standard?  Are we obliged to use it for our development work?

I think our detailed correspondence regarding the project would best 
be done off-list, among Greg and the participants, which at present 
appear to be Robert and myself.  Add Josef to the list.  I don't know 
whether he's a participant or a cheer leader ;-)  But his help and 
advice are certainly welcome in either role.

Suggestions, comments, ???

Thank you very much.

Leigh


> 
> Hi Leigh
> 
> > How do we proceed?
> 
> Greg said he had some limited contact with them before by email.  So I
> think the fist step is try to and follow on from those emails.
> 
> I think the main thing I would need to get started would be more
> information on the current user applications, functional specifications
> and detailed datasheets for the device(s).  Hardware access would be
> nice but isn't an initial requirement.
> 
> > This is my first one.
> 
> Me too. :)
> 
> Robert





More information about the prjmgr mailing list