Transfer BOB streams repo to nodejs org

I hope this is the correct issue tracker for this.

I propose we move https://github.com/Fishrock123/bob into the nodejs github org under a more appropriate name.

"Future Streams (BOB)", maybe.

This should be done to help prevent that work from being lost/forgotten, as it is very hard to progress alone, and my primary projects presently do not relate to node.

The project is licensed under MIT (though I wish I'd put it under dual with BlueOak before any contributions were made), and has the DCO-1.1 in it's contributing document.

There are also a handful of related repos and npm modules:

• The status codes enum: bob-status (npm)
• A file system source: fs-source (npm)
• A file system sink: fs-sink (npm)
• A zlib transform: zlib-transform (npm)
• A crc32 transform: crc-transform (npm)
• Header for the C++ api: bob-base (npm)

I believe all of those are also MIT & DCO-1.1, and I'm not quite sure what to do with them, considering the "main" repo kinda depends on / tests them.

An alternate approach could be to stuff those additional modules all under a separate github org, I suppose.

cc @mcollina, @jasnell, @raynos

Beginne mit der Überprüfung des verlinkten BOB-Repositorys, verwandter Repositorys und npm-Module und prüfe anschließend deren Eigentumsverhältnisse, Lizenzen, DCO-Dokumente und Abhängigkeiten. Als erledigt gilt die Erreichung einer Entscheidung über die Übertragung, Benennung und Handhabung der zugehörigen Projekte, wobei die administrativen Schritte identifiziert sind.