Adding a POC must require an email address or phone number #1044
Comments
|
+1 |
|
May I have another +1 please, @peeringdb/pc |
|
how many existing and active accounts are affected? % without one or the
other?
+1 but not certain about priority.
…On Sat, Dec 11, 2021 at 20:42 Arnold Nipper ***@***.***> wrote:
May I have another +1 please, @peeringdb/pc
<https://github.com/orgs/peeringdb/teams/pc>
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#1044 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFA2YQRTVLBMRRJIA5KMIODUQP4YLANCNFSM5C77ZUEA>
.
|
|
@martinhannigan, this issue is not about fixing existing poc w/o (email and phone), but to make sure that new ones have an email or phone specified. For your questions: the API is your friend :) |
|
On Tue, Dec 14, 2021 at 2:48 AM Arnold Nipper ***@***.***> wrote:
@martinhannigan <https://github.com/martinhannigan>, this issue is *not*
about fixing existing poc w/o (email and phone), but to make sure that new
ones have an email or phone specified.
I think this makes sense. So +1, without the supporting data I suggest its
low unless there’s some support that it affects a large amount of data
historically. It also sounds easy to enforce something although details
matter.
For your questions: the API is your friend :)
If I’m submitting an issue and justifying it then it certainly is.
—
… You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1044 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFA2YQSZYEDRHUXEE4UMQNTUQ3ZDRANCNFSM5C77ZUEA>
.
|
|
+1 |
|
summary
|
|
yay |
vegu
added a commit
that referenced
this issue
Oct 11, 2022
vegu
added a commit
that referenced
this issue
Oct 11, 2022
Adding a POC must require an email address or phone number #1044 See merge request gh/peeringdb/peeringdb!321
Merged
grizz
pushed a commit
that referenced
this issue
Oct 11, 2022
* Add export tool to https://peeringdb.com/cp/peeringdb_server #586 * IX-F importer fails on nulled ipv4 / ipv6 properties in vlan_list entries #1244 * Adding a POC must require an email address or phone number #1044 * Selenium tests * ping django-peeringdb and rdap and poetry relock * linting * linting * remove selenium tests cruft * comment out django-peeringdb and search data mounts * regen docs
prithvimanikonda
pushed a commit
to prithvimanikonda/peeringdb
that referenced
this issue
Oct 12, 2022
* Add export tool to https://peeringdb.com/cp/peeringdb_server peeringdb#586 * IX-F importer fails on nulled ipv4 / ipv6 properties in vlan_list entries peeringdb#1244 * Adding a POC must require an email address or phone number peeringdb#1044 * Selenium tests * ping django-peeringdb and rdap and poetry relock * linting * linting * remove selenium tests cruft * comment out django-peeringdb and search data mounts * regen docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Currently, you can add a POC w/o email address or phone number. Having this information is what the POC is for
To Reproduce
Add a POC w/o email address and phone number yourself
Expected behavior
A POC must have an email address or (logical) phone number
Who is affected by the problem?
What is the impact?
useless entries
Are there security concerns?
no
Are there privacy concerns?
no
What are the proposed actions?
make email address or phone number mandatory
What is the proposed priority?
normal
Provide a rationale for any/all of the above
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: