Reword the call to action in the data sovereignty section
This commit is contained in:
parent
f880710236
commit
61eadfb105
|
@ -300,11 +300,10 @@ also the principal developer and operator of PyPI. For these reasons, a
|
||||||
solution for the problem of data sovereignty has been deferred and is
|
solution for the problem of data sovereignty has been deferred and is
|
||||||
considered outside of the scope for this PEP.
|
considered outside of the scope for this PEP.
|
||||||
|
|
||||||
If someone for whom the issue of data sovereignty matters to them wishes to
|
The data sovereignty issue will need to be addressed by someone with an
|
||||||
put forth the effort, then at that time a system can be designed, implemented,
|
understanding of the restrictions and constraints involved. As the author of
|
||||||
and ultimately deployed and operated that would satisfy both the needs of non
|
this PEP does not have that expertise, it should be addressed in a separate
|
||||||
US users that cannot upload their projects to a system on US soil and the
|
PEP.
|
||||||
quality of user experience that is attempted to be created on PyPI.
|
|
||||||
|
|
||||||
|
|
||||||
Rejected Proposals
|
Rejected Proposals
|
||||||
|
|
Loading…
Reference in New Issue