← Back to team overview

meadl-devel team mailing list archive

mEADL Hardware change & blueprints

 

Hola All,

As you can gather from the launchpad updates, I have been working on
getting the hardware ready for development. I decided to switch from the
ArduinoBT board to the normal Arduino plus a Bluetooth module called
Bluesmirf. This change has no effect on any other work and development
can continue as expected since both solutions work exactly the same, the
reason for the change was a minor cost reduction and the fact that the
normal Arduino board is a bit easier to deal with when programming,
testing & debugging. Also, since it is more widely used, there are lots
more resources we can potentially leverage in the future.

I also take this opportunity to remind everyone that in order to start
coding we absolutely and with no exception need to have the appropriate
documentation proposed and accepted. Some of you have started coding
without even general specifications, and although I understand that some
of your coding is part of the learning process, you are running into the
risk of doing work that may have to be re-written or re-designed later
on, so I think it is worth to do it properly from the start.

In order to work on any feature, program, or task, we need a blueprint.
If you are working on something that there is not a blueprint for, then
please add it using this form:
https://blueprints.launchpad.net/meadl/+addspec

If you are eager to start working and we haven't yet defined what
exactly you will be doing, suggesting a blueprint for it is also the
best way to get the ball rolling.

Blueprints, specs and reports are essential for the success of an open
source project, so please don't underestimate their role in helping
coordinate the work. Of course, I also encourage everybody to read and
critique other's blueprints. The whole point of this exercise is to make
sure we all know what others are doing so we have a chance to contribute
suggestions, ideas, thoughts, etc...

cheers!
Jorge