878096 - Investigate migrating Popcorn Maker users to Webmaker users

Status: RESOLVED FIXED

(Webmaker Graveyard :: DevOps, defect)

Description

[Brett Gaylor [:brett]]

We have some tens of thousands of users of Popcorn Maker.

How do we make them webmaker users?  Particularly important for creating a series of featured projects.

Comment 1

[Brett Gaylor [:brett]]

From etherpad:    
best case scenario:
-existing popcorn maker user makes new webmaker.org account
-when they do, they're able to see their old popcorn maker projects
-Current problem: list of open projects is done via MakeAPI
-they're able to re-publish these and have them populate MakeAPI/work

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

How would you feel, Brett, about forcing Popcorn Maker users to be migrated to Webmaker users on their next login? I think that's the best / clearest way forward. The experience would be like:

 - user signs in (via Persona) to Popcorn Maker
 - we present a page that says "Congratulations, you're a Webmaker!", tells them that they get theirUserName.makes.org and that means their project links have changed
 - behind the scenes we quickly republish all of their makes through the MakeAPI
 - behind the scenes we also build redirects from old share URIs -> new share URIs from MakeAPI
 - ta-dah

Comment 3

[Brett Gaylor [:brett]]

beltzner yes, that is an even better-case scenario :)

Jbuck - when you investigate this, could you report into this ticket?

Comment 4

[Jon Buckley [:jbuck]]

Okay, Beltzner's experience is pretty spot on. The userbar that we have now in Thimble/Webmaker.org could provide steps 1 and 2. I think we need to run steps 3 and 4 as a one-off migration process though. The reason is that we're planning on having users open projects from the user bar, which is a list populated from the MakeAPI.

We'll create a script that publishes all projects in the butter prod DB to the MakeAPI. This will work, because we store the email address in the butter prod DB, and we can just re-use that for the MakeAPI.

I'm not sure how we should handle existing content on popcorn.webmadecontent.org. Should we just leave content on popcorn.wmc.o alone? Definitely the easiest solution, no code required! Should we write a redirect when the user publishes popcorn v1.0 project? Also possible, may provide the best UX too...

Comment 5

[Brett Gaylor [:brett]]

> We'll create a script that publishes all projects in the butter prod DB to
> the MakeAPI. This will work, because we store the email address in the
> butter prod DB, and we can just re-use that for the MakeAPI.

OK - file that bug, sir!

> 
> I'm not sure how we should handle existing content on
> popcorn.webmadecontent.org. Should we just leave content on popcorn.wmc.o
> alone? Definitely the easiest solution, no code required! Should we write a
> redirect when the user publishes popcorn v1.0 project? Also possible, may
> provide the best UX too...

Yes, just leave them as is.  Just to confirm, though - their work in app will still be the same, and when re-published, will go to makeAPI w/ new URL? That's best case scenario for real.

Comment 6

[Jon Buckley [:jbuck]]

(In reply to Brett Gaylor from comment #5)
> OK - file that bug, sir!

File bug 880569

> Yes, just leave them as is.  Just to confirm, though - their work in app
> will still be the same, and when re-published, will go to makeAPI w/ new
> URL? That's best case scenario for real.

Yes, that's correct