Bring in existing Best Practices

[BigBlueHat]

@w3c/json-ld-wg-admin was there a reason we didn't bring over the CG's Best Practices content?

If not, then I'd like to use that as a foundation to build up from.

@ajs6f thoughts?

[ajs6f]

Yes, my thought is: let's please start from that excellent foundation!

[BigBlueHat]

@iherman at this point does it make the most since for @ajs6f or I to just copy that HTML into here (we'll loose change history...sadly), or would it be possible for use to fork that history into this repo (using amazing jedi git skills no doubt)?

[gkellogg]

@BigBlueHat we thought about this for the -syntax, -api, and -framing documents but decided not to import history.

Note that the BP document from json-ld.org will need to be updated similar to how the -syntax document is for using common files and common CSS. Probably examples too.

[iherman]

@BigBlueHat I do not have any wizzardy to use; you can move a whole repository to a new owner, you can rename a repository, I believe there is also, these days, a beta facility to transfer issues from one repo to another (never used that yet), but I do not think it is possible to extract one document with its history and move it to a new repo.

I think it is perfectly all right if we start with a clean slate, forking the document itself. As @gkellogg said, this is what we did with the other documents...

[BigBlueHat]

@iherman it is possible, but given the follow-up changes @gkellogg pointed out (and that he's the principle author), it's probably simplest to bring over just the content and not the surrounding CG-centric ephemera.

I do think starting from that baseline content will save us some time, though--which we seem to all agree.

[iherman]

I did not know it is possible; you will have to show me once. But that is not relevant for us here then...

[ajs6f]

I lost track of this for a while, but it looks like our best option is the old-fashioned cut-and-paste? Or did I miss something?

[BigBlueHat]

I lost track of this for a while, but it looks like our best option is the old-fashioned cut-and-paste? Or did I miss something?

That sounds right. Want me to do it @ajs6f? or are you on it? Feel free to assign this (and others) accordingly!

[ajs6f]

I think can take a crack at this next week, but I cannot assign tickets here.

[iherman]

My mistake. I have added you as a collaborator with write access.

[ajs6f]

Thank @iherman!

[ajs6f]

Hm, I poked around https://github.com/w3c and https://github.com/json-ld but I wasn't able to find the source of https://json-ld.org/spec/latest/json-ld-api-best-practices/. @iherman or @gkellog, I'm guessing I'm missing something obvious?

[gkellogg]

Here's the source: https://github.com/json-ld/json-ld.org/tree/master/spec/latest/json-ld-api-best-practices

[ajs6f]

Thanks @gkellogg!

[azaroth42]

Resolved.