Closed jcolomb closed 1 year ago
I think a more important question we need to answer is "Who is this project for?".
At its current state, there are two things being built in this repository:
Of course, 2 is built using 1 and serves both as the first service that demonstrates what one can do with the library but also informs some of the design decisions of the library itself. I don't expect or intend for the project creation service to be the only implementation of this.
The intended user for the core library is developers who want to build something similar to work with either GIN or any of the other servers we might support. The intended user for the project creation service is researchers and research admins. I want to be careful with the language and the way we present each part of this to avoid confusion and mixed signals. Perhaps it was a mistake to put the two in the same repository, but that can easily be remedied, and as the labproject
service grows, I think it'll be inevitable. For now it makes development easier as the development of one affects the other.
Given all that, we should think about the branding and naming at both levels. For the project creation and curation tool/service, we can talk about what it can do to facilitate open and reproducible research but the tonic library (as it stands now) is a bit separate from that, and pointing researchers or research lab admins to this repository might be confusing, at least for now.
I think people interesting in point 2 (like me) do not care about what happens in this github repository and will only access the service. I thought about putting the service page on a nice domain name.
People from group 1 will probably not care about an external website, but only want to look at the library (i.e. the gitub repository). For them the readme file here is probably the point of entry.
Since the tool will not be gin specific, the tonic name makes little sense. "go library for Git4science" might be a better name for them ??
I think people interesting in point 2 (like me) do not care about what happens in this github repository and will only access the service. I thought about putting the service page on a nice domain name.
People from group 1 will probably not care about an external website, but only want to look at the library (i.e. the gitub repository). For them the readme file here is probably the point of entry.
Completely agree.
Since the tool will not be gin specific, the tonic name makes little sense. "go library for Git4science" might be a better name for them ??
I think the repetition of the word "for" in that title sounds a bit awkward. Why not just Git4science?
Templates to Organise Nice Information Containers
Templates and Other Necessary Instruments for git Control
(neafty not working because pronounce like Nifti the data format)
Closing this as we have https://gin-tonic.netlify.app, and "tonic" is not an acronym
After the experience to search 5 min each time I used to search for the GIN homepage via google, it might be interesting to think about the name of the tool and maybe purchase a good domain name, in order to facilitate google search for the gin-tonic tool ? We would like to avoid people to end up on pages explaining the science of gin tonic taste when looking for us...
What about gintonic4science.io ?