microsoft/PowerShellForGitHub

Remaining work for API Completeness

Open

#70 opened on Dec 11, 2018

View on GitHubContributor guide
 (12 comments) (0 reactions) (0 assignees)PowerShell (189 forks)auto 404
api completenessenhancementgood first issuehelp wanted

Repository metrics

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

Description

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

Contributor guide

Research direction
Pick an unchecked item from the list, create a new issue to track it, implement the corresponding GitHub API endpoint in PowerShell, and submit a pull request.
Tech stack
shell
Domain
apibackend
Issue type
Feature
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PowerShellGitGitHub API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70