Centralized place (wiki, issues, etc.) for end users and developers #12
Description
We currently have the “vivo-isf/vivo-isf” GitHub repository to serve as a central place for issues and wiki pages that are for the general community and external stakeholders (not developers, contributors, etc.). The idea was to simplify what this group of people needs to understand. For example, if a VIVO user would like to propose that the VIVO-ISF needs to add a specific term or subdomain, this user should not have to figure out which specific repository deals with this, who to contact, etc. The user can go to the central place and create the issues. Someone on the core team will pick it up from there and implement and then update the issue to point the user to a more specific place for more details.
These users also have a Google Groups mailing list.
Does this setup work? Is it needed or useful? What should we change?
I think there is some confusion regarding the current setup due to the naming problem rather than the issue numbers. I think once we have a new name for the organization, we can make it very clear by following something like this:
https://github.com/new-name/community (currently vivo-isf/vivo-isf)
https://github.com/new-name/developers (currently vivo-isf/vivo-isf-dev)