As discussed before, moving all redux-devtools related repositories to reduxjs organization doesn't look sustainable (though it's still open for discussion). A better way, especially for new contributors, would be to have everything in a monorepo. We could do that in redux-devtools-extension as discussed in zalmoxisus/redux-devtools-extension#412 since there's more activity, but using just redux-devtools name sounds better and everything started here. So the plan is to keep only this repository, the rest will be archived and the code moved here. I'll add credits for every readme. Maybe we could even add authors of the monitors in the extension, just need an UI for that (something like a monitors store).

The list of repos to be merged (some will be renamed as suggested bellow):

• redux-devtools (from current repo)
• redux-devtools-instrument
• react-json-tree
• redux-devtools-inspector
• redux-devtools-log-monitor
• redux-slider-monitor
• redux-devtools-test-generator
• d3tooltip
• map2tree
• devui
• remotedev-utils -> redux-devtools-core
• remotedev-app -> redux-devtools-core
• remotedev-server -> redux-devtools-cli
• redux-devtools-extension npm package
• browser extension

These repositories could still be maintained outside as either having a maintainer or no changes needed in future (?):

• d3-state-visualizer (?)
• redux-devtools-chart-monitor (?)
• remotedev-serialize -> serialize-immutable (?)
• redux-devtools-dock-monitor (?)
• redux-devtools-themes (?)
• redux-devtools-filter-actions (?)
• remote-redux-devtools (?)
• redux-remotedev (?)
• atom-redux-devtools (?)

If everybody agrees on, we still have to finish the work in progress in opened PRs, so first will need to:

• fix all issues, except feature requests, for 2.16,
• finish stack trace functionality started in Show stack traces zalmoxisus/remotedev-app#43 and move to a separate redux-devtools-trace-monitor package,
• finish all refactoring, work in progress, implement new UI and all the updates for 3.0.