Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

278 kill toc anchors in faq on website #281

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

278 kill toc anchors in faq on website #281

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
c83b9f8
Correct heading levels
erget Sep 14, 2022
0839587
Remove manual HTML formatting
erget Sep 14, 2022
65ad49b
Remove spurious HTML
erget Sep 14, 2022
5972b2a
Update line breaks
erget Sep 14, 2022
dc65f7e
Remove TOC
erget Sep 14, 2022
dbe5713
Add TOC
erget Sep 21, 2022
215fe0b
Merge branch 'main' into 278-kill-toc-anchors-in-faq-on-website
erget Sep 21, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
# cf-convention.github.io

This repo contains the source files for CF Conventions web site:
[http://cfconventions.org].
This repo contains the source files for [the CF Conventions web site](cf-website).

[cf-website]: http://cfconventions.org/
39 changes: 25 additions & 14 deletions about-trac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,35 +5,45 @@ title: Governance

## CF Trac Website

This page is an archive copy, kept only for historical interest, of information about the former [CF Metadata Trac](Data/trac.html) 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](discussion.html). The following information should be read in the past tense.

This page is an archive copy, kept only for historical interest, of information about the former [CF Metadata Trac](Data/trac.html) 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](discussion.html).
The following information should be read in the past tense.

## How the Ticket System Works

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.
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.



## Joining the Discussion

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:
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 [email protected] 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.
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.

1. Request a Trac account by sending your first name, last name, and preferred username to: [email protected]

As a member of the [email protected] mailing list, you will automatically be subscribed to the new [email protected] 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 protected] and subscribe instead to one or more of the sub-lists.
As a member of the [email protected] mailing list, you will automatically be subscribed to the new [email protected] 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 protected] and subscribe instead to one or more of the sub-lists.


If you ARE NOT already a member of the [email protected] 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.
Note: Step 1 is only required if you want to post messages.
If you only want to listen in, skip to Step 2.

1. Request a Trac account by sending your first name, last name, and preferred username to: [email protected].
2. Subscribe yourself to the mailing lists you're interested in. You will automatically be subscribed to the cf-conventions and cf-standard-names mailing lists. You must independently subscribe to the working group lists.

2. Subscribe yourself to the mailing lists you're interested in.
You will automatically be subscribed to the cf-conventions and cf-standard-names mailing lists.
You must independently subscribe to the working group lists.

## Components and Mailing Lists

Expand All @@ -52,7 +62,6 @@ cf-wg-in-situ-obs | [email protected] | How to handle in situ obs
cf-wg-discovery | [email protected] | How to include discovery information in CF.
cf-wg-compliance | [email protected] | Reference implementations, CF API, CMOR, sample datasets.


## Subscribing to the Mailing Lists

To subscribe to any of the above mailing lists, send a message to [email protected] with the following contained in the email body:
Expand All @@ -76,4 +85,6 @@ where <list-name> is one of the Component names (not the full mailing list name)

## Posting to the Mailing Lists

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.
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.
Loading