Latest news + banner, cypress tests, open source copy, general style tweaks (#13)

* Adding latest news and banners * Adding first draft of cypress specs and github actions workflow * Adding sticky position for top banner * Tweak styles for new latest news section * Tweak styles for text__layout innerHTML * Fix Cypress homepage test spec * Fix mobile navi z-index with sticky top banner * Fix sticky banner z-index bug with mobile navi * Refactor markdown tools to support pages beyond developer docs * Adjust TADHACK text max-widths for small mobile * initial changes for open source copy * more copy * more copy * updated open source structure * minor * typo * more copy * Adjust styles for Open Source markdown small text * Update readme and remove floats from docs webhooks markdown * Add readme notes on Cypress and flesh out navi spec tests * Fix main navi highlight when on sub-sections of markdown pages Co-authored-by: Dave Horton <daveh@beachdognet.com>
2026-10-25 21:04:31 +00:00 · 2021-07-22 12:34:01 -04:00
1 parent ac33cdaac1
commit db94b17829
@@ -0,0 +1,13 @@
+# How we contribute
+
+Of course, our main contribution to the open-source ecosystem has been to create the [jambonz](https://jambonz.org) and [drachtio](https://drachtio.org) projects, and to make them freely available under the MIT License.  As part of this, we provide an extensive amount of unpaid support by responding to issues on github, email or [our slack channel](https://joinslack.jambonz.org).
+
+However, we are also a [consumer of open-source products](/open-source/commitment/oss-we-use/), and we believe that we have a responsibility to try to find additional ways to support the RTC open-source ecosystem where possible.
+
+To that end, this year we are sponsoring [TADHack Global 2021](https://tadhack.com/2021/), providing both funds for prize money as well as free services for participants.  Depending on the covid situation, we hope to travel to Orlando to attend in person.
+
+We have also sponsored other conferences in the past, including the wonderful [CommCon](https://2019.commcon.xyz/) conference in the UK (run by the awesome Dan Jenkins of [Nimble Ape](https://nimblea.pe/)), and have attended and spoken at other open-source conferences, including [SimCon](https://blog.simwood.com/2020/06/simcon4-and-something-new/).
+
+We provided a small amount of funding this year to support the openSIPS security audit via their [gofundme](https://www.gofundme.com/f/opensips-security-audit-penetration-tests) initiative.
+
+And, finally, last but not least, we tried to purchase enough yummy baked goods last year to help save the awesome [Bearkery Bakery](https://bearbakeshop.com/), which was run by one of the best people in the RTC community, [Fred Posner](https://qxork.com/).  Ultimately, we were defeated by the pandemic, but we don't regret a moment of the effort (gurgle, burp).
@@ -0,0 +1,26 @@
+# Open source that we make
+
+We<sup>*</sup> make [jambonz](https://jambonz.org), a communication platform-as-a-service (CPaaS) designed for use by service providers.
+
+We also make <a href="https://drachtio.org" target="_blank">drachtio</a>, a programmable [SIP]() server.  drachtio is one of the main open source components that is used in jambonz.
+
+We release both jambonz and drachtio under the <a href="https://github.com/jambonz/jambonz-feature-server/blob/main/LICENSE" target="_blank">MIT License</a>.
+
+<span class="mxs"><sup>*</sup>We = Drachtio Communications Services, LLC.</span>
+
+<div id="why-mit"></div>
+
+#### Why we chose the MIT License
+A few words might be in order on why we chose the MIT License, because we notice that quite often purveyors of "free as in beer" FOSS seem to be pictured by their user base as an austere sect of itinerant, karma-seeking monks who have taken a vow of poverty and wander the open source-scape doing saintly good deeds here and there - like providing free support, or adding any old feature that anyone thinks up, at any time, at no charge.  
+
+And sometimes, the fact that software is provided at no cost seems to result in a sense on the part of the consumer (not all mind you, but some) that it must accordingly have little or no value.
+
+First of all, as big consumers of beer, we resent the implication that free beer has no value.  That's just wrong.
+
+More seriously, companies choose different open source licenses because they have different business models.  We chose the MIT license - arguably the most permissive open-source license - because we are focused on encouraging trials, usage and adoption, and we wanted to remove as many barriers as possible that could stand in the way of that goal.
+
+We believe that jambonz fills a void in the market by delivering a true service provider-focused CPaaS.  There is a need for it.  But we acknowledge that we are competing in an arena with well-heeled commercial vendors. In this environment, delivering our solution in open-source format - as unrestricted as we could make it - is a purely tactical business decision.  We are after a faster pace of play - an increased tempo of create / find / fix / create / repeat. We are playing catch-up (as every startup has to, at the outset) but we are looking to establish a rate of product improvement that closed-source commercial vendors can not match.  
+
+The fuel that drives that product improvement tempo is contributions from the user base - unleashed of any licensing concerns or restrictions and with their imaginations fired by their ability to innovate freely on our platform. The MIT license is our way of enabling you to help us.  Together, we can win.
+
+
@@ -0,0 +1,31 @@
+# Open source that we use
+
+We are proud to have built jambonz by standing on the shoulders of some awesome open-source products. 
+
+Building an application like jambonz requires curating a selection of the best open source products, and without exception these products have been a delight to work with and are well-supported by talented teams of developers. Please consider supporting them!
+
+| product        | used for | license  |
+| ------------- |-------------| -----|
+| <a href="https://drachtio.org" target="_blank">drachtio</a> | application logic and call control | <a href="https://github.com/drachtio/drachtio-srf/blob/master/LICENSE" target="_blank">MIT</a> |
+| <a href="https://github.com/sipwise/rtpengine" target="_blank">rtpengine</a> | media proxy and transcoding | <a href="https://www.gnu.org/licenses/quick-guide-gplv3.html" target="_blank">GPL v3.0</a> |
+| <a href="https://github.com/signalwire/freeswitch" target="_blank">freeswitch</a> | media server | <a href="https://github.com/signalwire/freeswitch/blob/master/LICENSE" target="_blank">MPL v1.1</a> |
+| <a href ="https://github.com/drachtio/drachtio-freeswitch-modules" target="_blank">freeswitch plugins</a> | audio integrations w/ google, AWS, others| <a href="https://github.com/drachtio/drachtio-freeswitch-modules/blob/master/LICENSE" target="_blank">MIT</a> |
+| <a href="https://www.apiban.org/" target="_blank">apiban</a> | SBC protection from bad actors |<a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target="_blank">GPL v2.0</a>  |
+| <a href="https://expressjs.com/" target="_blank">express</a> | HTTP middleware and web framework |<a href="https://github.com/expressjs/expressjs.com/blob/gh-pages/LICENSE.md" target="_blank">Creative Commons v3.0</a>  |
+| <a href="https://nodejs.org/" target="_blank">Node.js</a> | Javascript runtime |<a href="https://github.com/nodejs/node/blob/master/LICENSE" target="_blank">MIT</a>  |
+| <a href="https://libwebsockets.org/" target="_blank">libwebsockets</a> | websockets library |<a href="https://github.com/warmcat/libwebsockets/blob/main/LICENSE" target="_blank">MIT</a>  |
+| <a href="https://www.mysql.com/" target="_blank">mysql</a> | susbcriber database |<a href=" http://oss.oracle.com/licenses/universal-foss-exception" target="_blank">GPL v2.0 with FOSS Exception</a>  |
+| <a href="https://github.com/influxdata/telegraf" target="_blank">Telegraf</a> | metrics agent | <a href="https://github.com/influxdata/telegraf/blob/master/LICENSE" target="_blank">MIT</a> |
+| <a href="https://github.com/influxdata/influxdb" target="_blank">Influxdb</a> | time series database | <a href="https://github.com/influxdata/influxdb/blob/master/LICENSE" target="_blank">MIT</a> |
+| <a href="https://redis.io/" target="_blank">Redis</a> | key-value store | <a href="https://redis.io/topics/license" target="_blank">3-clause BSD</a> |
+| <a href="https://github.com/sipcapture" target="_blank">Homer (optional)</a> | SIP capture | <a href="https://github.com/sipcapture/homer/blob/homer7/LICENSE" target="_blank">AGPL v3.0</a><span style="vertical-align: super; color: #da1c5c; font-size: 80%">*</span> |
+| <a href="https://www.postgresql.org" target="_blank">Postgresl (optional)</a> | homer database | <a href="https://www.postgresql.org/about/licence/" target="_blank">PostgreSQL License</a> |
+| <a href="https://grafana.com/" target="_blank">Grafana (optional)</a> | Monitoring dashboard | <a href="https://github.com/grafana/grafana/blob/main/LICENSE" target="_blank">AGPL v3.0</a> |
+
+<span class="mxs"><sup>*</sup> Note that:</span>
+
+<ol class="mxs">
+  <li>When using Homer (or Grafana) with the AGPL v3 license, any changes that you make to the jambonz source code <strong>are not</strong> considered a "covered work" by that license, as the two programs are not linked.<br/>TLDR: any changes you make to jambonz source code remain under the more permissive MIT license</li>
+  <li><a href="https://qxip.net/" target="_blank">QXIP</a>, the creator of Homer and the <a href="https://github.com/sipcapture/HEP" target="_blank">HEP protocol</a>, also offer a non-GPL option (<a href="https://hepic.tel" target="_blank">HEPIC</a>) that is specifically designed for the needs of large-scale telcos and Communications Service Providers.  We highly recommend it to those who need a carrier-class monitoring and SIP capture solution.</li>
+  <li>If, after reading the above, you (or the company you work for) are still scared off by the AGPL v3 license, and are not interested in <a href="https://hepic.tel" target="_blank">HEPIC</a> (have you checked it out?), then know that neither Homer nor Grafana are required components of jambonz: simply don't install them, or remove if already installed.</li>
+</ol>
@@ -0,0 +1,27 @@
+# How you contribute
+
+The MIT open source license spells out your legal requirements when using the jambonz software, and these, by design, are minimal.
+
+However, since you are using the software we would expect that you have a vested interest in seeing the project grow more healthy, and the capabilities and reliability of the software improve.  To that end, please consider ways that you can help make this happen.  
+
+Here are some easy (i.e. no cost) ways you can contribute:
+
+- Report bugs (open issues on github, or raise them on our [slack channel](https://joinslack.jambonz.org)), providing as much detail in possible and offering to help recreate and to test fixes. 
+- Offer to help test new or experimental features
+- Have coding skills (Node.js, React, Voip/SIP, or C++)? We'd love your help as a code contributor.
+- Evangelize.  Talk the project up to your friends and business contacts. Allow us to use your success stories in our marketing materials.
+
+All of these can be really helpful in moving a project forward.
+
+There are also several easy ways you can provide direct financial support to the project:
+
+- <a href="mailto:support@jambonz.org?subject=Hey,%20I'd%20like%20to%20discuss%20a%20project%20with%20you!">Hire us for services</a>: our business model is providing services around jambonz and drachtio, and we are available to assist customers with jambonz deployments as well as custom development of VoIP applications.
+- Sign up for a monthly subscription on [jambonz.us](https://jambonz.us) - you get a hosted jambonz account while supporting the project.
+- Use our [AWS Marketplace offering](https://aws.amazon.com/marketplace/pp/prodview-7lmody7uv2sye) to build your own jambonz system on AWS.
+- [Sponsor us on Github](https://github.com/sponsors/drachtio/).
+
+Finally, we encourage you to think about supporting open-source RTC projects more generally.  
+
+In fact, we don't think you should think of supporting open-source in a purely symmetrical fashion - e.g., "I use project A, so I should figure out how to send money to project A".  
+
+We'd encourage you to think in a more asymmetric fashion. Supporting project A is great, but if you can't manage that, perhaps you can send some of your staff to an open-source conference this year, or maybe even provide sponsorship for one.  Or maybe you can allow project A to use your experience publicly as a success story on their web site.  The point is, there are many ways to support the overall ecosystem that you are now part of. All you need to do is care.