-
-
Notifications
You must be signed in to change notification settings - Fork 19
Meta: Naming of Modules and Subworkflows #150
Copy link
Copy link
Open
Labels
sigIssue to be further discussed by the Neuroimaging Special Interest GroupIssue to be further discussed by the Neuroimaging Special Interest GroupwaitingIssue waiting on another issue, discussion or PR elsewhereIssue waiting on another issue, discussion or PR elsewhere
Description
Metadata
Metadata
Assignees
Labels
sigIssue to be further discussed by the Neuroimaging Special Interest GroupIssue to be further discussed by the Neuroimaging Special Interest GroupwaitingIssue waiting on another issue, discussion or PR elsewhereIssue waiting on another issue, discussion or PR elsewhere
Type
Fields
Give feedbackNo fields configured for issues without a type.
Following up on #149, I was wondering about a specific policy for how to name things.
I would recommend being as close to upstream as possible.
Secondarily, the "grouping" of modules/subworkflows, should they be based on upstream group, or group base on "what the module does" broadly.