Project Setup

[glutengo]

• [x] Fork Repository
• [x] Clone Repository
• [x] Get to know the source code
• [x] Run the project locally
• [x] Find possible improvements

[glutengo]

To get the project running locally, the following changes were needed:

• [Dockerfile] Explicitly install npm as suggested here
• [Dockerfile] Install python. This was required to be able to build some libraries, e.g. node-sass
• [docker-compose.yml] Exclude node_modules from volume as suggested here. This is required because the full working directory was mounted to the docker container as a volume. If the working directory does not contain the node_modules, these were not available at runtime even though they were installed during the build process of the image. Using the node_modules folder of the working directory is also not an option because the OS is likely to be different (e.g. Mac OS on the development machine vs. Alpine Linux in the Docker container).
• [yarn.lock] remove and re-create. Some versions were deprecated and could not be built anymore.

The changes which were made in the Dockerfile must probably be ported to Dockerfile.production and Dockerfile.travis-cli later

After the changes were made, the application could be started by running npm run dev. Once the application was running, the database needed to be migrated (npm run db:migrated) and seeded (npm run db:seed). After that, it was possible to login with one of the predefined users:

User	Role
user1@htw-berlin.de	student
user2@htw-berlin.de	student
user3@htw-berlin.de	student
user4@htw-berlin.de	instructor
user5@htw-berlin.de	instructor

As the LDAP user management is not used in development mode, any password allows access.

[glutengo]

Possible Improvements / suggestions

• Design Overhaul:
  • Material design?
  • Responsiveness
• Idea for new feature: session/transaction-based changes to backlog:
  • When the backlog (or a sprint) is to be changed, a new session is created. The context of a such session could be a Scrum Meeting such as Backlog Refinement or Sprint Planning. All changes happening in this session are staged and can be commited at the end of the session. A status message (e.g. "Adjustments made during Sprint Planning in calender week 23") can be added optionally (similar to git commit messages).
  • While a session is running, the projects backlog / sprints are locked so no one else can make changes.
  • While a session is running, other project members can watch the changes (live data)
• Idea for new feature: Connection to SCM. Git commits can reference stories so they are automatically closed or (alternatively or instead) a comment is added.
• Bug? Story IDs changes while sorting
• Console Error message when sorting stories in backlog
• TBC