From 4b21b1d3b60ce1f3bb4005af9427eee29fae48c7 Mon Sep 17 00:00:00 2001 From: Jacob Gilbert Date: Wed, 21 Feb 2024 11:14:44 -0700 Subject: [PATCH 1/3] Update README.md for Community Extension Info Also has some other misc changes... --- README.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index ad95b2b..9e51b74 100644 --- a/README.md +++ b/README.md @@ -76,24 +76,28 @@ discussions, the more useful the standard is likely to be! ## Extensions -The "Core" SigMF standard is intentionally kept limited in scope, additional metadata fields can be added through [SigMF Extensions](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/sigmf-spec.md#extension-namespaces). For example, the [signal extension](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/extensions/signal.sigmf-ext.md) provides a standard way to specify modulation schemes and other attributes of wireless comms signals. Several general purpose canonical extensions live within this repository directly in the [extensions directory](https://github.com/gnuradio/SigMF/tree/sigmf-v1.x/extensions), while others are maintained by third parties. Below we include a listing of some popular, compliant SigMF extensions. To have your extension reviewed for inclusion on this list, please open a PR adding the repository to the list below: +The "Core" SigMF standard is intentionally kept limited in scope, additional metadata fields can be added through [SigMF Extensions](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/sigmf-spec.md#extension-namespaces). For example, the [signal extension](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/extensions/signal.sigmf-ext.md) provides a standard way to specify modulation schemes and other attributes of wireless comms signals. Several general purpose canonical extensions live within this repository directly in the [extensions directory](https://github.com/gnuradio/SigMF/tree/sigmf-v1.x/extensions), while others are maintained by third parties. Below are some popular sources for SigMF extensions. To have your extension reviewed for inclusion on this list, please open a PR adding the repository to the list below: + +* [SigMF's Community Extension Repository](https://github.com/sigmf/community-extensions) * [NTIA's series of extensions](https://github.com/NTIA/sigmf-ns-ntia) +In general, extension publication pull requests should go into the Community Extension repository. Occasionally there is an extension that is so general purpose that it may be warranted to include in the core SigMF Repository `extensions` directory. Opening an issue in this repository for discussion (or noting this in a pull request in the Community Extension repository), or discussing on the SigMF Matrix Chat room is the best way to make that happen. + ## Frequently Asked Questions ### Is this a GNU Radio effort? -*No*, this is not a GNU Radio-specific effort. It is hosted under the GNU Radio -Github account because this effort first emerged from a group of GNU Radio core -developers, but the goal of the project to provide a standard that will be -useful to anyone and everyone, regardless of tool or workflow. +*No*, this is not a GNU Radio specific effort. This effort first emerged from +a group of GNU Radio core developers, but the goal of the project to provide +a standard that will be useful to anyone and everyone, regardless of tool or +workflow. ### Is this specific to wireless communications? *No*, similar to the response, above, the goal is to create something that is generally applicable to _signal processing_, regardless of whether or not the -application is communications related. +application is RF or communications related. ### It seems like some issues take a long time to resolve? From 73ea70cec97ea5968c6d2ed0059b598c4436a49c Mon Sep 17 00:00:00 2001 From: Marc Lichtman Date: Wed, 21 Feb 2024 13:56:30 -0500 Subject: [PATCH 2/3] typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9e51b74..241e6b7 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ In general, extension publication pull requests should go into the Community Ext ### Is this a GNU Radio effort? *No*, this is not a GNU Radio specific effort. This effort first emerged from -a group of GNU Radio core developers, but the goal of the project to provide +a group of GNU Radio core developers, but the goal of the project is to provide a standard that will be useful to anyone and everyone, regardless of tool or workflow. From 1647997efd9a4181405e4e08ef7b459e18bf6bea Mon Sep 17 00:00:00 2001 From: Teque5 Date: Fri, 12 Apr 2024 12:21:53 -0700 Subject: [PATCH 3/3] Update README.md --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 241e6b7..8a2443f 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,6 @@ discussions, the more useful the standard is likely to be! The "Core" SigMF standard is intentionally kept limited in scope, additional metadata fields can be added through [SigMF Extensions](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/sigmf-spec.md#extension-namespaces). For example, the [signal extension](https://github.com/gnuradio/SigMF/blob/sigmf-v1.x/extensions/signal.sigmf-ext.md) provides a standard way to specify modulation schemes and other attributes of wireless comms signals. Several general purpose canonical extensions live within this repository directly in the [extensions directory](https://github.com/gnuradio/SigMF/tree/sigmf-v1.x/extensions), while others are maintained by third parties. Below are some popular sources for SigMF extensions. To have your extension reviewed for inclusion on this list, please open a PR adding the repository to the list below: * [SigMF's Community Extension Repository](https://github.com/sigmf/community-extensions) - * [NTIA's series of extensions](https://github.com/NTIA/sigmf-ns-ntia) In general, extension publication pull requests should go into the Community Extension repository. Occasionally there is an extension that is so general purpose that it may be warranted to include in the core SigMF Repository `extensions` directory. Opening an issue in this repository for discussion (or noting this in a pull request in the Community Extension repository), or discussing on the SigMF Matrix Chat room is the best way to make that happen.