Proposal.

[watatuki]

Currently, this repository doese not create a branch that corresponds to the version of the Yocto ( such as dizzy, fido, etc...). I propose to create two branches "fido" and "dizzy". When the Yocto2.0 was released, there is a need to create a one more new branch. It will be released end of october.

In addition, I propose to specify "AS IS" for this recipes. For example, MIT license, BSD license, etc...

[jharley-eb]

I thought I'd add my vote to this as well 👍

I'm working on the TK1 for a customer, and used your code as a base, like watatuki I then added the fido branch as that is what we're currently working on. My customer has recently given me the ok to release the changes I've made (although most are very similar to watatuki's changes, some taken from his fork) which is great but it's going to be awkward without the branches in your repository to merge back into.

I do agree with the sentiment that it doesn't make sense having lots of disparate forks.