Ask.CI and Ask.cyberinfrastructure.org now both point to our site. Hope that everyone will help to pass the word along!
Please join us on Fridays at 11AM ET, 10AM CT, 9AM MT, 8 AM PT for a weekly informal zoom conference call with the moderators to discuss all topics related to “Ask”.
I noticed that ask.ci is for sale: https://ask.ci/ Are most folk OK with “CI” (CyberInfrastructure) standing in for “RC” (Research Computing)? Too broad or too narrow?
@jacks9 Hoping @Chris will weigh in since he has the cyberinfrastructure.org domain, but my understanding is this Q&A site is for the national/global research computing community, hence its presence in this domain.
NECyberteam-specific tools are at necyberteam.org. We can move other tools we are developing over to cyberinfrastructure.org in the future if/when they similarly take on scope beyond the NECyberteam. Thanks for asking!
@jacks9 The history behind the cyberinfrastructure.org DNS was from way back when NSF Office of Advanced Cyberinfrastructure first started. Some clever guys at MIT registered that name when NSF coined that term and it has basically gone unused since then.
@syockel (and @Chris), that’s awesome. Since whatever name we choose, the URL for the Discourse site will be <the_name>.cyberinfrastructure.org, correct? So voting for this entry is actually voting for “Ask” as the name, correct? The brand name could be “Ask.CI”.
@jacks9 I really like the idea of the shorter http://ask.ci/ as “cyberinfrastructure” is a mouthful, but as a term I like the fact that it is more inclusive of the wider lens in our community which is more than just the computing side, but spans data, networking, and other stuff that is useful for our research communities.
I’ve always had trouble with the word cyberinfrastructure since NSF adopted it. It’s a real mouthful and hard to explain to people outside the NSF OAC context. It’s even in my title (Cyberinfrastructure Coordinator). We do need to continue promoting it as a wider term (beyond the hardware/software) to include people, training, data resources, professional development, facilitation, advocacy, etc. - as the whole ecosystem supporting Research Computing.