ayojs/ayo

fork setup work to be done

Open

#16 opened on Aug 24, 2017

View on GitHub
 (10 comments) (1 reaction) (0 assignees)JavaScript (97 forks)batch import
good first issuehelp wanted

Repository metrics

Stars
 (1,676 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Here's a couple things off the top of my head. I'm certainly willing to help do some guidance on any but I have limited experience in some of these areas. Digging though the commits back to January 2015 in the related files folders will surly turn up related reference-able commits for the io.js days.

... more to be added

Contributor guide

Research direction
Examine the referenced PR #10 for context on the Vcbuild.bat changes, then review the osx pkg.pmdoc and msvs directories to adapt the installers for 'ayo' instead of 'node'.
Tech stack
nodejs
Domain
build systemtoolingrelease
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40