potiuk commented on PR #2:
URL: https://github.com/apache/comdev/pull/2#issuecomment-4431826453

   > > Thank you for the mention @potiuk @sebbASF is not wrong about this, and 
we have to take this into consideration.
   > > I will need a few days to read the PR and respond to this properly.
   > 
   > I was wondering if you have been able to give this any more thought? This 
is one of several mcp tools that we would like to add to this repo, and I don't 
want to get into git conflict hell if I can avoid it. Thanks.
   
   Indeed  @grobmeier . Also I have proposed this RFC 
https://cwiki.apache.org/confluence/display/ASFP/RFC-AI-0003+privacy-aware+LLM+routing+for+foundation+private+information
 - based mainly of the current implemetnation of privacy gates and guards in 
the current "Steward (to be renamed)" implementation  - which implements I 
think set of quite "strict" options we might have:
   
   * local LLMs for accessing PII-containing data
   * privacy Gate that strips out/anonymises PII
   * dedicated llms (for example llms.apache.org) that are known to be 
privacy-compliant
   
   And I have a reference implementation of it in 
https://github.com/apache/airflow-steward/tree/main/tools/privacy-llm -> 
including implementation of privacy redactor and checker. The RFC is open for 
comments and adjustments, and also it is pending the policy. 
   
   But I think in this context - leaving the opt-in option in PonyMail to 
enable access to certain "private" mailing list is a reasonable idea - 
providing that people use one of the above options. It's pretty "neutral" when 
it comes to which privacy protection you will use - and in the current version 
it blocks all private lists by default, you need to opt-in to enable them.
   
   I think We should be able to merge it - without waiting for policy to be 
finalized.
   
   WDYT @grobmeier ?


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to