How to contribute

Prerequisites

• You'll need to be in the dspace-angular github team to get the required access. Send your github username to Art Lowel (Atmire) to get an invite.
• Fork the repository on Github

Workflow

• Have a look at the waffle board

• Take an issue that’s in the ready section and has nobody assigned to it

• assign yourself

• When you start working on it, move the issue to the “in progress” section

• Work on a separate branch for the issue on your fork

• Add a link to the branch on your fork as a comment to the task on the waffle board. That way people can 

• When you’re ready, fire a pull request

• in the comments of the pull request, write something akin to “this PR connect’s to #{the ID of the issue}”. That way the issue will be moved automatically to the review column.

• When at least two people have reviewed and approved your PR, it can be merged in master.

• You can also help out by reviewing the pull requests of other people

• Please keep an eye on your pull request afterwards, the reviewers may have questions or comments about it, or ask you to tackle things in a different way, before they can approve it

• Most discussions about the task or the pull request can happen through the github & waffle board comments.

• If it’s more complex you can bring it up in one of these meetings.

• After your Pull Request has been merged, drag the issue to the done column on the waffle board. (this can also be automated by adding “this merge closes #{the id of the issue}” in the merge comment.

Learning Resources

General

Angular 2 Resources

...

• https://angular.io/styleguide - The official Angular2 for TypeScript Style Guide
• https://angular.io/docs/ts/latest/ - The official documentation for Angular 2 (with TypeScript). Includes a "5-min quick start", "step-by-step guide" and official API docs
• https://github.com/angular/angular - The official codebase for Angular 2. Where to submit issues, follow the code progression, etc.
• http://angularjs.blogspot.com/ - The Angular blog, which contains updates and blog posts from the Angular team.
• https://groups.google.com/forum/#!forum/angular - Google Group for Angular 1 or 2 discussions.
• https://angularair.com/ - A live video podcast all about Angular
• https://www.npmjs.com/package/npm-check-updates - A npm package for dependency management
• Scotch.io has a bunch of articles on various angular 2 topics

Typescript

...

• http://www.typescriptlang.org/ - The official documentation for the TypeScript language. Includes links to sample code, as well as a live in-browser editor/samples.
• See also the TypeScript Guidelines on the Prototype's wiki

...

• The concepts are explained clearly, though independently from angular in the main redux docs
• There is also a great free video course on egghead
• @ngrx is an implementation of Redux for Angular 2 using RxJS
• Ducks is a way to structure redux applications to keep them as modular as possible that works well in practice.

How to contribute

Prerequisites

• You'll need to be in the dspace-angular github team to get the required access. Send your github username to Art Lowel to get an invite.
• Fork the repository on Github

Workflow

• Have a look at the waffle board

• Take an issue that’s in the ready section and has nobody assigned to it

• assign yourself

• When you start working on it, move the issue to the “in progress” section

• Work on a separate branch for the issue on your fork

• Add a link to the branch on your fork as a comment to the task on the waffle board. That way people can 

• When you’re ready, fire a pull request

• in the comments of the pull request, write something akin to “this PR connect’s to #{the ID of the issue}”. That way the issue will be moved automatically to the review column.

• When at least two people have reviewed and approved your PR, it can be merged in master.

• You can also help out by reviewing the pull requests of other people

• Please keep an eye on your pull request afterwards, the reviewers may have questions or comments about it, or ask you to tackle things in a different way, before they can approve it

• Most discussions about the task or the pull request can happen through the github & waffle board comments.

• If it’s more complex you can bring it up in one of these meetings.

• After your Pull Request has been merged, drag the issue to the done column on the waffle board. (this can also be automated by adding “this merge closes #{the id of the issue}” in the merge comment.