Many thanks for the help, all. I'll continue to repair our fork (https://github.com/fluenttechnology/json-ld.net) which will be helpful in the interim. If still necessary, and time permitting I'll look at modernising the build, test and runtime sometime in May/June of this year. I'll reply to this thread again if Nuget doesn't start merging in some changes in a month or so. On 10 Apr 2018, 21:20, at 21:20, "Asbjørn Ulsberg" <asbjorn@ulsberg.no> wrote: > 2018-04-10 2:17 GMT+02:00 David I. Lehn <dil@lehn.org>: > >> Having the main organization host implementations seems to add a >whole >> bunch of responsibilities that are avoided by using external links. >> The group would have to handle licensing, ownership, finding >> maintainers, manage user access, maybe handle package manager release >> access, etc. That being said, it would be nice to have a central >> place for implementations. Although certainly would be weird if the >> json-ld org is only hosting the .NET lib! > >Good points. I'm happy to report that the issue I created earlier >today regarding the stewardship of the json-ld.net repository has >gotten replies from Microsoft: > >https://github.com/NuGet/json-ld.net/issues/26 > >So, I guess we'll just have to await their decision. > >-- >Asbjørn Ulsberg -=|=- asbjorn@ulsberg.no >«He's a loathsome offensive brute, yet I can't look away»
Received on Tuesday, 10 April 2018 20:42:03 UTC