[aprssig] central repository

Jason KG4WSV kg4wsv at gmail.com
Tue Nov 22 08:25:36 EST 2016

On Tue, Nov 22, 2016 at 5:40 AM, Jim Alles <kb3tbx at gmail.com> wrote:

> I appreciate the discussion. Except for exploring & discussing the
> examples, I would like a decision on this to go on hold until after
> Thanksgiving.
> I see several things to take into consideration:
>    1. Ham-owned hosting & maintenance vs. cloud based hosting.
>    2. File storage & retrieval - for original source document archiving &
>    retrieval (PDFs)
>    3. Security capabilities & control of the mechanism by a Ham.
>    4. Familiarity & accessibility for the masses.
>    5. Backup mechanism, offsite storage.
> <http://www.tapr.org/pipermail/aprssig/2016-November/046325.html>

Here are some to consider first, IMO:

There's already a discussion list for the subject (you're reading it).
Fragmentation is not your friend.

There are ham wikis out there already.  ( https://xkcd.com/927/ )

A wiki is a horrible tool for maintaining a specification document.  A
specification needs revision control, version numbers, etc.  A wiki is a
free for all.  Fine for documentation, but not the actual specification.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161122/675baf4f/attachment.html>

More information about the aprssig mailing list