Thanks, yeah looks like they are wanting to build on their own reader app.

https://elevenlabs.io/blog/omnivore-joins-elevenlabs

Everyone has a hobby 🙃

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)

Appreciate it, i wasn’t familiar with the project and didn’t see that!

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

Wait, if they suspended your domain, can you even transfer it away? if not, that’s really fucking scary.

Njalla takes ownership of every domain purchased on their platform. They do let you transfer domains to another registrar where you could be the owner if your account is in good standing but seems like that may not be the case here (since account suspended)

That may be great for some domain use cases but for most stuff it would be better to have your name on the domain registration

I really like that it is a static website being updated and built on a schedule from github actions.

Open source is generally understood as libre, and an OSI approved license.

I think you’re thinking of source-available.

Additional reading: https://news.itsfoss.com/open-source-source-available/

Anyway, thanks for the list!

Umami has a free tier of their cloud hosting.

The difference is that commercialization is inherent with a free (libre) open source license. Whereas going against the intent, but still legally gray area, is imo malicious compliance because it circumvents what the license was intended to solve in the first place.

But that’s all i really care to add to this convo, since my initial comment my intent was just to say that the AGPLv3 license does not stop corporations from getting free stuff and being able to charge for it-- especially documentation. Have a good one

No. I said even if they don’t maliciously comply with the license [by making the open sourced code unusable without the backend code or some other means outside of scope of this conversation] then they can charge for it.

The malicous part is in brackets in the above paragraph. The license is an OSI approved license that allows commercialization, it would be stupid for me to call that malicious.

Nothing. The context of this comment thread is “fuck corporations” and then proposing AGPL to solve that. I am merely pointing out that if their goal is to have a non-commercial license then AGPL doesn’t solve that, which is why i mention they can charge for their services with AGPL.

Who hurt you!?

AGPL is the most restrictive OSI approved license (of the commonly used ones), but it is still a free (libre) open source license. My understanding is just that the AGPL believes in the end-users rights to access to the open source needs to be maintained and therefore places some burden to make the source available if it it’s being run on a server.

In general, companies run away from anything AGPL, however, some companies will get creative with it and make their source available but in a way that is useless without the backend. And even if they don’t maliciously comply with the license, they can still charge for their services.

As far as documentation goes, you could license documentation under AGPL, and people could still charge for it. It would just need to be kept available for end-users which i don’t think is really a barrier to use for documentation.