You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's open a discussion around maintenance and future development of FMMAX.
FMMAX has won some adoption among academic researchers of nanophotonic design, and it represents a useful new tool in the inverse design software ecosystem. This is a nice early outcome for an open-source Meta project. For this to be sustained, however, FMMAX must be maintained and expanded, e.g. by fixing breakages, security issues, adding new features, examples, and documentation to help onboard new users.
This development has slowed or stopped, primarily due to the fact that developers have either left Meta or moved on to other internal projects. I believe we should find some way to address this, so that FMMAX remains useful to the research community.
One possibility would be to transfer the repo to an owner who takes on the maintenance/development burden. This is something that I am willing to do. Let's start a discussion around this and other possibilities for moving forward.
Let's open a discussion around maintenance and future development of FMMAX.
FMMAX has won some adoption among academic researchers of nanophotonic design, and it represents a useful new tool in the inverse design software ecosystem. This is a nice early outcome for an open-source Meta project. For this to be sustained, however, FMMAX must be maintained and expanded, e.g. by fixing breakages, security issues, adding new features, examples, and documentation to help onboard new users.
This development has slowed or stopped, primarily due to the fact that developers have either left Meta or moved on to other internal projects. I believe we should find some way to address this, so that FMMAX remains useful to the research community.
One possibility would be to transfer the repo to an owner who takes on the maintenance/development burden. This is something that I am willing to do. Let's start a discussion around this and other possibilities for moving forward.
FYI @smartalecH
The text was updated successfully, but these errors were encountered: