This page is an archive copy, kept only for historical interest, of information about the former CF Metadata Trac site, which itself also is now kept only as an archive. The Trac site was used until July 2018 for discussion of enhancements to the CF convention. New proposals are now discussed in GitHub. The following information should be read in the past tense.
A Trac ticket is more or less equivalent to a discussion thread. The ticket system is aligned with a series of email lists corresponding to various thrusts of CF evolution (represented as “components” in Trac). The biggest change in the new system is that individuals no longer send email directly to the mailing list. Instead, the Trac system will automatically send email to the appropriate list(s) each time you create or modify a ticket. The mailing lists are arranged in such a way that you can choose to subscribe to only the discussions of interest to you - or you can subscribe to the parent list and receive an email for every single message post.
In summary, you send messages using the Trac web interface and you receive messages via the mailing lists you subscribe to or by reading the messages in your web browser.
Spammers have managed to make our lives miserable, and they are getting more sophisticated. They now even have bots that create spam Trac tickets! For this reason, each person is required to have an account in Trac to create and modify tickets. Follow the steps below to get started:
If you ARE already a member of the firstname.lastname@example.org mailing list: Note: Step 1 is only required if you want to post messages. If you only want to listen in, you don’t have to do anything.
As a member of the email@example.com mailing list, you will automatically be subscribed to the new firstname.lastname@example.org mailing list. At a later date, if you wish to limit email traffic to certain aspects of CF discussions, you can unsubscribe yourself from email@example.com and subscribe instead to one or more of the sub-lists.
If you ARE NOT already a member of the firstname.lastname@example.org mailing list: Note: Step 1 is only required if you want to post messages. If you only want to listen in, skip to Step 2.
|N/Aemail@example.com||Parent list. Subscribe to this list to receive all messages.|
|firstname.lastname@example.org||Discussion related to the CF Checker.|
|email@example.com||Discussion related to CF Conventions. Proposals to extend the conventions.|
|firstname.lastname@example.org||Discussion related to CF Standard Names. Proposals for new names.|
|email@example.com||Website, nuts and bolts of document maintenance.|
|firstname.lastname@example.org||Structured & unstructured grids.|
|email@example.com||Relationship between GIS grids and metadata to CF.|
|firstname.lastname@example.org||Exploring possibilities for CF Standard Name evolution.|
|email@example.com||Understanding relationship between CF and NetCDF4.|
|firstname.lastname@example.org||How to handle in situ observations in CF.|
|email@example.com||How to include discovery information in CF.|
|firstname.lastname@example.org||Reference implementations, CF API, CMOR, sample datasets.|
To subscribe to any of the above mailing lists, send a message to email@example.com with the following contained in the email body:
subscribe <list-name> end where <list-name> is one of the Component names (not the full mailing list name).
For example, to subscribe to firstname.lastname@example.org:
subscribe cf-wg-gis end
Unsubscribing from the Mailing Lists Send a message to email@example.com with the following contained in the email body:
unsubscribe <list-name> end
Don’t send email directly to the mailing lists. Rather, use the Trac ticketing system, which will automatically send mail to the correct lists. If you accidentally reply to an email sent by Trac or send mail directly to one of the mailing lists, the message will be delivered to the mailing list maintainer, who will politely remind you to use the Trac system instead.