You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From #7:
I think the easiest way to go about this is to have the file generated by the homepage.
Since callsigns and frequencies are stored there anyway, adding the identifier for the teamspeak bot shouldn't be a big deal.
Pro: Reduce the amount of places where frequencies/callsigns/identifiers have to be changed
Con: Reduce the accessibility of this data, since only people with administrative access to the stations (nav leadership only I believe) can edit this.
I believe that this is a minor drawback though, considering the frequency of changes to this file anyway.
If this is changed the README.md and CONTRIBUTING.md have to be changed to accomodate for this workflow change.
The text was updated successfully, but these errors were encountered:
From #7:
I think the easiest way to go about this is to have the file generated by the homepage.
Since callsigns and frequencies are stored there anyway, adding the identifier for the teamspeak bot shouldn't be a big deal.
Pro: Reduce the amount of places where frequencies/callsigns/identifiers have to be changed
Con: Reduce the accessibility of this data, since only people with administrative access to the stations (nav leadership only I believe) can edit this.
I believe that this is a minor drawback though, considering the frequency of changes to this file anyway.
If this is changed the README.md and CONTRIBUTING.md have to be changed to accomodate for this workflow change.
The text was updated successfully, but these errors were encountered: