Welcome to the G4CMP Developer's Consortium! This is a group within which we'll organize work to be done to upgrade G4CMP and share compute resources for doing so.
Staying Plugged in
Contributing to G4CMP, and Authorship Policy
- If you plan to contribute to this community at all, please read through the Statement of Community Values (TBD)
- If you are interested in being an author on a G4CMP Consortium Paper, please read this draft of authorship policy document (TBD)
- Contributing to G4CMP: If you want to contribute effort as a developer, we ask that you read through the Developer Coordination page, which contains useful links for who is doing what, coding guidelines, etc.
Accessing Shared Resources
Proposed two-tier consortium member system
To keep the internal side of the G4CMP Developer's Consortium flexible for members, we could use a two-tiered system. It may not be possible for new members to identify their "tier" in advance, and what "tier" someone is at may evolve over time, based on actual contributions (and ability to contribute). The goal is to be as inclusive as possible.
Tier 0: Access to G4CMP software, but no development
- G4CMP library is Open Source, so anyone can clone and build
- G4CMP Confluence is read-only public, so anyone can get to the documentation, instructions, etc.
- Doesn't include access to computing resources or code-development access (GitHub pushes)
Tier 1: Access to resources, but not on collective G4CMP publications.
- Access to restricted/internal confluence pages (How easy to do restricted confluence access for folks that don't already have SLAC accounts? Alternatively, how easy to make confluence accounts for these folks?)
- Access to SLAC compute resources – what accounts necessary?
- SLAC has created a Confluence/Jira user group for G4CMP – can request to become member of user group and log in with own institutional login, and once Noah approves, you will be able to log in to resources.
- Caveat here: eventually, if you end up using lots of resources, we should ask you to do service work to offset that resource use (bumping you up to Tier 2).
- Basically want a tier so that members who temporarily don't have time/students for service/development work don't lose all access to "internal" resources: meeting notes, SLAC resources, etc.
Tier 2: Inclusion on G4CMP "consortium" papers
- Includes everything related to Tier 1, above.
- Institutions that have made "significant enough" contributions to development to be added to papers
- What is "significant enough"?
- Will want to draft an actual set of guidelines soon, but want to solicit input here.
- Currently leaning towards being more inclusive when in doubt.
- Possibly involves "service work" (software development, resource management, something) to contribute to supporting the group.
Goal for next few months: decide on some guidelines for membership and refine the above tier system.