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
Some times ago, you committed 761e800 which changed the README file to indicate that the project was discontinued.
You pushed a few commits since then, but if you do not plan to maintain this software package anymore, I am wondering if it would make sense to move the project to an organization (e.g. smpc-project) and open the project to more contributors? If you do so, I would like to be added to this project in order to support further smpc. @neomilium, who I have been working with for many years, would also be interested in joining-in.
However, if the change committed to the README file was unexpected, you can also simply revert this commit 😉.
Thanks!
The text was updated successfully, but these errors were encountered:
the commits were to clean up the backend code. I'll continue on this as this is quite generic and can be used for further qt projects.
After this I'll consider it. Maybe it could be like an SMPC project of a github group that includes the mpd part as a subproject or so. But at first a lot of cleanup has to be done because the code is quite messy. It was done with a hot iron
Hi @djselbeck,
Some times ago, you committed 761e800 which changed the
README
file to indicate that the project was discontinued.You pushed a few commits since then, but if you do not plan to maintain this software package anymore, I am wondering if it would make sense to move the project to an organization (e.g. smpc-project) and open the project to more contributors? If you do so, I would like to be added to this project in order to support further smpc. @neomilium, who I have been working with for many years, would also be interested in joining-in.
However, if the change committed to the README file was unexpected, you can also simply revert this commit 😉.
Thanks!
The text was updated successfully, but these errors were encountered: