amtm Announcing AMTM-OSR, AMTM Orphaned Script Revival repository

[thelonelycoder]

Life just happens - to all of us. Interests and priorities change and we get older everyday. Some are no longer with us, others have moved on to other pastures.
We're all glad you were part of this amazing community.
So, thank you to all of you for what you contributed script wise. You know who you are.

After much deliberation* some of the still active script coders decided to re-organize ourselves and find a home for orphaned amtm supported scripts that still get some love from us.

Feel free to head over to AMTM-OSR and see what we're up to and which scripts got green lighted to get continued support, if for some only limited.
I'm only the messenger here, give thanks to @Martinski and @ExtremeFiretop and the ones you think helped out.

*) It only took us maybe 20 Minutes to agree, with most of this being time lag

 

[Jeffrey Young]

One word - Fantastic

 

[visortgw]

The adoption is complete!

 

[thelonelycoder]

The adoption is complete!

I’m sure @Martinski and @ExtremeFiretop had such a move in mind but never voiced it to me.
I suggested a change and @ExtremeFiretop had the solution.

 

[ColDen]

The future looks brighter!!!

 

[Stephen Harrington]

some of the still active script coders decided to re-organize ourselves and find a home for orphaned - amtm supported - scripts

Fantastic news and many thanks to @Martinski and @ExtremeFiretop for your ongong generous genious support of our beloved/pesky routers!

 

[ExtremeFiretop]

Fantastic news and many thanks to @Martinski and @ExtremeFiretop for your ongong generous genious support of our beloved/pesky routers!

I'm currently wrapping up the initial setup for the GitHub Organization, which may take a few more days to fine-tune.

The main goal is to reignite development on several AMTM add-ons that have been left without active maintainers—regardless of the reason.

As @thelonelycoder aptly noted, life happens. People move on, and sometimes sadly pass on. Yet the tools they’ve created often remain useful to many, even as the code sits untouched and slowly decays over time.

To address this, we're establishing an official process and a centralized repository that @thelonelycoder can use to mark scripts as "orphaned," defining what that means in terms of future support.

Bringing these projects under one roof—with access for multiple contributors—will be crucial for ensuring continued maintenance and collaborative development.

The plan is for AMTM-OSR to be community-driven: anyone will be able to submit pull requests, and work with a team of experienced script authors which will review and approve the changes to maintain quality and reliability..

The project and team will grow as we get more contributions from people

 

[SomeWhereOverTheRainBow]

I’m sure @Martinski and @ExtremeFiretop had such a move in mind but never voiced it to me.
I suggested a change and @ExtremeFiretop had the solution.

Great solution @ExtremeFiretop and @Martinski. I think this is an opportunity for all devs to collaborate. I see we have been trying to do that, but @ExtremeFiretop is off to a wonderful idea on how to do that. Even if devs have stepped away, we can still work together in our free time to improvise or share ideas to keep the old alive in today's new. I am onboard! @thelonelycoder I am hoping that AMTM gets a separate prefix for AMTM-OSR. It will streamline our communications to improve, test, improvise, and collaborate here with people who are testing fixes in real time.

 

[ExtremeFiretop]

@thelonelycoder I am hoping that AMTM gets a separate prefix for AMTM-OSR. It will streamline our communications to improve, test, improvise, and collaborate here with people who are testing fixes in real time.

Interestingly, this was actually one of the ideas I brought up in our internal Org chat.

Having a clearly separated section within AMTM for these community-maintained scripts would make it obvious which ones are in "life support" mode. It would also open up space in the main AMTM menu for new scripts that are gaining traction but haven’t been officially added yet.

I think this is an opportunity for all devs to collaborate. I see we have been trying to do that, but @ExtremeFiretop is off to a wonderful idea on how to do that.

I completely agree. Many script authors naturally work in silos, and that’s perfectly okay. But there's clearly growing interest in a more collaborative approach. This initiative gives us a chance to focus our efforts where they’re most needed. Some contributors may focus on code, others on reviewing functionally and approving. either way, we all stand to benefit, both for our personal projects and for supporting orphaned add-ons.

 

[dave14305]

Do you accept repository transfers? Asking for a friend…

 

[SomeWhereOverTheRainBow]

Interestingly, this was actually one of the ideas I brought up in our internal Org chat.

While I haven't subscribed in the internal org chat "yet", I do want the community to know I am on board with helping any way I can, and that I support the ideas presented here in this thread. Until June, my support is kinda limited because of my job, but I can review and offer suggestions until I am able to be of more active help. @ExtremeFiretop I am excited you have sparked this initiative.

 

[ExtremeFiretop]

Do you accept repository transfers? Asking for a friend…

Welcome to the team @dave14305 . Official invite sent. Message me if you have any issues with access rights.

While I haven't subscribed in the internal org chat "yet", I do want the community to know I am on board with helping any way I can, and that I support the ideas presented here in this thread. Until June, my support is kinda limited because of my job, but I can review and offer suggestions until I am able to be of more active help. @ExtremeFiretop I am excited you have sparked this initiative.

Same goes to you @SomeWhereOverTheRainBow ; however can you confirm your Github username to make sure I get it right?
Is it jumpsmm7 ?

 

[SomeWhereOverTheRainBow]

Welcome to the team @dave14305 . Official invite sent. Message me if you have any issues with access rights.



Same goes to you @SomeWhereOverTheRainBow ; however can you confirm your Github username to make sure I get it right?
Is it jumpsmm7 ?

Correct!

 

[ExtremeFiretop]

Correct!

Invite sent

 

[JGrana]

Great stuff! Congratulations @thelonelycoder @Martinski @ExtremeFiretop and @dave14305 - and many thanks.

Good time to remind everyone that uses and enjoys these addons and the efforts all the developers put into - not only creating, but supporting them:

Asuswrt-Merlin AddOn Developers Donation Links

AddOn developers create many useful scripts, WebUI addon pages, system extensions and useful utilities to enhance Asuswrt-Merlin supported routers. These "devs", like RMerlin, do this all voluntarily. This requires lots of time, effort, support of users, upkeep and maintenance. They do it for...

www.snbforums.com

 

[ExtremeFiretop]

Great stuff! Congratulations @thelonelycoder @Martinski @ExtremeFiretop and @dave14305 - and many thanks.

Good time to remind everyone that uses and enjoys these addons and the efforts all the developers put into - not only creating, but supporting them:

Asuswrt-Merlin AddOn Developers Donation Links

AddOn developers create many useful scripts, WebUI addon pages, system extensions and useful utilities to enhance Asuswrt-Merlin supported routers. These "devs", like RMerlin, do this all voluntarily. This requires lots of time, effort, support of users, upkeep and maintenance. They do it for...

www.snbforums.com

Hey there! @JGrana

Wanted to say thank you and I much appreciate the shout‑out! I'm sure many of the other devs do as well All the script authors deserve some support.
It's great to see the community rally and highlight all the work going into these addons.

3 Cheers to keeping the community goin'!

 

[elorimer]

We also have the developer branch contributions for scribe and dn-vnstat that haven't been merged and might be candidates.

 

[thelonelycoder]

We also have the developer branch contributions for scribe and dn-vnstat that haven't been merged and might be candidates.

We can only do so much. Some scripts will undoubtedly have too many compatibility issues that they will no longer be supported in future amtm releases.