User talk:Duggabe: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
(Initial creation)
 
(64 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== "Recycle Bin": content we no longer link to that we may eventually just delete ==
== Analysis of Zammad helpdesk software ==


* [[Guided_Tutorial_GNU_Radio_in_Python|Programming GNU Radio in Python]]
Our intended use of the Zammad software is to handle all emails received by <code>grcon@gnuradio.org</code>, <code>tickets@gnuradio.org</code>, and <code>sponsor@gnuradio.org</code>. It assigns a ticket number to each initial customer interaction and tracks the progress of the response, keeping subsequent emails within the same ticket as a "thread".
* [[TutorialsRemoteGUI|Remote GRC Operations]] - needs updating!
* [[UsingVim|Using VIM plugins for GNU Radio development]]
* [[TutorialsQTGUI|QTGUI Tutorial]] - A tutorial on how to develop Python GNU Radio applications.
* [[Guided_Tutorial_Extras_Sample_Rates#E2.3._A_Note_on_Resampling]] - covered by Understanding sample rate
* [[TutorialsCoreConcepts|Core concepts of GNU Radio applications]] - content used in other pages
* [[TutorialsWritePythonApplications|WritePythonApplications]] - content used in other pages
* [[OutOfTreeModulesConfig|Tutorial on how to configure OOT packages to find and link against GNU Radio]] - for 3.7; also, most of the content is covered in Writing blocks in C++
* [[TutorialPythonFunctions|Writing a Python Function for GRC]] - for 3.7; content used in other pages; it doesn't work as written!
* [[TutorialsDebugging|How to debug your applications]] - not well written; would need major rework and update


== QT GUI Block Docs Status ==
=== Configuration and Use ===


These 3.9 GUI Widgets do not have doc pages:
==== Overview Selection Panel ====


* App Background
The area of the Overviews screen which selects what emails to display currently combines four different filters into one:
* Az-El Plot
* Email source (grcon, tickets, or sponsor)
* Compass
* STATE (new, open, closed, pending)
* Dial
* All
* Dial Gauge
* Assigned to me
* Digital Number Control
* Distance Radar
* Fast Auto-Correlator Sink
* Graphic Item
* Graphic Overlay Sample Source
* LED Indicator
* Level Gauge
* Msg CheckBox
* Msg Push Button
* Toggle Button
* Toggle Switch


== Notes from GRCon20 Docs breakout ==
This leads to at least 14 selections. This is not ideal (in my opinion), but can be used for initial trials. A better solution would be to have two or three dropdown menus to do the selection (or maybe Github issues selection style).
* document msg ports
* we need a list of blocks without params or example flowgraphs
* "How can I know which blocks to assemble to do X application"
* "I want to do X processing, Is there a block already that does it, and if so, what's its name?"


== Notes from GRCon20 HamRadio breakout ==
==== Tags ====
* I mean, I guess, if this is as wildly popular as it looks right now, there's probably a critical mass for just saying something like "Vote for next month's meetup(s) topic" and then have someone give a short intro / slides / talk /RTTY transmission and then making this an awesome series
 
* So, my proposal: Barry Duggan will push out a news entry on the gnuradio.org homepage as soon as a kickoff seems feasible :) I'll help as good I can
If Tags must be selected from a pre-defined list, more options need to be defined.
* start a Ham Radio wiki page
 
** poor SSB always gets the short shrift.  ;-)
=== Success Requires Full Participation ===
** list of starter RF components for HF
 
** It would be way cool to demonstrate bad signals in simulation, so that we can recognize them when we see them on air, and not be the ones doing bad things on the air ourselves.
For the Zammad software to work for us, every person who processes email for any of the sources (grcon, tickets, or sponsor) must have full read and write privileges, and <b>MUST USE ZAMMAD instead of direct access to the Gmail interface.</b> Mixing the two would lead to confusion and lack of coordination.
 
=== Path Forward ===
 
I propose that I be given 'admin' privileges to create a workable configuration for further testing and evaluation.

Latest revision as of 16:53, 19 February 2024

Analysis of Zammad helpdesk software

Our intended use of the Zammad software is to handle all emails received by grcon@gnuradio.org, tickets@gnuradio.org, and sponsor@gnuradio.org. It assigns a ticket number to each initial customer interaction and tracks the progress of the response, keeping subsequent emails within the same ticket as a "thread".

Configuration and Use

Overview Selection Panel

The area of the Overviews screen which selects what emails to display currently combines four different filters into one:

  • Email source (grcon, tickets, or sponsor)
  • STATE (new, open, closed, pending)
  • All
  • Assigned to me

This leads to at least 14 selections. This is not ideal (in my opinion), but can be used for initial trials. A better solution would be to have two or three dropdown menus to do the selection (or maybe Github issues selection style).

Tags

If Tags must be selected from a pre-defined list, more options need to be defined.

Success Requires Full Participation

For the Zammad software to work for us, every person who processes email for any of the sources (grcon, tickets, or sponsor) must have full read and write privileges, and MUST USE ZAMMAD instead of direct access to the Gmail interface. Mixing the two would lead to confusion and lack of coordination.

Path Forward

I propose that I be given 'admin' privileges to create a workable configuration for further testing and evaluation.

Retrieved from "https://wiki.gnuradio.org/index.php?title=User_talk:Duggabe&oldid=13776"