Skip to content

Conversation

@area
Copy link
Member

@area area commented Jun 9, 2018

If there's going to be a public instance of the network anywhere, we need to make sure that people can't mess it up. This adds permissions to

  • addGlobalSkill (colony owner only, and only works from metaColony, so effectively only the metaColony's owner)
  • addDomain (colony owner only)
  • setTaskRoleUser, setTaskDomain, setTaskSkill are now restricted to the manager of the task.

I also took the opportunity to fix a couple of issues floating around in the reputation miner that I needed fixed.

@area
Copy link
Member Author

area commented Jun 9, 2018

For our peace of mind, I would appreciate a post hoc review of these changes at some point, @elenadimitrova.

Copy link
Contributor

@elenadimitrova elenadimitrova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine. Even the suggested modifiers will become obsolete with Filip's implementation in #224. There we extend the permissions of addDomain to the entire adminRole group as defined in Authority.

skillExists(_skillId)
globalSkill(_skillId)
{
require(tasks[_id].roles[MANAGER].user == msg.sender);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our modifier vs inline logic argument again :)
Like here, for me this should have been managerOnly modifier in all three instances.

@elenadimitrova elenadimitrova deleted the maintenance/permissions branch June 11, 2018 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants