Live data from Hacker News

Pijul – A free and open source distributed version control system

pijul.org

11–20 of 180 posts

Re: Pijul – A free and open source distributed version control system

#13
Is there any sound reason to use AGPL3 license in this case? Is it to avoid private, non-public modifications by some future pijulhub.com? Something, somewhere feels irrational in my head, especially when I think about popular projects like SQLite which seem to be doing just fine without the whole license thing.

Re: Pijul – A free and open source distributed version control system

#14
post #11

AGPL3 sounds like a death sentence given recent RethinkDB struggles, which is just sad, because the project looks very cool.

Any sources behind the claim that agpl is behind the lack of success for rethinkdb?

I am very bullish about agpl. As far as I understand, the choice of agpl has no effect on your code which you put in a repository. Is that not the case?

Re: Pijul – A free and open source distributed version control system

#15
post #12

Why don't I ever see CC on OSS? Always these complicated licenses.

https://creativecommons.org/faq/#can-i-apply-a-creative-comm...

> Unlike software-specific licenses, CC licenses do not contain specific terms about the distribution of source code, which is often important to ensuring the free reuse and modifiability of software. Many software licenses also address patent rights, which are important to software but may not be applicable to other copyrightable works. Additionally, our licenses are currently not compatible with the major software licenses, so it would be difficult to integrate CC-licensed work with other free software. Existing software licenses were designed specifically for use with software and offer a similar set of rights to the Creative Commons licenses.

Re: Pijul – A free and open source distributed version control system

#16
post #10

Sadly, I'm afraid the AGPL license is going to make this untouchable to businesses… :-( [Edit] Interestingly, they cover that. I suppose if you're just running Pijul rather than integrating with its code, it might be safe to use in a corporate environment. Still, it's likely to be offputting.

I may be wrong but I think some (most? all?) companies that are blacklisting agpl3 won't bother going into small print details, license alone is a no-go, no?

Re: Pijul – A free and open source distributed version control system

#17
post #10

Sadly, I'm afraid the AGPL license is going to make this untouchable to businesses… :-( [Edit] Interestingly, they cover that. I suppose if you're just running Pijul rather than integrating with its code, it might be safe to use in a corporate environment. Still, it's likely to be offputting.

Why do you find it offputting? IANAL but it basically doesn't allow you to add code to (or get code from) Pijul itself and making it in another license. You can use it to store closed source code, you can host it yourself, offer it as a sevice for money, you can even create your own extensions as long as you release them AGPL...

I feel that AGPL for a product is misunderstood and pre-rejected without justification by far too many. Now, if you are developing a library, then AGPL sucks as a license for it, but for a cohesive product? Seems acceptable to me (not sure if it's my favorite choice)

Re: Pijul – A free and open source distributed version control system

#18
post #11

AGPL3 sounds like a death sentence given recent RethinkDB struggles, which is just sad, because the project looks very cool.

The reasons RethinkDB the company failed very probably have little to do with AGPL.

http://www.defstartup.org/2017/01/18/why-rethinkdb-failed.ht...

Re: Pijul – A free and open source distributed version control system

#19
post #14
post #11

AGPL3 sounds like a death sentence given recent RethinkDB struggles, which is just sad, because the project looks very cool.

Any sources behind the claim that agpl is behind the lack of success for rethinkdb? I am very bullish about agpl. As far as I understand, the choice of agpl has no effect on your code which you put in a repository. Is that not the case?

As I wrote in another comment here I'm really surprised by the shallow reasoning of fellow developers regarding AGPL: https://news.ycombinator.com/item?id=13643645

I mean, I might not understand the finer legal details but thinking "all your code you see after using anything GPL has to be GPL" is really weird, did this people ever used a linux kernel? (yes I know GPL is different from AGPL and at a high level I also know what is different)

Post reply on HN