Open-source communities Sample Clauses

Open-source communities. The INSPIRE-5Gplus consortium is well aware of the growing importance in the networking landscape of open-source communities, and their influence to accelerate standardization by means of their interaction with SDOs, either direct or indirect, and by means of their ability to produce reference implementations of those standards. To identify possible targets for contributions among the increasing number of open-source communities, a first classification of them and their main characteristics can provide useful insights. First, we can identify a set of communities focused of what we can call the cloud foundations, comprising OpenStack (xxxxx://xxx.xxxxxxxxx.xxx/), Kubernetes (xxxxx://xxxxxxxxxx.xx/) and the more recent CNCF (xxxxx://xxx.xxxx.xx/). While the impact of potential contributions to these communities would be high, given the number of potential contributors and the width of their scope, the actual probabilities of acceptance are limited and would require a continuous and extremely high effort. A second category is related to development of network infrastructures and infrastructure management mechanisms, where specific security enablers could be quite welcome, and therefore constitute one of the main targets for contributions. This category includes the O-RAN alliance 12 xxxxx://xxx.xxxxxxxxx-xxx.xxx/ (xxxxx://xxx.x-xxx.xxx/), a hybrid approach to virtualised RAN technologies, TIP (xxxxx://xxxxxxxxxxxxxxxxxxx.xxx/), focused on telecommunications under the wider OCP (xxxxx://xxx.xxxxxxxxxxx.xxx/) umbrella, and CNTT (xxxxx://xxxx-x.xxxxxx.xx/CNTT/), a recent initiative sponsored by the GSMA for NFVI profiling and certification based on OPNFV (xxxxx://xxx.xxxxx.xxx/). The consolidation of the software approach to networking through SDN and NFV has implied the relevance of orchestration framework as mechanisms to deploy and activate security enablers, and coordinate tasks of threat detection and mitigation. The two reference projects in this space are ONAP (xxxxx://xxx.xxxx.xxx/) and OSM (xxxxx://xxx.xxxx.xxx/) that seems to slowly converge towards a common approach. In addition, we must consider the SONATA (xxxxx://xxxxxx.xxx/sonata-nfv/) framework as source of additional innovation, and the OpenTAP (xxxxx://xxx.xxxxxxx.xx/) project in what relates to testing. The nature of this class of projects makes them more suitable to contributions in the form of proofs of concept for the applicability of the orchestration frameworks to address security concern...
Sample 1
AutoNDA by SimpleDocs
Open-source communities. As special attention has been given to the use of open source software and standards, partial success of the project’s dissemination and exploitation activities will depend on the acceptance of the project within the open source community. To improve the chances of acceptance by this community, the project was positioned from the beginning at various conferences held by the open source community (e.g. ApacheCon, Berlin Buzzwords, FOSDEM, etc.) and/or such conferences where the primary and secondary target audience is members from the open source community.
Sample 1

Related to Open-source communities

  • Open Source 15.1 All software created for the Buyer must be suitable for publication as open source, unless otherwise agreed by the Buyer.

  • Open Source Assurance Program For Software that is Red Hat branded, purchases under this Agreement may entitle Client to participate in Red Hat’s Open Source Assurance Program which is described at xxxx://xxx.xxxxxx.xxx/rhel/details/assurance/. The terms for this optional program are subject to a separate agreement which can be viewed at xxxx://xxx.xxxxxx.xxx/legal/open_source_assurance_agreement.html.

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Third Party Software/Open Source Nothing in this Agreement shall restrict, limit or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under any applicable open source licenses to any open source code contained in the Software. The Software may include or be bundled with other software programs licensed under different terms and/or licensed by a licensor other than Licensor. Use of any software programs accompanied by a separate license agreement is governed by that separate license agreement. Any third party software that may be provided with the Software is included for use at Your option.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Creative Commons Attribution-Non-Commercial-NoDerivs License The Creative Commons Attribution Non-Commercial-NoDerivs License (CC-BY-NC-ND) permits use, distribution and reproduction in any medium, provided the original work is properly cited, is not used for commercial purposes and no modifications or adaptations are made. (see below) Use by commercial "for-profit" organizations Use of Wiley Open Access articles for commercial, promotional, or marketing purposes requires further explicit permission from Wiley and will be subject to a fee. Further details can be found on Wiley Online Library xxxx://xxxxxxx.xxxxx.xxx/WileyCDA/Section/id-410895.html Other Terms and Conditions:

  • California Independent System Operator Corporation a California nonprofit public benefit corporation having a principal executive office located at such place in the State of California as the CAISO Governing Board may from time to time designate (the “CAISO”).

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • COMPUTER SOFTWARE The Grantee certifies that it has appropriate systems and controls in place to ensure that state funds will not be used in the performance of this Grant Agreement for the acquisition, operation, or maintenance of computer software in violation of copyright laws.

Time is Money Join Law Insider Premium to draft better contracts faster.