gliderlabs/com

What else for 1.0?

Open

#2 opened on Nov 9, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (4 forks)github user discovery
help wantedquestion

Repository metrics

Stars
 (92 stars)
PR merge metrics
 (PR metrics pending)

Description

Besides stable APIs, solid docs, and more test coverage ... what else should we focus on for a 1.0 release? Also, where can the docs be improved? Where are there questionable API choices?

I'm putting a deadline of Feb 1 on the 1.0 milestone. That gives a timeline constraint. Hopefully we use it enough in that time to know what a solid 1.0 API looks like.

Contributor guide

Research direction
Review the current API and documentation, identify areas for improvement, and propose specific changes or additions for the 1.0 release. Consider stable APIs, solid docs, and test coverage as mentioned.
Tech stack
go
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Unclear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50