[aprssig] Information organization

[Steve Dimse]

I think this in particular is premature. 

Hessu is filling a short term need, the issuing of ongoing tocalls which is why I think that is OK with the proviso it comes under the control of the APRS group in the future.  

A good deal of the confusion on the protocol is there are so many different sources. We don't need another, we need a single definitive document.

We have two proposals for groups that will assume managing the spec. One is a resurrection of the APRS Working Group in the control of a handful of software authors, the other a group that represents all stakeholders. How the integration of the spec, new and old info on aprs.org, and new additions will be handled depends on which group moves forward. Those infrastructure decisions ought tp be made by the people that have to live with them.

Also, I think we need to focus on the organization now. Separate discussions of protocol issues divert attention from the creation of a strong organization that can move APRS forward. We need to decide on a structure and get it implemented.

If you want to prepare for that time when we do start moving forward and you can offer your services to the APRS group I think that is great, but I think it is not yet time for public protocol documentation.

Steve K4HG



> On Feb 17, 2022, at 12:14 PM, Scott Howard <showard at nd.edu> wrote:
> 
> Hi Everyone,
> 
> I started trying to synthesize the specification related content from
> aprs.org into a more structured format. Following Hessu's example, I
> made the following github repo to organize the notes. The goal is not
> to revise or change anything, just to make an inventory, collect
> thoughts, and begin structuring what already exists. The hope is to
> both give some clarity for newcomers as well as organize info for
> whatever comes next. It's a bit work-in-progress, so it's very open to
> suggestions, corrections, additions, and edits.
> 
> The document is here:
> https://github.com/KD9PDP/aprs-notes/blob/main/protocol.md
> 
> You can make comments to specific lines here:
> https://github.com/KD9PDP/aprs-notes/pull/1/commits/b52e576ca444b2ee100cb1c6d4bd6291ff197280
> 
> There's a bunch that can be done, so if anyone has any interest in
> tackling anything, please go ahead and build on it. You can file an
> "issue" to let others know what you're working on so people don't
> duplicate effort.
> 
> -Scott
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org