- [PROPOSAL] new repository for .NET driver
Re: [PROPOSAL] new repository for .NET driver
Florian Hockmann <f...@...>
toggle quoted messageShow quoted text
Thanks, I'm now member of the group and apparently have write access to all JanusGraph repos, except for the two new ones: janusgraph-dotnet and janusgraph-python. I get permission denied
when I try to push something there and I also can't set an assignee in the New Issue
dialogue which should be possible with write access
(this works now for the other repos). Could you please check the permissions again for the two repos?
Am Mittwoch, 15. August 2018 15:40:12 UTC+2 schrieb Jason Plurad:
You're right, we'll get you updated on that list.
On Wednesday, August 15, 2018 at 7:11:45 AM UTC-4, Florian Hockmann wrote:
Looks like I don't have access to it. At least I can't see its settings or anything. Do I need to be member of the JanusGraph org
Am Mittwoch, 15. August 2018 00:45:27 UTC+2 schrieb Jason Plurad:
Apologies for the delay, but I've created
Committers and maintainers should have access to it.
On Sunday, August 5, 2018 at 9:25:48 AM UTC-4, Florian Hockmann wrote:
Looks like we have reached consensus here. I have already created a stand-alone version of the library in its own repo:
I can create a PR to transfer it to JanusGraph as soon as we have a repo ready to target the PR against.
Am Dienstag, 31. Juli 2018 20:47:11 UTC+2 schrieb Misha Brukman:
Makes sense that client libraries should be in a separate repo than the server:
- enables a separate release cadence
- allows for a different set of maintainers, even in the same org
- each client library will be written in a different language
Having said that, this means that we'll have to keep track of version compatibilities between client library versions + server versions. Hopefully, they will be mostly backwards-compatible until a major version change.
Join email@example.com to automatically receive all group messages.