Opened 4 years ago

Closed 3 years ago

#21411 closed defect (fixed)

Commit access for Linda

Reported by: lnl Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I plan to do some work on; this requires me to have commit access to:

Is there anything I should know about that I wouldn't know from using github? For instance, I didn't know until I wrote my first blog post that 1) didn't have a link to the login page from anywhere in the site 2) the comments couldn't be moderated per post ... etc.

I would rather find out things sooner than later, and if it's only 10 minutes of someone's time, I'd love to get some instructions on what to set up to interact with the repo, if there is any protocol to do so (do I ask anyone before I push things to staging? to the master?), etc.

Child Tickets

Change History (3)

comment:1 in reply to:  description Changed 4 years ago by weasel

Component: Internal Services/Service - gitUser Experience/Website
Owner: changed from tor-gitadm to hiro

Replying to lnl:

I plan to do some work on; this requires me to have commit access to:

Git access requests for new users need to come from somebody who already has access, see

The list of people who have access can be seen in the gitolite-admin repo. For webwml it is currently arma atagar boklm erinn gk hiro hiviah mikeperry nickm nima weasel.

They might also be able to explain workflows. The git team doesn't know all the workflows.

Reassigned to website.

comment:2 Changed 4 years ago by arma

Ok, some conclusions from the mess that happened from this ticket:

A) There is a process for adding people to groups, but nobody knows the process, and there's no plan for teaching anybody that there is a process, so each person is going to fall into this trap until we fix that. Who should lead the process of teaching our people about our processes? Is that Erin? Is it a spot that is not filled currently?

B) Separate from the website in particular, we need to teach people about how git works . In particular, the workflow where you get your own personal version of a git repository, and make your own commits on it, and then ask whoever manages the main git repository to examine and consider merging your commits. We need to teach our new people about how git works -- what is the right process for that, and who should be leading that process? I am guessing it is not Erin, since I don't think Erin does or knows git. But that said, maybe Erin still has a role in making sure the teaching-about-git is on the master checklist, and that whatever the teaching is, it's effective.

C) The website is not getting much attention lately, and those who volunteer their time to maintain it are dropping out one by one because of the perception that they're not appreciated. And this perception is strengthened by the fact that we don't teach our new people about the above two items. This lack of apparent prioritization is producing problems in a variety of areas. How can we care more about on-boarding?

Other useful outcomes?

comment:3 Changed 3 years ago by hiro

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.