StanfordHCI / flash-teams

2 stars 0 forks source link

Popovers can be edited in worker view before team is started #187

Open dretelny opened 10 years ago

dretelny commented 10 years ago

Not sure if this is necessarily a bad thing but worth discussing. See attached screenshot

image

negarrahmati commented 10 years ago

When I was hiring experts, sending the link to the project on Foundry before hiring the experts usually helped them understand the project and how they were going to work with others. That is why I suggested having read only pop overs for users before starting the team.

dretelny commented 10 years ago

I agree that they should be able to see the workflow and that the popovers should be read only. The way it works right now, however, is that the popovers can be edited by the workers before the team has started (e.g., they are not read only)

Daniela Retelny Stanford University Department of Management Science and Engineering (914) 450-2033 dretelny@stanford.edu www.danielaretelny.com

On Jun 24, 2014, at 6:33 PM, Negar notifications@github.com wrote:

When I was hiring experts, sending the link to the project on Foundry before hiring the experts usually helped them understand the project and how they were going to work with others. That is why I suggested having read only pop overs for users before starting the team.

— Reply to this email directly or view it on GitHub.

negarrahmati commented 10 years ago

You are saying that you agree that this is a bug and should be fixed?

Negar

On Tue, Jun 24, 2014 at 6:35 PM, dretelny notifications@github.com wrote:

I agree that they should be able to see the workflow and that the popovers should be read only. The way it works right now, however, is that the popovers can be edited by the workers before the team has started (e.g., they are not read only)

Daniela Retelny Stanford University Department of Management Science and Engineering (914) 450-2033 dretelny@stanford.edu www.danielaretelny.com

On Jun 24, 2014, at 6:33 PM, Negar notifications@github.com wrote:

When I was hiring experts, sending the link to the project on Foundry before hiring the experts usually helped them understand the project and how they were going to work with others. That is why I suggested having read only pop overs for users before starting the team.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/StanfordHCI/flash-startups/issues/187#issuecomment-47051357 .

dretelny commented 10 years ago

Yes, this is a bug and should be fixed. The popovers should always be read only in the worker view regardless of whether the project has been started.

Having said that, if we decide to let worker’s author their own workflows then we would want the popovers to be in edit mode...

Daniela Retelny Stanford University Department of Management Science and Engineering (914) 450-2033 dretelny@stanford.edu www.danielaretelny.com

On Jun 24, 2014, at 6:41 PM, Negar notifications@github.com wrote:

You are saying that you agree that this is a bug and should be fixed?

Negar

On Tue, Jun 24, 2014 at 6:35 PM, dretelny notifications@github.com wrote:

I agree that they should be able to see the workflow and that the popovers should be read only. The way it works right now, however, is that the popovers can be edited by the workers before the team has started (e.g., they are not read only)

Daniela Retelny Stanford University Department of Management Science and Engineering (914) 450-2033 dretelny@stanford.edu www.danielaretelny.com

On Jun 24, 2014, at 6:33 PM, Negar notifications@github.com wrote:

When I was hiring experts, sending the link to the project on Foundry before hiring the experts usually helped them understand the project and how they were going to work with others. That is why I suggested having read only pop overs for users before starting the team.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/StanfordHCI/flash-startups/issues/187#issuecomment-47051357 .

— Reply to this email directly or view it on GitHub.