#538 Create a New Fedora Acceptable Use Policy
Closed: resolved 3 months ago by jflory7. Opened 8 months ago by jflory7.

Summary

We need to create a new Fedora Acceptable Use Policy (AUP) to serve as the Terms and Conditions for our Matrix server and potentially other services.

Background

We received a notification from our Element Matrix Services (EMS) provider about an upcoming migration to a new authentication system. This will finally unblock Element X client use for fedora.im Matrix accounts. This migration, planned for June or early July, requires us to provide a URL for our Terms and Conditions, as the provider can no longer host our custom terms. This presents an opportunity to establish a formal AUP for Fedora-hosted services, starting with Matrix.

Details

To proceed with the server migration, we must create and host our own Terms and Conditions. The proposed course of action is to:

  1. Draft a new Fedora Acceptable Use Policy: This document will define the terms of use for the Fedora Matrix service.
  2. Ensure Compliance: The new AUP must be compliant with the existing Fedora Privacy Policy.
  3. Get Council Support: Members of the Fedora Council need to support the drafting and approval process for this new policy by Red Hat Legal.
  4. Host and Implement: Once finalized, the AUP will be hosted with Fedora's legal docs, and the URL will be provided to EMS to unblock the Matrix migration.

Outcome

A new, Council-approved Acceptable Use Policy for the Fedora Matrix server will be created and implemented, ensuring compliance and allowing the critical server migration to proceed.


Can the required AUP url just be the existing CoC url?

We already use the CoC url in the FAS login screen.

Metadata Update from @jspaleta:
- Issue assigned to jspaleta

7 months ago

@jlovejoy @ref There is a PR waiting for feedback from you both if you could take a look and ack/nack at your earliest convenience please.

Metadata Update from @amoloney:
- Issue untagged with: Next Meeting

7 months ago

This was discussed in todays meeting.

Once the PR is reviewed and ackd it can be merged and this ticket can be closed as complete. Any help unblocking this final step would be very appreciated.

AUP is now live.

I've filed a ticket with element support to make them aware at their request.

I believe that takes care of the council level blocking item around infrastructure plans to transition the matrix instance.

Sorry I spoke to soon.

Element needs to be informed via the matrixadmin@fedoraproject.org, which is probably an email alias, that I am not on. Need to sort out who has access to that alias, so they can drive the information to element in a way that is actionable because they need some assurance the request is valid. A ticket from my email account is not sufficient.

This policy is now published and in effect:

https://docs.fedoraproject.org/en-US/legal/chat-aup/

I am closing this ticket as resolved. Thanks @jspaleta for working on this one.

Metadata Update from @jflory7:
- Issue close_status updated to: resolved
- Issue status updated to: Closed (was: Open)

3 months ago

Log in to comment on this ticket.

Metadata