starshipwinepineapple
Thanks, yeah looks like they are wanting to build on their own reader app.
So are they somehow able to relicense by buying off the contributors? Or does Eleven Labs intend to host/use something under AGPLv3? Just trying to figure out what their plan is and how they’re dealing with it being open source
Right, the other thing i considered is that you could just create a company and “buy” the data from them for a ridiculous amount of money and then you have less requirement to detail the data. Similarly you could deem the data unsharable and fudge the provenance.
Like locks, it will only keep honest people honest.
the actual license text part being questioned .
Data Information: Sufficiently detailed information about the data used to train the system so that a skilled person can build a substantially equivalent system. Data Information shall be made available under OSI-approved terms.
In particular, this must include: (1) the complete description of all data used for training, including (if used) of unshareable data, disclosing the provenance of the data, its scope and characteristics, how the data was obtained and selected, the labeling procedures, and data processing and filtering methodologies; (2) a listing of all publicly available training data and where to obtain it; and (3) a listing of all training data obtainable from third parties and where to obtain it, including for fee.
(The rest of the license goes on to talk about weights, etc).
I agree with you somewhat. I’m glad that each source does need to be listed and described. I’m less thrilled to see “unshareable” data and data that cost $ in there since i think these have potential to effectively make a model not able to be retrained by a “skilled person”.
It’s a cheap way to make an AI license without making all the training data open source (and dodging the legalities of that).
+1 for gitlab. You can programmatically generate a csv file that can be used to generate issue(s) which support markdown format. Then your checklists could be issues and marked as completed when done.
You could also for instance set up a weekly pipeline schedule to generate issue(s) from the csv if some of the issues are needed on an interval.
If gitlab isn’t an option then id still look into generating the .md files this way and finding a home for the .md files that works for your user(s)
I don’t see a CLA so this is somewhat surprising that all ~30 contributors would be okay moving away from open source.
Unless this was a unilateral decision
And it makes no mention that they were modifying and using GPL code prior to making their code “open source”.
Id argue that this story is not over until the GPL code can be confirmed removed by a third party
Reading the sidebars, this is android news for developers, and the one you linked is more generalized.
Beyond that, servers have different compositions so discussions can vary, and funneling everyone into single communities just leads to risk of reddit-style mod/admin abuse.
There are much smaller projects that ask for more from commits/merge messages. This is a normal ask
