Checklist for maturity

[elliottower]

Checklist for Maturity

Copied from shimmy a few months ago, feel free to mark things as complete (I believe anyone can)

• Support serialization via Pickle/EzPickle
• Fully deterministic
  • As far as possible
• Explicit Versioning
• Farama Notifications
• PyPI
• Full Package Description
• Deploy via GH Actions
• Website
• Linux and MacOS
• Precommit
• Typehinting
• Docstrings
• CI Testing
• Logo
• CoC (code of conduct)
• Gymnasium/PZ API
• Python Versions
• JKTerry and Mark as owners (pypi)
• TOTP (time based one time password)
• Google Analytics
• License
• Sponsor this project button

[MatPoliquin]

@elliottower For "Support serialization via Pickle/EzPickle", you mean for serializing envs?

[elliottower]

@elliottower For "Support serialization via Pickle/EzPickle", you mean for serializing envs?

Yeah that’s for environments, but if it’s not possible here due to the complex emulators it’s probably not a big deal

[MatPoliquin]

@elliottower For explicit versioning, does shimmy plan to use that? looking at the repo it's still using the 3 number versions

[elliottower]

Oh sorry I think there’s a misunderstanding. Explicit versioning is for environments so like whenever you change the logic or anything that would make training go differently, change it from pong_v0 to v1, etc. For emulated envs like here I would think it would be more similar to shimmy having DmControlCompatibilityWrapperV0 for example, which gets updated when it loads the envs differently or would somehow otherwise affect training like rewards changed etc. See the farama.org project standards for more info

[MatPoliquin]

@elliottower So the checklist is progressing, there is two remaining items I have questions with:
Google Analytics ID, where can I get the ID that Farama uses?
For the Farama notifications, is there a guide on how to integrate that?

[elliottower]

Tagged you in a discord thread with the web dev guy manuel and a thread in all devs about farama notifications