https://github.com/unfoldingword-dev/ts-requirements

https://github.com/unfoldingword-dev/ts-requirements

Last synced: 3 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/unfoldingword-dev/ts-requirements
• Owner: unfoldingWord-dev
• License: other
• Created: 2015-04-24T02:32:07.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2016-03-25T20:23:25.000Z (over 10 years ago)
• Last Synced: 2026-01-01T07:38:00.214Z (6 months ago)
• Language: Cucumber
• Size: 39.1 KB
• Stars: 3
• Watchers: 10
• Forks: 0
• Open Issues: 131
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
translationStudio Requirements

---

These are the requirements and specifications for translationStudio. The projects using these requirements are

* [tS Android](https://github.com/unfoldingWord-dev/ts-android)

* [tS Desktop](https://github.com/unfoldingWord-dev/ts-desktop)

* [tS Server](https://github.com/unfoldingWord-dev/ts-server)

##Format

The requirements are written in [Gherkin](https://github.com/cucumber/cucumber/wiki/Gherkin) so that they can be ran through [Cucumber](https://cukes.info/). You can also read about Gherkin at [Behat](http://docs.behat.org/en/latest/guides/1.gherkin.html). The documentation there is a little cleaner.

##Purpose

These requirements provide a unified definition of features to be implimented in tS. This allows for more reliable testing, better collaboration, and helps to maintain focus on the long term goals of tS.

The practical application of these requirements will be in the establishment of acceptance tests. We will potentially use [PioneerJs](http://pioneerjs.com/) to run these tests.

##Process for Adding Features

To better control new features in Translation Studio we use a simple triage system to evaluate features and assign them to the correct work queues. The process will be as shown in the following workflow.

Triage: Determine the correct priority, labels, flesh out details, split to atomic units of work (could be multiple repo backlogs) 

Controlled by Product Owner and Lead in each repo (e.g. Jesse, Joel, Vicky)


Lead in each repo creates issue in their queue


Discussed by Team as needed


Weekly meeting unless other urgent need arises