├── Armo ├── images │ ├── kubescape.png │ ├── Armo_PR_banner.png │ └── Armo_PR_banner_big.png └── README.md ├── Nirmata ├── images │ ├── kyverno_logo.png │ ├── Nirmata_PR_banner.png │ └── Nirmata_PR_banner_big.png └── README.md ├── Wix.com ├── images │ ├── Wix_PR_banner.png │ └── Wix_PR_banner_big.png ├── README-Hebrew.md └── README.md ├── Cloudify.co ├── images │ ├── cloudify_logo.png │ ├── cloudify_plugins.png │ ├── Cloudify_PR_banner.png │ └── Cloudify_PR_banner_big.png └── README.md ├── Livecycle ├── images │ ├── Livecycle_PR_banner.png │ └── Livecycle_PR_banner_big.png └── README.md ├── Memphis.dev ├── images │ ├── Memphis_PR_banner.png │ └── Memphis_PR_banner_big.png └── README.md ├── checkmarx.com ├── images │ ├── Checkmarx_PR_banner.png │ └── Checkmarx_PR_banner_big.png └── README.md ├── README.md └── Fiberplane └── README.md /Armo/images/kubescape.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Armo/images/kubescape.png -------------------------------------------------------------------------------- /Armo/images/Armo_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Armo/images/Armo_PR_banner.png -------------------------------------------------------------------------------- /Nirmata/images/kyverno_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Nirmata/images/kyverno_logo.png -------------------------------------------------------------------------------- /Wix.com/images/Wix_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Wix.com/images/Wix_PR_banner.png -------------------------------------------------------------------------------- /Armo/images/Armo_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Armo/images/Armo_PR_banner_big.png -------------------------------------------------------------------------------- /Cloudify.co/images/cloudify_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Cloudify.co/images/cloudify_logo.png -------------------------------------------------------------------------------- /Nirmata/images/Nirmata_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Nirmata/images/Nirmata_PR_banner.png -------------------------------------------------------------------------------- /Wix.com/images/Wix_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Wix.com/images/Wix_PR_banner_big.png -------------------------------------------------------------------------------- /Cloudify.co/images/cloudify_plugins.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Cloudify.co/images/cloudify_plugins.png -------------------------------------------------------------------------------- /Cloudify.co/images/Cloudify_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Cloudify.co/images/Cloudify_PR_banner.png -------------------------------------------------------------------------------- /Livecycle/images/Livecycle_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Livecycle/images/Livecycle_PR_banner.png -------------------------------------------------------------------------------- /Memphis.dev/images/Memphis_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Memphis.dev/images/Memphis_PR_banner.png -------------------------------------------------------------------------------- /Nirmata/images/Nirmata_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Nirmata/images/Nirmata_PR_banner_big.png -------------------------------------------------------------------------------- /Livecycle/images/Livecycle_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Livecycle/images/Livecycle_PR_banner_big.png -------------------------------------------------------------------------------- /Memphis.dev/images/Memphis_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Memphis.dev/images/Memphis_PR_banner_big.png -------------------------------------------------------------------------------- /checkmarx.com/images/Checkmarx_PR_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/checkmarx.com/images/Checkmarx_PR_banner.png -------------------------------------------------------------------------------- /Cloudify.co/images/Cloudify_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/Cloudify.co/images/Cloudify_PR_banner_big.png -------------------------------------------------------------------------------- /checkmarx.com/images/Checkmarx_PR_banner_big.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Pull-Request-Community/open-source-rel/HEAD/checkmarx.com/images/Checkmarx_PR_banner_big.png -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # open-source-rel 2 | 3 | In this repository, you'll find testimonies by companies, stating their vision about OSS, and how they actively contributing to the OSS realm. 4 | 5 | 01/04/22 [Wix](https://github.com/Pull-Request-Community/open-source-rel/tree/main/Wix.com) 6 | 7 | 02/05/22 [Cloudify](https://github.com/Pull-Request-Community/open-source-rel/tree/main/Cloudify.co) 8 | 9 | 14/05/22 [Checkmarx](https://github.com/Pull-Request-Community/open-source-rel/tree/main/checkmarx.com) 10 | 11 | 27/06/22 [Livecycle](https://github.com/Pull-Request-Community/open-source-rel/blob/main/Livecycle) 12 | 13 | 30/06/22 [Memphis.dev](https://github.com/Pull-Request-Community/open-source-rel/blob/main/Memphis.dev) 14 | 15 | 18/07/22 [Armo](https://github.com/Pull-Request-Community/open-source-rel/blob/main/Armo) 16 | 17 | 18/10/22 [Nirmata](https://github.com/Pull-Request-Community/open-source-rel/blob/main/Nirmata) 18 | 19 | 17/07/23 [Fiberplane](https://github.com/Pull-Request-Community/open-source-rel/blob/main/Fiberplane) 20 | -------------------------------------------------------------------------------- /checkmarx.com/README.md: -------------------------------------------------------------------------------- 1 | # Checkmarx & Open Source 2 | 3 | PR <3 Checkmarx 4 | 5 | [Checkmarx](https://checkmarx.com/) is a software security company that creates solutions to help developers build security-aware applications. Checkmarx has multiple solutions that integrate into the SDLC process - static code testing (SAST and IAST), dependency analysis (SCA), supply chain security (SCS), infrastructure as code security testing (KICS), and application security training (Codebashing). 6 | 7 | Jossef Harush Kadouri, Head of Engineering of Supply Chain Security at Checkmarx, says that the good intention of giving back to the community and enhancing the OSS realm are worth the value of publishing code as open source. 8 | 9 | Jossef also believes that Checkmarx active participation in the OSS realm is not only good for the company brand itself, but also for their developers - The sense of community belonging and pride seeing their artifacts being employed by external users is the fuel that keeps them going and contributing to OSS projects. 10 | 11 | Checkmarx loves contributing and creating [open source projects](https://github.com/Checkmarx). Here are some of the many projects on its [GitHub page](https://github.com/Checkmarx): 12 | 13 | - [KICS](https://github.com/Checkmarx/kics) (i.e. Keeping Infrastructure as Code Secure) - This tool helps you find security vulnerabilities, compliance issues, and infrastructure misconfigurations early in the development cycle of your infrastructure-as-code 14 | 15 | 16 | - [ChainAlert](https://github.com/Checkmarx/chainalert-github-action) - A free service for the OSS community that scans popular packages (npm and more) and alerts in case there is a suspicion those packages' accounts were hacked. It compares tags on GitHub to the tags listed on the registry, and if there’s no match - It opens issues and alerts the maintainers. You can add ChainAlert's GitHub action to your repository to be notified in case of a suspected takeover of one of your dependencies, giving you the chance to rapidly respond and protect yourself and your users 17 | 18 | 19 | - [ChainJacking](https://github.com/Checkmarx/chainjacking) - A tool that helps you find which of your Golang direct GitHub dependencies is susceptible to ChainJacking attacks. This project Can be incorporated into CI - CI process will fail if a sub-dependency is detected as exposed to ChainJacking 20 | -------------------------------------------------------------------------------- /Livecycle/README.md: -------------------------------------------------------------------------------- 1 | # Livecycle & Open-Source 2 | 3 | PR <3 Livecycle 4 | 5 | [Livecycle](https://livecycle.io) is an inclusive collaboration platform that helps teams 10x the speed of PR reviews so they can ship code faster. 6 | 7 | Once Livecycle is installed on the Git repository, an ephemeral "playground" environment is created for every PR and commit, and is accessible with a single click. Each Livecycle playground has built-in annotation tools, so teammates can leave review comments in their full context on top of the product UI. The comments are organized in Livecycle and also synced back to Git so the code owners can understand and resolve the issues quickly and easily. 8 | 9 | According to CTO and co-founder Yshay Yaacobi, open-source project maintenance is one of Livecycle’s most important use cases: “Livecycle, like many other solutions today, is built on top of amazing open-source solutions. Our core product functionality lies on the top of the PR process that was popularized by OSS, and we’re on a mission to make this process more accessible and inclusive to everyone. Livecycle will be **free forever for OSS projects**, as we hope to enable seamless collaboration between maintainers and contributors (including non-technical stakeholders).” 10 | 11 | Yshay adds that in an OSS context, this becomes [very powerful](https://livecycle.io/blogs/oss/): “The OSS workflow is distributed and unpredictable by nature, and so the ability to provide instant visibility to a particular code change, and to streamline communication between project maintainers and contributors can really make an impact on the success of the project”. 12 | 13 | ## Livecycle's OSS activities: 14 | 15 | In addition to the benefits of the product itself, Liveycle is also giving back to the OSS community in other ways: 16 | 17 | - **Sponsorship** - They’ve decided as a company to support any open-source project that brings them value day-to-day (a recent example of this is Chakra UI) 18 | - **Sponsorship advocacy** - They’ve also taken these efforts one step further and [openly encourage](https://livecycle.io/blogs/why-we-support-open-source-chakra/) other companies to do the same, and “give back” to the creators of the open-source tools that the community is benefiting from. 19 | - **[The Dev-X Project](https://livecycle.io/devx/)** - Livecycle’s growing DX community features leading developers from across the industry, with an emphasis on highlighting those who believe in the power and the importance of open-source. 20 | -------------------------------------------------------------------------------- /Armo/README.md: -------------------------------------------------------------------------------- 1 | # ARMO, Kubescape & Open-Source 2 | 3 | PR <3 Armo 4 | 5 | [ARMO](https://www.armosec.io/), the company behind [Kubescape](https://cloud.armosec.io/dashboard), is building the first end-to-end open-source Kubernetes Security platform (with their patented technology), made for DevOps, to ensure Kubernetes components are all secured E2E. 6 | 7 | Kubescape is a Kubernetes open-source platform providing a multi-cloud K8s single-pane-of-glass, including risk analysis, security compliance, misconfiguration scanning, RBAC visualizer, and image vulnerabilities scanning. 8 | 9 | Kubescape by Armo 10 | 11 | ### Why is Kubescape open-sourced? 12 | 13 | ARMO believes that open-source can be a great game-changer for K8s security as it has been for many aspects of cloud-native, coding, and DevOps. When asked why ARMO is taking an open-source approach for Kubernetes security generally, [Shauli Rozen](https://www.linkedin.com/in/shaulirozen/), ARMO CEO & Co-Founder, answered: 14 | 15 | ##### Today, DevOps teams are being forced to choose: 16 | 1. Make an attempt to integrate several different and fragmented open-source tools together, which are pretty complex to monitor and manage, and require a large amount of effort to generate synergy. 17 | 2. Commit to a proprietary solution that they can’t adapt, access the code, influence the roadmap or contribute.” 18 | That’s why they decided that their main product - Kubescape - should be open-sourced. On one hand, be the one-stop-shop, eliminating the need to integrate several different and fragmented tools, and on the other hand - Leverage what open-source can offer to enhance the product - Developers can collaborate and contribute to a broader range of issues, collecting more knowledge and expertise, eventually making K8s security much more resilient. 19 | 20 | According to Shauli Rozen, “Kubernetes is open-source, and Kubernetes security should be open-sourced too, following the same culture of transparency and collaboration. Dev and DevOps teams want to adopt and enforce K8s security but in their own “DevOps”, OSS based, way like they are used to. ARMO is committed to making Kubernetes security - open-source, usable, transparent, and community-driven so everyone can benefit from – and contribute to – the most secure k8s platform available.” 21 | 22 | ARMO welcomes the Kubernetes community to give feedback and ideas for improvement, thus inviting anyone who wants to [contribute and collaborate](https://github.com/armosec/kubescape/issues?q=is%3Aissue+is%3Aopen+label%3A%22open+for+contribution%22) with them on their [GitHub page](https://github.com/armosec/kubescape) and/or their [discord channel](https://armosec.github.io/kubescape/) to help make Kubescape more robust and complete as Kubernetes develops. 23 | -------------------------------------------------------------------------------- /Wix.com/README-Hebrew.md: -------------------------------------------------------------------------------- 1 | # Wix & Open-Source 2 | 3 | PR <3 Wix 4 | 5 | חברת [וויקס](https://www.wix.com) מצטרפת לחברות נהדרות ומבוססות אחרות כמו מיקרוסופט, גוגל, איי.בי.אם ועוד, שמבינות שלקוד פתוח יש תפקיד מרכזי בעולם ההייטק ועיצובו המתמיד. 6 | וויקס תומכת גם בספריות קוד פתוח מבוססות (אשר יש בהן שימוש פנימית בתהליכים ובאינטגרציה עם הקוד הקיים בחברה) וכן גם בספריות פחות מבוססות (כאלה שאין בהן שימוש פנימי בוויקס או שהשימוש בהן מועט). ספריות מבוססות מקבלות תשומת לב רב יותר ומשאבים שמנותבים לתחזוקה של אותן ספריות - תחזוקה שוטפת של קהילות הדיסקורד ושל הספריות עצמן, בעוד שספריות פחות מבוססות מתוחזקות על בסיס זמן פנוי- כחלק משבוע גילדה שמתקיים בחברה אחת לרבעון, ובימים מרוכזים של תרומה לקוד פתוח. 7 | 8 | 9 | ## וויקס תורמת בצורה אקטיבית לעולם הקוד פתוח במספר דרכים: 10 | 11 | ### _פעילויות ציבוריות_: 12 | 1. חסויות - וויקס החליטה להעניק חסות ל-8 הספריות השימושיות ביותר (בתוך וויקס). כדי להחליט אילו ספריות הן אכן השימושיות ביותר ושהיוו את ההשפעה הרבה ביותר על גילדות הפיתוח, הם יצרו סקר שהופץ לכל החברה בו ביקשו להציע ספריות, ולאחר מכן גם להצביע לאותן ספריות. 8 הספריות שקיבלו את אחוז ההצבעה הגבוה ביותר החל לקבל חסות מוויקס. 13 | 14 | 2. שחרור פרויקטים לגיטהאב - וויקס שחררו מספר רב של פרויקטים וחלקי קוד כקוד פתוח (אותם ניתן למצוא בלינק [הזה](https://github.com/wix)), ובנוסף ישנם אנשי ונשות פיתוח בוויקס שמוקצים לתחזק את הפרויקטים הללו על בסיס יומי קבוע כדי לוודא שהם עומדים בסטנדרטים של אינקובטור. 15 | 16 | ### _פעילויות פנימיות_: 17 | 1. קווים מנחים לתרומה לקוד פתוח - וויקס יצרה פרויקט גיטהאב פנימי עבור עובדיה שמטרתו להבין ולכסות את הדברים הנדרשים לשחרור פרויקט כפרויקט קוד פתוח - הוא מכיל דוקומנטציה ורשימות אשר העובד/ת י/תוכל לעקוב ולוודא שהכל נעשה, ובעצם מלווה אותם בתהליך הזה. 18 | 19 | 2. תמיכה היקפית - וויקס מציעה עזרה עם מגוון היבטים הקשורים לקוד פתוח - 20 | 21 | 2.1 דוקומנטציה - היא מקצה כותבים טכניים שיעזרו בכתיבת הדוקומנטציה של פרויקט הקוד הפתוח, במידה ויש עניין בכך. 22 | 2.2 מיתוג ועיצוב - היא עוזרת ביצירת לוגו, שפה עיצובית ואלמנטים מיתוגיים אחרים עבור פרויקט הקוד פתוח. 23 | 2.3 רישוי והתאמה לדרישות חוקיות - היא מבצעת סריקת רשיון כדי לוודא שלפרויקט יש מינימום פגיעויות וכן שיש התאמה לדרישות החוקיות של קוד פתוח. 24 | 2.4 קידום ושיווק - היא עושה שימוש בכלים שנועדו לשווק ולקדם את הפרויקט לקהלי יעד רלוונטיים. 25 | 2.5 מיגרציה לריפו הציבורי של וויקס - היא מבצעת מיגרציה של הפרויקט לריפו הציבורי של וויקס, דבר שנותן חשיפה רבה ואף תמיכה רשמית של וויקס באותו פרויקט. 26 | 27 | 3. תרומה לקוד פתוח בשבוע גילדה - וויקס מקיימת שבוע גילדה בכל רבעון שבו עובדים/ות יכולים/ות לבחור לתרום ולקחת חלק פעיל בפעילויות מגוונות שהם לא חלק מהמשימות היומיומיות שלהם. אחד מהמסלולים המוצעים הוא תרומה לקוד פתוח - פעם ברבעון, עובד/ת י/תוכל לבחור במסלול זה ובמשך שבוע שלם לעבוד על פרויקט קוד פתוח לבחירתו/ה ולתרום לו. 28 | 29 | 4. ימי תרומה מרוכזים - ימים מרוכזים שמתרחשים מעת לעת בהם עובדים/ות יכולים/ות לקחת חלק ולתרום לקוד פתוח. 30 | 31 | 5. הדרכת גיטהאב עבור תרומה לקוד פתוח. 32 | 33 | 6. מדיניות ״דלת פתוחה״ - כל עובד/ת שרוצה לתרום לקוד פתוח או לעשות כל דבר בעולם הרחב הזה, יכול/ה ליצור קשר עם אנשים ונשים רלוונטיים/ות בארגון ולקבל את העזרה והתמיכה בנושא. 34 | -------------------------------------------------------------------------------- /Memphis.dev/README.md: -------------------------------------------------------------------------------- 1 | # Memphis.dev & Open Source 2 | 3 | PR <3 Memphis.dev 4 | 5 | [Memphis.dev](https://memphis.dev "Memphis.dev") is an open-source, modern replacement for Apache Kafka, built out of the struggles of developers working with event-driven architectures, troubleshooting, and scaling. Memphis enables devs to get a fully-optimized message broker and achieve all other message brokers' benefits in a fraction of the time. 6 | 7 | When asked what Memphis's future would be in terms of open-source, **Idan Asulin, CTO & Co-Founder**, replied: 8 | > Memphis.dev started as, and always will be an open-source project next to a future managed version. Community-driven product is one of Memphis’ fundamental beliefs to create a value-first solution to real users’ struggles. 9 | 10 | According to Idan, the main advantages behind building an open-source first product are - 11 | - **Community Power** - Community is one of the biggest strengths any product can have. First, feature validation is one of the biggest challenges any PM or developer has. With an engaging community that follows the product's evolutions and core DNA, it is easier to understand if the feature made the right impact and was built correctly. With a community of followers, submitting a poll on the project’s chat platform and reviewing the responses will provide great value. Second, Instead of creating your roadmap based on several minds of your team, share it with your followers and get 10X more ideas that would have a higher chance of solving a real pain. 12 | - **No Vendor-lock** - This one goes both ways. Open core allows customers (both large and small companies) to go inside the implemented system's core and provide much-needed ability to troubleshoot and better tune it based on the environment's needs. 13 | - **Elasticity** - When built right, open-source is a great way to allow your contributors and community to stretch the project abilities, like creating SDKs, required components, features, UI enhancements if they exist, and more. 14 | - **Easier adoption** - Getting early adopters or adopting an open-source project is much more straightforward than proprietary software. Why? (a) Open-source adoption usually doesn't require a formal commitment of any kind. (b) Support is made by the community and does not require the creator to hire support engineers on day 1. ( c) If appropriately documented, the onboarding process should be self-served and performed autonomously by the users. 15 | 16 | Memphis actively contributes to Open-Source in several ways: 17 | - Memphis core components such as UI, Broker, CLI, SDKs are [open-sourced](https://github.com/memphisdev/memphis-broker "open-sourced"). 18 | - The architecture of Memphis is entirely pluggable. In the current version, the community can further extend SDKs to include most of the popular languages. 19 | In the future, a marketplace of connectors and functions will enable even wider extensions and work with Memphis as with building blocks. 20 | - Memphis is also a contributor and an active participant in “Data on Kubernetes” Community, CNCF, and NATS.IO. 21 | -------------------------------------------------------------------------------- /Cloudify.co/README.md: -------------------------------------------------------------------------------- 1 | # Cloudify & Open Source 2 | 3 | PR <3 Cloudify 4 | 5 | Cloudify is an Open-Source orchestration platform that helps DevOps teams structure their environments and enable developer self-service. 6 | 7 | Cloudify and Plugins 8 | 9 | Cloudify Environment as a Service (EaaS) enables engineers to turn their existing Kubernetes, Helm, Terraform, etc. into self-service development and production environments. 10 | 11 | 12 | When asked why they utilize Open-Source as the main product’s vertical, Nati Shalom, CTO & Founder of Cloudify, replied: 13 | * **Disruption** - Open-Source is a very effective tool for a startup to disrupt a market that is highly dominated by non-open source incumbent players. In our case that was VMware or the public cloud providers (See [Summit 2017: A David vs. Goliath Tale of Triumph](https://www.reversim.com/2018/02/summit-2017-david-vs-goliath-tale-of.html)). 14 | 15 | * **Win large customers** - Open-Source allows large enterprises to adopt software solutions from small startups by reducing the lock-in risk. 16 | 17 | * **DevOps friendly** - The DevOps automation space is often built out of integration of many tools (a tool chain). The integration between Open-Source tools is often much easier than non Open-Source tools, which is why most DevOps tools take the Open-Source route. 18 | 19 | * **Ideology** - We believe that Open-Source forces companies to write high quality software simply since everyone can see the code. It also helps to drive a more collaborative and transparent company culture. 20 | 21 | Cloudify actively contributes to Open-Source in several ways: 22 | 23 | * The Cloudify manager and all supporting infrastructure, such as the UI, is [Open-Source.](https://github.com/cloudify-cosmo) 24 | 25 | * The Cloudify architecture is pluggable. The Open-Source Cloudify manager can be further extended through the development of plugins. Cloudify open sources and [releases](https://github.com/orgs/cloudify-cosmo/repositories?q=plugin&type=all&language=&sort=) all of their officially supported plugins, which are written in Python. Users can also develop their own plugins and extend the resource library, the UI, and the automation language itself. 26 | 27 | * Cloudify provides an [Open-Source community](https://github.com/cloudify-community/) of blueprints and actively [accepts contributions](https://github.com/cloudify-community/contributing) of both plugins and blueprints from their community of users. 28 | 29 | * Cloudify designed and maintains the [Wagon packaging format](https://github.com/cloudify-cosmo/wagon) for bundling Python wheels together for offline installation. Wagon provides the ability to combine multiple Python wheels into a single archive that can be distributed in offline environments. While originally designed to work with Cloudify’s plugin architecture, Wagon packages can be used in any environment where distributing combined sets of offline Python wheels is necessary, such as in secure or limited environments. 30 | -------------------------------------------------------------------------------- /Wix.com/README.md: -------------------------------------------------------------------------------- 1 | # Wix & Open-Source 2 | 3 | PR <3 Wix 4 | 5 | [Wix](https://www.wix.com) joins other great & well established companies like Microsoft, Google, IBM and more that understands that Open-Source has a key role in the tech landscape. 6 | Wix supports both established OSS projects (Libraries that are used internally) and non-established OSS projects (Libraries that are not directly used or rarely used internally) in their daily approach towards OSS. 7 | Established projects gets more attention and resources - Actively Managing their Discord communities, and assign internal resources upfront to maintain the projects, whereas non-established projects are being handled on a spare-time, guild-week / contribution days basis. 8 | 9 | 10 | 11 | ## Wix actively contributing to the Open-Source realm in several ways: 12 | 13 | ### _External Activities_: 14 | 1. Sponsorship - It decided to sponsor the 8 most used OSS libraries. To decide which libraries are the most used and contributed the most to the SW guilds, It conducted a survey that was spread over the entire company and requested its employees to suggest any libraries and later on have a vote for the suggested libraries to determine which libraries contributed the most, according to the voters. Then, once the 8 libraries were selected - Wix started sponsoring them. 15 | 16 | 2. Projects Public Releases - It releases a lot of projects and useful pieces of code as OSS (you can see them in this [link](https://github.com/wix)) and 17 | there are Software Developers at Wix that are assigned to maintain these projects on a daily basis to make sure they follow the Incubator standards. 18 | 19 | ### _Internal Activities_: 20 | 1. OSS Contribution Guidelines - It created an internal GitHub repository for internal employees that solely deals with how to start and release an OSS project- it contains documentation and checklists that an employee could follow to make sure they know exactly what to do since the guidelines are clearly laid out for them to use. 21 | 22 | 2. OSS Peripheral Support - It offers help with various aspects related to OSS - 23 | 24 | 2.1 Documentation - Assigning technical writers to help with OSS documentation. 25 | 2.2 Design & Branding - Helping to create a design language, logo and other branding elements for the OSS project. 26 | 2.3 Licensing & Legal Compliance - Perform a license scan to make sure the project has minimal vulnerabilities & complies with OSS licensing requirements. 27 | 2.4 Promotion - Utilizing tools to push the project to target audiences. 28 | 2.5 Wix Public Migration - Transferring the project to Wix’s public library. 29 | 30 | 3. OSS Guild-Week Contribution - It holds guild-weeks in which employees can choose to contribute and engage in various activities which are not part of their day-to-day tasks. One of those guild-week tracks are OSS Contribution - Once in a quarter, an employee could choose this track and for an entire week, work on an OSS project to contribute to. 31 | 32 | 4. Contribution Days - Centralized days in which employees can participate and contribute to OSS. 33 | 34 | 5. GitHub trainings for OSS contributions. 35 | 36 | 6. An Open-Door Policy - Whoever wants to contribute to OSS or do anything in this realm, knows they have a direct access to do so, and Wix will gladly help. 37 | -------------------------------------------------------------------------------- /Fiberplane/README.md: -------------------------------------------------------------------------------- 1 | # Fiberplane & Open Source 2 | [Fiberplane](https://fiberplane.com/) has a strong approach to [building open-source tools](https://fiberplane.com/opensource) and contributing to the wider open-source ecosystem. The company has started a fully Open Source project called Autometrics and also baked in open-source components in their SaaS products: Fiberplane notebooks. 3 | 4 | A [Discord](https://discord.gg/6eZyhxFBmC) space for community interaction, questions, and support regarding both projects is available. 5 | 6 | ## Autometrics 7 | [Autometrics](https://autometrics.dev/) is an open-source micro framework for developer-first observability. Its goal is to make it easy to instrument your code base and get metrics out of the box based on the functions in your code. From there, it helps you to generate SLOs and alerts. 8 | 9 | 10 | It is built on top of the open-source projects [Prometheus](https://prometheus.io/) and [OpenTelemetry](https://opentelemetry.io/). 11 | 12 | The micro framework is available for multiple languages. Fiberplane officially supports four languages (Python, TS, Go, and Rust), and there are community contributions for two languages (Java and C#). The language packages, IDE extensions, and shared sources are in a dedicated [Autometrics-Dev GitHub organization](https://github.com/autometrics-dev). There are [discussions on GitHub](https://github.com/orgs/autometrics-dev/discussions) for future development. In general, the whole development happens in the open, and besides the GitHub discussions, more conversations are taking place in the mentioned Discord space above. 13 | 14 | ### Why is Autometrics open source? 15 | The tool aims to make observability developer friendly. Hence making open-source, developers can contribute to this approach. 16 | 17 | Autometrics provides a simple way to instrument your code and get metrics from the functions in your code base. Because it is an easy tool to get started with observability, open source supports this approach and lowers the barrier to adopting the solution. 18 | 19 | Additionally, it is built on top of other open-source tools and uses those components. Therefore an exchange with existing communities is important to provide the best outcome and value to the users of the microframework. 20 | 21 | ## Fiberplane notebooks 22 | Fiberplane Notebooks is a SaaS solution that allows you to debug your infrastructure, resolve incidents and create runbooks collaboratively. 23 | 24 | Engineering teams can write queries within the notebooks and connect them to their observability data backends like Prometheus, Elastic Search, and Loki. Those are called Providers. The whole [provider stack is open-source](https://fiberplane.com/blog/opensourcing-providers). The open-source stack allows you to write own providers and create your own observability stack. Besides the providers, the [CLI tool fp](https://github.com/fiberplane/fp) and [Fiberplane template](https://github.com/fiberplane/templates) are open source too. All projects are in [Fiberplane's GitHub repo](https://github.com/fiberplane). 25 | 26 | 27 | ### Why are parts of Fiberplane notebooks open source? 28 | The main reason for providing open-source components is to make Fiberplane notebooks extensible and flexible toward integrating multiple tools and vendors. 29 | 30 | Further, it benefits the community and generates a shared basis for example, for useful Fiberplane templates. Further, opening the provider stack allows people to understand how data is processed. It enables transparency and good quality when building Software. 31 | 32 | 33 | ## Fiberplane's contribution to Open Source 34 | 35 | Besides building open-source software, Fiberplane contributes to other communities too. 36 | 37 | Within the OpenTelemetry community, Fiberplane developers engage in discussion towards further development and contribute code too. 38 | -------------------------------------------------------------------------------- /Nirmata/README.md: -------------------------------------------------------------------------------- 1 | # Nirmata & Open Source 2 | 3 | PR <3 Nirmata 4 | 5 | [Nirmata](https://nirmata.com/) is the creator of [Kyverno](https://kyverno.io), the Kubernetes native policy engine OSS. Nirmata’s mission is to make Kubernetes secure and easy to use by addressing the critical needs of DevOps teams. 6 | 7 | Kyverno was created by Nirmata in 2019 and donated to [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/) as a Sandbox project in November 2020. Kyverno provides the ability to secure and automate Kubernetes, using policies written as native Kubernetes resources with no new language to learn. Kyverno policies can validate, mutate, and generate Kubernetes configurations. It has seen rapid adoption from the CNCF community and in July 2022 graduated to CNCF Incubating status. CNCF [graduated and incubating projects](https://www.cncf.io/projects/) are considered stable and used successfully in production. 8 | 9 | “Software is transforming the world, and open-source is transforming how software is built and consumed”, says Jim Bugwadia, co-founder and CEO at Nirmata. “Cloud computing is powered by open-source tools like Kubernetes and it's important for us to contribute to and drive the future of these pivotal technologies.” 10 | 11 | ## Why is Kyverno open-sourced? 12 | 13 | Kyverno 14 | 15 | When asked why Kyverno was open-sourced, Jim replied, “Kubernetes is not secured by default, and over 80% of security incidents are caused by misconfigurations. Working with early adopters, Nirmata believes that native policies offer the best way to secure and automate Kubenetes, and hence should be available to all users. By growing Kubernetes usage and policy adoption, Nirmata and ecosystem vendors can offer value-added commercial capabilities to organizations that need features for collaboration and integrations. 16 | 17 | 18 | Nirmata open-sourced Kyverno and donated it to the CNCF so that it is freely available to the entire Kubernetes community and ecosystem. This allows end users the peace of mind to pick a CNCF backed project that has a large and fast-growing community and is not a single vendor-led project.” 19 | 20 | ## Nirmata’s contributions to Open-Source 21 | 22 | As mentioned, In November 2020 Nirmata donated Kyverno to the Cloud Native Computing Foundation (CNCF). This means that Nirmata no longer owns the Kyverno project or its trademarks and that Kyverno is now owned and backed by the CNCF which is a part of the Linux Foundation. 23 | 24 | This helps mitigate the risk of using a single vendor controlled OSS project in production for users and also allows other vendors to freely build their own commercial or open source solutions on Kyverno. 25 | 26 | In addition to making their main product open-source under the CNCF umbrella, Nirmata has a full team of developers who develop and mantain the Kyverno project along with contributors from the CNCF ecosystem and end user community. You can meet the Kyverno team (virtually) in any of their regular [community meetings](https://kyverno.io/community/#community-meetings) where contributors and end users discuss upcoming features and issues. All maintainers and several end-users are also available via the [Kyverno slack channel](https://kyverno.io/community/#slack-channel). 27 | 28 | In 2022, Nirmata was also a gold sponsor of several [DevOpsDays](https://devopsdays.org/) events, which openly advocates and provides a stage for Open-Source related talks, and the Nirmata team actively contributes to other OSS communities within the Linux Foundation via presentations and project deliverables in the OSS realm. 29 | --------------------------------------------------------------------------------