What are the ECR Code Sharing Use Cases?

The current ECR Uses cases include the following:

Push and Forget

If this is a one-time thing, then you would simply push your code to ECR Bitbucket, create a community branch, set that as the default branch in the Bitbucket UI, and then walk away.  This approach can easily be converted to a periodically synchronized project.

Push and Sync

This model is used when you want to make periodic updates to your code, and share those updates with the community.  When you do this, you will push your branches (master, develop etc.) and then you will create a Pull Request (PR) to merge the changes from the develop branch into the community branch.  You could just pull your changes into community, but the PR allows everyone to see what changes are coming, and to even give a thumbs up/down vote on accepting the changes.

Setting up this type of project is basically the same as the Push and Forget model. You will push your code to ECR Bitbucket, create the community branch and then set it as the default branch.  The only thing remaining is to occasionally push updated code to ECR.

Push and Pull

The final use case is when you not only want to share code in ECR, but you are expecting that other developers in Leidos will want to share changes back with you.  Setup is the same as Push and Sync, however, when updates are made to the community branch, developers will create PRs that you will moderate (accept, reject), and then you will - when you want, pull those changes back to your original repo.  This is the GitHub model.

Fork or Clone

This last use case, was not listed in the group of use cases above, because its not a "sharing" model per se.  The Fork or Clone model is simply one where you are not sharing code, but rather you are reusing code shared by someone else.  In this case, you will clone the existing repository to your local disk and then make use of the code in your own project.  You can also fork the code.  Git does not really have an underlying fork command.  Forking code in Bitbucket will result in you getting a new repository created that you can manage from Bitbucket.  You can create PRs from your Forked code, back to ECR. This is also the GitHub model, but in this case, you adopt the code, maintain it, and if there is something that you want to share back, you do that using PRs.