Transfer BOB streams repo to nodejs org
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, javascript, nodejs
Research direction
Start by reviewing the linked BOB repository, related repositories, and npm modules, then check their ownership, licenses, DCO documents, and dependencies. Done means reaching a decision about the transfer, naming, and handling of the related projects, with the administrative steps identified.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sugarlabs/musicblocks#8924 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ArduPilot/ardupilot_wiki#8088 ·
-
[BUG] createTool tools cannot be registered with Mastra when exactOptionalPropertyTypes is enabled Opencustomer-eng status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100