-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move FoxDot repositories and the project governance to community-based approach #255
Comments
Instead of forking the foxdot repositories inside the new group, I suggest moving them there instead, since that way you retain things like issues, pull requests, projects etc within the new group. If you create forks, the open issues/etc stay with the old repos. |
Nowadays looks like that the FoxDot community is organized around the fork below: |
Any news on this point ? FoxDot is a very cool project, and it would be nice if it can continue |
The only news I have is that the FoxDot community is working and evolving the fork below: |
I note that iShapeNoise is an individual user too like @Qirky, so
this approach will possibly have the same problems as the old effort,
much better would be to have a GitHub/GitLab org/group instead.
…--
bye,
pabs
https://bonedaddy.net/pabs3/
|
In the README, I see a that synth and samples have been added. Are every added thing under a FOSS licence ? |
Hello @Qirky,
I would like first to say thank you very much for all your great work on FoxDot, and it is a shame that you are no longer available to keep the project going on.
Said that I would like to ask you if you agree to move the FoxDot governance to a community-based group, in practicals ways it means:
Are you ok to move in this direction? Someone else would like to propose something different? I put myself as volunteer to organize the group, repositories, documentation, etc...
Best,
The text was updated successfully, but these errors were encountered: