Thanks for the additional context Rich. I might have derailed a bit since I
was looking to improve the onboarding of new contributors (without ASF ID)
into the apache ecosystem, which IMO has some intersection with the badging
system, but it's definitely not the same thing.
I'll sleep on this, do
> On Mar 20, 2024, at 11:59 AM, Paulo Motta wrote:
>
> Rich:
>
> I need some time to better elaborate this. I will prepare sometime in the
> next week or so a short doc explaining what am I proposing, what problem it
> solves and how it intersects with the badging tool object of this working
>
Rich:
I need some time to better elaborate this. I will prepare sometime in the
next week or so a short doc explaining what am I proposing, what problem it
solves and how it intersects with the badging tool object of this working
group.
I suspect we might be thinking about similar things but in
On Tue, Mar 19, 2024, 16:55 Paulo Motta wrote:
> > it looks like there’s no way to run this on the hosted service and have
> it integrated with ASF LDAP, as each individual badge recipient would have
> to create an account through their tooling.
>
> Backing off a bit, do we really need logins
> And what if someone else later joins as an ASF committer with the id
'doejohn'?
What would their badge page be?
That particular badging username would be unavailable and they would have
to select another handle for their badging page when registering as
committer (if they opt-in to the badging
On Wed, 20 Mar 2024 at 15:59, Paulo Motta wrote:
>
> This is fair Sebb. I concede a separate namespace makes sense. This would
> also likely simplify the solution so we don't need to worry about clashes.
>
> Instead of overloading people.apache.org namespace which is associated with
> an ASF ID,
This is fair Sebb. I concede a separate namespace makes sense. This would
also likely simplify the solution so we don't need to worry about clashes.
Instead of overloading people.apache.org namespace which is associated with
an ASF ID, I think it makes more sense to create a separate namespace
On Wed, 20 Mar 2024 at 14:02, Paulo Motta wrote:
>
> The ID reservation for 1 year is an optimistic "vote of confidence" that
> the contributor will remain active in the community and eventually become a
> committer.
There are already issues with 3rd party Wiki and Jira ids.
Let's not add
The ID reservation for 1 year is an optimistic "vote of confidence" that
the contributor will remain active in the community and eventually become a
committer.
Existing committers can enter a "waiting list" for reserved handles. If the
reserved handle owner is no longer active after 1 year, the
Also we would need to have a way to detect malicious agents doing bogus
contributions to reserve handles. This is a separate issue that I would
prefer to keep out of this discussion for now.
On Wed, 20 Mar 2024 at 10:47 Paulo Motta wrote:
> One question that could come up is:
>
> * what if
One question that could come up is:
* what if someone does a single commit, and the ID is reserved and blocked
for posterity
We could add a 1 year TTL where the contributor would need to do another
commit within the next year to continue reserving the ID. This would
incentivize people with
> Imagine you've been granted committer privileges but you can't pick the
ID you want because it has been "reserved" by a non-committer,
This can not possibly happen, because the committer that was granted
committer privileges has already reserved its own ID when it became a
contributor in its
I don't think we should allow IDs to be "reserved": Imagine you've
been granted committer privileges but you can't pick the ID you want
because it has been "reserved" by a non-committer, it seems backward.
Gary
On Wed, Mar 20, 2024 at 8:37 AM Paulo Motta wrote:
>
> This is right Claude.
Elaborating a bit more on this phase of the contributor onboarding pipeline:
> 3. John Doe fills a simple form and selects the username "doejohn", which
is not an ASF id, but just a handle to a people.apache.org page. If an ASF
id exists with the same name, then the request is rejected.
This
This is right Claude. Essentially, the people.apache.org handle can be seen
as a “handle reservation” to a future ASF ID handle, that will be granted
when the contributor becomes a committee.
So it’s basically a pre-ASF ID handle granted to contributors without any
privileges or login (except the
On Wed, Mar 20, 2024 at 12:55 AM Paulo Motta wrote:
>
> 3. John Doe fills a simple form and selects the username "doejohn", which
> is not an ASF id, but just a handle to a people.apache.org page. If an ASF
> id exists with the same name, then the request is rejected.
> 6. After some years of
OK, Let's keep the conversation here and prefix any CoC Europe 2025
messages with [C/C Europe 25].
Are either of you planning on attending C/C Europe 24 in Bratislava?
Have either of you worked on a conference before?
Do either of you have a particular thing you want to do for the conference?
On Wed, Mar 20, 2024 at 9:31 AM Roman Shaposhnik wrote:
> ...does it get rebuilt automatically...
Yes [1], although there might be some latency in kicking the build
process, a few minutes IIRC.
-Bertrand
[1] https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/
This is awesome! Quick question: does it get rebuilt automatically or
is there a human kick needed to update the page based on .md and .json
data?
Thanks,
Roman.
On Tue, Mar 19, 2024 at 4:45 AM Bertrand Delacretaz
wrote:
>
> Hi,
>
> The new "ASF volunteer mentors & speakers" page [0] is live,
19 matches
Mail list logo
