License? about efcore.nestedsets

[joshcomley]

Sure, but actually I'm no good with licenses! Which one means, essentially, free for anything? Additionally, I have better nested set code that works with EF Core SPECIFICALLY and only with SQL as the database provider, if you'd prefer that I could publish it. Kind regards, Josh

…

On Thu, 17 Oct 2019, 07:05 Nelson Chen, ***@***.***> wrote: Could a license be added to the code in this repository? https://help.github.com/en/articles/adding-a-license-to-a-repository — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AAGIKNW6XVHFWN4ZT3HQ7HDQO76DDA5CNFSM4JBUUZP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HSLLKPA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGIKNX6TKZEHSM7FPLNDMLQO76DDANCNFSM4JBUUZPQ> .

[nelsonjchen]

Free for anything would let anybody rip off your name and not provide attribution. That's not cool. So we want some protection at least. That said, I think choosing the MIT License like the one used in .NET Core would be the one in your interest.

I'm interested in using this with PostgreSQL so an SQL Server-only version wouldn't interest me that much.

[nelsonjchen]

https://github.com/dotnet/corefx/blob/master/LICENSE.TXT

.NET Core didn't even bother with the year. So it can be even lower maintenance.

[nelsonjchen]

Actually, I am interested in the SQL server version. It wouldn't happen to be using hierarchyid would it which is making it SQL Server only? I would be interested in using it as a reference for a PostgreSQL using ltree or adding ltree support to it. It be great as a separate project though.

I'm looking at moving some model from using a Rails nested sets to ASP.NET Core nested sets then eventually to ltree.