Stream: contributing

Topic: Permissions

Christoph Rüßler (Aug 13 2022 at 16:55):

@Richard Feldman I wanted to start working on the next item in https://github.com/roc-lang/roc/issues/3513 (X86 dev backend Num functions), but I can’t seem to convert individual tasks to issues any longer. @Brendan Hansknecht suggested I ping you saying this might be a permissions issue caused by the repository going public.

Richard Feldman (Aug 13 2022 at 17:56):

ah, I suspect that's because:

• Brendan originally created the issue, so by default he's the only person who has permission to edit it
• In the private repo, everyone who was invited had full edit access, so you could edit other peoples' posts (this was unavoidable because the private repo wasn't in an organization, because private organizations cost $$$, and if you're not an organization, inviting someone gives them full edit access)
• Now that it's public, we have normal permissions, which means you aren't able to edit Brendan's post

Richard Feldman (Aug 13 2022 at 17:57):

so I think an easy system we could transition to is to create another issue and then leave a comment on the main issue that you've split off another one

Richard Feldman (Aug 13 2022 at 17:57):

and then whoever made the original issue can edit it to add the link, when they get around to it!

Richard Feldman (Aug 13 2022 at 17:58):

as an aside, I'm excited that you're working on the x86 backend - that's really awesome! :smiley:

Christoph Rüßler (Aug 13 2022 at 19:56):

Just to double-check: are you suggesting that I create this separate issue to track the subset of tasks that I will be working on so that I have full edit access?

Richard Feldman (Aug 13 2022 at 22:44):

oh I was thinking just make another issue to track the 1 that you're working on, and then leave a comment at the bottom of the original issue linking to the new one

Richard Feldman (Aug 13 2022 at 22:44):

like "hey FYI I'm gonna start working on this one, here's an issue for it: [link]"

Folkert de Vries (Aug 13 2022 at 22:55):

that is less nice though. Brendan could also just make issues for the first X items

Brendan Hansknecht (Aug 13 2022 at 23:05):

If we are fine with issue spam, I can start making a bunch of sub issues.

Richard Feldman (Aug 14 2022 at 02:47):

works for me! :+1:

Brendan Hansknecht (Aug 14 2022 at 17:23):

I think we may still have too much of a restriction? I can't seem to assign the newly created issue to @Christoph Rüßler . I can only assign the issue to a maintainer. Maybe he can sell assign? https://github.com/roc-lang/roc/issues/3792

Brendan Hansknecht (Aug 14 2022 at 17:27):

Also, spinning off sub tasks is mildly more work than I thought. Github doesn't just creates a blank issue with the direct name. So I have to add a prefix to the name, re-add labels, re-add the project, and edit the description to link back to the original task for some more context.

Brendan Hansknecht (Aug 14 2022 at 17:27):

Not hard, just will take more time than I expected.

Anton (Aug 15 2022 at 09:21):

I assigned @Christoph Rüßler. You can only assign people that are not a member of the organization after they left a comment :shrug:
From what I could find this is a fixed rule and can not be changed in settings.

Brendan Hansknecht (Aug 15 2022 at 13:01):

That is a weird set of permissions.

Last updated: Jul 26 2025 at 12:14 UTC