GitHub not updated

[Max R. P. Grossmann]

Hi Chris,

I'm certain I'm missing something: Where can I find the Git repository with oTree's more recent versions? This doesn't seem to be the correct one as it has not been updated in over a year: https://github.com/oTree-org/oTree-core

(I'm aware that the source code is available using other approaches, but this is much more cumbersome)

Thanks,

Max

[Peter Cock]

I would echo this request, having raised the same point as a GitHub issue over a year ago:

https://github.com/oTree-org/otree-core/issues/542

Thank you,

Peter

[Ali Seyhun Saral]

I also would like to have that. I asked a similar question in the group (couldn't find the thread though) a while ago and Chris responded:

the repo is indeed often behind the latest release (because I do not like to use Git and in the past when I used Github actively I did not get much engagement there). If you want to patch something, you should use the latest release from PyPI. Either go to your interpreter's Lib/site-packages folder, where oTree's source code is already located, or download and unzip this file: https://pypi.org/project/otree/#files

If Chris understandably still feels the same way (given that already he has been putting a superhuman level of work for supporting the community), perhaps some trusted people can put a mirror repository on GitHub and take the load from his shoulders. Maybe that wouldn't help for the feature/pull requests but it would be helpful to track the changes and conveniently work on it.

But that made me wonder: there is no change in the open-source status of the software right? (I guess it's MIT Licence + Citation Requirement). So @Chris how would you feel about such a mirror repo?

Best,

ali

--
You received this message because you are subscribed to the Google Groups "oTree help & discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to otree+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/otree/e570d300-fcbd-4d90-80ff-70ef7d8b9d60n%40googlegroups.com.

[Chris @ oTree]

Hi, yes that is right. Adding new features to otree-core is already really challenging and I don't want to change the workflow I have now. However, if someone wants to make a script that makes git diffs out of the releases on PyPI from here then I would be happy to host that repo on the official oTree GitHub account, so that people can browse the difference between releases.

As for pull requests & contributions to otree-core, the best way to start is with a discussion of the proposed functionality, either through email, this discussion group, or GitHub. Once we have agreed on a design, then merging in the changes will be the easy part :)

Though I haven't felt the need to set up more of a process for that, since there are not many people proposing contributions, either in oTree-core or the other oTree repositories such as oTree HR, the sample games, docs, etc here: https://github.com/oTree-org/. By the way these other repos are ripe for external contributions, and much easier to contribute to.

Chris

[Peter Cock]

That sounds like a good idea, even one commit per release covers many of
the use cases. I wonder if there is an existing bot framework to automate
this when Chris updates PyPI?

Even something like my old script https://github.com/peterjc/tarball2git plus
PyPI monitoring in a cron job would be crude but get the job done.

If not, volunteers doing this by hand once in a while would still be welcome.

Peter

> You received this message because you are subscribed to a topic in the Google Groups "oTree help & discussion" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/otree/foKpjU43pgo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to otree+un...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/otree/3cbf2204-9e09-416d-81b1-4c97dc3b8b35n%40googlegroups.com.

[Chris @ oTree]

This URL provides all oTree releases in JSON format: https://pypi.org/pypi/otree/json

It has links to the tarballs. A cron job could check this page once a day or so.