-
Notifications
You must be signed in to change notification settings - Fork 19
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
phys2denoise 1.0 #13
Comments
Do you want to organize 1.0 into a project board or make a milestone? |
I'm pro project board! |
I'm normally pro-milestone, but I don't think we have a deadline and hey, learning new things is fun. Let's keep this issue open for discussion around necessary steps to get to 1.0 |
I'm happy to add my perspective on what may be helpful to include in the phys2denoise package. What is the best way to do that - on this thread, on separate issues, on the project board (<How best should that be used?)? Thanks. |
Count on me (depending on my time and my limited expertise) |
@physiopy/all , I'm opening this issue so that we can start tracking the development of
phys2denoise
, but especially so that we can decide what do we expect from it before promoting it out of testing stages.Please feel free to add ideas and start a discussion!
The text was updated successfully, but these errors were encountered: