W3C home > Mailing lists > Public > public-linked-json@w3.org > April 2018

Re: json-ld implementations (.NET)

From: Andrew Gibson <tinycode2@gmail.com>
Date: Mon, 23 Apr 2018 21:56:56 +0100
To: Asbjørn Ulsberg <asbjorn@ulsberg.no>
CC: "David I. Lehn" <dil@lehn.org>,Gregg Kellogg <gregg@greggkellogg.net>, Linked JSON <public-linked-json@w3.org>,Tomasz Pluskiewicz <tomasz@t-code.pl>
Message-ID: <cab87783-2dd5-4c90-b33c-688656a4d0dc@gmail.com>
Unfortunately Nuget seem very against the idea of retaining the repo within their organisation, even with volunteers to administer it.

It would be good to find a new home with some street cred. For example, a central org for client implementations might work well. Someone with more connections than me would perhaps have some luck drawing the various implementers together.

Alternatively, I think Nuget would be happy to transfer their repo into the freshly minted https://github.com/orgs/linked-data-dotnet which I have just registered.

Any other ideas? Or does anyone else wish to stake a claim to the repo?

⁣Sent from TypeApp ​

On 17 Apr 2018, 09:14, at 09:14, Andrew Gibson <tinycode2@gmail.com> wrote:
>Nuget are now acknowledging the need for new maintainers and are
>looking for ideas about where to host the repo moving forward.
>I've also raised the possibility of outside maintainers for the package
>while it remains under their organisation to see if there's any
>Ideas/suggestions would be welcome:
>⁣Sent from TypeApp ​
>On 10 Apr 2018, 21:41, at 21:41, Andrew Gibson <tinycode2@gmail.com>
>>Many thanks for the help, all.
>>I'll continue to repair our fork
>>(https://github.com/fluenttechnology/json-ld.net) which will be
>>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"
>>> 2018-04-10 2:17 GMT+02:00 David I. Lehn <dil@lehn.org>:
>>>> Having the main organization host implementations seems to add a
>>>> 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
>>>> access, etc.  That being said, it would be nice to have a central
>>>> place for implementations.  Although certainly would be weird if
>>>> 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:
>>>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 Monday, 23 April 2018 20:57:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:51 UTC