[minima] Re: pcbs for the minima
- From: farhanbox@xxxxxxxxx
- To: minima@xxxxxxxxxxxxx
- Date: Tue, 25 Feb 2014 09:24:28 +0000
Let's get on with it!
Sent from BlackBerry® on Airtel
-----Original Message-----
From: Thomas Sarlandie <thomas@xxxxxxxxxxxxx>
Sender: minima-bounce@xxxxxxxxxxxxx
Date: Tue, 25 Feb 2014 01:04:28
To: minima@xxxxxxxxxxxxx<minima@xxxxxxxxxxxxx>
Reply-To: minima@xxxxxxxxxxxxx
Subject: [minima] Re: pcbs for the minima
Sounds good to me. We can do more permissive licenses for the libraries if
there is ever a need for it.
I can make a pull request to GPL-ify the project.
Thomas
On Tuesday, February 25, 2014, <farhanbox@xxxxxxxxx> wrote:
> How about GPLv3? I'd love to see all the brach outs easily accessible to
> us. Shall we add gpl to our github account?
> Sent from BlackBerry® on Airtel
> ------------------------------
> *From: * Thomas Sarlandie
> <thomas@xxxxxxxxxxxxx<javascript:_e(%7B%7D,'cvml','thomas@xxxxxxxxxxxxx');>>
>
> *Sender: *
> minima-bounce@xxxxxxxxxxxxx<javascript:_e(%7B%7D,'cvml','minima-bounce@xxxxxxxxxxxxx');>
> *Date: *Tue, 25 Feb 2014 00:09:08 -0800
> *To:
> *minima@xxxxxxxxxxxxx<javascript:_e(%7B%7D,'cvml','minima@xxxxxxxxxxxxx');>
> <minima@xxxxxxxxxxxxx<javascript:_e(%7B%7D,'cvml','minima@xxxxxxxxxxxxx');>
> >
> *ReplyTo: * minima@xxxxxxxxxxxxx
> *Subject: *[minima] Re: pcbs for the minima
>
> Farhan,
>
> I would be happy to help with the software part of the project. I have
> more experience there ;) and I already have several projects on my github
> account that receive regular contributions (my pwm module for the raspberry
> pi is the most popular: https://github.com/sarfata/pi-blaster).
>
> I am sure we can find easy and clean ways to support multiple
> configuration of the minima (with encoder, with different screen, different
> cpus, etc). We just have to set reasonable limits otherwise it will become
> very complicated to understand the source code, and contributors will not
> be able to test their changes on every configuration.
>
> One thing you should really do first to encourage contributions is define
> a clear license for the source code. I think most people like to do MIT
> License nowadays. It is very permissive and allows re-use in commercial and
> non-commercial context.
> GPL would be a good choice too here: no-one would be allowed to distribute
> the program without the source. All changes will have to be re-published.
> Both are fine with me!
>
>
> 73,
> thomas
>
>
> On Mon, Feb 24, 2014 at 7:41 PM, <farhanbox@xxxxxxxxx> wrote:
>
> Joe,
> I hope we can refactor our code to use various 'device drivers'. But right
> now, it is messy. We did manage to separate out the si570 code. But we will
> need to similarly break it up into bandswitching, tuning and cw modules.
> Then we could generate our own versions to confirm to various hardware.
> For instance, I can see that the arduino could be used to control bitx
> class of transceivers. We will need to restrict the frequency range, remobe
> bandswitching etc.
>
> My dabbling with open source had been limited to writing few modules for a
> few software. I'd appreciate if someone can be the benevolent dictator of
> the radiono software.
>
> - f
> Sent from BlackBerry® on Airtel
> ------------------------------
> *From: * Joe Street <jstreet@xxxxxxxxxxxx>
> *Sender: * minima-bounce@xxxxxxxxxxxxx
> *Date: *Mon, 24 Feb 2014 22:15:59 -0500
> *To: *<minima@xxxxxxxxxxxxx>
> *ReplyTo: * minima@xxxxxxxxxxxxx
> *Subject: *[minima] Re: pcbs for the minima
>
> I don't understand your comment that " it has a software component that
> cannot be forked for different pcb layouts". Why not? That is usually
> what happens in open source projects because different people want to use
> different parts and do different things. Is there some reason why this
> cannot be the case here?
>
> Joe
>
> On 24/02/2014 12:48 PM, Ashhar Farhan wrote:
>
>
> the minima is a combination of software and hardware. we cannot have
> multiple versions of design as that will lead to multiple versions of the
> arduino software.
>
> the circuit is still evolving and given that it has a software component
> that cannot be forked for different pcb layouts, i have asked everybody to
> refrain from commercializing the design. the software may need some changes
> in the circuit as well. builders may be disappointed.
>
> 1. now it is clear to me that the T/R line needs an external pull-up as
> different arduino boards have different pull-up resistors. I have also
> eliminated the need for a bulky relay in the BFO.
>
> 2. In the interest of PCB layout, it might be better if we swapped some
> of the digital lines around from the arduino.
>
> 3. we are still debating over the best way to switch the
>
>
Other related posts:
