You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by GitBox <gi...@apache.org> on 2021/08/12 15:24:17 UTC

[GitHub] [whimsy] dave2wave commented on issue #125: How to file ICLAs

dave2wave commented on issue #125:
URL: https://github.com/apache/whimsy/issues/125#issuecomment-897732212


   This is an interesting topic and approach. One question to consider is if there is a way other than a contributor emailing secretary@? Perhaps there can be a web form somewhere that can handle the submission of the ICLA. This could be followed by the secretary handling any linkage / "deduplication" through assignment of an Apache ID.
   
   The web form could have the same information as the pdf/odt form only it can actually validate proper project names and apache ids. There would be three cases:
   
   1. Contributor. This would lead to the current workflow minus the filing of the ICLA which would automatically be done by the user's action.
   2. Committer filling out a new ICLA with access to my id. This is essentially like existing id.a.o and whimsy.a.o changes.
   3. Committer filling out a new ICLA to regain access to my id. There would be a special workflow with the secretary.
   
   A public web form would need some type of rate limiting / queueing to prevent abuse.
   
   I agree that naming the files with a hash protects PII. There would need to be some type of index building/validation which would include the metadata for existing/older ICLA files.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@whimsical.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org