public-transport/friendly-public-transport-format

fptf 2.0.0 checklist

Open

#37 opened on Mar 27, 2018

View on GitHub
 (7 comments) (1 reaction) (0 assignees) (3 forks)github user discovery
breaking-changedesignenhancementhelp wanted

Repository metrics

Stars
 (139 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Things we need to work on for fptf 2.0.0:

  • add a code of conduct (?) #36
  • decide on / implement stopover type #35
  • [ ] decide on major design changes proposed in #61
  • [ ] add the canceled attribute #27
  • decide on wether to "forbid" redundant origin/destination information in journeys #34
  • [ ] decide on proposed information up-to-dateness attribute #43
  • [ ] decide on modes / products #62

This issue's intention is not to rush publishing the next version, it should just provide a neat checklist for what we still have to work on.

Contributor guide

Research direction
Review the linked issues and discussions to understand the design decisions needed for fptf 2.0.0.
Tech stack
None
Domain
data
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.
Mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30