Move repository to D3 Organization?

[curran]

Proposal: move this repository from github.com/curran/d3-component to github.com/d3/d3-component.

[curran]

I'd like to start a conversation with D3 organization members on whether a module like d3-component would be welcome under github.com/d3 .

@mbostock @biovisualize @jasondavies @jheer @justincormack @RichMorin @NelsonMinar @n8agrin @larskotthoff @syntagmatic @tmcw @xaranke

What do you think? Does it solve a common need? Is it a reasonable idea? Is the abstraction too heavy or high level to fit within the philosophy of D3? Is the API OK (revision proposal at #70)?

It looks like it's starting to take off, judging by the npm downloads, so I'd love to hear any feedback. Ultimately I'd like to see this module find a home at github.com/d3/d3-component, but only if it's welcome by the community.

For more context on the purpose of this module, see #43

[DougManuel]

What about merging with https://github.com/gka/d3-jetpack?

[curran]

What would be the benefit?

Closing this issue as it seems not realistic/relevant anymore.