why was dev taken private?

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, node.js
Domain
release

Research direction

The issue names no source file, test, or entry point and asks why the development repository was made private. Start by reviewing the repository and published npm package links in the issue. Done means a maintainer explains the repository status and whether a public future is planned.

Written by the indexing model from the issue text.

Description

This MIT codebase is no longer maintained but the published package at npmjs.com is and is also MIT. The catch is that https://github.com/mapbox/node-or-tools-internal is not a public repo.

Why did Mapbox take this private? Is a public future on the horizon?

Dominant language
C++
Stars
155
Forks
47
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/node-or-tools

All issues in mapbox/node-or-tools

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.