<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I understand that, my question is why was it "moved" and not forked.
I setup the AllStarLink github account as part of AllStarLink. No
matter what pttlink does the resource is AllStarLink.<br>
<br>
Steve N4IRS <br>
<br>
<div class="moz-cite-prefix">On 12/30/20 8:46 PM, Andrew Sylthe
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMbt3dtY=ofXknxJaYU9xCUK31y=LH4xHTkMFnqXk_2DTNSyYg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Steve,
<div><br>
</div>
<div>It appears to have been moved to <a
href="https://github.com/pttlink/Asterisk"
moz-do-not-send="true">https://github.com/pttlink/Asterisk</a></div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 30, 2020 at 7:43
PM Steve Zingman <<a href="mailto:szingman@gmail.com"
moz-do-not-send="true">szingman@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Stacy,<br>
Do you know why the AllStarLink <<a
href="https://github.com/AllStarLink" rel="noreferrer"
target="_blank" moz-do-not-send="true">https://github.com/AllStarLink</a>>
github <br>
repositories are gone? Was this part of the actions of the
board?<br>
<br>
Steve N4IRS<br>
<br>
On 12/30/20 8:06 PM, Stacy wrote:<br>
> A bit on this change:<br>
><br>
> Nobody on the admin side that runs what was the
AllStarLink (ASL)<br>
> infrastructure (now PTTLink) was ever informed this was
going to<br>
> happen. Yesterday afternoon (12/29/20) at around 5:00 PM
(Pacific) our<br>
> monitoring system started going crazy with alerts telling
us systems<br>
> were down. Investigation showed that the SOA record for
<a href="http://allstarlink.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">allstarlink.org</a><br>
> was changed to what it is now (Cloudflare) and this broke
numerous<br>
> things. Both the wording and timing of this announcement
is very much a<br>
> jab (or middle finger) pointed directly at me since I'm
the main person<br>
> who has been running things. I am one who has ensured
that the ASL<br>
> Network (and associated infrastructure) remained
operational and was<br>
> able to handle the increasingly growing number of nodes
(well over<br>
> 5,100). This was done solely through me investing both
my own time and<br>
> money without the help or participation of the ASL
Board. In addition<br>
> to this "re-engineering" I have also had my account on
the ASL Slack<br>
> workspace suspended without notice and any and all admin
access to the<br>
> ASL Web portal was removed too (among other things).<br>
><br>
> For quite some time, well before Bryan Fields (W9CR) or
Fred Moses<br>
> (W8FSM) stopped their involvement in ASL directly, the
AllStarLink, Inc<br>
> Board (ASL Board) has done its best to alienate,
patronize, ridicule,<br>
> demean, and basically exclude the admin team from
anything substantial<br>
> regarding the ASL infrastructure for which they had no
understanding of<br>
> nor did they attempt to understand. Numerous attempts
were made by<br>
> myself and others to try to fix the issues that were very
apparent, and<br>
> yet they were met with disdain and ignored. This
included on several<br>
> occasions attempts at impassioned pleas by myself and
others directly to<br>
> the ASL Board members regarding the issues that we saw
and asking for<br>
> reparations to make things better. Of which included
being open<br>
> regarding any decisions being made which directly
affected the admin<br>
> team. Additionally, any and all attempts to ask what is
happening on/at<br>
> the board level regarding ASL were ignored or told that
it didn't<br>
> involve or concern us. Instead, they continued on the
same course of<br>
> action that served to alienate more and more people from
participating<br>
> in ASL on the admin side with the results of me being the
sole admin<br>
> person left.<br>
><br>
> This "re-engineering" and the resulting chaos and outages
are serve as a<br>
> testament to the ASL Board again attempting to change
things without<br>
> understanding the system itself and without telling
anyone.<br>
><br>
>> This is part of an ongoing two-year project to
provide sufficient<br>
> resources for projected node growth and additional
stability. In<br>
> addition, this will create a stable framework for new
types of clients<br>
> to participate in the future.<br>
><br>
> Again, nobody told me (or anyone else associated with the
admin team)<br>
> about this "two year project". Each and every time the
ASL Board has<br>
> attempted a change (and broken something), the current
node registration<br>
> system was brought up. For example, the Round Robin DNS
(RRDNS) has<br>
> been a sticking point for a certain unnamed ASL Board
member, and during<br>
> discussions this unnamed individual had the audacity to
state that<br>
> DSNMGR messages regarding changes to the IP address of
the server at<br>
> <a href="http://register.allstarlink.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">register.allstarlink.org</a>
was "trashing his node". One of the long<br>
> since alienated admin team members had to explain that
you could adjust<br>
> logging in Asterisk through a config file. This is one
of many examples<br>
> that demonstrated the lack of knowledge of AllStarLink,
Asterisk, and<br>
> app_rpt by a member of the ASL Board. Yet we are to
believe that a<br>
> "two year project" has been in the works by this same
group that is<br>
> supposed be a "re-engineered" system to promote growth
and stability?<br>
><br>
>> You should also be aware that some specific
volunteers (past and<br>
> current) have opposed this sort of design change and we
suspect that you<br>
> may be reading negative comments from them on various
platforms. The<br>
> board’s staffing goals are to promote technical
innovation from as many<br>
> hams as want to get involved and bring new features and
clients to Allstar.<br>
><br>
> Don't be fooled by this attempt at taking the high
ground. The<br>
> opposition they are implying results from attempts at
changes from the<br>
> ASL Board without understanding the underlying technical
issues behind<br>
> how/why things run and causing outages that they wouldn't
(or couldn't)<br>
> fix. Each and every time an ASL Board member brought up<br>
> "re-engineering" the registration system, the reply that
I empathically<br>
> gave was that yes, the system can be improved upon but
there needs to be<br>
> a plan. I personally have stated that I am open to
improvements to this<br>
> system that were the result of planning, testing and made
sense. The<br>
> ASL Board thought that moving the system to AWS or Google
would "solve"<br>
> everything yet when pressed for details on how this would
be done, we<br>
> were met with crickets or arguments that it was just
better and that was<br>
> that. And when asked about a budget for such a move we
were again met<br>
> with silence. The "resistance" that is alluded to was
with regards to<br>
> actually sitting down and creating a plan on how to move
forward with<br>
> "re-engineering" this system, and not just what amounted
to throwing<br>
> scat at the wall and seeing what stuck (resulting in
either myself or<br>
> others on the admin team having to figure out what broke
and fix it,<br>
> since most of these changes were done without telling
us). At no point<br>
> during the any of occasions in which I said this has any
ASL Board<br>
> member taken the initiative to actually have this
discussion with me (or<br>
> anyone on the admin team) and come up with a viable plan
to both<br>
> "re-engineer" and do a proper cut over that isn't as
disruptive as the<br>
> one we are experiencing now.<br>
><br>
> There is a history of the ASL Board doing things that
have broken<br>
> registration and parts of the infrastructure in the past,
and this is no<br>
> different.<br>
><br>
> PTTLink was formed due to the ASL Board's actions which
forked the<br>
> AllStarLink network by changing the DNS records without
prior notice.<br>
><br>
> The PTTLink Network can be thought of as an "overlay" to
what had been<br>
> in operation as the AllStarLink Network. This change was
done simply by<br>
> changing the domain name in use on the servers to <a
href="http://pttlink.org" rel="noreferrer" target="_blank"
moz-do-not-send="true">pttlink.org</a>. Your<br>
> existing credentials will continue to work unless you
change them.<br>
> However, PTTLink, as a result of the ASL Board's
egregious and careless<br>
> action, is now a separate entity from the AllStarLink
Network. I call<br>
> upon the ASL Board to restore DNS back to the way it was
before they<br>
> forked it, moving everything back to the perfectly
working<br>
> infrastructure that uses what are now the <a
href="http://pttlink.org" rel="noreferrer" target="_blank"
moz-do-not-send="true">pttlink.org</a> servers.<br>
> Additionally, I call upon them to restore all access that
was revoked<br>
> from me (both recently, and that which was revoked before
without notice).<br>
><br>
> I am very disappointed in the egregious actions that the
ASL Board has<br>
> taken (or more importantly have directed others to take)
with regards to<br>
> the AllStarLink infrastructure and their statement. Such
actions are<br>
> clearly indicative of a group that is unfit to be the
stewards to the<br>
> legacy of the late Jim Dixon or properly be of service to
the community<br>
> without trying to benefit from it. Additionally, I feel
that these<br>
> actions, as made clear in their statement, were directed
at me in an<br>
> attempt to "punish" me for my insistence and diligence at
keeping the<br>
> ASL (now PTTLInk) infrastructure running when others made
disruptive<br>
> changes to it. If so, then this is very troubling
indeed.<br>
><br>
> As I have very plainly stated before to the ASL Board
members and<br>
> others, as long as I have the resources to support ASL
they will remain<br>
> available. In that I will pledge to my fellow hams that
PTTLink will<br>
> remain operational and available for use as long as I am
able to<br>
> continue to provide the time and other resources to
keeping it<br>
> operational. Fortunately, I am no longer alone in this
endeavor and<br>
> others have volunteered to help.<br>
><br>
> The new links for PTTLInk sites are as follows:<br>
><br>
> PTTLink Portal - <a href="https://www.pttlink.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.pttlink.org</a><br>
><br>
> PTTLink Stats Server - <a
href="http://stats.pttlink.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://stats.pttlink.org</a><br>
><br>
> PTTLink Registration Server - <a
href="http://register.pttlink.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">register.pttlink.org</a><br>
><br>
> PTTLink Node List Server - nodes(x).<a
href="http://pttlink.org" rel="noreferrer" target="_blank"
moz-do-not-send="true">pttlink.org</a><br>
><br>
> PTTLInk is on Reddit - <a
href="https://www.reddit.com/r/pttlink" rel="noreferrer"
target="_blank" moz-do-not-send="true">https://www.reddit.com/r/pttlink</a><br>
><br>
><br>
> Additionally, you can use the DNS node lookup developed
by W9CR (which<br>
> was working with <a href="http://allstarlink.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">allstarlink.org</a>
before the ASL Board forked the network):<br>
><br>
> IP Address of registered node: dig <node#>.<a
href="http://nodes.pttlink.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">nodes.pttlink.org</a><br>
><br>
> TXT record showing DNS registration info: dig TXT
<node#>.<a href="http://nodes.pttlink.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">nodes.pttlink.org</a><br>
><br>
> Additionally, you can utilize the app_rpt-users mailing
list for support<br>
> by subscribing at<br>
><br>
><br>
> 73,<br>
> Stacy<br>
> KG7QIN<br>
><br>
> _______________________________________________<br>
> App_rpt-users mailing list<br>
> <a href="mailto:App_rpt-users@lists.keekles.org"
target="_blank" moz-do-not-send="true">App_rpt-users@lists.keekles.org</a><br>
> <a
href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
><br>
> To unsubscribe from this list please visit <a
href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
> Unsubscribe posts to the list will result in public
shaming.<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@lists.keekles.org"
target="_blank" moz-do-not-send="true">App_rpt-users@lists.keekles.org</a><br>
<a
href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a
href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
Unsubscribe posts to the list will result in public shaming. <br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">Andrew Sylthe<br>
KC9ONA<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.keekles.org">App_rpt-users@lists.keekles.org</a>
<a class="moz-txt-link-freetext" href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
Unsubscribe posts to the list will result in public shaming.
</pre>
</blockquote>
<br>
</body>
</html>