Got the invite and was able to accept.

Thanks a lot John!

On Tue, Jun 6, 2023 at 6:11 PM Greg Harris <greg.har...@aiven.io.invalid>
wrote:

> John,
>
> I saw the invite be re-sent, and accepted it.
>
> Thanks for following up!
> Greg
>
> On Tue, Jun 6, 2023 at 3:08 PM John Roesler <vvcep...@apache.org> wrote:
> >
> > Hello Greg, Andrew, and Victoria,
> >
> > I have just re-added you to the file, so you should receive new invites.
> Please let us know if you have any trouble!
> >
> > Thanks,
> > -John
> >
> > On Tue, Jun 6, 2023, at 10:31, John Roesler wrote:
> > > Hello all,
> > >
> > > I put in a ticket with Apache Infra to re-send these invites, and they
> > > told me I should just remove the usernames in one commit and then
> > > re-add them in a subsequent commit to trigger the invites again.
> > >
> > > I will go ahead and do this for the users who requested it on this
> > > thread (Greg and Andrew, as well as for Victoria who asked me about it
> > > separately). If there is anyone else who needs a re-send, please let us
> > > know.
> > >
> > > I'm sorry for the confusion, Hao. The docs claimed we could add 20
> > > users, but when I actually checked in the file, I got an automated
> > > notification that we could actually only have 10.
> > >
> > > As for triggering the build, I don't believe you'll be able to log in
> > > to Jenkins, but you should be able to say "retest this please" in a PR
> > > comment to trigger it. Apparently, that doesn't work anymore, though.
> > > I'll file an Infra ticket for it.
> > >
> > > Thanks all,
> > > John
> > >
> > > On Fri, Jun 2, 2023, at 18:46, Hao Li wrote:
> > >> Hi Luke,
> > >>
> > >> Sorry for the late reply. Can you also add me to the whitelist? I
> believe
> > >> I'm supposed to be there as well. Matthias and John can vouch for me
> :) My
> > >> github ID is "lihaosky".
> > >>
> > >> Thanks,
> > >> Hao
> > >>
> > >> On Fri, Jun 2, 2023 at 4:43 PM Greg Harris
> <greg.har...@aiven.io.invalid>
> > >> wrote:
> > >>
> > >>> Luke,
> > >>>
> > >>> I see that the PR has been merged, but I don't believe it re-sent the
> > >>> invitation.
> > >>>
> > >>> Thanks
> > >>> Greg
> > >>>
> > >>>
> > >>> On Wed, May 31, 2023 at 6:46 PM Luke Chen <show...@gmail.com> wrote:
> > >>> >
> > >>> > Hi Greg and Andrew,
> > >>> >
> > >>> > Sorry, I don't know how to re-sent the invitation.
> > >>> > It looks like it is auto sent after the .asf.yaml updated.
> > >>> > Since updating collaborator list is part of release process based
> on the
> > >>> doc
> > >>> > <https://kafka.apache.org/contributing>, I just created a new
> list and
> > >>> > opened a PR:
> > >>> > https://github.com/apache/kafka/pull/13790
> > >>> >
> > >>> > Hope that after this PR merged, you'll get a new invitation.
> > >>> >
> > >>> > Thanks.
> > >>> > Luke
> > >>> >
> > >>> > On Thu, Jun 1, 2023 at 5:27 AM Andrew Grant
> <agr...@confluent.io.invalid
> > >>> >
> > >>> > wrote:
> > >>> >
> > >>> > > Hi all,
> > >>> > > Like Greg I also received an invitation to collaborate but was
> too
> > >>> slow to
> > >>> > > accept the invite :( I'm also wondering if there's a way to
> resend the
> > >>> > > invite? I'm andymg3 on GitHub.
> > >>> > > Thanks,
> > >>> > > Andrew
> > >>> > >
> > >>> > > On Tue, May 30, 2023 at 12:12 PM Greg Harris
> > >>> <greg.har...@aiven.io.invalid
> > >>> > > >
> > >>> > > wrote:
> > >>> > >
> > >>> > > > Hey all,
> > >>> > > >
> > >>> > > > I received an invitation to collaborate on apache/kafka, but
> let the
> > >>> > > > invitation expire after 7 days.
> > >>> > > > Is there a workflow for refreshing the invite, or is an admin
> able to
> > >>> > > > manually re-invite me?
> > >>> > > > I'm gharris1727 on github.
> > >>> > > >
> > >>> > > > Thanks!
> > >>> > > > Greg
> > >>> > > >
> > >>> > > > On Wed, May 24, 2023 at 9:32 AM Justine Olshan
> > >>> > > > <jols...@confluent.io.invalid> wrote:
> > >>> > > > >
> > >>> > > > > Hey Yash,
> > >>> > > > > I'm not sure how it used to be for sure, but I do remember
> we used
> > >>> to
> > >>> > > > have
> > >>> > > > > a different build system. I wonder if this used to work with
> the
> > >>> old
> > >>> > > > build
> > >>> > > > > system and not any more.
> > >>> > > > > I'd be curious if other projects have something similar and
> how it
> > >>> > > works.
> > >>> > > > >
> > >>> > > > > Thanks,
> > >>> > > > > Justine
> > >>> > > > >
> > >>> > > > > On Wed, May 24, 2023 at 9:22 AM Yash Mayya <
> yash.ma...@gmail.com>
> > >>> > > wrote:
> > >>> > > > >
> > >>> > > > > > Hi Justine,
> > >>> > > > > >
> > >>> > > > > > Thanks for the response. Non-committers don't have Apache
> > >>> accounts;
> > >>> > > > are you
> > >>> > > > > > suggesting that there wasn't a need to sign in earlier and
> a
> > >>> change
> > >>> > > in
> > >>> > > > this
> > >>> > > > > > policy is restricting collaborators from triggering Jenkins
> > >>> builds?
> > >>> > > > > >
> > >>> > > > > > Thanks,
> > >>> > > > > > Yash
> > >>> > > > > >
> > >>> > > > > > On Wed, May 24, 2023 at 9:30 PM Justine Olshan
> > >>> > > > > > <jols...@confluent.io.invalid>
> > >>> > > > > > wrote:
> > >>> > > > > >
> > >>> > > > > > > Yash,
> > >>> > > > > > >
> > >>> > > > > > > When I rebuild, I go to the CloudBees CI page and I have
> to
> > >>> log in
> > >>> > > > with
> > >>> > > > > > my
> > >>> > > > > > > apache account.
> > >>> > > > > > > Not sure if the change in the build system or the need
> to sign
> > >>> in
> > >>> > > is
> > >>> > > > part
> > >>> > > > > > > of the problem.
> > >>> > > > > > >
> > >>> > > > > > >
> > >>> > > > > > > On Wed, May 24, 2023 at 4:54 AM Federico Valeri <
> > >>> > > > fedeval...@gmail.com>
> > >>> > > > > > > wrote:
> > >>> > > > > > >
> > >>> > > > > > > > +1 on Divij suggestions
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > > On Wed, May 24, 2023 at 12:04 PM Divij Vaidya <
> > >>> > > > divijvaidy...@gmail.com
> > >>> > > > > > >
> > >>> > > > > > > > wrote:
> > >>> > > > > > > > >
> > >>> > > > > > > > > Hey folks
> > >>> > > > > > > > >
> > >>> > > > > > > > > A week into this experiment, I am finding the
> ability to
> > >>> add
> > >>> > > > labels,
> > >>> > > > > > > > > request for reviewers and ability to close PRs very
> useful.
> > >>> > > > > > > > >
> > >>> > > > > > > > > 1. May I suggest an improvement to the process by
> > >>> requesting
> > >>> > > for
> > >>> > > > some
> > >>> > > > > > > > > guidance on the interest areas for various
> committers. This
> > >>> > > would
> > >>> > > > > > help
> > >>> > > > > > > us
> > >>> > > > > > > > > request for reviews from the right set of
> individuals.
> > >>> > > > > > > > > As a reference, we have tried something similar with
> Apache
> > >>> > > > TinkerPop
> > >>> > > > > > > > (see
> > >>> > > > > > > > > TinkerPop Contributors section at the end) [1],
> where the
> > >>> > > > committers
> > >>> > > > > > > self
> > >>> > > > > > > > > identify their preferred area of interest.
> > >>> > > > > > > > >
> > >>> > > > > > > > > 2. I would also request creation of the following new
> > >>> labels:
> > >>> > > > > > > > > tiered-storage, transactions, security, refactor,
> > >>> zk-migration,
> > >>> > > > > > > > > first-contribution (so that we can prioritize
> reviews for
> > >>> first
> > >>> > > > time
> > >>> > > > > > > > > contributors as an encouragement), build, metrics
> > >>> > > > > > > > >
> > >>> > > > > > > > > [1] https://tinkerpop.apache.org/
> > >>> > > > > > > > >
> > >>> > > > > > > > > --
> > >>> > > > > > > > > Divij Vaidya
> > >>> > > > > > > > >
> > >>> > > > > > > > >
> > >>> > > > > > > > >
> > >>> > > > > > > > > On Mon, May 15, 2023 at 11:07 PM John Roesler <
> > >>> > > > vvcep...@apache.org>
> > >>> > > > > > > > wrote:
> > >>> > > > > > > > >
> > >>> > > > > > > > > > Hello again, all,
> > >>> > > > > > > > > >
> > >>> > > > > > > > > > Just a quick update: after merging the changes to
> > >>> asf.yaml, I
> > >>> > > > > > > received
> > >>> > > > > > > > a
> > >>> > > > > > > > > > notification that the list is limited to only 10
> people,
> > >>> not
> > >>> > > > 20 as
> > >>> > > > > > > the
> > >>> > > > > > > > > > documentation states.
> > >>> > > > > > > > > >
> > >>> > > > > > > > > > Here is the list of folks who will now be able to
> triage
> > >>> PRs
> > >>> > > > and
> > >>> > > > > > > > trigger
> > >>> > > > > > > > > > builds: Victoria Xia, Greg Harris, Divij Vaidya,
> Lucas
> > >>> > > > Brutschy,
> > >>> > > > > > Yash
> > >>> > > > > > > > > > Mayya, Philip Nee, vamossagar12, Christo Lolov,
> Federico
> > >>> > > > Valeri,
> > >>> > > > > > and
> > >>> > > > > > > > andymg3
> > >>> > > > > > > > > >
> > >>> > > > > > > > > > Thanks all,
> > >>> > > > > > > > > > -John
> > >>> > > > > > > > > >
> > >>> > > > > > > > > > On 2023/05/12 15:53:40 John Roesler wrote:
> > >>> > > > > > > > > > > Thanks again for bringing this up, David!
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > As an update to the community, the PMC has
> approved a
> > >>> > > > process to
> > >>> > > > > > > make
> > >>> > > > > > > > > > use of this feature.
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > Here are the relevant updates:
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > PR to add the policy:
> > >>> > > > > > > https://github.com/apache/kafka-site/pull/510
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > PR to update the list:
> > >>> > > > > > https://github.com/apache/kafka/pull/13713
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > Ticket to automate this process.. Contributions
> > >>> welcome :)
> > >>> > > > > > > > > > https://issues.apache.org/jira/browse/KAFKA-14995
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > And to make sure it doesn't fall through the
> cracks in
> > >>> the
> > >>> > > > mean
> > >>> > > > > > > time,
> > >>> > > > > > > > > > here's the release process step:
> > >>> > > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > >
> > >>> > >
> > >>>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-UpdatetheCollaboratorsList
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > Unfortunately, the "collaborator" feature only
> allows
> > >>> 20
> > >>> > > > > > usernames,
> > >>> > > > > > > > so
> > >>> > > > > > > > > > we have decided to simply take the top 20
> non-committer
> > >>> > > authors
> > >>> > > > > > from
> > >>> > > > > > > > the
> > >>> > > > > > > > > > past year (according to git shortlog).
> Congratulations
> > >>> to our
> > >>> > > > new
> > >>> > > > > > > > > > collaborators!
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > Victoria Xia, Greg Harris, Divij Vaidya, Lucas
> > >>> Brutschy,
> > >>> > > Yash
> > >>> > > > > > > Mayya,
> > >>> > > > > > > > > > Philip Nee, vamossagar12, Christo Lolov, Federico
> > >>> Valeri, and
> > >>> > > > > > andymg3
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > Thanks,
> > >>> > > > > > > > > > > -John
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > > > On 2023/04/27 18:45:09 David Arthur wrote:
> > >>> > > > > > > > > > > > Hey folks,
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > I stumbled across this wiki page from the
> infra team
> > >>> that
> > >>> > > > > > > > describes the
> > >>> > > > > > > > > > > > various features supported in the ".asf.yaml"
> file:
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > >
> > >>> > >
> > >>>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > One section that looked particularly
> interesting was
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > >
> > >>> > >
> > >>>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > github:
> > >>> > > > > > > > > > > >   collaborators:
> > >>> > > > > > > > > > > >     - userA
> > >>> > > > > > > > > > > >     - userB
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > This would allow us to define non-committers as
> > >>> > > > collaborators
> > >>> > > > > > on
> > >>> > > > > > > > the
> > >>> > > > > > > > > > Github
> > >>> > > > > > > > > > > > project. Concretely, this means they would
> receive
> > >>> the
> > >>> > > > "triage"
> > >>> > > > > > > > Github
> > >>> > > > > > > > > > role
> > >>> > > > > > > > > > > > (defined here
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > >
> > >>> > >
> > >>>
> https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role
> > >>> > > > > > > > > > ).
> > >>> > > > > > > > > > > > Practically, this means we could let
> non-committers
> > >>> do
> > >>> > > > things
> > >>> > > > > > > like
> > >>> > > > > > > > > > assign
> > >>> > > > > > > > > > > > labels and reviewers on Pull Requests.
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > I wanted to see what the committer group
> thought
> > >>> about
> > >>> > > this
> > >>> > > > > > > > feature. I
> > >>> > > > > > > > > > > > think it could be useful.
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > > > Cheers,
> > >>> > > > > > > > > > > > David
> > >>> > > > > > > > > > > >
> > >>> > > > > > > > > > >
> > >>> > > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > >
> > >>> > >
> > >>>
> > >>
> > >>
> > >> --
> > >> Thanks,
> > >> Hao
>

Reply via email to