New Documentation Links

[OnRelay Support]

We have updated and published the updated sipXcom documentation as follows:

• We have worked from the Sphinx documentation received from Matt Keys. The corresponding Wiki is now published as GitHub Pages on https://onrelay.github.io/sipxecs/.
  

• You can also access it via the GitHub Wiki at https://github.com/onrelay/sipxecs/wiki and the README file of the main repository.
  

• We have added / edited up-to-date pages for installing, upgrading and building sipXcom. We will also add a changelog before release.

• For anybody who wants to contribute to the documentation the corresponding Sphinx source is in the sipXwiki folder of the main code repository at https://github.com/onrelay/sipxecs.
  

WARNING: sipXcom 24.01 RPMs and sources are now available for installation and builds from GitHub and our repos as documented above, but 24.01 is not yet fully tested and released, so install and use at own risk!

[Jean-Francois Aubin]

Nice Job!

[Keith Laidlaw]

Yes, looks good.  Looks like a commitment to put it the work to keep the project up to date.

I only scanned the docs quickly but noticed two things right away:

1. I went to "Upgrade" and it talked about upgrading from 21.04 but never mentioned what we are upgrading TO.  Yes, I know the only release possible is 24.01 but it doesn't say that.  Perhaps this is because you don't want to maintain the version number in that page.  If so, perhaps referring to "Update to current version" would suffice and the page could be changed when an architectural change requires different upgrade from different versions.

2. Similar to the above, perhaps you could have a tab of "Revision History" which would also have or link to "Revision Notes" for each version starting with 24.01

3. I still see "SipXecs".  As I recall, SipXcom is a fork of SipXecs and both were active at one time.  I suspect SipXecs fork is dead.  No need to change the SipXcom fork to eliminate every occurence of SipXecs as that is developer code but can we not say "Welcome to SipXecs"?

Small points that shouldn't shadow the big point that it's nice to see the definite commitment. 

Thank you.

On Wednesday, April 24, 2024 at 5:13:56 PM UTC-4 OnRelay Support wrote:

[OnRelay Support]

Keith,

1. Thanks! Just updated Sphinx doc with the upgrade clarification.

2. We try to keep it simple and use the standard GitHub issues and release mechanisms for version tracking.

See https://github.com/onrelay/sipxecs/releases/tag/24.01.0-update-000 for the 24.01 release description.

There is also a link to all 24.01 changes at https://github.com/onrelay/sipxecs/milestone/1?closed=1.

3. It is hardly consistent, but here we generally refer to sipxecs the overall (historic) project, with all its forks, and sipxcom the (current) resulting product. I.e. sipxecs is like Linux and sipxcom is like CentOS.

[Todd Hodgen]

Maybe Mike Picher can chime in here.  I am pretty sure underlying code is still attributed to sipxecs, and is a part of sipXcom.  There may be legal responsibilities that require calling some things sipXecs still.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/aa4c2273-5104-4340-9efa-683390b36b6cn%40googlegroups.com.

[Keith Laidlaw]

we generally refer to sipxecs the overall (historic) project, with all its forks, and sipxcom the (current) resulting product

Very good way to look at it.  It had been very confusing  at times when SipFoundry had a web presence as I would say they looked at sipxecs as both the project and product.  I see that sipfoundry.org is now gone so we can safely adopt your way of looking at it!

Thanks.  I'm very encouraged, indeed.