New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move individual Reporta projects to seperate revision controlled repositories. #2

Open
seamustuohy opened this Issue Jan 8, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@seamustuohy

seamustuohy commented Jan 8, 2016

Happy to see you have taken the step to open source this project. I would suggest making individual project repositories for each of the sub-projects for a variety of reasons.

Keeping each project in its own version controlled repository encourages users to participate by removing the requirement that they download and unzip the current code bases to see the code. Furthermore it allows you to directly tie community concerns and requests directly to the code you changed to address them, and allows developers to browse the changes that you have made directly in the web-interface. It also allows outside developers to use git and github's built in functionality for forking, adding features/fixes, and submitting code back to your project. These are only a few of the cool things that can be done when you put the files directly in the repository instead of in a zip file.

I have gone ahead and made repositories with your android, admin, and iOS, code bases that you can just fork to your organizations repository list to make it easier for you. I used githubs default gitignore files so that your repositories would automatically filter out some of the well known binary and compiled files that might sneak in.

I did NOT make a repository for the v8 php_code_helper_using_phpdoc because I did not know if it was a part of the Reporta admin backend or a separate project that you would rather link to. So, you will have to add that to your admin repository if that is desired.

@IWMF

This comment has been minimized.

Show comment
Hide comment
@IWMF

IWMF Jan 13, 2016

Contributor

Hi Seamus--

Don't know how I missed your email earlier--- just popped up this AM.

Thanks for your advice on posting on Github. I initially just wanted to get the code posted and available-- we weren't sure anyone would really want to pull it down and take a look

I'll follow up on your suggestions asap!

Tom

Tom McGuire
IWMF
1625 K Street, NW, Suite 1275
Washington, D.C. 20006
p:(415) 902-tel:%28202%29%20567-26059486
f: (202) 496-1977tel:%28202%29%20496-1977
http://www.iwmf.orghttp://www.iwmf.org/http://www.iwmf.org/

[25 Logo Final_R1_SMALL2_RGB (4)]


From: Seamus Tuohy notifications@github.com
Sent: Friday, January 8, 2016 4:50 PM
To: ReportaIWMF/Reporta-apps-and-backend-db
Subject: [Reporta-apps-and-backend-db] Move individual Reporta projects to seperate revision controlled repositories. (#2)

Happy to see you have taken the step to open source this project. I would suggest making individual project repositories for each of the sub-projects for a variety of reasons.

Keeping each project in its own version controlled repository encourages users to participatehttp://producingoss.com/en/getting-started.html#vc-and-bug-tracker-access by removing the requirement that they download and unzip the current code bases to see the code. Furthermore it allows you to directly tie community concerns and requests directly to the code you changed to address themhttps://github.com/blog/957-introducing-issue-mentions, and allows developers to browse the changes that you have made directly in the web-interface. It also allows outside developers to use git and github's built in functionality for forking, adding features/fixes, and submitting code backhttps://guides.github.com/introduction/flow/ to your project. These are only a few of the cool thingshttps://github.com/features that can be done when you put the files directly in the repository instead of in a zip file.

I have gone ahead and made repositories with your androidhttps://github.com/elationfoundation/Reporta-Android, adminhttps://github.com/elationfoundation/Reporta-backend, and iOShttps://github.com/elationfoundation/Reporta-iOS, code bases that you can just forkhttps://guides.github.com/activities/forking/ to your organizations repository list to make it easier for you. I used githubs default gitignore fileshttps://help.github.com/articles/ignoring-files/ so that your repositories would automatically filter out some of the well known binary and compiled files that might sneak in.

I did NOT make a repository for the v8 "php_code_helper_using_phpdoc" because I did not know if it was a part of the Reporta admin backend or a separate project that you would rather link to. So, you will have to add that to your admin repository if that is desired.

Reply to this email directly or view it on GitHubhttps://github.com//issues/2.

Contributor

IWMF commented Jan 13, 2016

Hi Seamus--

Don't know how I missed your email earlier--- just popped up this AM.

Thanks for your advice on posting on Github. I initially just wanted to get the code posted and available-- we weren't sure anyone would really want to pull it down and take a look

I'll follow up on your suggestions asap!

Tom

Tom McGuire
IWMF
1625 K Street, NW, Suite 1275
Washington, D.C. 20006
p:(415) 902-tel:%28202%29%20567-26059486
f: (202) 496-1977tel:%28202%29%20496-1977
http://www.iwmf.orghttp://www.iwmf.org/http://www.iwmf.org/

[25 Logo Final_R1_SMALL2_RGB (4)]


From: Seamus Tuohy notifications@github.com
Sent: Friday, January 8, 2016 4:50 PM
To: ReportaIWMF/Reporta-apps-and-backend-db
Subject: [Reporta-apps-and-backend-db] Move individual Reporta projects to seperate revision controlled repositories. (#2)

Happy to see you have taken the step to open source this project. I would suggest making individual project repositories for each of the sub-projects for a variety of reasons.

Keeping each project in its own version controlled repository encourages users to participatehttp://producingoss.com/en/getting-started.html#vc-and-bug-tracker-access by removing the requirement that they download and unzip the current code bases to see the code. Furthermore it allows you to directly tie community concerns and requests directly to the code you changed to address themhttps://github.com/blog/957-introducing-issue-mentions, and allows developers to browse the changes that you have made directly in the web-interface. It also allows outside developers to use git and github's built in functionality for forking, adding features/fixes, and submitting code backhttps://guides.github.com/introduction/flow/ to your project. These are only a few of the cool thingshttps://github.com/features that can be done when you put the files directly in the repository instead of in a zip file.

I have gone ahead and made repositories with your androidhttps://github.com/elationfoundation/Reporta-Android, adminhttps://github.com/elationfoundation/Reporta-backend, and iOShttps://github.com/elationfoundation/Reporta-iOS, code bases that you can just forkhttps://guides.github.com/activities/forking/ to your organizations repository list to make it easier for you. I used githubs default gitignore fileshttps://help.github.com/articles/ignoring-files/ so that your repositories would automatically filter out some of the well known binary and compiled files that might sneak in.

I did NOT make a repository for the v8 "php_code_helper_using_phpdoc" because I did not know if it was a part of the Reporta admin backend or a separate project that you would rather link to. So, you will have to add that to your admin repository if that is desired.

Reply to this email directly or view it on GitHubhttps://github.com//issues/2.

@seamustuohy

This comment has been minimized.

Show comment
Hide comment
@seamustuohy

seamustuohy Feb 15, 2016

Hey Tom,

You could easily do this simply by forking the repo's that I created for you. All you will have to do is visit the following three links and click the fork button on the top right. This will copy those repositories into the Reporta Project page where you can update them as you change the code, etc. Once you have forked the repositories you can change the names, titles, url's, README's etc. however you wish. But, it would make the code immediately available to the public from your organizations page.

seamustuohy commented Feb 15, 2016

Hey Tom,

You could easily do this simply by forking the repo's that I created for you. All you will have to do is visit the following three links and click the fork button on the top right. This will copy those repositories into the Reporta Project page where you can update them as you change the code, etc. Once you have forked the repositories you can change the names, titles, url's, README's etc. however you wish. But, it would make the code immediately available to the public from your organizations page.

@kjantin

This comment has been minimized.

Show comment
Hide comment
@kjantin

kjantin Feb 21, 2017

Please make your code easier to access and provide feedback on, as @seamustuohy has so kindly guided you on above!

kjantin commented Feb 21, 2017

Please make your code easier to access and provide feedback on, as @seamustuohy has so kindly guided you on above!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment