FlowmapBlue proposal to join vis.gl

[chrisgervang]

Transferring ucfoundation/tac#37 to the TSC repo.

@ilyabo please review the URLs, names, and other content are up to date. I made some modifications from the original after noticing repos have been renamed and moved to the FlowmapBlue github org. Also, let us know if you'd like to add anything from your OpenJS application.

Question to the TSC, do we want anything added to this proposal, like an approval status header?

What should our onboarding checklist contain?

• Domain transfer (if any)
• Either github org transfer to vis.gl, or TSC admin access to FlowmapBlue org.
• NPM admin access to the TSC.
• OpenJS Code of Conduct adoption
• OpenJS footer

[chrisgervang]

@ilyabo please say which repos are transferring to the vis.gl org. Just FlowmapBlue or also flowmap.gl? Any other repos?

[ilyabo]

@chrisgervang I would like to transfer flowmap.gl most of all, but FlowmapBlue/flowmap.gl org is a partial rewrite of flowmap.gl which is still owned by Teralytics. They don't develop further, but I am not sure whether my new version can be transferred to OpenJS since it still has some code from the old one. Would just keeping the old lincense with the reference to Teralytics be enough? Maybe I should also rename it, e.g. into FlowmapBlue.gl? What do you think?

[chrisgervang]

The best thing to do it to ask Teralytics for their written support in transferring flowmap.gl to OpenJS within vis.gl. OpenJS may have some example paperwork for this, or if not, I have an old one from Uber for hubble.gl you can look at. But it's really not complicated if they haven't registered a trademark - they just need to grant copyright to the name.

The license, copyrights, and their acknowledgements/credit would not be removed.

Technically, the license doesn't prohibit a fork under a different name. But that's not our preference. You'd need to treat the fork as a completely new package, like for example, how maplibrae and mapbox are cleanly split (though with your Apache license, you don't need to be as strict about sharing code between projects - just follow the license terms).

[ilyabo]

The best thing to do it to ask Teralytics for their written support in transferring flowmap.gl to OpenJS within vis.gl. OpenJS may have some example paperwork for this, or if not, I have an old one from Uber for hubble.gl you can look at. But it's really not complicated if they haven't registered a trademark - they just need to grant copyright to the name.

I actually asked them when joining UCF and they verbally agreed, but when I sent them the papers they never signed them. I reminded them 3 times, they still didn't. I am not sure I want to try that again :)

So if renaming the library to FlowmapBlue.gl would be an option for you, I'd probably go with that approach. What do you say?

[ibgreen]

Maybe we could reach out to them from OpenJS / LF or vis.gl side and offer some marketing coverage, e.g featuring their contribution in a blog post etc?

[ilyabo]

Maybe we could reach out to them from OpenJS / LF or vis.gl side and offer some marketing coverage, e.g featuring their contribution in a blog post etc?

Not even sure who we could reach out to. I am not acquainted with their current CTO. I had a good relationship with the head of marketing though. I will DM you.