-
Notifications
You must be signed in to change notification settings - Fork 2
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
Align SORTÆD taxonomy with CodeMeta role proposal #41
Comments
Thanks @stain for creating this issue. I believe that this is an accurate mapping for the current SOTAED taxonomy. In my opinion, having a broad role
Maintenance is a sys-admin role which includes packaging, deployment, etc. Another comment, funding in CodeMeta is not an author role but has it's own metadata property. |
Thanks, @moranegg -- I am also sceptical about having too much of a catch-all "Development", but dropping it means many aspects of Development then has to be unrolled like Architecture, Integration, Models, APIs, Graphical Design. I also wish we had a category for Releasing/Packaging -- for instance some software is packaged in Conda or Docker by people who are otherwise not affiliated with the project, and often struggle to get recognition even if their work is used by thousands of users. I think our "Funding" category is misleading, it is more of an "Owner" to denote responsibility, sponsorship etc. and there may be some person involved in that without doing day-to-day Management. This would also cover PIs etc. On the other side a broader "Outreach" would cover roles like "Open Source Advocates" not included in "Training", "Support" or "Management" |
I also stumbled upon this list of contributors to software: https://allcontributors.org/docs/en/emoji-key |
After reviewing the all-contributors list, it is also very high-level for development role called |
See issue codemeta/codemeta#240 proposing:
Mapped to ours SORTÆD:
It seems from this that our
Development
is a bit too broad and theirSupport
,Architecture
andDesign
too narrow, andMaintenance
a bit unclear.The text was updated successfully, but these errors were encountered: