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

auto-connect E-mail addresses to maintainer IDs #373

Closed
DandelionSprout opened this issue Aug 22, 2018 · 2 comments
Closed

auto-connect E-mail addresses to maintainer IDs #373

DandelionSprout opened this issue Aug 22, 2018 · 2 comments
Labels
directory-data changes to basic FilterLists data ops processes, devops, infrastructure wontfix will not be worked on

Comments

@DandelionSprout
Copy link
Contributor

I got an idea.

If a filterlist in FilterList.json has both an E-mail address and is listed in FilterListMaintainer.json, then all other lists with the same E-mail address would be auto-assigned the same maintainer ID. This will help with avoiding cases where lists occasionally aren't accredited to specific maintainers, when most of their other lists are.

This can to a smaller degree also be done with the existing emailAddress field in Maintainer.json.

@DandelionSprout DandelionSprout changed the title connect E-mail addresses to maintainer IDs auto-connect E-mail addresses to maintainer IDs Aug 22, 2018
@DandelionSprout
Copy link
Contributor Author

DandelionSprout commented Aug 22, 2018

Alternately (or additionally), maintainer IDs could be generated based on E-mail addresses. It'd save the hassle of dealing with Maintainer.json and FilterListMaintainer.json, although it'd mean that lists would be accredited to E-mail addresses (i.e. "More lists by example@example.com:") until proper names are added to those maintainer IDs later on.

@collinbarrett collinbarrett added enhancement ops processes, devops, infrastructure directory-data changes to basic FilterLists data labels Aug 22, 2018
@collinbarrett
Copy link
Owner

collinbarrett commented Aug 24, 2018

I like the idea, but should probably be addressed as part of #372 . Not sure it carries priority enough to warrant custom dev time outside of that, and it would be obsoleted by #372

@collinbarrett collinbarrett added wontfix will not be worked on and removed wontfix will not be worked on labels Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
directory-data changes to basic FilterLists data ops processes, devops, infrastructure wontfix will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants