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
Comments
@arnoldnipper suggests that the same applies to IXPs |
@arnoldnipper said:
|
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. |
I think this will be solved by simply allowing suggestions as version 1 did, yes? |
What exactly do you mean by this? |
Version 1 had forms to "suggest" new Facilities which then went to the AC to approve |
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 |
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? |
Vote: in favour of proposal of @grizz |
Vote: in favour of @grizz 's proposal |
+1 @grizz |
Agreeing with @grizz's proposal. +1 |
+1 for what grizz suggested. |
+1 Grizz |
Yes on grizz's "suggest" proposal |
+1 on @grizz suggestion. |
+1 |
Implemented in 2600ee4 |
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.
The text was updated successfully, but these errors were encountered: