Skip to content

alrotech/mspay.github.io

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

MS Payments Project

Overall high-level description of the project. Some parts of documentation and descriptions may be placed to appropriate repositories. This repository represents the public part of the entire project. Generated copy of this documentation available on the website about.mspay.by or mspay.github.io (if original domain by any reason will be lost).

Development Process

Development process and work in general under the project base on Agile principals but are not fully covered. We are using Projects, Epics, User Stories to describe tasks, that should be done. These terms were adopted a bit to have the ability to use them via built-in tools, that GitHub provides.

That means that we use GitHub Projects for describing the projects, by Agile it is a replacement for Initiatives. Epics are done via milestones with or without setting the date of end. From an Agile perspective, it may look strange, but the main goal to show real state and progress at any time. User Stories are usual Issues.

Roles for user stories not strictly defined, it based on the context of usage. In case of a technical story, the role may be a developer, if we a describing user experience, it may be a customer or author of extra, etc.

Projects

Projects on GitHub works as Initiatives from Agile methodology and combine inside all work, related to the goal, that should be reached. The project is an overall piece of work, unrelated to any repository, service, or any other things. The task in the project can include work under code, documentation stuff, dealing with the authorities, etc.

The most important goal of project to provide visibility of the progress of the work. How much should be done, what left to implement and solve, how far from or close to the finish we are.

Below is a list of active projects with their short descriptions. Follow the links to see the progress of each and see all linked repositories.

Work that is related to extensions for payment gateways.

Development tools for generating MODX-compatible packages.

Managing users, roles, scopes, authorization and authentication, JWT-processing and other related to users and their accounts work.

Managing, uploading, updating and building the packages and their versions.

  • Packages and Versions models
  • UI for package management
  • Pulic package listing

Managing licenses, packs of licenses, access keys, and all that replated to packages protection, including encryption.

All work that is related to receiving money. Integration of payment system, setting prices and subscriptions, handling cashless payments.

  • UI for account payment information

Managing all customer's requests for any reason.

  • Tickets models and structure (api)
  • UI for tickets management (admin)
  • UI for tickets creating (client)

Services

Service usually is live environment, available for end-users. As well, based on the context of usage, service may mean a staging/testing environment or repository with a code of service. Below presented matrix of services and their sources and instances.

Name Links Description
Data Live / Test / Repo Backend API for marketplace
Langing Live / Test / Repo The main website of the payment solutions service
Extras Live / Test / Repo Repository REST service for MODX, based on Slim Framework
Admin Live / Test / Repo Admin dashboard. While development, it uses a temporary name and hosted on the Netlify
Client Live / Test / Repo Client dashboard. While development, it uses a temporary name and hosted on the Netlify