Contributing to PyCorrFit

[varunkas]

Dear Paul Mueller,

Firstly, thank you for developing PyCorrFit. It is being very useful for my work - I started using it around 5 months ago. I have limited experience with FCS, but my current research is dependent on it. I am located at University of New South Wales, Sydney.

I wish to contribute to this project. If I can financially contribute to the project, I would require an invoice that I can pay for. I am also reasonably good at LaTeX, so can contribute to documentation.

Please let me know.

Cheers,
Varun

[paulmueller]

Dear Varun,

thank you for your offer.

Regarding financial contributions: Due to tax regulations, I think I am currently not able to send an invoice outside the European Union. An alternative would be to create a nonprofit organization to which you would be able to donate (e.g. via bank transfer or https://en.liberapay.com). I will have to get legal advice here. How much money are we talking about?

Regarding contributions to the documentation: The most pressing task right now is to convert the old LaTeX documentation to the new reStructuredText documentation.
In principle, once you are familiar with forks and pull requests on GitHub, have understood how sphinx works, and you have set it up successfully, there is no one stopping you. If you run into any questions, please ask them here. It would probably also be good to update the new documentation with a step-by-step guide on how to contribute to the documentation with the experience you have gathered on the way.

[varunkas]

Dear Paul, As a research, this contribution will come from my research funds. So, an invoice might be necessary. If this is not possible, then I will have to contact our finance team. I am thinking something around $500. Please let me know. OK, I will look into how I can contribute to conversion of documentations. Thanks, Varun Thanks, Varun Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

…

________________________________ From: Paul Müller <notifications@github.com> Sent: Tuesday, June 19, 2018 7:07:14 PM To: FCS-analysis/PyCorrFit Cc: varunkas; Author Subject: Re: [FCS-analysis/PyCorrFit] Contributing to PyCorrFit (#184) Dear Varun, thank you for your offer. Regarding financial contributions: Due to tax regulations, I think I am currently not able to send an invoice outside the European Union. An alternative would be to create a nonprofit organization to which you would be able to donate (e.g. via bank transfer or https://en.liberapay.com). I will have to get legal advice here. How much money are we talking about? Regarding contributions to the documentation: The most pressing task right now is to convert the old LaTeX documentation<https://github.com/FCS-analysis/PyCorrFit/tree/develop/doc> to the new reStructuredText documentation<https://github.com/FCS-analysis/PyCorrFit/tree/develop/docs>. In principle, once you are familiar with forks<https://help.github.com/articles/fork-a-repo/> and pull requests<https://help.github.com/articles/creating-a-pull-request-from-a-fork/> on GitHub, have understood how sphinx<http://www.sphinx-doc.org/en/stable/> works, and you have set it up<https://pycorrfit.readthedocs.io/en/stable/sec_contribute.html#for-documentation-writers> successfully, there is no one stopping you. If you run into any questions, please ask them here. It would probably also be good to update the new documentation with a step-by-step guide on how to contribute to the documentation with the experience you have gathered on the way. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#184 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AmgRyxYLWawBqa0_yalQl5Q3U_4-xflsks5t-L9CgaJpZM4UssN4>.