To be clear, I think what Brian is saying is that we'd use a free OSS account if the PMC would like access. Since it is licensed by user, Tabular would have a separate one that doesn't take up the free accounts for our DevRel team.
On Tue, May 30, 2023 at 12:54โฏPM Jack Ye <[email protected]> wrote: > Sounds good to me! > > -Jack > > On Tue, May 30, 2023 at 12:39โฏPM Brian Olsen <[email protected]> > wrote: > >> Iโve spoken to Ryan and the understanding is that anyone in the community >> would have access upon request. Assuming theyโre only getting read roles to >> public repos like these apps request for anyways. >> >> Tools like Orbit have a free open source tier that can be used but it is >> limited to 3-5 users. We are paying for Common Room in Tabular and >> Confluent/Kafka and Imply/Druid have this integration set up as well. >> >> Iโd be happy to discuss getting one of these set up for PMC usage but I >> would mostly be using the one in Tabular. So the PMC one would be a shared >> way to manage a view off the community for PMC work vs DevRel work. >> >> Does that make sense? >> >> On Tue, May 30, 2023 at 11:57 AM Jack Ye <[email protected]> wrote: >> >>> Seems like a valuable and interesting product to use! >>> >>> Are there any restrictions on Apache side to use such product >>> integration? Is it a free product for us to use? >>> >>> Best, >>> Jack Ye >>> >>> On Tue, May 30, 2023 at 9:23โฏAM Brian Olsen <[email protected]> >>> wrote: >>> >>>> Great question! >>>> >>>> I asked the same questions to Common Room and this is what they >>>> responded with: >>>> >>>> So with the app, we can pull deltas. With using the method with our own >>>>> auth, we donโt. Iโm not sure if itโs a limitation in how it was written, >>>>> since our auth was written years ago, before we supported all the activity >>>>> types. But I do understand that activities like stars would have to be >>>>> repulled every time with our method, so we opt not to do that. >>>> >>>> >>>> I looked into how their competitor does it >>>> <https://orbit.love/docs/all/github-integration#aed6c486fcd746098531d5dda92a641c> >>>> and they also do the same. I'm not sure why. I imagine scraping is much >>>> more difficult and limited as the website is always subject to change. We >>>> used Orbit in the Trino community and none of the data they scraped >>>> required private access. So my best guess is that GitHub doesn't allow >>>> incremental updates and no way of scraping the site without pulling >>>> everything, all at once. Which is what they do when you run a proof of >>>> concept with them. >>>> >>>> Other Apache communities have connected with them so maybe a next step >>>> could be to reach out to some of those communities or I'd be happy to bring >>>> anyone who is interested on to a phone call with Common Room to ask any >>>> other quesitons. >>>> >>>> Let me know what you think. >>>> >>>> >>>> >>>> On Tue, May 30, 2023 at 10:54 AM Russell Spitzer < >>>> [email protected]> wrote: >>>> >>>>> Could you please elaborate on what Common room really is and why it >>>>> needs special permissions? I'm would have thought just generic public >>>>> access would be enough to check PR's, Issues and such? >>>>> >>>>> On Tue, May 23, 2023 at 7:17โฏPM Anton Okolnychyi >>>>> <[email protected]> wrote: >>>>> >>>>>> Seems valuable to me. >>>>>> >>>>>> - Anton >>>>>> >>>>>> On May 18, 2023, at 2:44 PM, Brian Olsen <[email protected]> >>>>>> 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 <https://www.commonroom.io/> >>>>>> Room <https://www.commonroom.io/> 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 >>>>>> <https://docs.commonroom.io/get-started/integrations/github#required-permissions> >>>>>> 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? >>>>>> >>>>>> >>>>>> -- Ryan Blue Tabular
