Allow tasks to be read-only by public #69421

New Issue

Dalai Felinto · 2019-09-02T19:38:50+02:00

Dalai Felinto commented

2019-09-02 19:38:50 +02:00

We are trying to find ways to keep the discussion focused in some tasks before opening them up for the public contribution.

For that it would be nice if we could restrict the access to reply in some tasks to a subgroup of phabricator users.

Example of tasks we would like to try this system:

#69403 (Projects for Pablo Dobarro)
#69399 (Projects for Germano Cavalcante)

This could be used for design tasks as well, where we first have it writable by the module members, and later we open for the public. For example, #69132 got overwhelmed too early by noisy and unfriendly comments.

Since this is a sensitive matter (on our quest to be as open as possible), we would like to restrict this for the mentorship tasks at first, before considering it broad usage.

We are trying to find ways to keep the discussion focused in some tasks before opening them up for the public contribution. For that it would be nice if we could restrict the access to reply in some tasks to a subgroup of phabricator users. Example of tasks we would like to try this system: * #69403 (Projects for Pablo Dobarro) * #69399 (Projects for Germano Cavalcante) This could be used for design tasks as well, where we first have it writable by the module members, and later we open for the public. For example, #69132 got overwhelmed too early by noisy and unfriendly comments. Since this is a sensitive matter (on our quest to be as open as possible), we would like to restrict this for the mentorship tasks at first, before considering it broad usage.

Dalai Felinto commented

2019-09-02 19:38:50 +02:00

Added subscribers: @dfelinto, @jesterking, @ideasman42

noki paike commented

2019-09-03 11:35:05 +02:00

Added subscriber: @nokipaike

noki paike commented

2019-09-03 11:35:05 +02:00

Maybe this suggestion I'm about to make, someone won't like it, but it doesn't matter,
I have something to say that I think is important.

Don't lock yourself up to be more comfortable, don't be afraid of noise.

People rarely intervene, and when they do it is because they have to suggest something they know well.

This of the Transform object origins design task was something that many users knew well from other environments in which they used it, and some suggestions were initially asked.

Not frightening "of noise", maybe it seems that it makes you lose some time at first, but from brainstorming you always come up with useful tricks and corrections that you miss. People have great respect for you Devs, don't forget it.

Look at the examples of the now fantastic GSoCs Outliner and Custom bevel profiles. they have become masterpieces also thanks to all the suggestions that users have given to devs.

While people rarely intervene in things they don't know, even if they are fascinating ... such as the VR support via openXR.

If you don't want noise here on the development platform, at least create a system that opens a discussion on devtalk automatically and diverts the suggestions of ordinary people there.

Greetings Masters.

Maybe this suggestion I'm about to make, someone won't like it, but it doesn't matter, I have something to say that I think is important. Don't lock yourself up to be more comfortable, don't be afraid of noise. People rarely intervene, and when they do it is because they have to suggest something they know well. This of the **Transform object origins design task** was something that many users knew well from other environments in which they used it, and some suggestions were initially asked. Not frightening "of noise", maybe it seems that it makes you lose some time at first, but from brainstorming you always come up with useful tricks and corrections that you miss. People have great respect for you Devs, don't forget it. Look at the examples of the now fantastic GSoCs Outliner and Custom bevel profiles. they have become masterpieces also thanks to all the suggestions that users have given to devs. While people rarely intervene in things they don't know, even if they are fascinating ... such as the VR support via openXR. If you don't want noise here on the development platform, at least create a system that opens a discussion on devtalk automatically and diverts the suggestions of ordinary people there. Greetings Masters.

Dalai Felinto commented

2020-11-11 12:56:04 +01:00

Changed status from 'Confirmed' to: 'Archived'

Dalai Felinto closed this issue

2020-11-11 12:56:04 +01:00

Dalai Felinto self-assigned this 2020-11-11 12:56:04 +01:00

Dalai Felinto commented

2020-11-11 12:56:04 +01:00

I will archive this. The need for this faded a bit recently, and we can already do something like this using custom policies.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Allow tasks to be read-only by public #69421