This session will provide an introduction to The Apache Software Foundation – it’s history, organization and principles, and how Apache projects work. You will learn about The Apache Way of managing meritocracy-based and community driven projects as is practiced by all of the 100+ Apache projects, the levels of participation in Apache projects, and how you can get involved. This talk will also touch on the how the Apache governance process and the permissive Apache 2.0 license help ensure longer-lived open source projects, and provide a different opportunity for engagement than some other source communities and license models.
Shane Curcuru was elected as a Member of the ASF in 2002, and has been volunteering on public relations, conferences, brand management, and various other areas at Apache ever since. He also serves as a Director.
Improving Your Apache Project's Image And BrandShane Curcuru
Want to find new ways to draw in contributors to your project? Looking to attract ideas and attention from some of the corporate vendors, but don't want to lose your independence? Don't know how to approach your employer's plans to launch BigCo's SuperLucene product?
Learn how to improve your project's brand, drawing in newcomers as productive contributors, and defending your brand from aggressive vendors. Dealing fairly and firmly with companies mis-using your good reputation seems hard, but it doesn't need to be.
Learn about what uses of Apache brands that are OK, versus infringing uses hungry vendors try to use - and how to stop them. The strong independent reputation of your project and Apache overall relies on every PMC policing their own brand effectively and fairly. The Trademarks Committee is here to help!
Practical Trademark Law for FOSS ProjectsShane Curcuru
Looking for ways to capitalize on the emerging FOSS brands that are driving innovation? Want to “make a new open source community” for your product, but not sure how to control the trademarks? Wondering if you should let the marketing team run with the great new brand campaign, or if you need to ask the lawyers about trademarks first?
Successfully Profiting From Apache BrandsShane Curcuru
Does your company want to capitalize on Apache project brand? Are you interested in seeing how closely you can tie your marketing into the latest Apache projects, and gain a competitive advantage? Do you recognize the importance of supporting the Apache ecosystem, not just with code contributions but other actions?
As VP of Brand Management for all Apache projects, I'll help show you how your company can successfully profit and "partner" with Apache projects. Apache is happy for you to make a profit off of our software in all sorts of ways - as long as you give credit to our volunteer-led and independent project communities. You may even incorporate Apache brands within your brands, but in specific ways that still give our communities credit. And if you're interested in having more influence over the technology, we have tips for how to contribute to Apache projects in all sorts of ways. We're here to help!
How To Keep Your Apache Project's IndependenceShane Curcuru
How Apache open source projects can improve their reputation and longevity by attracting new contributors and by better managing their own brand and trademarks.
Profiting From Apache Brands Without Losing Your SoulShane Curcuru
Does your company want to capitalize on the Apache brand? Are you interested in seeing how closely you can tie your marketing into the latest Apache projects? Do you recognize the importance of supporting the Apache ecosystem, not just with code contributions but other actions?
As VP of Brand Management for all Apache projects, Shane can help show business and technical leaders some of the ways they can respectfully and successfully market and position their own services and products in relation to Apache project brands. The key message is: Apache project governance is independent; but we are happy to have businesses build their software and services on any Apache software products. You may incorporate Apache brands within your brands, but in specific ways that still give our communities credit. We're here to help!
Presentation licensed under the Apache License v2.0 allowing broad re-use!
In the modern open source world, where licenses and DVCS’ allow instant and infinite forking, the only true control point for a community-based open source project is its name, its logo, and its identity. Your brand is your identity: this is how the rest of the world sees you and your project.
How can a volunteer-led open source project control it’s own identity and brand? How do you manage your project’s brand when most of your volunteers are coders who don’t want to get involved with lawyers or deal with enforcing trademarks? How can the community keep their brand independent and free of commercial influence, so they can ensure the maximum number of people and corporations are interested in participating in their project?
Similarly, how can businesses respectfully use open source brands to their own advantage – without being seen as co-opting and independent or open community open source project solely for their own gain? The desire to control the next hot project for your profit may quickly turn on you when another company simply forks the code under a better marketed service.
Learn the basics of all these topics and more with Shane Curcuru, who volunteers as Vice President, Brand Management for The Apache Software Foundation. Over the past few years Shane has led a group of volunteer ASF Members to define and implement a consistent brand policy for all 100 Apache projects – spanning from the veritable HTTPD and Tomcat to the newest CouchDB and Hadoop.
State of the Feather - Apache:Big Data - BudapestShane Curcuru
An update on the Apache Software Foundation and an overview of its projects. A quick look at how the ASF works and the key events affecting the foundation in recent history.
Improving Your Apache Project's Image And BrandShane Curcuru
Want to find new ways to draw in contributors to your project? Looking to attract ideas and attention from some of the corporate vendors, but don't want to lose your independence? Don't know how to approach your employer's plans to launch BigCo's SuperLucene product?
Learn how to improve your project's brand, drawing in newcomers as productive contributors, and defending your brand from aggressive vendors. Dealing fairly and firmly with companies mis-using your good reputation seems hard, but it doesn't need to be.
Learn about what uses of Apache brands that are OK, versus infringing uses hungry vendors try to use - and how to stop them. The strong independent reputation of your project and Apache overall relies on every PMC policing their own brand effectively and fairly. The Trademarks Committee is here to help!
Practical Trademark Law for FOSS ProjectsShane Curcuru
Looking for ways to capitalize on the emerging FOSS brands that are driving innovation? Want to “make a new open source community” for your product, but not sure how to control the trademarks? Wondering if you should let the marketing team run with the great new brand campaign, or if you need to ask the lawyers about trademarks first?
Successfully Profiting From Apache BrandsShane Curcuru
Does your company want to capitalize on Apache project brand? Are you interested in seeing how closely you can tie your marketing into the latest Apache projects, and gain a competitive advantage? Do you recognize the importance of supporting the Apache ecosystem, not just with code contributions but other actions?
As VP of Brand Management for all Apache projects, I'll help show you how your company can successfully profit and "partner" with Apache projects. Apache is happy for you to make a profit off of our software in all sorts of ways - as long as you give credit to our volunteer-led and independent project communities. You may even incorporate Apache brands within your brands, but in specific ways that still give our communities credit. And if you're interested in having more influence over the technology, we have tips for how to contribute to Apache projects in all sorts of ways. We're here to help!
How To Keep Your Apache Project's IndependenceShane Curcuru
How Apache open source projects can improve their reputation and longevity by attracting new contributors and by better managing their own brand and trademarks.
Profiting From Apache Brands Without Losing Your SoulShane Curcuru
Does your company want to capitalize on the Apache brand? Are you interested in seeing how closely you can tie your marketing into the latest Apache projects? Do you recognize the importance of supporting the Apache ecosystem, not just with code contributions but other actions?
As VP of Brand Management for all Apache projects, Shane can help show business and technical leaders some of the ways they can respectfully and successfully market and position their own services and products in relation to Apache project brands. The key message is: Apache project governance is independent; but we are happy to have businesses build their software and services on any Apache software products. You may incorporate Apache brands within your brands, but in specific ways that still give our communities credit. We're here to help!
Presentation licensed under the Apache License v2.0 allowing broad re-use!
In the modern open source world, where licenses and DVCS’ allow instant and infinite forking, the only true control point for a community-based open source project is its name, its logo, and its identity. Your brand is your identity: this is how the rest of the world sees you and your project.
How can a volunteer-led open source project control it’s own identity and brand? How do you manage your project’s brand when most of your volunteers are coders who don’t want to get involved with lawyers or deal with enforcing trademarks? How can the community keep their brand independent and free of commercial influence, so they can ensure the maximum number of people and corporations are interested in participating in their project?
Similarly, how can businesses respectfully use open source brands to their own advantage – without being seen as co-opting and independent or open community open source project solely for their own gain? The desire to control the next hot project for your profit may quickly turn on you when another company simply forks the code under a better marketed service.
Learn the basics of all these topics and more with Shane Curcuru, who volunteers as Vice President, Brand Management for The Apache Software Foundation. Over the past few years Shane has led a group of volunteer ASF Members to define and implement a consistent brand policy for all 100 Apache projects – spanning from the veritable HTTPD and Tomcat to the newest CouchDB and Hadoop.
State of the Feather - Apache:Big Data - BudapestShane Curcuru
An update on the Apache Software Foundation and an overview of its projects. A quick look at how the ASF works and the key events affecting the foundation in recent history.
Embracing InnerSource for your adaptive Digital TransformationPiergiorgio Lucidi
During this session you'll be able to discover how InnerSource will bring a disruptive cultural change for approaching Digital Transformation. Everything will be shared in a smart way to be faster on any change, the meritocracy approach will reward people involved and attract new talents. Finally prepare an action plan with your team for any improvement of your architecture adding new technology bricks when the business needs.
The Apache Way - Dataworks Summit 2017Brett Porter
The Apache Way is a phrase used to describe the style of community-led development that characterises projects at the ASF. This talk covers how the ASF is structured to support that, how we apply The Apache Way, and why that has led to such successful projects.
The Journey of Apache ManifoldCF: Learning from ASF's SuccessesPiergiorgio Lucidi
Every ASF project has a story to tell and behind a story we find people contributing with a real love in technologies.
They share the Open Source philosophy and this honest commitment in terms of personal effort for achieving any kind of improvement for the project means that there are individual contributors following a common light: The Apache Way.
Piergiorgio will describe the path taken by the Apache ManifoldCF Community for getting these results, starting from the incubation process to the promotion as Top Level Project and then engaging new contributors.
Finally Piergiorgio explains how the Community can help with a huge benefit also in the strategic view for a project.
Each contributor shares his own specific expertise on the field and his technological sensibility will bring added value until to drastically improve the scope of the entire project. Listen to the Community!
In the modern open source world, where licenses and DVCS’ allow instant and infinite forking, the only true control point for a community-based open source project is its name, its logo, and its identity. Your brand is your identity: this is how the rest of the world sees you and your project. Your brand is most of what your users see, and is a key way to attract new contributors.
How can a volunteer-led open source project control it’s own identity and brand? How do you manage your project’s brand when most of your volunteers are coders who don’t want to get involved with lawyers or deal with enforcing trademarks? How can the community keep their brand independent and free of commercial influence, so they can ensure the maximum number of people and corporations are interested in participating in their project?
Similarly, how can businesses respectfully use open source brands to their own advantage – without being seen as co-opting an independent or open community open source project solely for their own gain? The desire to control the next hot project for your company's profit may quickly turn on you when another company simply forks the code under a better marketed service.
Learn the basics of all these topics and more with Shane Curcuru, who volunteers as Vice President, Brand Management for The Apache Software Foundation. Over the past few years Shane has led a group of volunteer ASF Members to define and implement a consistent brand policy for all 100+ Apache projects – spanning from the veritable HTTPD and Tomcat to the newest CouchDB and Hadoop.
Including Everyone: Web Accessibility 101Helena Zubkow
Shouldn’t the web be awesome for everyone? That's not always the case, but it could be.
Designed for developers, project managers, and directors alike, the goal of this session is to introduce everyone to the wonderful world of web accessibility. We'll cover the basic standards and regional expectations for accessibility, as well as the principles and concepts that make up the accessibility field. This session will touch on Section 508, WCAG 2.0 standards, and the financial viability of a web accessibility initiative in an industry where time is money.
This session is proposed as a conceptual prelude to our more developer-oriented accessibility session that is taking place at the Higher Ed Summit. Based on my experience as a web accessibility specialist from both the perspective of a project manager and a front-end developer, I'll share the knowledge I've gained with you to address the following important questions:
- What is web accessibility?
- Why does web accessibility matter to my users?
- Why does web accessibility matter for my company and clients?
- How will a web accessibility initiative affect my bottom line?
- How can I include web accessibility in my company's culture and work plans?
- What tools can I use to assess and improve accessibility in my projects?
- How can I help the web accessibility community?
Understanding and Supporting Web AccessibilityRachel Cherry
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is accessible, all users can access your content and functionality no matter their abilities. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device. Most accessibility features will also improve your SEO.
When your site is inaccessible, research shows you could be excluding up to 20 percent of your users.
This talk will cover the basics of accessibility, why it’s important, and how you can support accessibility in your projects.
My slides on the Open University project to develop an accessible, easily embeddable, maintainable multimedia player for student and public facing OU sites. Presentation to the a11yLDN conference, London, 19 September 2012.
http://a11yldn.org.uk
The "Apache Way" is the process by which Apache Software Foundation projects are managed. It has evolved over many years and has produced over 100 highly successful open source projects. But what is it and how does it work?
In this session Ross Gardler will describe how an Apache project is managed. He will describe how the foundation provides an technical and legal infrastructure for each project and how the Apache Way provides the governance scaffolding for individual projects. This provides the framework for Apache projects which are then free to apply the Apache Way to ensure their project succeeds.
Having attended this session you will have a better understanding of the inner workings of both the foundation and its projects. With this understanding you will be better equipped to engage with and benefit from Apache projects.
Throw out best practices, double email conversion (15 minute version)A. Litsa
Watch on YouTube: http://www.youtube.com/watch?v=YdFDAjieEpw
We figured out how to increase email-campaign conversion by 146%!
Last summer my team studied post-transaction email with the goal to influence more shoppers to review recent purchases. After much trial and error and one major pivot, we learned something key to conversion: email is a mobile thing.
This eureka moment motivated the team to explore the relationship between smartphones, email campaigns, and website traffic. In this session you will
• Get compelling statistical evidence of the strong relationship between email and mobile
• Hear the story of our trial and error, and what lead to a major pivot in the study
• Learn why and how you can double email campaign conversion too
• Discover the potential impact of mobile device usage in a least two other major marketing channels
• Find out what critical oversight web-analysts make when measuring mobile traffic
Enjoy! And please tweet feedback to @a_litsa
Embracing InnerSource for your adaptive Digital TransformationPiergiorgio Lucidi
During this session you'll be able to discover how InnerSource will bring a disruptive cultural change for approaching Digital Transformation. Everything will be shared in a smart way to be faster on any change, the meritocracy approach will reward people involved and attract new talents. Finally prepare an action plan with your team for any improvement of your architecture adding new technology bricks when the business needs.
The Apache Way - Dataworks Summit 2017Brett Porter
The Apache Way is a phrase used to describe the style of community-led development that characterises projects at the ASF. This talk covers how the ASF is structured to support that, how we apply The Apache Way, and why that has led to such successful projects.
The Journey of Apache ManifoldCF: Learning from ASF's SuccessesPiergiorgio Lucidi
Every ASF project has a story to tell and behind a story we find people contributing with a real love in technologies.
They share the Open Source philosophy and this honest commitment in terms of personal effort for achieving any kind of improvement for the project means that there are individual contributors following a common light: The Apache Way.
Piergiorgio will describe the path taken by the Apache ManifoldCF Community for getting these results, starting from the incubation process to the promotion as Top Level Project and then engaging new contributors.
Finally Piergiorgio explains how the Community can help with a huge benefit also in the strategic view for a project.
Each contributor shares his own specific expertise on the field and his technological sensibility will bring added value until to drastically improve the scope of the entire project. Listen to the Community!
In the modern open source world, where licenses and DVCS’ allow instant and infinite forking, the only true control point for a community-based open source project is its name, its logo, and its identity. Your brand is your identity: this is how the rest of the world sees you and your project. Your brand is most of what your users see, and is a key way to attract new contributors.
How can a volunteer-led open source project control it’s own identity and brand? How do you manage your project’s brand when most of your volunteers are coders who don’t want to get involved with lawyers or deal with enforcing trademarks? How can the community keep their brand independent and free of commercial influence, so they can ensure the maximum number of people and corporations are interested in participating in their project?
Similarly, how can businesses respectfully use open source brands to their own advantage – without being seen as co-opting an independent or open community open source project solely for their own gain? The desire to control the next hot project for your company's profit may quickly turn on you when another company simply forks the code under a better marketed service.
Learn the basics of all these topics and more with Shane Curcuru, who volunteers as Vice President, Brand Management for The Apache Software Foundation. Over the past few years Shane has led a group of volunteer ASF Members to define and implement a consistent brand policy for all 100+ Apache projects – spanning from the veritable HTTPD and Tomcat to the newest CouchDB and Hadoop.
Including Everyone: Web Accessibility 101Helena Zubkow
Shouldn’t the web be awesome for everyone? That's not always the case, but it could be.
Designed for developers, project managers, and directors alike, the goal of this session is to introduce everyone to the wonderful world of web accessibility. We'll cover the basic standards and regional expectations for accessibility, as well as the principles and concepts that make up the accessibility field. This session will touch on Section 508, WCAG 2.0 standards, and the financial viability of a web accessibility initiative in an industry where time is money.
This session is proposed as a conceptual prelude to our more developer-oriented accessibility session that is taking place at the Higher Ed Summit. Based on my experience as a web accessibility specialist from both the perspective of a project manager and a front-end developer, I'll share the knowledge I've gained with you to address the following important questions:
- What is web accessibility?
- Why does web accessibility matter to my users?
- Why does web accessibility matter for my company and clients?
- How will a web accessibility initiative affect my bottom line?
- How can I include web accessibility in my company's culture and work plans?
- What tools can I use to assess and improve accessibility in my projects?
- How can I help the web accessibility community?
Understanding and Supporting Web AccessibilityRachel Cherry
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is accessible, all users can access your content and functionality no matter their abilities. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device. Most accessibility features will also improve your SEO.
When your site is inaccessible, research shows you could be excluding up to 20 percent of your users.
This talk will cover the basics of accessibility, why it’s important, and how you can support accessibility in your projects.
My slides on the Open University project to develop an accessible, easily embeddable, maintainable multimedia player for student and public facing OU sites. Presentation to the a11yLDN conference, London, 19 September 2012.
http://a11yldn.org.uk
The "Apache Way" is the process by which Apache Software Foundation projects are managed. It has evolved over many years and has produced over 100 highly successful open source projects. But what is it and how does it work?
In this session Ross Gardler will describe how an Apache project is managed. He will describe how the foundation provides an technical and legal infrastructure for each project and how the Apache Way provides the governance scaffolding for individual projects. This provides the framework for Apache projects which are then free to apply the Apache Way to ensure their project succeeds.
Having attended this session you will have a better understanding of the inner workings of both the foundation and its projects. With this understanding you will be better equipped to engage with and benefit from Apache projects.
Throw out best practices, double email conversion (15 minute version)A. Litsa
Watch on YouTube: http://www.youtube.com/watch?v=YdFDAjieEpw
We figured out how to increase email-campaign conversion by 146%!
Last summer my team studied post-transaction email with the goal to influence more shoppers to review recent purchases. After much trial and error and one major pivot, we learned something key to conversion: email is a mobile thing.
This eureka moment motivated the team to explore the relationship between smartphones, email campaigns, and website traffic. In this session you will
• Get compelling statistical evidence of the strong relationship between email and mobile
• Hear the story of our trial and error, and what lead to a major pivot in the study
• Learn why and how you can double email campaign conversion too
• Discover the potential impact of mobile device usage in a least two other major marketing channels
• Find out what critical oversight web-analysts make when measuring mobile traffic
Enjoy! And please tweet feedback to @a_litsa
Dokumentenerzeugung als zentraler Bestandteil der Kundenkommunikation ist heutzutage jedoch noch immer häufig ein manueller und damit sehr fehleranfälliger Prozess. Ein zentrales Dokumentengenerierungssystem bietet Ihnen viele Vorteile. Flexibilität sowie ein hoher Automatisierungsgrad helfen Ihnen dabei, kosteneffizient eine fehlerfreie Kundenkommunikation aufzubauen.
Datamatics’ Document System Solution (DSS) ist ein sehr flexibles Produkt für die Erzeugung von Dokumenten, mit dem sowohl die Massendokumentgenerierung als auch die Erstellung einzelner Ad-hoc-Dokumente innerhalb nur eines Systems möglich sind. Der Geschäftsprozess umfasst die gesamte Dokumentengenerierung vom Zugriff auf die Quelldaten über Dokumentformatierung, Generierung der Ausgabeformate bis hin zur Verteilung auf die verschiedenen Ausgabekanäle und die Archivierung.
The Hop project entered Apache Software Foundation as an Incubator project in 2020, and Julian Hyde, one of their mentors, gave this presentation to educate the initial committers on the Apache Way and what to expect during the Incubation process.
The talk was given by Julian Hyde on October 1st, 2020, with the original title "Apache Incubation - What's it all about?"
The Apache Way: A Proven Way Toward SuccessEvans Ye
With innumerous successful Apache projects that dominate the big data world, the working model of Apache communities clearly deserved a study. In this talk, I'll walk you through how Apache communities and the Apache Software Foundation work generally. The whole thing behinds it is so called "The Apache Way".
For audience whose an engineer, I'll share with you why you should be part of the Apache family, how to do it, and what you can get from it. Moreover, I'll cover this with some actionable tips, and closing up with some career advices. For those being managers or at CXO level, I'll talk about some aspects on building engineering culture which can alternately pace your team and business toward success.
"Open Source and the Choice to Cooperate" by Brian Behlendorf @ eLiberatica 2007eLiberatica
This is a presentation held at eLiberatica 2007.
http://www.eliberatica.ro/2007/
One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.
The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.
Software management plans in research softwareShoaib Sufi
Slides from the 14th August 2019 webinar presentation as part of the Best Practices for HPC Software Developers (Webinar) series - https://ideas-productivity.org/events/hpc-best-practices-webinars/ - more info at https://www.exascaleproject.org/event/smp-rp/ and a recording on YouTube is at - https://www.youtube.com/watch?v=7sELeZStzdY&feature=youtu.be
Abstract:
Software is a necessary by-product of research. Software in this context can range from small shell scripts to complex and layered software ecosystems. Dealing with software as a first class citizen at the time of grant formulation is aided by the development of a Software Management Plan (SMP). An SMP can help to formalize a set of structures and goals that ensure your software is accessible and reusable in the short, medium and long term. SMP’s aim at becoming for software what Data Management Plans (DMP’s) have become for research data (DMP’s are mandatory for National Science Foundation grants). This webinar takes you through the questions you should consider when developing a Software Management Plan, how to manage the implementation of the plan, and some of the current motivation driving discussion in this area of research management.
4. Apache RocketMQ 5.0, embracing the Distributed Messaging Standard OpenMes...振东 刘
vongosling(RocketMQ Core-creator, Committer/PMC member)'s topic mainly focused on the understanding of Apache way, development of RocketMQ Community, RocketMQ 5.0 and OpenMessaging.
At the heart of much of the Bigdata revolution is the Apache Software Foundation. Many of the projects, including the big ones like Hadoop, Spark, Hive, and Kafka, are Apache projects. This means they follow "The Apache Way". Maybe you have heard phrases like "community over code" or "if it didn't happen on the lists, it didn't happen" and wondered what they meant. Maybe you would like to get involved with one or more of these projects but have not been sure how. Maybe you would just like to learn how Apache works, and how its process differs from the way companies build software. If so, this talk is for you. This talk will introduce Apache, how it is organized, the roles people play, who can contribute (hint, it is not just coders), Apache's tenants of community, meritocracy, collaboration, and openness, give some practical tips for new contributors and even old hands, as well as touch briefly on licenses and trademarks.
Supporting Apache Brands While Making A Profit - ApacheCon 2014Shane Curcuru
Does your company want to capitalize on the Apache brand? Are you interested in seeing how closely you can tie your marketing into the latest Apache projects? Do you recognize the importance of supporting the Apache ecosystem, not just with code contributions but other actions?
As VP of Brand Management for all Apache projects, I can help show business and technical leaders some of the ways they can respectfully and successfully market and position their own services in relation to Apache project brands. The key message is: Apache project governance is independent; but we are happy to have businesses build their software and services on any Apache software products.
Licensed under the Apache License 2.0
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Welocme to ViralQR, your best QR code generator.ViralQR
Welcome to ViralQR, your best QR code generator available on the market!
At ViralQR, we design static and dynamic QR codes. Our mission is to make business operations easier and customer engagement more powerful through the use of QR technology. Be it a small-scale business or a huge enterprise, our easy-to-use platform provides multiple choices that can be tailored according to your company's branding and marketing strategies.
Our Vision
We are here to make the process of creating QR codes easy and smooth, thus enhancing customer interaction and making business more fluid. We very strongly believe in the ability of QR codes to change the world for businesses in their interaction with customers and are set on making that technology accessible and usable far and wide.
Our Achievements
Ever since its inception, we have successfully served many clients by offering QR codes in their marketing, service delivery, and collection of feedback across various industries. Our platform has been recognized for its ease of use and amazing features, which helped a business to make QR codes.
Our Services
At ViralQR, here is a comprehensive suite of services that caters to your very needs:
Static QR Codes: Create free static QR codes. These QR codes are able to store significant information such as URLs, vCards, plain text, emails and SMS, Wi-Fi credentials, and Bitcoin addresses.
Dynamic QR codes: These also have all the advanced features but are subscription-based. They can directly link to PDF files, images, micro-landing pages, social accounts, review forms, business pages, and applications. In addition, they can be branded with CTAs, frames, patterns, colors, and logos to enhance your branding.
Pricing and Packages
Additionally, there is a 14-day free offer to ViralQR, which is an exceptional opportunity for new users to take a feel of this platform. One can easily subscribe from there and experience the full dynamic of using QR codes. The subscription plans are not only meant for business; they are priced very flexibly so that literally every business could afford to benefit from our service.
Why choose us?
ViralQR will provide services for marketing, advertising, catering, retail, and the like. The QR codes can be posted on fliers, packaging, merchandise, and banners, as well as to substitute for cash and cards in a restaurant or coffee shop. With QR codes integrated into your business, improve customer engagement and streamline operations.
Comprehensive Analytics
Subscribers of ViralQR receive detailed analytics and tracking tools in light of having a view of the core values of QR code performance. Our analytics dashboard shows aggregate views and unique views, as well as detailed information about each impression, including time, device, browser, and estimated location by city and country.
So, thank you for choosing ViralQR; we have an offer of nothing but the best in terms of QR code services to meet business diversity!
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Essentials of Automations: Optimizing FME Workflows with Parameters
The Apache Way
1. About: Apache
The Foundation,
The Apache Way,
100+ Apache Projects
Shane Curcuru | @shanecurcuru
Vice President, Brand Management
The Apache Software Foundation
http://communityovercode.com/2012/05/camelone-presentation/
2. Agenda
● Who am I: Introduction
● What is it: Apache Software Foundation
● How does it work: The Apache Way
● Who does the work: Apache projects
● Why Apache?
– Compare / Contrast open source groups
3. Who am I: Introduction
● Shane Curcuru
● Apache Software Foundation
– Member, Director
– VP, Brand Management
– PMCs: Community Development, Conferences;
Apache OpenOffice Mentor
Also an Applications Architect at IBM
4. What Is It?
● Who am I: Introduction
● What is it: Apache Software Foundation
● How does it work: The Apache Way
● Who does the work: Apache projects
● Why Apache?
– Compare / Contrast open source groups
5. What is it: The ASF
● Membership-based corporation; Non-profit US
501(c)3 Charity
● Directors, officers all unpaid volunteers
● Paid contractors: sysadmins, press officer, EA
● Broad-based Membership of individuals
ensures independence
➔ Collection of Apache project communities
6. Apache Org Chart
Nominate, elect
Members
Directors annually Organizational
~400 Oversight
Technical
Board of Oversight
Nominate, elect 9 Directors
new members
Create &
update upon
Appoint officers PMC request
Report monthly Report quarterly
PMCs
Officers 100++
~10
Define organizational &
legal policies Committers Nominate, elect Vote for
new committers project releases
~3,000
Write project code
7. Apache Board of Directors
● Elected by ASF Membership annually
● Long-time directors: Jim Jagielski, Greg Stein,
Roy Fielding, Sam Ruby
● Newer directors: Bertrand Delacretaz, Doug
Cutting, Shane Curcuru, Brett Porter, Dan Kulp
● Provide legal and organizational oversight
9. Apache Mission: What
● Provide open source software to the public free
of charge
– “Apache aims to provide a pragmatic, non-technical
framework to it's projects.”
- Justin Erenkrantz
● Let coders code; Foundation exists to do rest
10. Apache Mission: How
● Provide legal, organizational, and technical
infrastructure for open source software
development, and perform oversight to ensure
project independence
● Provide shelter for individual volunteers from
legal suits directed at Apache projects
● Provide a legal entity to serve as an
independent recipient of donations
11. Budget and Sponsorship
● Annual budget: est. 790K USD in 2012
● Sponsorship program ensures independence
● Primary budget categories: sysadmin
contractors; hardware & bandwidth; publicity
● Apache does not pay for software development
12. Apache Sponsors
● Platinum: Citrix, Facebook, Google, Microsoft,
Yahoo!
● Gold: AMD, Hortonworks, HP, IBM
● Silver: Basis Technology, Cloudera, Go Daddy, Huawei, Matt
Mullenweg, PSW Group, SpringSource
● Bronze: AirPlus Intl., BlueNog, Digital Primates, FuseSource, Intuit, Liip AG
SA Ltd., Lucid Imagination, Talend, Twitter, Two Sigma Investments,
WANdisco
● Separately: Long-term hosting & bandwidth providers
13. Apache License
● Apache projects use the Apache License 2.0
● Pragmatic and permissive
– Maximum freedom for users
● Requires attribution “Give me credit”
● Includes patent grant
● Easily and frequently used by other groups
14. Contributor License Agreements
● AKA “ICLA” for Individuals – 4649 signed
– ICLA required to become committer
● CCLA for Corporations – 318 signed
● Ensures that contributors have the right to
contribute, and that ASF has right to license to
the public under Apache license
● No copyright assignments – only a license
15. How does it work?
● Who am I: Introduction
● What is it: Apache Software Foundation
● How does it work: The Apache Way
● Who does the work: Apache projects
● Why Apache?
– Compare / Contrast open source groups
16. The Apache Way
● Meritocracy – those who do, decide
● Peer-based – participate as individuals
● Oversight – responsible and independent
● Decisions – made by consensus
● Collaboration – public and asynchronous
● Participation – by individuals
17. Apache Way: Merit
● Merit is based on actual accomplishments
within a project
● Existing community measures value
● Merit never expires
● Merit is not transferable
19. Apache Way: Oversight
● PMCs provide technical oversight of all project
releases, new committers/PMC members
– Ensure clean IP in all Apache releases
● Board provides organizational oversight of all
Apache projects
– Ensure PMCs function independently
20. Apache Way: Decisions
● Decisions made by consensus, discussion
– If consensus is not obvious, then vote
● Votes are by +1 / +-0 / -1
● All -1 or veto votes must have a reason
– Releases may not be vetoed
● PMCs vote on all releases
– Committers vote on code changes
21. Apache Way: Collaboration
● “If it didn't happen on the mailing list, it didn't
happen.” - Roy Fielding
● Any discussions F2F, IRC, wherever must be
reported back to mailing list
● All decisions must be made on-list, and with a
72+ hour window for voting/discussion
● Lists are asynchronous and publicly archived
●
22. Apache Way: Participation
● Committers participate as individuals
– Expected to wear appropriate “hat”
● Releases must have three +1 votes
– Ensures multiple and independent eyes
● Corporations are never made committers,
members, nor PMC members
23. Who does the work?
● Who am I: Introduction
● What is it: Apache Software Foundation
● How does it work: The Apache Way
● Who does the work: Apache projects
● Why Apache?
– Compare / Contrast open source groups
24. Apache Projects
● Over 100 code-producing community driven
projects
– 50+ Podlings in Incubation
● “Apache Projects include millions of lines of code overseen
by an all-volunteer community across six continents.
Apache technologies power more than half the Internet,
petabytes of data, teraflops of operations, billions of
objects, and enhance the lives of countless users and
developers.”
25. Apache Projects: Incubator
● New project proposals are made to the Apache
Incubator PMC
– PMC votes to accept on community merits
● Incubation process ensures podling community
understands Apache Way
– No technical direction required by incubation
● PMC votes to graduate podlings to TLPs
(Top Level Projects)
26. Apache Projects: Attic
● Projects that cannot reliably report and/or find
three +1 PMC votes to create releases
● When community lacks participation or diversity
– not for technical reasons
● Board votes to “box up” the project and place in
the Attic
● All resources are read-only for posterity
27. Apache Projects: Technology
● Apache projects provide leading technology:
– Webservers, Java tools & stacks, search, cloud, big
data, build tools, CMS/web framework, databases,
OSGi containers, graphics, foobles...
– And end user Office suites!
● “Competing” project technology is OK
– If an active community f ollowing t he Apache Way
want s t o j oin, great !
28. Apache Projects: Development
● Apache never pays for development
● Some committers/PMC members are corporate
sponsored; some are not
– Consultants, authors, students, researchers
● Each Apache project is an independent
community of committers and users
29. Apache Projects
● Diverse communities provide independence
● Planning activities happen on-list
● “Powerplant” checkins are counter-productive
30. Apache Projects: Join Now!
● To join a project, subscribe to the mailing list
● All productive input is appreciated
● PMC members nominate and vote new
committers periodically
● Every project has different expectations
● Many ways to contribute: patches, bugs,
documentation, training, graphics,...
31. Don't Feed The Trolls
● All-inclusive public discussions and archives
sometimes bring out the worst in people
– Don't let them derail community
● “How Open Source Projects Survive Poisonous
People (And You Can Too)”
– Ben Collins-Sussman & Brian Fitzpatrick
http://s.apache.org/DontFeedTheTrolls
32. Why Apache?
● Who am I: Introduction
● What is it: Apache Software Foundation
● How does it work: The Apache Way
● Who does the work: Apache projects
● Why Apache?
– Compare / Contrast open source groups
33. Apache and Eclipse
Apache: Eclipse:
● Multiple projects ● Multiple projects
● Permissive license ● Semi-copyleft license
● Individual members ● Corporate backing
● Free to participate ● Membership dues
One key difference:
Eclipse governance & board includes Strategic
Developers & Consumers – corporations.
34. Apache and Outercurve
Apache: Outercurve/CodePlex:
● Multiple projects ● Multiple projects
● Permissive license ● Various licenses
● Individual members ● Corporate backing
● Board oversight ● Individual governance
One key difference:
Microsoft backing, and each project provides own
style and set of governance.
35. Apache and Python
Apache: Python:
● Multiple projects ● Single project
● Permissive license ● Permissive license
● Individual members ● Individual members
● Independent board ● Guido as BDFL
One key difference:
Python focuses on just the programming language.
36. Apache and FSF / GNU
Apache: FSF / GNU:
● Multiple projects ● Multiple projects
● Permissive license ● Copyleft license
● License contribution ● Holds copyright
● Individual members ● Corporate staff
One key difference:
FSF advocates software freedom as ideology.
37. Apache and Mozilla
Apache: Mozilla:
● Multiple projects ● Multiple projects
● Permissive license ● Semi-copyleft license
● Individual members ● Corporate staff
● No specific technical ● End user project
focus focus
One key difference:
Mozilla's end user focus means different level of
marketing, trademark, and release management.
38. Apache Similarities
● What's similar about these groups?
● Most explicitly adopted parts of Apache Way
● Voting; consensus & community; merit
● Independent foundations
● Several have explicitly noted the copying of
their ways from Apache
39. Colophon
● Credits
– Past Apache Way slides by Jim Jagielski
– & Justin Erenkrantz
– Collective wisdom of the Apache Membership
● Apache OpenOffice 3.4 Impress
● Open Sans fonts
http://communityovercode.com/2012/05/camelone-presentation/
40. Thank You!
• Questions? @shanecurcuru
• Learn more about Apache:
http://community.apache.org/
41. Apache's Tagline
“We are more than a group of projects sharing a
server; we are a community of developers and
users... sharing a common Apache Way of
developing software.”
Editor's Notes
Put the item people are least familiar with, but which is really most important, first. While the Apache Projects provide all the code, it's the Foundation and the Apache Way that enable them to do that – independently, and for the long-term.
Note that currently 100% of my time on Apache work is as an unpaid volunteer; my IBM job is completely unrelated (both technically and organizationally).
The Apache Software Foundation, or ASF, is actually the most important, yet probably least interesting component here. But it's important to understand how the Foundation behind the projects ensures their longevity.
The most important thing to realize on this slide: while the Foundation provides a home for over 100 projects, each of those projects is really an independent community of developers and users.
Fundamentally, the organization is pretty simple. The Membership elects a Board of Nine Directors annually. The Board sets overall policy and provides oversight for all operations. Note especially that officers and PMCs report directly to the board. The President and VP, Infrastructure manage day-to-day operations – but only of the infrastrucutre itself, not of our projects. The most important thing to realize from this picture is (click) that everything to the left of the page only provides organizational oversight. All technical decisions are made on the right hand half – within the PMCs and projects individually.
Having both founding members – Jim and Roy – as well as a number of newer members – including Dan Kulp, who's also speaking here at CamelOne – ensures continuity and fresh ideas. The board provides organizational oversight through reviewing the monthly and quarterly reports from all foundation activities. This ensures that PMCs and officers are acting indepdnently on behalf of their projects. Note that “technical” is not something the board oversees or comments on (unless it's a security issue or the like).
So what is the purpose of the ASF? Fundamentally, that's it: provide software for the public good. But there's got to be more to the Foundation's mission, hasn't there?
It's really that simple. The Foundation's purpose is to serve as a stable and independent home for it's projects. The Foundation should only be there to handle the stuff coders don't want to do or aren't good at handling; everything else – and especially all technical decisions – are made by the coders in PMCs and projects.
These are the key services the Foundation provides to it's projects. Thinking of the ASF as a service provider to like-minded software development communities is a good metaphor.
Our annual budget has just about doubled in the past 4 years. Sponsors' annual donations from multiple sources ensures a steady stream of income, which helps to ensure indepdence from outside commercial influence. Along with system administrators to keep our dozens of servers running, expenses include publicity assistance that's available to our projects – including the press release today.
Thank you to our sponsors! Note that the majority of sponsors are recurring and strong supporters of our work, both financially and technically, in terms of their donations of code or their employee's engineering time to many Apache projects.
All Apache software should be useable under our license. This ensures maximum freedom for users. This also ensures that software released with our license is available to the public.
Apache ensures clean IP by ensuring that all contributions to our projects are properly licensed to us under the Apache License – and thus are properly licensed to you under the Apache license. Corporations are welcomed and encouraged to provide a CCLA, although it is not required. ICLAs are required for becoming a committer. Per policy, we do not accept modified ICLAs or CCLAs, or software grants. Note that Apache has never asked for copyright assignment, and doesn't particularly want It. All we need is contributions clearly under our license, so it's free to use – by us or by you.
That's what the Foundation as a corporation itself is. Here is the how – how we require our projects to operate, so that they can remain independent and long-lived communities providing free software.
Some of these are rules for Apache projects; many are best practices. These are all techniques that a community-driven project can maintain independence, and promote longevity for the project.
There is very little technical hierarchy in Apache projects. Merit defines what you can do within a project community. Truly, those who do the work get to decide. Note that each community measures merit – for example, the merit to become a committer – differently. Similarly, Merit is not transferable between individuals. Just because you're a committer doesn't mean your coworker – or boss – gets any merit within the project. Each individual needs to prove themselves publicly to the whole project community. Merit applies to the membership as well: new members are selected for the merit they've shown on multiple Apache projects, or on organizational goals.
This is a critical factor in maintaining independent and long-lived communities. People are expected to serve as individuals – not as representatives of their company. This doesn't mean you can't work on the code your company wants to add – but you do need to work within the project itself to get the code accepted. Diversity is the key to longevity. Having a useful technical project that has contributors from multiple employers means that even if your company happens to change business direction, there is still enough of a community to continue the project goals. And when we say all votes are equal, that's all. PMC chairs, Apache directors or members, whoever – all get one vote on projects they've earned merit on.
In terms of ensuring Apache projects may be freely used by all, PMCs have the most important role. PMCs are expected to ensure that all contributions to the project are properly licensed, and that all releases are tested and reviewed. PMCs are also expected to keep a diverse and healthy community; however in cases where PMC diversity or health have failed, the board is always reading their reports. In extreme cases – when a PMC cannot self-correct when it's issues are pointed out – the board will – and has – step in to make corrections. The board is a blunt instrument of last resort, but it does ensure independence from commercial influence for all Apache project communities.
For all the talk we have of voting – Google got the +1 from us, by the way – votes in healthy communites should be rare. Discussion and consensus is the best way to move a project forward. Since the projects have technical goals, this can often be a simpler discussion: does the new code/feature/change make the product better or not? Vetoes should be rare; when they are made they must have a specific and defensible technical reason. Every Apache release must be voted +1 by at least three PMC members. This ensures that the source code released is done as an act of the project of the Foundation, and not as individuals. Releases may not be vetoed; if at least three PMC members vote +1, then we might as well let the public use the code!
Collaboration must be public, open, archived, and timely. That is: timely, meaning plenty of time for a sufficient part of the community to have a chance to comment. These rules are not negotiable. While in some cases this may seem to slow the speed of progress, using lists and allowing time is critical to ensure the whole community can participate in decisions. 72 hours is the minimum, it's often good to wait longer if there is a discussion ongoing.
Again, these guidelines ensure independence in our project governance and releases. “Hats” is a concept where people should explicitly state who they are representing at any particular time. PMC members should cast votes based on the merits within a project – while they may separately advocate for new ideas at the behest of their employer. It should be obvious to list readers who you are speaking on behalf of. Corporations or organizations are never given votes, made committers, members, or other positions at the ASF or at Apache projects. This ensures that all governance is by individuals – many of whom may be employed by various companies – but who also keep their Apache roles through job changes.
For those wondering “but where's the code”, you're right – the Foundation itself doesn't really do much interesting to the outside world, other than providing a stable home. It's the Apache projects that do the work!
This is a great quote from today's press release by the ASF. We also have about a dozen past projects, and a number of other, non-code projects to assist with operations. Conferences committee, Community Development, and others are tasked to manage various operations like events and educating new contributors (Legal, Brand Management, Fundraising, and Marketing & Publicity are all officers, not PMCs)
Note that the Incubator operates as a PMC; that is it reports to the board on it's operations of mentoring and growing these new podling communities into Apache projects. Not all projects succeed. Failure is determined by community metrics – not technology choices. Note that failing to create an actual release can be a failure – code that can't be put together easily by end users is a requirement.
Any boxed up projects in the attic would be happy to have a new, fresh community come take them out. People are free to always fork the code. New communities – if they should appear – would likely go through the incubator to show they have sufficient diversity.
Apache does not have technical goals for it's projects, other than providing open source code for the public good. The Foundation exists to serve as a stable home for like-minded communities. Congratulations to the Apache OpenOffice podling on having it's 3.4 release of the previous OpenOffice.org code!
Apache does not pay for development on it's projects. If there isn't an interested community of people in the world already interested in coding a project then... it must not be an interesting project yet. Each Apache project is truly independent. While many share community members and norms / behaviors, some are very different, and social expectations may be different across projects.
This last bullet is critical for any development managers out there. “powerplanting”, or building a complete great new feature and then shoving it into a project is not a best practice. This bypasses the community, and often leads to resentment. Besides, who's to say if the community had had a chance to comment, that they wouldn't have come up with a better feature? Large engineering teams take note: make sure you're doing your techincal planning and discussions on the list . This allows the community to participate. IT also allows your other fellow employees – who are not yet committers – to show their individual merit to the community.
Contributing to a project really is that easy: just join the list, and make your suggestion. Patches and well written bugs are especially appreciated in most projects, and are a simple way to show your merit and interest in the project.
This is a talk that is worth every community member's time to see once. A key point is: the most valuable things in an open source community are attention and focus. Don't let those be derailed by trolls.
Projects in outercurve supply their own governance, so the oversight – and ensured independence – of Apache is not there.