elk-audio/elk-examples

Missing release files

falkTX opened this issue · 5 comments

At least the documentation on https://github.com/elk-audio/elk-docs/blob/master/documents/getting_started_with_development_kit_software.md links to a few releases that should be on this repo, but nothing is available yet.
Please remove the links or upload the release files in question.

This announcement was really rushed guys... There is almost nothing actually published yet!

HI @falkTX , I replied in a similar way to your other issue in the repository.

Sorry about this, we needed to announce at least two weeks before the release at the ADC conference so people going there can organize a little and contact us to getting the boards, etc.

But I don't think we claimed something differently than what we have now. The website says "In the upcoming weeks a beta version of the Elk Audio Operating System will be made available under a Dual licensing model (open-source & commercial),", and on the main Github page here there is a diclaimer note saying "only docs & SDK available now, binaries for the RPi and source code repositories will come soon."

So please just wait a few more weeks, we will keep adding things. The links are missing because we are migrating stuff from private Bitbucket repositories, Sushi AppImage will come soon.

palms commented

@stez-mind - sorry to bug you, but is there any update on this in the past 2+ weeks? I know you guys are busy with ADC, excited to get up running

I don't want to open a new issue about this, sure enough you must be busy with ADC stuff, but the binaries in https://github.com/elk-audio/elk-adc-workshop-material also do not have source code provided. MVerb at least is GPLv3, so code is required when publishing a binary like that

Hi guys,
boards will be shipping next week and at the same time we will start populating the repositories here, so when people will receive the boards will have everything.

@falkTX: technically speaking, GPLv3 doesn't require to immediately publish the code at the same time when a binary is released. Anyway, I'm not nitpicking but just saying that we want to play this fair & square, no worries about that, we're just hyper-busy so things might arrive few days later, which is still complying with GPLv3.

Forks of plugin repos like MVerb & OB-Xd will be published in the upcoming week.

As for proof of own goodwill, in the HW repo:
https://github.com/elk-audio/elk-pi-hardware

we even published the complete production files for manufacturing, i.e. anyone can print the boards on her/his own.

So,
we have been slowly but steadily adding repositories during the past weeks, now everything is here.

We always tried to give priorities to source code that people requested for their use first. @falkTX : the sources for MVerb & other plugins have been published literally a couple of days after your notice and the forks are now kept in the separate community Github organization.

Sorry if this took us some time but it is not trivial to turn a previously closed-source codebase into open-source making sure that all the licenses are in place, setting up a workflow to maintain both closed-source and open-source version (there were few features that we couldn't open-source in userspace, but not included in the binary release), etc.

Now there are 23 repositories just in this organization (plus those in the community section), that cover every single detail of both source code and build system. This is not always the case on other open-source embedded projects, where sometimes the Buildroot or Yocto configuration is missing, making difficult for the end-users to actually build their own images and flash them to the device.

@falkTX : please take a look and close the issue once verified.

Cheers,
Stefano