FOOD FOR THOUGHT Incredible PBX Code Collaboration

[Samot]

By the way, where can we read about your [faxing] solution??

Well I just started on mine over the weekend while watching Night of Champions but I should have it ready. by next week.

 

[wardmundy]

Well I just started on mine over the weekend while watching Night of Champions but I should have it ready. by next week.

Still waiting on your Incredible PBX installer rewrite... but it's only been a couple years.

 

[Samot]

Still waiting on your Incredible PBX installer rewrite... but it's only been a couple years.

You mean the rewrite I started on Incredible PBX 2025 last year? Hence me asking all these questions last July on where to get actual current versions of things? It's a project I literally started on July 11, 2025....so yeah...couple years have passed. But since everything is now on a new OS and a new version of FreePBX....it was restarted a couple months back.

 

[billsimon]

Still waiting on your Incredible PBX installer rewrite... but it's only been a couple years.

@wardmundy , @Samot if you are serious about open source collaboration for IncrediblePBX could we have the scripts on a code repo please? I'd be willing to contribute but not by passing tarballs around.

 

[Samot]

@wardmundy , @Samot if you are serious about open source collaboration for IncrediblePBX could we have the scripts on a code repo please? I'd be willing to contribute but not by passing tarballs around.

That's my plan. I'll share it with you after the long weekend.

 

[wardmundy]

My bad... only been a year minus 9 days. TIP: New versions come out almost every year so, at your current pace, we're probably not going to see anything during our lifetimes.

 

[wardmundy]

@wardmundy , @Samot if you are serious about open source collaboration for IncrediblePBX could we have the scripts on a code repo please? I'd be willing to contribute but not by passing tarballs around.

It's not a tarball. It's just ONE SCRIPT...

https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/IncrediblePBX2026.sh

 

[Samot]

It's not a tarball. It's just ONE SCRIPT...

https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/IncrediblePBX2026.sh

That's not what he is talking about. He's talking about not having to do some work, save the work, tarball it up to share with someone else so they can also do some work and then tarball it up and send it back. I.e. "passing tarballs around"

 

[wardmundy]

That's not what he is talking about. He's talking about not having to do some work, save the work, tarball it up to share with someone else so they can also do some work and then tarball it up and send it back. I.e. "passing tarballs around"

As if managing a code repo is no "work" on our end. I think I'll pass. If you can't post a text file with your additions/corrections/improvements/new-script so that others can review it, then do it your way... elsewhere.

 

[wardmundy]

And FWIW, I will be glad to host your improvements in the same way that we host ours, on pCloud. Anyone that is interested can then download the scripts just as they would do with a proprietary code repo owned by M$FT.

pCloud - IncrediblePBX2026

filedn.com

Why Microsoft's decision to bury GitHub in its CoreAI group is the end of an era

GitHub's independence within the Microsoft ecosystem was treasured by company executives in the years following in 2018 acquisition. But that era is over, and GitHub is now just another Microsoft product.

www.runtime.news

 

[billsimon]

Good luck @Samot .

 

[wardmundy]

Carpers Gonna Carp

 

[chris_c_]

For those that hate github (I don't) because of microsoft adding it to the AI division, an alternative is gitlab.

IMHO ipbx is more than one script, it depends on these 14 tarballs, without these it'll fail to build:
1. menuselect tarball,
2. iksemel tarball,
3. FreePBX backup of core incrediblepbx system tarball,
4. iptables-persistent tarball,
5. iptables4 tarball
6. rootfiles-debian10 tarball,
7. asteridex tarball,
8. ipbx-licenses tarball,
9. today3 tarball,
10. root folder update tarball,
11. ipbx2024 tarball,
12. ipbx-custom tarball,
13. PKCS-debian13 tarball,
14. incrediblepbx-17.0.0 tarball,

The above 14 should be made part of the repo.

PLUS obviously it needs these two:
15. freepbx-latest tarball,
16. asterisk-current tarball.

These 2 need not be made part of the repo.

 

[wardmundy]

@chris_c_: Are you volunteering to maintain the repo? FWIW: The tarballs in your list that are maintained by us have been static for at least 2 years and, in many cases, much longer. Wading through and debugging someone else's code that changes any of that code would be a job none of the current maintainers are willing to undertake primarily because of time constraints. But, by all means, have at it. And my offer to host the contributions still stands once you or anyone else has documented changes/improvements that need to be made.

As has always been the case, everyone is more than welcome to start things off by telling us what's not currently working. There's almost nothing on my list. And tell me again who else currently supports Asterisk 22 and 23 with FreePBX 17?

 

[wardmundy]

@chris_c_: You've apparently never been burned by an Asterisk or FreePBX update, or you would have included 15 and 16 in your repo wishlist. We keep working copies of them on pCloud just in case. The links are also included but commented out in the Incredible PBX 2026 installer script. It takes less than a minute to update the script when the wheels come off.