Comments (29)
@asbjornu , @goofballLogic thanks for bringing this to our attention. I will work with the team to determine the best course of action.
from json-ld.net.
have outsiders maintaining a package in your name
Isn't that the essence of open source collaboration? π
As long as there is an active maintainer who would take care of code quality and coverage I think it's a good choice to stay under the NuGet organisation.
from json-ld.net.
Hi @skofman1 looks like we're ready to move on this.
- Lets go ahead with this transfer to https://github.com/linked-data-dotnet please
- Could you add me as an owner on Nuget (https://www.nuget.org/profiles/goofballLogic)
@asbjornu we need at least one other owner for the org to be secure. Shall I add you? Any other volunteers?
from json-ld.net.
@skofman1 @rrelyea would you help make a decision on this?
I would really like to see this project move forward, and these look like great suggestions for allowing that to happen.
NuGet gallery still uses this library as far as I know, but the current implementation works fine for them and there has not been any work done by the NuGet team in quite some time. My guess is that consumers of nuget.org aren't reading it as json-ld, so even if things are incorrect, no one is reporting it. Which is why this isn't being updated.
The issues and PRs coming in for this repository require a lot of technical expertise on RDF and json-ld. It takes a effort to determine if a PR is actually the correct fix for an issue just based on the json-ld output. @sblom, @johnataylor, and myself who previously worked on this library are no longer on the NuGet team which has made this more difficult.
from json-ld.net.
Note that jsonld-java is, itself, only lightly maintained. Other implementations are updating with features from the JSON-LD 1.1 CG Spec, and a new JSON-LD Working Group is being chartered, so if developers are interested in moving this version forward, it would be shame if they are handicapped by less progress on the jsonld-java side.
There is no substitute for active and interested maintainers.
from json-ld.net.
- Tom Marsh (@tmarshbing) who coordinates Microsoft (incl. Bing's) participation in Schema.org
from json-ld.net.
Thanks @danbri. I will follow up with @skofman1 offline.
from json-ld.net.
Those who responded on the public-linked-json W3 mailing list agree that it would be good for the repo to remain part of the Nuget organisation. This would mean:
- Creating a repo-specific group for maintainers with administrative privileges over this repository and adding volunteers
- Specifying the members of this group as "Package Owners" for purposes of publishing to Nuget
Is this something that you are open to @skofman1 ?
from json-ld.net.
Sounds good @goofballLogic !
Will handle the transfers next week.
from json-ld.net.
from json-ld.net.
Plans exist to try and update the library by the end of next month. However, this will likely be just getting the 1.0 version up to date.
Once updated, the upgrade path to 1.1 should be much simpler and PRs will be welcome.
from json-ld.net.
Thanks everyone, for you enthusiasm in making contributions or taking this repository forward.
After a conversation internal to the NuGet team, we realized that we did not have any expertise left on the team who can successfully maintain this repository and either contribute directly to it or manage our community contributions. While NuGet.org has a dependency on this package, we have not really required any code changes for many years now, and we donβt see this changing.
In order to take this repository forward as expressed by the community, we are proposing the following:
β’ We will work with anyone in the community who has a strong interest in this code-base to transfer ownership of the repository to you (or a set of you).
β’ We will transfer the repository from being under the NuGet organization to another organization that the owners decide.
β’ We will also transfer ownership of the packages on NuGet.org to another account that the owners decide.
There will be no changes that the NuGet team will propose the licensing terms, code of conduct, and such and we will defer all future decisions regarding the code in this repository to its new owners. The transfer of ownership will be as-is.
Please let us know your thoughts about this plan. If there is general consensus, we will work on the next steps to identify a set of future owners for this repository.
from json-ld.net.
I have a strong interest in this code base.
I'll mention this on the public-linked-json W3 mailing list to see if others are interested, and to encourage brainstorming ideas about where best to host the repository moving forward.
Note that I personally would have no objections to maintaining the repository within the Nuget organisation as the Nuget name lends some authority to the package. However, I can understand you may not wish to have outsiders maintaining a package in your name.
from json-ld.net.
@tmarshbing - as mentioned above to @skofman1 we think it would be good for this library's profile to remain within the NuGet organisation. Is it possible to set up a group of maintainers (I am volunteering) with administrative rights over just this repo, and the ability to publish to NuGet ?
from json-ld.net.
As long as there is an active maintainer who would take care of code quality and coverage I think it's a good choice to stay under the NuGet organisation.
There's no one in the NuGet team that can maintain the repository, since, as was mentioned before, we have no knowledge left on the team on this code base. We can't lend our name to a code base we can't guarantee the quality off, hence, to allow open source collaboration, the repository must move out of NuGet's GitHub organization.
from json-ld.net.
I suggest that the repo is moved to the https://github.com/linked-data-dotnet organisation which I have set up as a (temporary?) location so we can start fixing things. @tpluscode @asbjornu @gkellogg @tmarshbing - anyone wish to propose otherwise?
from json-ld.net.
@goofballLogic: As the repository can be moved from @linked-data-dotnet whenever we find a better home for it, I give it my two thumbs up. π
from json-ld.net.
I was going to propose https://github.com/json-ld but I see that it doesn't really host any implementations. I guess I too agree with @goofballLogic. The only other org I found is https://github.com/RDF-Utilities-dotnet which doesn't offer much more visibility either.
from json-ld.net.
@tpluscode You can always put in under the https://github.com/dotnetrdf org for old times sake ;)
from json-ld.net.
HA! It did cross my mind but I don't know what @kal would say given recent effort for dotNetRDF's own JSON-LD support π
from json-ld.net.
Thanks @tpluscode! As much as I would like to support this code base too I think I have my hands full with dotNetRDF :-)
from json-ld.net.
The proposal to move to https://github.com/linked-data-dotnet sounds good to me.
from json-ld.net.
@goofballLogic: Sure. We can always rejuggle ownership and administration after the transfer is complete.
from json-ld.net.
@goofballLogic , I need permissions to create repositories in https://github.com/linked-data-dotnet in order to perform the transfer.
from json-ld.net.
from json-ld.net.
Repo transfer completed π
Regarding the package on nuget.org, I recommend that you create an organization to own the package, and add all other contributors to this org. Documentation here: https://docs.microsoft.com/en-us/nuget/reference/organizations-on-nuget-org
from json-ld.net.
Thanks @skofman1 I have set up https://www.nuget.org/profiles/linked-data-dotnet for this purpose
from json-ld.net.
@goofballLogic , ownership request sent. After you accept I will remove 'nuget' as an owner.
from json-ld.net.
In my humble opinion, a general purpose .NET Standard 2.0 compatible, easy to digest JSON-LD 1.1 library is difficult to find and considering the importance, I find it a bit odd there isn't one baked into the official framework. Just in case, I'd like to page @RehanSaeed of https://github.com/RehanSaeed/Schema.NET. It'd would be great to see efforts pooled, unfortunately for the time being I lack the expertice to contribute much anything. It's the knowledge-available time gap.
from json-ld.net.
Related Issues (20)
- Rename `master` to `main`
- Version 1.0.7 is missing on nuget.org HOT 7
- @embed not supported? HOT 2
- Microsoft.Bcl.Async is deprecated HOT 2
- JsonLdProcessor.Frame(...): poor performance on large sets of objects HOT 2
- Release 1.0.6 HOT 1
- Strong name sign json-ld.net assemblies HOT 7
- Control order of graph nodes and children nodes HOT 1
- Getting OutOfMemoryError while try to frame JsonLd HOT 3
- Replace Travis with GitHub Actions HOT 1
- Proposed .NET version compatibility HOT 10
- Evolve or Rewrite? HOT 13
- Support dependency-free API HOT 16
- Support dependency-injection HOT 3
- Support System.Text.Json HOT 2
- Add Markdown guidelines
- Support for signing HOT 9
- Reduce public API to a bare minimum HOT 3
- Add LINQPad NuGet samples HOT 4
- API advertised in documentation/samples is now `internal` HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-ld.net.