Gitlab issueshttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues2023-12-05T18:45:51Zhttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/15User permissions in TPO2023-12-05T18:45:51ZGabagaba@torproject.orgUser permissions in TPO- [ ] Move this into guides/documentation
- [ ] Include clear criteria on when to create an account in gitlab and how to assign permissions.
- [x] Can somebody else review who has permission to what group under tpo? Right now we have
tp...- [ ] Move this into guides/documentation
- [ ] Include clear criteria on when to create an account in gitlab and how to assign permissions.
- [x] Can somebody else review who has permission to what group under tpo? Right now we have
tpo:
* gaba - owner
* isabela - reporter
* roger - reporter
core:
* dgoulet - owner
* asn - owner
* nickm - owner
* ahf - owner
* gaba - owner
tpa:
* ahf-admin - owner
* hiro - owner
* weasel - owner
* gaba - owner
applications:
* acat - owner
* ahf-admin - owner
* antonela - owner
* sysrqb - owner
* gk - owner
* brade - developer
* mcs - developer
* bolkm - developer
* gaba - owner
ux:
* antonela - owner
* diogosergio - maintainer
* pili - maintainer
* emmapeel - maintainer
* torproject-pusher - maintainer
* nah - develper
* dunqan - developer
* gaba - owner
community:
* gus - owner
* pili - owner
* kat - guest
* alison - mantainer
* kushal - developer
* emmapeel - developer
* gaba - owner
metrics:
* ahf-admin - owner
* karsten - owner
* acute - developer
* djackson - developer
* phw - developer
* gaba - owner
anti-censorship:
* cohosh - owner
* phw - owner
* hiro- developer
* arma - developer
* gaba - owner
* antonela - developer
network health:
* dgoulet - owner
* gk - owner
* phw - owner
* arma - owner
* gaba - owner
web:
* gus - owner
* hiro - mantainer
* pili - maintainer
* emmapeel - maintainer
* torproject-ppusher - maintainer
* antonela - developer
* stephw - developer
* protechthor-guest - developer
* clash - reporter
* arma - reporter
* aya - developer
* bunnyapocalypse-guest - guest
* nemaniarjun-guest - guest
* claromes-guest - guest
* jacobo-guest - guest
* kjedidiahpark-guest - guest
* raviteja-guest
* rotationmatrix-guest - guest
* jaruga - guest
* gaba - owner
scalability:
* mikeperry - maintainer
* arma - maintainer
* gaba - owner
external users:
* all contributors that are not in a specific group/team. Limit projects creation to 5.
What should we change? I think we should at least remove admin users from ownership. They already have access to everything.
Permissions and roles in Gitlab: https://gitlab.torproject.org/help/user/permissionshttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/21publish the migration source code2021-10-21T15:14:10Zanarcatpublish the migration source codeit would be great to have the migration source code public, if that is safe at all.
it would serve a few purposes:
1. it would allow us to diagnose problems better if they come up
2. it would give good examples on how to talk to the ...it would be great to have the migration source code public, if that is safe at all.
it would serve a few purposes:
1. it would allow us to diagnose problems better if they come up
2. it would give good examples on how to talk to the API
3. it would show others how we did it
Of course the code would need to be sanitized for secrets, but it doesn't have to be clean.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/28How we are going to use Gitlab for organizing projects and Tor's work2020-11-13T17:50:19ZGabagaba@torproject.orgHow we are going to use Gitlab for organizing projects and Tor's work- [ ] ***CONVERT THIS THREAD INTO DOCUMENTATION* (Tails example https://tails.boum.org/contribute/working_together/GitLab/)**
Attention @tpo/core @tpo/ux @tpo/metrics @tpo/anti-censorship @tpo/community @tpo/applications @tpo/tpa
We ...- [ ] ***CONVERT THIS THREAD INTO DOCUMENTATION* (Tails example https://tails.boum.org/contribute/working_together/GitLab/)**
Attention @tpo/core @tpo/ux @tpo/metrics @tpo/anti-censorship @tpo/community @tpo/applications @tpo/tpa
We have [user stories](#26) for how we need to use Gitlab. I'm writing down here a proposal on how to use Gitlab, open up for discussion.
**SPONSOR/PROJECT PLANNING AND WORK**
- To track a sponsor's project, including how much time there is for the project and what is still not assigned (pm user stories #26):
Create a milestone per objective of the project OR for the whole project, depending on size. The milestone should be in the group that includes all groups working on this project. Examples:
* For OnionPerf https://gitlab.torproject.org/groups/tpo/metrics/-/milestones/1
* For objectives in the Sponsor 30: https://gitlab.torproject.org/groups/tpo/-/milestones/4
Each milestone will have:
* dates when the project/objective starts or end
* information about the project or objective
* all the tickets that need to be completed with this milestone
To mark that a ticket could be in a specific sponsor/project:
* Mark that ticket with the label for the sponsor. For example label 'Sponsor 55'. The tickets with this label may not go into the sponsor but are a possible fit for it.
To divide objectives/tickets into smaller tasks (dev stories for sponsor planning):
* Create an issue for that objective with the label 'project'
* In that issue write down a list of "children" that are the tasks that need to be completed. Each child is a new issue. Example: https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/31274
**RELEASE PLANNING**
To decide which open bugs must be finished before we can put out the next release.
* Create a milestone for each release. The milestone will be at the level of the team's group or project. For example:
* Tor 0.4.4 https://gitlab.torproject.org/groups/tpo/-/milestones/tor-044x-final?title=Tor%3A+0.4.4.x-final
* Tor unspecified https://gitlab.torproject.org/groups/tpo/-/milestones/tor-unspecified?title=Tor%3A+unspecified
**TEAM WORK**
To organize work per team or per project (TBB, tor, onionperf, etc):
* Create a kanban board where we can set stacks with:
* backlog: indicates all the work that we have planned to do
* next: indicates all the work that we are doing in the next sprint. (decide with your lovely PM and your team how long your sprint should be)
* doing: indicates all the tickets that people are working on right now
* needs review: some teams needs this label to indicate the tickets/issues that needs somebody to review them.
* Each "stack" in the board will be a label. The labels that we are all using for this are: backlog, next, doing, needs review.
* The issues at the top of the stack are the ones with the most priority in that stack.
For example:
1. OnionPerf https://gitlab.torproject.org/tpo/metrics/onionperf/-/boards
1. SysadminXs https://gitlab.torproject.org/groups/tpo/tpa/-/boards
1. Network https://gitlab.torproject.org/groups/tpo/core/-/boards
**To decide on what to work next**
* There is this neat place where you can see all the issues assigned to you, issues that you were mentioned in, merge requests. https://gitlab.torproject.org/dashboard/todos
**To assign reviews**
* Issues in Gitlab do not have a review but merge requests do have them. To work around this (as we still need to mark down issues for review) we will have labels at the project or group level (not TPO level) to mark who is reviewing which issue. The labels will be "review-by-X" with X the name of the person.
**COMMUNICATION BETWEEN TEAMS**
In an issue you can mention a group (for example @core) and that issue gets into the dashboard of all the people in that group. Use this power with responsability.
**REPORTING BUGS**
We still do not have signups in Gitlab so for now people have to send a mail to gitlab-admin@torproject.org to be able to get an account in Gitlab. Once they have an account they can easily report a bug in https://gitlab.torproject.org/groups/tpo/-/boards or https://gitlab.torproject.org/groups/tpo/-/issues
I'm not totally sure if that board in TPO is the best one so we need to think a little more about how to show all the work happening as well as all the work to be done in the whole organization. https://gitlab.torproject.org/groups/tpo/-/boards
I would like to add issue templates to all projects so people can easily follow the template to post the information that we need from the issue. Example: https://gitlab.torproject.org/ahf/lobby/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
**Templates** to report a bug should contain:
* summary
* steps to reproduce
* expected results
* actual results
* version that the bug was found in
For people to search between all the issues in TPO (if they for example want to check all the issues they authored) they can do it in https://gitlab.torproject.org/groups/tpo/-/issues
**VOLUNTEERING WORK**
To help volunteers I think we could have labels that help people find something they can collaborate to:
* Documentation
* 1st contribution
**We are discussing email interaction with Gitlab on #29**
**We are discussing labels in #4**
Please, make commments, things that may not work, something that I maybe forgot.Gabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/29document how to use GitLab through email2021-01-30T22:56:52ZGabagaba@torproject.orgdocument how to use GitLab through email(Note: this is just for issues right now as I've not been dealing with merge requests lately. But a bunch of the notes below should apply to them, too)
@gk started writing this and I'm moving it into an issue.
**Creating a new issue**
...(Note: this is just for issues right now as I've not been dealing with merge requests lately. But a bunch of the notes below should apply to them, too)
@gk started writing this and I'm moving it into an issue.
**Creating a new issue**
Clicking on the per project issues gives a link at the bottom of the page, say "Email a new issue to this project".
That link should go into the From of your email. The subject is the title of the issue and the body the description. You can start right away using shortcuts in the body, like /assign @foo, /estimate 1d etc. (see: https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#new-issue-via-email for more details)
**Adding a comment to an existing issue**
Replying to an existing comment
You need to have notifications enabled for this part and then just reply to the particular comment as you would reply to an email in a thread (see: https://docs.gitlab.com/ee/administration/reply_by_email.html for more details)
Creating a new comment
This is not easily doable right now (see: https://gitlab.com/gitlab-org/gitlab/-/issues/18816). However, it works if you have notifications enabled and then reply to any notification email for the issue of interest by replacing everything that would get quoted with the comment you want to add. This works as well with shortcuts like /estimate 1d or /spend -1h (note: for those you won't get notification emails back, though, while for others like /assign @foo you would).
**Using quick actions to update an issue**
There are a bunch of quick actions available which are handy to update an issue (see: https://gitlab.torproject.org/help/user/project/quick_actions.md). As mentioned above they can be sent by email as well, both within a comment (be it as a reply to a previous one or in a new one) or just instead of it. So, if you for example want to update the amount of time spent on ticket $foo by one hours, find any notification email for that issue and reply to it by replacing any quoted text with "/spend 1h".anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/31document gitlab user creation, project adhesion and permission policies2020-10-20T15:42:39ZGabagaba@torproject.orgdocument gitlab user creation, project adhesion and permission policiesWe need
* clear criterias on adding a user to a project
* clear criterias on which role/permissions to give users added to a projectWe need
* clear criterias on adding a user to a project
* clear criterias on which role/permissions to give users added to a projectGabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/56Packages wiki page getting discontinued2021-10-21T15:17:20ZGabagaba@torproject.orgPackages wiki page getting discontinuedAtagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doct...Atagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doctor.git/tree/package_versions.py would have to get adapted to gitlab.https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/128Broken link on help page2022-08-30T21:03:58ZStefani BanerianBroken link on help pagepage
https://gitlab.torproject.org/help/gitlab-basics/start-using-git#merge-a-branch-with-default-branch
has a broken link, right under the code section.
https://gitlab.torproject.org/help/user/project/merge_requests/ gives a '404'page
https://gitlab.torproject.org/help/gitlab-basics/start-using-git#merge-a-branch-with-default-branch
has a broken link, right under the code section.
https://gitlab.torproject.org/help/user/project/merge_requests/ gives a '404'anarcatanarcat