Add disclaimer and link to official upstream repository

[sdimitro]

Per the discussion in Slack @mmaybee @prakashsurya

[prakashsurya]

Hm.. can we go further, and archive this repo, and point to @sdimitro's?

[sdimitro]

@prakashsurya that's what we decided before but it's been a couple of months now and I don't want to keep bothering y'all. Besides even if this repo is archived having the pointer in the readme is good regardless. It's also a good stop-gap solution until the archival of this repo is done.

[prakashsurya]

is there anything you're aware of in our repo, that's not in yours? I'll look into making the switch.

[sdimitro]

@prakashsurya you can double-check just in case but I cherry-picked the commits that you added and for each of them I cleaned it to make lint checks pass and wrote tests for them with output against the regression test crash dumps so I ensure I don't introduce regressions for you in the future.

[prakashsurya]

@sdimitro FYI, I just landed #360 .. moving forward, we'll pull from your repo as our official upstream.. there's a note w.r.t. this in our downstream README.. it would be neat if we could add the github linkage, so this appears as a fork in the repository graph, but I don't know if that's feasible, and maybe the note in the README is sufficient..?

[sdimitro]

@prakashsurya - thank you so much for working on this Prakash! Yeah, looking into this, it seems like there is no way to make Github establish such a relationship after the fact (the repo existing). The README is sufficient and I really appreciate you guys working on this with me <3

[prakashsurya]

@prakashsurya - thank you so much for working on this Prakash! Yeah, looking into this, it seems like there is no way to make Github establish such a relationship after the fact (the repo existing). The README is sufficient and I really appreciate you guys working on this with me <3

@sdimitro thank you, I still remember where the S in SDB came from 😜