How can I collaborate with code?

Software Support
,
1

I’d like to collaborate with this patch of OJS 3.0.1:
https://github.com/pkp/ojs/compare/ojs-3_0_1-0…ojs-stable-3_0_1

I found 4 points inside this patch that I believe need to change.
How can I collaborate with code? (I need to use or create a branch)

PS.: It’s my first time that I try to collaborate with code.

2

We have an introductory document regarding our use of git branches here:
https://pkp.sfu.ca/wiki/index.php?title=Github_Documentation_for_PKP_Contributors

1 Like
3

Thanks @ctgraham
Now, when I try to push in a new branch, this error appear:
fatal: unable to access ‘GitHub - pkp/pkp-lib: The library used by PKP's applications OJS, OMP and OPS, open source software for scholarly publishing.’: The requested URL returned error: 403

I did the commands with this sequence:

git clone GitHub - pkp/pkp-lib: The library used by PKP's applications OJS, OMP and OPS, open source software for scholarly publishing.
cd pkp-lib
git checkout -b ptBR origin/ojs-dev-2_4
git submodule update --init --recursive
git add .
git commit -m ‘Translation of tag to pt_BR’
git push origin ptBR

4

You’ll want to fork the pkp-lib repo to your own account on Github. Then push the branch to your fork, rather than to the the “pkp” repository. You can use multiple remotes in your local git repo to stay in touch with the pkp repo and your own fork’s branches.

For example, I use my department’s account (ulsdevteam).

git clone https://github.com/ulsdevteam/pkp-lib.git
cd pkp-lib
git remote add upstream https://github.com/pkp/pkp-lib.git
git fetch upstream
git checkout -b my-new-feature upstream/ojs-dev-2_4
git add .
git commit
git push origin my-new-feature
2 Likes
5

It works! =D
Now, how the official development team knows about my contribution, to analise if it is useful?

6

I guess I discover. \o/
I need to use the botton “New pull request” and to compare the branches.
Is this? @ctgraham

7

That is correct. In GitHub, create a new pull request, comparing against the branch you used as the basis of the feature. This should send your changes for review back up to the upstream repository.

1 Like