Skip to content

gerald24/possy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

author
Gerald Leeb
Sep 9, 2019
d5b1f35 · Sep 9, 2019

History

89 Commits
Sep 9, 2019
Sep 8, 2019
Sep 9, 2019
Sep 6, 2019
Sep 6, 2019
Sep 8, 2019
Aug 24, 2019
Sep 8, 2019
Aug 21, 2019
Sep 8, 2019
Sep 9, 2019
Sep 8, 2019

Repository files navigation

possy Build Status Quality Gate Status Coverage daemon Heroku possy-daemon service Heroku possy-service

Possy was created based on Boris's idea to print out tasks, bugs and other issues on POS Printer (e.g. Epson TM-T20II) instead of using Post-it®, or print it on regular paper and use the scissor. Possy is an addition for physical scrum and kanban boards.

Overview

Overview

Components

  • possy-daemon (print job)
  • possy-service (print requests and Planner)
  • CUPS (print platform) - see also Installation Guide for setup
  • providers lika Jira, GitHub, etc. (currently only Jira supported)

possy-daemon

The daemon part connects to a possy-service and fetches print requests (simply text or image content). For each print request a PDF will be generated and printed via CUPS to a specific POS Printer(s). The daemon job might run on a Pi.

possy-service

The service is a Vaadin frontend, which creates print requests either by retrieving content from Jira (or other Providers) or get manually entered issues.

Issuetypes

Possy knows 4 different types of issues:

  • Stories
  • Tasks
  • Bugs
  • Freeform (like a note)

Printers

An issuetype is mapped to a specific printer (currently up to 3 different printer):

  • Stories -> white
  • Tasks -> white
  • Bugs -> pink
  • Freeform -> yellow

Get Started

Contributing

You want to contribute? Great! Thanks for being awesome! Please see the project related issues before you start coding. Pull requests are always welcome!

Code & Style

In short, we provide an .editorconfig file. For more information please have a look at https://editorconfig.org/.