If people are working on both Gizmocopter and POGO and now some folks are modeling the testing device (GizmoCopter is a model, right) then I think it would be quicker and cheaper to build POGO and crash it a couple of times (or maybe you get lucky!). It would probably be more fun too! Just saying your wiring will work because you will follow some set rules just ain't real. You have enough space at the ranch to build a safe tethered test device. It makes a lot more sense then modeling a model. Perhaps working in tethered 2D would be better.

David Weinshenker wrote:

Alex Fraser wrote:


What is the sequence or plan to get the Gizmo Copter Hardware
transitioned into POGO? When will the actual real computer controller
get in the real POGO airframe. I'm not trying to force a schedule or
hurry anyone up, I'm looking at the process and not seeing the plan.
Is there a cutoff point for Gizmo copter? Will the flight computer be
used to test the engines? Are the folks involved in building
GizmoCopter's airframe the same folks doing the POGO airframe? If they
are not won't they go through post partum depression? "Oh my poor baby"
in the hands of the POGO brutes. I am being unserious here, but in
industry wouldn't the old crew get laid off? I have been on enough
projects to know that when a crew gets toward the end of a project a
little "milking the cow" happens. THIS IS human nature and if you don't
make sure Gizmo folks transition in the organization, officially
transition, they will not let their baby go. This is what you might call
organisational slosh.



There's enough overlap of people between projects that that sort of thing
really isn't a problem. It's not like Gizmocopter (or any of our endeavors) is in the kind of "separate organizational box" that you seem to be imagining... and the concept of "transitioning within the organization" assumes a formal structure not in evidence.


-dave w
_______________________________________________
ERPS-list mailing list
[EMAIL PROTECTED]
http://lists.erps.org/mailman/listinfo/erps-list






--
----<<<<<<<<<<<<<<<<<
........ Alex Fraser  N3DER .........
......... [EMAIL PROTECTED] .......
[~]_>^</\-[~]_>^</\-[~]_>^</\-[~]_>^<


_______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list

Reply via email to