Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COMMUNITY-ROLES: update list of owners #1925

Merged
merged 1 commit into from
Jan 29, 2018
Merged

COMMUNITY-ROLES: update list of owners #1925

merged 1 commit into from
Jan 29, 2018

Conversation

waldyrious
Copy link
Member

This completes the recent updates to the owners of the tldr-pages organization, following the actions described at #1878 (comment)

I managed to dig up public references for the invitations for @agnivade and @sbrl, and for @rprieto it was easy: I simply located the first commit in the repo. From now on, according to the documented procedure, there will be issues we can refer to, so the next additions should be easier.

I couldn't find public discussions about my own addition, but I had the invitation email so I could get the date. That said, if I recall correctly, @rubenvereecken added me and @Ostera at the same time, or at least in close succession. Could any of you let me know more exact dates for your addition, and hopefully a link to (or vague memory about) a discussion in this repo, possibly in an unrelated PR, where we decided on the addition of both of us? I already searched the Gitter logs, but found nothing there.

I'd ask the same of the others: @igorshubovych, @felixonmars, @danzimm, @edgurgel, @Leandros: dates, and hopefully also the context, of your additions, would be great to make this document more complete.

@waldyrious waldyrious added the community Issues/PRs dealing with role changes and community organization. label Jan 22, 2018
@agnivade
Copy link
Member

Wow, it's just over a year. I thought it was like 2 or 3 years already. Seems like time doesn't fly at all. 😆

@waldyrious
Copy link
Member Author

waldyrious commented Jan 23, 2018

If I'm reading the git records correctly, your first PR was #626, a little over 2 years ago, so indeed it's been quite a while since you started becoming involved with the project ;)

Also, this highlights how easy it is to overlook how much work it is to maintain a FOSS project, and the potential for burnout. I'm happy we've managed to establish mantainer replenishing procedures while the current team is still active.

Copy link
Member

@sbrl sbrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me! 😺

@waldyrious
Copy link
Member Author

waldyrious commented Jan 25, 2018

I'd say let's wait about a week (counting from the opening of the PR, i.e. until 29 January) and then merge if nobody comments until then. We can always complete the missing info later.

@felixonmars
Copy link
Collaborator

I guess it was some discuss on gitter. Sorry but I really don't remember the date.

@waldyrious
Copy link
Member Author

@felixonmars didn't you get an email with the invitation?

@waldyrious
Copy link
Member Author

Merging per the discussion above. Hopefully we can get the rest of the historical information sometime in the future, for record-keeping.

@waldyrious waldyrious merged commit a186436 into master Jan 29, 2018
@waldyrious waldyrious deleted the update-owners branch January 29, 2018 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues/PRs dealing with role changes and community organization.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants