Launchpad should require agreement to terms of use at account creation

Bug #240900 reported by Matthew Revell
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

When creating a new Launchpad account, we should require the user to agree to our terms of use.

We should also keep track of which version of the ToS each user has agreed to and then email users with a change summary each time we make a change.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

<matsubara> I already confirmed it, but I'm curious, what motivated that report?
<mrevell> Someone emailed <email address hidden> to say that Launchpad didn't tell them that it uses cookies. I sent them a link to the Privacy and Data Retention Policy but then realised that we don't actually ask people to agree to our terms of use.

Changed in launchpad:
status: New → Confirmed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

These requirements were previously mentioned in bug 141062.

Revision history for this message
Matthew Revell (matthew.revell) wrote :

Thanks Matthew. I think it's worth keeping this bug report, though, as bug 141062 has been marked fix released without dealing with the need for people to agree to the ToS.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Yes, fixing this bug probably would involve reversing the fix to bug 141062.

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → Wishlist
status: Confirmed → Triaged
Curtis Hovey (sinzui)
visibility: private → public
Revision history for this message
Curtis Hovey (sinzui) wrote :

I am not sure this is valid now that all accounts in Ubuntu's SSO system. The account exits before launchpad is used. We may be able to ask for an agreement whe the profile is added for the account, but what of the case where the profile is created by import? I think we would need a model change, something like the Ubuntu CoC added to the profile to verify the person agrees.

Revision history for this message
Robert Collins (lifeless) wrote :

I think we may need a model change too. I think you are using the CoC as an example; its a bit more complex than we need here - probably just a (toc version, toc_accepted_date) in the Person would do.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.