Can we make a Google group or shared Google account for the commons PMC? On Sat, Apr 17, 2021 at 17:43 sebb <seb...@gmail.com> wrote:
> On Sat, 17 Apr 2021 at 18:05, Fabian Meumertzheim > <meumertzh...@code-intelligence.com> wrote: > > > > On Sat, Apr 17, 2021 at 3:58 PM Stefan Bodewig <bode...@apache.org> > wrote: > > > > > > I'm not sure I understand this. AFAIU I could never become a "primary" > > > or an "auto_cc" as I will not create a Google account. Do we need to > > > have one? In that case somebody who doesn't share my personal set of > > > allergic reactions may want to act as primary. > > > > > > But how does that translate to using a mailing list as recipient of > > > reports? The section you link says you need a google account to "get > > > full access" - I don't think the list will need "full access". > > > > Let me describe the restrictions in more detail, including example > reports. Everyone listed under "primary" or "auto_cc" will receive the bugs > created in the issue tracker at [1] in email form and can also add comments > by replying to the email thread, regardless of whether they have a Google > account or not. These bugs only include some basic information such as a > truncated stack trace and a suggested severity. See [2] for an example. > > > > The detailed report, reproducer testcase and crashing revision > information (everything hosted on oss-fuzz.com) requires authentication > and thus a Google account. The detailed report AFAIK even requires > authentication after the bug has become public. I attached an example > report as a crudely exported PDF, just to give you an idea of what > information it contains. Additionally, you get access to the raw fuzzer > logs, corpus as well as the option to manually upload a testcase. > > > > Regarding privacy concerns: You could consider creating a Google account > specifically for this purpose and only use it to log in to oss-fuzz.com > in a private browsing context. > > How do you ensure that a specific Google account is authorised to view > a particular project? > > We also need to ensure continuity of access should an existing Google > user leave the project or be unavailable. How is that managed? > > > Fabian > > > > [1] https://bugs.chromium.org/p/oss-fuzz/issues > > [2] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32208 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
