Sagemath integration GSOC project

[edwardchalstrey1]

Using this Discussion thread for @ameliekleber Google summer of code project discussions

Useful links:

• GSOC timeline
• Original plan
• Stale PR: gambit: Re-create as a pip package pygambit (help wanted!) sagemath/sage#37809
• Related discussion on SageMath interoperability tutorial [Tutorial]: SageMath interoperability tutorial #852

[edwardchalstrey1]

Getting started

Hi @ameliekleber here are some notes from our meeting yesterday to help you get started:

• Look into creating a personal project board (Kanban), where you can organise any issues you create on your forks of SageMath and Gambit (and any existing issues you end up working on from the upstream repos)
• We discussed as you work on the project, creating issues for individual changes you intend to make, and making pull requests specific to particular issues. One consideration we didn't discuss was an exact workflow for branches and pull requests, I suggest the following:
  • For Gambit, any pull requests should come from a branch on your fork and target the main branch in the upstream gambit repo
  • For SageMath, as you make individual changes, you can make pull requests to the develop branch within your fork when you want review from me and Rahul. Once the integration is completed and working well on your fork, you can make a single PR with all the changes from your fork to the upstream repo's develop branch (assuming this is the way SageMath handle contributions, which you should check)
• If you want to copy mkoeppe:gambit_repair branch over to her fork as well you can try, but it will likely be much more manageable to start from scratch and manually copy parts of this code as needed, making new commits as you go
• As discussed, once you begin the work, you could send a brief message @ kcrisman on the original PR and say you will fork SageMath from the develop branch (or whatever their contributor guidance says) and begin working there, now you are working with the Gambit team on this as part of GSOC

[edwardchalstrey1]

Once the integration is completed and working well on your fork, you can make a single PR with all the changes from your fork to the upstream repo's develop branch

One small suggestion from today's meeting relating to the above was (if you wanted) to open this PR early in draft form, to give Sagemath devs visibility of your work.