User talk:Duggabe: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
(Initial creation)
 
(79 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


== Status of gr-tutorial use with Tutorials ==
=== Configuration and Use ===


Of the seven original tutorials, the only one which references the files in gr-tutorial is Guided_Tutorial_PSK_Demodulation. There are 12 flowgraphs for it in https://github.com/gnuradio/gr-tutorial/tree/master/examples/tutorial7  Since there are pictures of all the flowgraphs and outputs, we could just have the one final flowgraph in-tree, and remove all the links to gr-tutorial.
==== Overview Selection Panel ====


The code for 'my_qpsk_demod' is not used, and none of the other files in gr-tutorial are used either.
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


My recommendations:
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).


# remove the links to the flowgraphs in https://wiki.gnuradio.org/index.php/Guided_Tutorial_PSK_Demodulation, revising the wording as needed.<br>
==== Tags ====
# remove references to gnuradio/gr-tutorial in https://wiki.gnuradio.org/index.php/Guided_Tutorial_GRC<br>
# mark https://wiki.gnuradio.org/index.php/Installing_the_Tutorials_Modules as deprecated.<br>
# change https://github.com/gnuradio/gr-tutorial/blob/master/README.md to say that it is deprecated; OR delete gnuradio/gr-tutorial entirely.<br>


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


== a dummy section ==
=== 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 <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.