Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I invoices.freedoomcop.eu
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • faircoopfaircoop
  • FairCoopTechFairCoopTech
  • FairCoopSitesFairCoopSites
  • invoices.freedoomcop.eu
  • Wiki
  • Requirements

Requirements · Changes

Page history
Update Requirements authored Apr 03, 2019 by santi's avatar santi
Hide whitespace changes
Inline Side-by-side
Requirements.md
View page @ 5a25db0b
......@@ -6,10 +6,21 @@ Discussion about this doc in #19
This doc describe the whole process of invoicing in FreedomCoop. It should detail the workflows, user roles, user permissions, translations, etc. This is not a tech doc but a description about how the future apps should work and what features are a must, desired, or optionals.
Customer: Organization or person invoiced. It receives the invoice and make a payment.
Partner: FreedomCoop partner wich wants to make an invoice to Customer.
Manager: FreedomCoop worker.
Admin: Supersuser, tech, issues, new features,...
### Common vocabulary
* Customer: Organization or person invoiced. It receives the invoice and make a payment.
* Partner: FreedomCoop partner wich wants to make an invoice to Customer.
* Manager: FreedomCoop worker.
* Admin: Supersuser, tech, issues, new features,...
### Definitions
RFC 2119 gives the following definitions:
MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.
MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.
SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)
## Workflow
......
Clone repository
  • Requirements
  • Home

gitlab project and software management by fairkom.eu - more open source web apps at fairapps.net