Re: json-ld implementations (.NET)

On Mon, Apr 9, 2018 at 3:53 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>  On Apr 9, 2018, at 12:09 PM, Asbjørn Ulsberg <asbjorn@ulsberg.no> wrote:
>> If we were to fork the repository, I would like to see it forked to
>> somewhere that feels just as or even more official than NuGet's
>> current repository. Would it be possible to fork it to
>> https://github.com/json-ld/json-ld.net? An answer from Gregg Kellogg
>> or anyone else with control over the "json-ld" organization on GitHub
>> would be great.
>
> No other implementations are hosted in the json-ld org, but it would aid stewardship. We’ll bring it up at the next CG meeting. I would create your own fork, for now, and then we can transfer that fork to the json-ld organization once we have a consensus to do so.
>

(Side note: This list *is* a continuous async cg meeting!)

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!  I'd say the easiest
approach for all is to work with current maintainers.  Make PRs, ask
for repo access if you want to be more involved, and if that fails and
you have superior code, advertise your fork and the main site can link
to it.

-dave

Received on Tuesday, 10 April 2018 00:18:26 UTC