mozilla/DeepSpeech

Redirect people to SWIG 4.1 instead of our fork

Open

#3,541 opened on Feb 25, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (26,755 stars) (4,093 forks)batch import
branch:masterdocumentationgood first bughelp wanted

Description

NodeJS v12-v15 has been merged upstream and should be part of SWIG 4.1 ; we should direct people to use that release instead of relying on our fork (which will continue only for TC integration purposes).

Contributor guide

Tech stack
nodejscpp
Domain
documentationdeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with SWIGknow where DeepSpeech documents its NodeJS bindings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Look for documentation files (e.g., README, CONTRIBUTING, or a NodeJS specific guide) that reference the fork of SWIG. Update the text to redirect users to the official SWIG 4.1 release for NodeJS v12 v15, noting that the fork will continue for TC integration only.