vercel/hyper

Improvements to the project's transparency

Open

#3,647 opened on May 10, 2019

View on GitHub
 (3 comments) (16 reactions) (0 assignees)TypeScript (44,582 stars) (3,558 forks)batch import
help wanted

Description

This is sort of an umbrella issue to discuss:

  • Issue organization
  • GitHub projects, milestones, goals
  • Minor / major version planning
  • Release schedule
  • Testing methodology

I'd love the input from the community to know what you'd like to see in terms of this goal.

Contributor guide

Tech stack
None
Domain
documentation
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.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Review the existing 3 comments in the issue to understand community input. Then create a concrete proposal for one of the sub items, such as defining a release schedule or setting up GitHub milestones. Focus on actionable steps that can be implemented without broad consensus.