Replies: 4 comments 4 replies
-
Overall, I think it is a good idea! The PyFixest package is not that large now, and the syntax is consistent. Hence, in the short term, I do not think it is necessary to create many repositories, especially as it would require significant work. You could start by creating the GitHub organization and add these projects there as the effect of this does not seem that big :) |
Beta Was this translation helpful? Give feedback.
-
Hi! This is a great project and idea. No issues with wildboottest being put under an org as long as I keep the same permissions 😀. But perhaps name it something more general? Theres a lot of interesting projects here that might not only be useful as modules in |
Beta Was this translation helpful? Give feedback.
-
Thanks Aleks (@amichuda) - of course you will keep all your rights to the |
Beta Was this translation helpful? Give feedback.
-
I've now moved both |
Beta Was this translation helpful? Give feedback.
-
Most successful open source project seem to be managed via a github organization. Would it make sense to move the pyfixest repository to a pyfixest org? What would be advantages and disadvantages?
Pro:
ccv
module, theritest
module, themultcomp
module, thedid
module), just as wildboottest . Moving these repositories out of pyfixest might allow for more general code that works with other regression packages (e.g. statsmodels). Additionally, it might decrease the CI runtime of the main repo, pyfixest, as most of the tests for e.g. the ccv repo would take place in the specialized repositories. This should speed up the development time of all new pyfixest features.Con:
@juanitorduz @NKeleher @aeturrell Do you have any thoughts / opinions / experiences on this topic? @amichuda, would you be open to move the
wildboottest
repo to apyfixest
org?Beta Was this translation helpful? Give feedback.
All reactions