Keykit licensing/distribution

[Olaf]

Hello²,

my second question is preying on my mind for a while. I assume it deserves an own thread.

For one of my private projects I've used Keykit as middle ware.
Now, the third version of the Raspberry Pi 3 was released. It has four cores and it's possible to run a Kinect, hand tracker and a synthesizer (i.e. fluidsynth, sonic_pi/supercollider ) directly on one embedded system. :-)
I want publish my project as (simply installable) software bundle for other Raspberry Pi users.

Your choice of distribution/licence of Keykit made it impossible for me to
a) share Keykit as installable binary package ( deb-package.)
b) share the source code of Keykit together with my modifications to made it compilable on Linux (some manual steps are required until 'make' compiles).

Currently, I refer if my install instruction to your site. All users (if there were anyone) needs to register on your site and patching+compiling the code manually. That's a really annoying, time-consuming process.

Did you has any plans to re-license Keykit as Open Source and put it on a modern code sharing platform like Github?


Regards,
Olaf Schulz

[Tim Thompson]

> Did you has any plans to re-license Keykit as Open Source and put it on a modern code sharing platform like Github?

No plans, sorry.   Sharing keykit things (source or binaries) between two people who have both signed the license should be fine, so if you ensure (or believe an assurance) that someone has signed up for the download site, I believe you can share your changes (or a package that includes them) directly, to simplify the scenario for them.

     ...Tim...

--
You received this message because you are subscribed to the Google Groups "KeyKit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keykit+un...@googlegroups.com.
To post to this group, send email to key...@googlegroups.com.
Visit this group at https://groups.google.com/group/keykit.
For more options, visit https://groups.google.com/d/optout.

[Tony Travolta]

Or simply share with Tim, so he can put your additions into next Keykit version?  But yes, the workflow would not be same as with Github.  But people could still enjoy your extras, thanks for your work, even having no Raspberry Pi.  I am still waiting for a fully programmable RGB-Led qwerty.  There is now something, but the software is not fully programmable, at least nothing for the selling company, we have to wait for future private solutions.  Something like this, combined with Keykit would be my dream musical (midi) controller, usually combined via AutoHotkey.

 

Push on hardware rgb-qwerty button  -->  AutoHotkey translating those keystrokes to Keykit phrase string input   -->   Keykit using text input and converting to midi output   -->   going to your favourite midi software or devices

 

With a programmable rgb-qwerty and AutoHotkey you can make your controller as complicated or simple as you like.  Enough colors, for enough special modes, enough keys.  Keykits possibilities are anyway endless.  Thanks Tim again.

 

Best regards

Tony

 

 

 

Gesendet: Samstag, 02. April 2016 um 21:20 Uhr
Von: "Tim Thompson" <m...@timthompson.com>
An: Olaf <funwit...@googlemail.com>
Cc: KeyKit <key...@googlegroups.com>
Betreff: Re: [keykit] Keykit licensing/distribution

[Tony]

Olaf, I am interested in your solution, could you please send it to my email, dj.t...@gmx.de , I am signed to Keykit's download page.  :)

Still no raspberry pi, but why not. 

Best regards

Tony

[Mike Edwards]

I am interested too. mick...@gmail.com