User talk:Duggabe: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
(→‎Cheers and Salutes: new section)
(Initial creation)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== GRCon23 A/V requirements ==
== Analysis of Zammad helpdesk software ==


The GRCon23 A/V requirements have been moved to https://docs.google.com/document/d/1iSZ91_EpV47iM2op8y0HuY59C7t_X-ry/edit
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".


== Cheers and Salutes ==
=== Configuration and Use ===


Hei, I am just a noob, looking for useful tutorials and stuff for my early stage family project (to become a tiny radio telescope for our garden). There I found your little small [https://www.youtube.com/watch?v=_HmbRk-UG8Q&list=PLbBQHMnVMR405Hz_Hqz2mIWoqgy8lUXqL|GNU Radio - Amateur Radio Meetup] and was looking at your python code - "a bit over my head" for now. I would like to let you know that even after three years those recorded talks can inspire some folks (=me)! Now back to ground I am diving in the beginner sections of Gnu-Radio and see if there is anything that can source and sink simple 2D-image files. I see with your code, that one CAN do stuff with Gnu-Radio... :-)
==== 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 <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.