Shane is founder of Punderthings℠ LLC consultancy, helping organizations find better ways to engage with the critical open source projects that power modern technology and business. He blogs and tweets about open source governance and trademark issues, and has spoken at major technology conferences like ApacheCon, OSCON, All Things Open, Community Leadership Summit, and Ignite.
Shane Curcuru serves as VP Brand Management for the ASF, wrote the trademark and branding policies that cover all 200+ Apache® projects, and assists projects with defining and policing their trademarks, as well as negotiating agreements with various software vendors using Apache software brands. Shane is serving a seventh term as an elected Director of the ASF, providing governance oversight, community mentoring, and fiscal review for all Apache projects.
Otherwise, Shane is: a father and husband, a BMW driver and punny guy. Oh, and we have cats! Follow @ShaneCurcuru and read about open source communities and see my FOSS Foundation directory.
Authored Comments
Agreed - a good name is the first thing newcomers will think of when they come to your project.
We're considering a follow up article with a more step-by-step process to how to evaluate names, so if folks have links that talk about the name choice process, let me know!
What about the licensing policies of various FOSS foundations and major vendors? I wonder if there are efficiencies in either tooling or documentation about license compliance and verification that can optimize the task of reviewing a specific product from those organizations?
For example, the ASF has a comprehensive policy for LICENSE and NOTICE construction that applies to every Apache software product release. While we may not always be perfect, there are checks and balances, and when issues arise the ASF board can require a project to fix the errors.
https://www.apache.org/legal/release-policy.html#licensing-documentation
https://www.apache.org/legal/src-headers.html