pinojs/pino

Add docs page: Switching from bunyan

Open

#727 opened on Oct 10, 2019

View on GitHub
 (4 comments) (3 reactions) (0 assignees)JavaScript (839 forks)batch import
documentationgood first issuehelp wanted

Repository metrics

Stars
 (13,157 stars)
PR merge metrics
 (Avg merge 1h 28m) (1 merged PR in 30d)

Description

I found Pino when googling for bunyan alternatives, because I'm hoping to replace bunyan in a Node web server project I've inherited.

It would be useful if Pino could add a "Switching from bunyan" docs page as a starting point for people in this position, to list any important conceptual differences and to map bunyan concepts to corresponding Pino concepts.

Contributor guide

Research direction
Review the existing Pino documentation structure and create a migration guide mapping bunyan concepts to Pino equivalents.
Tech stack
javascriptnodejs
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80