https://bluesock.org/~willkg/blog/enContents © 2026 <a href="mailto:willkg@bluesock.org">Will Kahn-Greene</a> CC BY-SA 3.0Fri, 05 Jun 2026 13:54:03 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://bluesock.org/~willkg/blog/mozilla/do_working_groups.htmlWill Kahn-Greene<div><section id="project"> <h2>Project</h2> <dl class="field-list simple"> <dt>time<span class="colon">:</span></dt> <dd><p>1 month</p> </dd> <dt>impact<span class="colon">:</span></dt> <dd><p>established cross-organization groups as a tool for collaboration</p> </dd> </dl> </section> <section id="problem-statement"> <h2>Problem statement</h2> <p>The Data Org architects, builds, and maintains a data ingestion system and the ecosystem around it. The group covers a swath of engineering and data science disciplines and problem domains. Many of us are generalists and have expertise and interests in multiple areas. Many projects cut across disciplines, problem domains, and organizational structures. Some projects, disciplines, and problem domains benefit from the participation of other stakeholders who aren't in the Data Org.</p> <p>In order to succeed in tackling the projects of tomorrow, we need to formalize the creation, maintenance, and disbanding of groups composed of interested stakeholders focusing on specific missions. Further, we need a set of best practices to help make these groups successful.</p> <p><a href="https://bluesock.org/~willkg/blog/mozilla/do_working_groups.html">Read more…</a> (7 min remaining to read)</p></section></div>datamozillaretrospectivestoryhttps://bluesock.org/~willkg/blog/mozilla/do_working_groups.htmlThu, 25 Feb 2021 15:00:00 GMT