Hi Brian, Thanks, CommonRoom looks interesting, I will take a look :)
If we have consensus from PMC members, it's OK, no need to do a formal vote (As Apache member, I have access to the Iceberg private mailing list, and I was surprised to have not seen this discussion here first). I agree with Ryan and you: having this discussion public makes sense. As we say at Apache: "if it didn't happen on the mailing list, it never happened" :) Thanks again, Regards JB On Tue, Jun 6, 2023 at 1:22 PM Brian Olsen <bitsondata...@gmail.com> wrote: > > Hi Jean-Baptiste, > > Common Room https://www.commonroom.io/, is an application used to > comprehensively understand activities happening across a community so that a > team focusing on developer relations can better respond to issues, understand > where bottlenecks exist, and many other potential applications around > optimizing releases and developer experience. > > Three of the PMC have already replied to this list and after talking about it > with Ryan Blue he said this discussion would make more sense in a public > forum for all to see. That said I’m more than happy off the PMC would like to > make a formal vote around adding this capability if any of them feel that is > necessary. > > On Tue, Jun 6, 2023 at 4:30 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: >> >> Hi Brian, >> >> Can you please describe a bit what you mean by Common Room ? >> >> At first glance, it looks like a good idea. However, from Apache >> standpoint, it has to be approved by the PMC members. Did you request >> so on the private mailing list ? >> >> Regards >> JB >> >> On Thu, May 18, 2023 at 11:44 PM Brian Olsen <bitsondata...@gmail.com> wrote: >> > >> > Hey all, >> > My name is Brian and I'm the new Head of Developer Relations working at >> > Tabular. I'd like to set up Common Room for us to have a bit of a pulse on >> > the community. I would like to see if the community is interested in >> > enabling read-only permissions for the apache/iceberg and >> > apache/icberg-docs for the GitHub integration. Here's how the information >> > would be used: >> > >> > Triage issues and PRs >> > Learn ways to improve developer/contributor experience in the community >> > Understand which PRs and issues are not getting attention and why >> > Set alerts and notifications for the Developer Relations team to follow up >> > on issues to help drive changes in Iceberg >> > Metrics reporting to showcase Iceberg usage to drive further adoption and >> > interest in Iceberg >> > Gaining a better understanding of the ways people use Iceberg and the >> > features they are interested in >> > Showcase the diversity of contributions the Iceberg project >> > >> > Is everyone okay with me setting this up so I can help the community with >> > things like roadmap updates and making sure we follow up on reviews?
