[OpenRelief Developer] Teams

[al Hart]

In relation to CNC machines, I am down for one of these has everyone seen this posting at DIYDRONES http://www.diydrones.com/group/diydrones-cnc-project/forum/topics/gauging-interest-in-the-cnc-machine?commentId=705844%3AComment%3A890467&xg_source=msg_com_gr_forum
 
Alan 
 



From: karl at qdh.org.uk
Date: Thu, 14 Jun 2012 11:17:10 +0100
To: developer at openrelief.org
Subject: Re: [OpenRelief Developer] Teams








There's not a lot I can add at this stage before the teams become more structured but I'd just like to volunteer my time when there's a chance I could be useful.  I'm equipped at home with enough tooling to make bespoke parts for the drones should we need them, I also have access to CNC machines which cut carbon fibre parts for formula 1 cars; light and strong this could prove useful in the future though it does move away from the aim of keeping it all open source.


On the contrary there's lots you can do! We're currently designing an open airframe design and you seem to have all the hardware to do that kind of work, we should work closely on designing the airframe so we can fit it into a manufacturing process.


Manufacturing processes are difficult to open source, but providing the parts templates/designs and instructions will be open source. 


Do you have dropbox? we're currently using it for sharing the airframe wireframes.


http://db.tt/gpnZIH0 < will refer you to dropbox


BR,
 K








Anyway, just wanted to introduce myself.  Hope to work with some of you soon.


Cheers,


Matt



> From: karl at qdh.org.uk
> Date: Thu, 14 Jun 2012 10:51:27 +0100
> To: developer at openrelief.org
> Subject: [OpenRelief Developer] Teams
> 
> We're organised into some loose teams with some crossover already. I suggest we make certain people the contact for each team, and responsible for managing them.
> 
> My team proposals are as follows
> 
> * Communications: Andrew Back
> Andrew will manage all of the communications related stuff, including data gathering, protocol selection, hardware selection and of all the related topics. 
> 
> * Computer Vision: (John) Daniel Bell
> Andrew will co-ordinate the vision development team, proposing solutions and allocating tasks for vision experts to work with.
> 
> * Airframes, Flight systems & robotics: Karl Lattimer
> Co-ordinate efforts to design and build open hardware robotics which utilises both of the above technologies. 
> 
> 
> 
> What are we missing? Tough one, I think firstly we need to fill the gap for drone management. 
> 
> The task should be something like, a web application for managing a fleet of drones.
> 
> * Each drone has an allocated ID - the ID can be used to access information on that drone. 
> * A page for viewing drone information
> * A page for submitting drone information manually e.g. I found your drone, it's broken and requires these parts... 
> * A page for requesting the loan of a drone for testing purposes. 
> * A RESTful interface for updating raw data e.g. location, speed etc... 
> * A RESTful interface for uploading pictures/video and/or setting a video stream up.
> * A RESTful interface for retrieving drone data
> 
> There will obviously need to be some access controls on the drone management side of things. We'll need 3 roles for that which would be.
> 
> * Casual user/reporter - someone who uses our web tools to inform us about seeing a drone or finding a crashed drone.
> * A drone manager - someone who owns a drone, and manages that particular drone, or group of drones.
> * A drone - an actual drone which can access the site and push its data and receive information. 
> 
> This crosses over with the information management but crucially allows us a point of contact for recovery of the drones. With airframes plastered with our web URL we should be able to get information back from the public. 
> 
> This should be kept as simple as possible, we really don't want to go too crazy with it, most important is having it correctly internationalised. 
> 
> BR,
> K
> _______________________________________________
> Developer mailing list
> Developer at openrelief.org
> http://openrelief.org/mailman/listinfo/developer_openrelief.org
_______________________________________________
Developer mailing list
Developer at openrelief.org
http://openrelief.org/mailman/listinfo/developer_openrelief.org

_______________________________________________ Developer mailing list Developer at openrelief.org http://openrelief.org/mailman/listinfo/developer_openrelief.org 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openrelief.org/pipermail/developer_openrelief.org/attachments/20120614/59a94ed5/attachment.html>