Skip to content
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

[ENH] Create a FAQ section in the wiki #175

Open
bclenet opened this issue Feb 14, 2024 · 0 comments
Open

[ENH] Create a FAQ section in the wiki #175

bclenet opened this issue Feb 14, 2024 · 0 comments
Labels
🧍 aspect: accessibility Concerns developers' experience with the codebase 📄 aspect: text Concerns the textual material in the repository 🏁 status: ready for dev Ready for work

Comments

@bclenet
Copy link
Collaborator

bclenet commented Feb 14, 2024

Goal

Help contributors and users to solve known bugs while using the project

Why this is useful

Contributors and users would benefit from a better experience using the project.
Especially as the installation process can be tricky, depending on the OS and knowledge of the users.

Timeline

No response

More specifically

List known bugs, such as:

  • issues / tips / notice with datalad
  • nipype execution bug when missing files / wrong file names
  • nipype behaviour when lack of space / memory
  • ...

Open questions

No response

@bclenet bclenet added 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🏁 status: ready for dev Ready for work 📄 aspect: text Concerns the textual material in the repository 🧍 aspect: accessibility Concerns developers' experience with the codebase and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧍 aspect: accessibility Concerns developers' experience with the codebase 📄 aspect: text Concerns the textual material in the repository 🏁 status: ready for dev Ready for work
Projects
None yet
Development

No branches or pull requests

1 participant