[aprssig] central repository

[Jim Alles]

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.

On #3 above, my previous comment about the thing getting trashed by spam
was actually quite serious. Unfortunately, that means we will need to deal
with the administrivia of authenticated accounts. I am hoping that the
application that we settle on has some way of automating that process using
calls signs. Maybe the QRZ site, FCC ULS, or the APRS passcode can be
useful.

Here is this thread's archive for review:
http://www.tapr.org/pipermail/aprssig/2016-November/046325.html

At the time, to me 'repository' meant collecting existing files that may be
scattered in multiple locations, distillations of meaty discussions on this
that establishes the operation of the existing system, and a place where
these things can be contributed by many, without modifying HTML directly
while depending on any individual ham operator.

No, I wasn't contemplating doing anything with this list or large
collections of intact messages in that repository. So no fracturing implied.

However, I have had a private discussion about getting search capabilities
for the entire message list archive.

Thanks for being here!

Jim A.

On Sun, Nov 20, 2016 at 9:42 PM, Javier Henderson <javier at kjsl.org> wrote:

> > On Nov 20, 2016, at 18:30, John D. Hays <john at hays.org> wrote:
> >
> > I missed the beginning of this thread, but if you are looking for a good
> place to run the mailing list and have a Wiki plus file store, calendar,
> database, etc. (and can integrate with GitHub for source code projects) --
> I have been doing quite a bit on Groups.io
> >
> > I created a group if people want to try it out.
> https://amateur-radio.groups.io/g/aprssig  -- subscribe, the first few
> messages from an individual are moderated.  I have currently set the Wiki
> to subscribers can edit and that it is publicly visible.
> >
> > If the list wants to do more with the group I created, I will extend
> moderator status to a core team. Or an entirely new group could be created
> that is not a child of amateur-radio
> >
> > Here is an active wiki on one of the groups https://nw-digital-radio.
> groups.io/g/udrc/wiki
> >
> > The Wiki has a gui editor or you can use markup -- it is not as rich as
> some, but pretty sufficient.
>
> So besides new wikis (multiple, apparently) this list is now being
> fractured?
>
> Awesome progress.
>
> 73,
> -jav k4jh
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161122/4a5ce2cb/attachment.html>