Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users are not able to create facilities for which they are not the owner #107

Closed
job opened this issue Jan 10, 2017 · 19 comments
Closed

Users are not able to create facilities for which they are not the owner #107

job opened this issue Jan 10, 2017 · 19 comments
Assignees
Labels
AC Admin Committee Outreach Outreach Committee Time:Major 4 - 10 hours work
Milestone

Comments

@job
Copy link
Contributor

job commented Jan 10, 2017

There should be some kind of checkbox, that PeeringDB users can indicate that they are present in a certain facility, but that they are just a tenant of the facility and not the owner.

The advantage for PeeringDB is that as the user base grows, more facilities are entered into PeeringDB. Even though the facility management might not actively participate in PeeringDB

The advantage for the AdminCom is that we don't need to discuss with the PeeringDB user whether they understand PeeringDB properly or not.

I'm not exactly sure how it should look from an UI perspective.

@job job added AC Admin Committee Outreach Outreach Committee usability labels Jan 10, 2017
@job
Copy link
Contributor Author

job commented Jan 11, 2017

@arnoldnipper suggests that the same applies to IXPs

@job
Copy link
Contributor Author

job commented Jan 11, 2017

@arnoldnipper said:

"And we have to do something to make it harder for users to register facilities and IXPS. 95+% are fake registrations. At best users want to associate their network with the facility or the IXP. Maybe the default should be not to show those tabs.
Somehow .... enable those tabs if Admins are quite sure that the organisation is also operating facilities and/or IXP"

@eloos
Copy link

eloos commented Jan 19, 2017

Could we resolve this by educating the users whom are going through a first experience? For instance by showing a pop-up over each field with an explanation on the proper use of the field. This would be shown to all users for an org that has nothing set up in terms of IXP, Facilities or networks and to everyone for whom this session is their first login.

@grizz
Copy link
Member

grizz commented Aug 17, 2017

I think this will be solved by simply allowing suggestions as version 1 did, yes?

@arnoldnipper
Copy link
Contributor

I think this will be solved by simply allowing suggestions as version 1 did, yes?

What exactly do you mean by this?

@grizz
Copy link
Member

grizz commented Aug 17, 2017

Version 1 had forms to "suggest" new Facilities which then went to the AC to approve

@arnoldnipper
Copy link
Contributor

Wouldn't it simply need an extra button in the "Add Facility/Exchange" template to implement this? If ticked, an extra field pops up, where I can add the organisation where the Facility/Exchange belongs to

@arnoldnipper
Copy link
Contributor

@vegu / @grizz ... could you pls make proposal(s)

@eloos eloos self-assigned this Dec 14, 2017
@grizz
Copy link
Member

grizz commented Dec 16, 2017

I'd propose:

New 'Suggest' button on each entity, only available for a logged in and verified user. Allows the same as any other request, but doesn't set the org, which would then create an AC ticket in the queue. AC would have to verify the entity is valid, assign the correct org, and approve.

If it's not legit, AC would deny.

Sound reasonable?

@eloos
Copy link

eloos commented Dec 17, 2017

Vote: in favour of proposal of @grizz

@arnoldnipper
Copy link
Contributor

Vote: in favour of @grizz 's proposal

@mcmanuss8
Copy link
Contributor

+1 @grizz

@kay23
Copy link

kay23 commented Dec 22, 2017

Agreeing with @grizz's proposal. +1

@job
Copy link
Contributor Author

job commented Dec 27, 2017

+1 for what grizz suggested.

@thatchrisp
Copy link

+1 Grizz

@karumugham
Copy link

Yes on grizz's "suggest" proposal

@fhibler
Copy link

fhibler commented Jan 9, 2018

+1 on @grizz suggestion.

@nopedial
Copy link

nopedial commented Jan 9, 2018

+1

@vegu vegu added the Time:Major 4 - 10 hours work label Mar 9, 2018
@vegu
Copy link
Contributor

vegu commented Jul 24, 2018

Implemented in 2600ee4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AC Admin Committee Outreach Outreach Committee Time:Major 4 - 10 hours work
Projects
None yet
Development

No branches or pull requests