kennethreitz/maya

sphinx docs

Open

#56 opened on May 25, 2017

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Python (199 forks)github user discovery
Contributor Friendlyhelp wanted

Repository metrics

Stars
 (3,413 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This issue does not include a description.

Contributor guide

Research direction
Review the existing Sphinx documentation and identify areas that need improvement or are missing.
Tech stack
python
Domain
backend
Issue type
Documentation
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.
Needs investigation
Prerequisites
GitSphinx
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75