874986 - Ensure /projects links points to learning projects

Status: RESOLVED FIXED

(Webmaker Graveyard :: Thimble, defect)

Description

[Pomax]

Right now we have learning projects (partner projects we made for thimble last year, london zoo etc) sitting in the thimble repository, where will these move?

Also, if they move somewhere else, how do we load their data into thimble? (we load from template right now, node-side, so if we move them webmaker.org instead, things get more complicated)

Comment 1

[Jon Buckley [:jbuck]]

Why not just leave them in the thimble.wm.o repository? Leave existing links working as-is, right?

Comment 2

[Pomax]

existing links no longer work, though. However, the learning/content team mentioned they'll be curating the projects to determine which to keep and which to prune, I suspect we can close this ticket in lieu of their work.

Comment 3

[Pomax]

setting Brett as a needinfo, to see whether we can close this or need to keep it open (might need to be moved to general webmaker if we do? not sure)

Comment 4

[Brett Gaylor [:brett]]

Will decide on these this week.

Comment 5

[Brett Gaylor [:brett]]

So this shouldn't be thimble specific.  We should pass through all webmaker.org/projects and decide on a list of what we want to keep

Lets make a list here and decide this week
https://etherpad.mozilla.org/webmakerv2contentmigration

Adding Kat, Jacob, Paula.

Comment 6

[Ross Bruniges [:boozeniges]]

I made a google doc that might make the decision process even easier - https://docs.google.com/spreadsheet/ccc?key=0Ao9wg_o18NI1dHJGc0h4bFhrb2xtd1lmTWwwNlJfdEE#gid=0

Comment 7

[Jacob [:Jacob]]

My initial reaction is that we should keep the ones that we made unless there's a reason not to?

We'll have to manually submit them as published makes and then copy/paste/format the instructions as a Thimble tutorial.

I can get started on it once the site is ready for submissions

Comment 8

[Brett Gaylor [:brett]]

Copied Ross' migration spreadsheet to our burndown google doc
https://docs.google.com/a/etherworks.ca/spreadsheet/ccc?key=0AkvvpcilLIOndFE1MURBQjRFcjV3cHlpVElDVmhGRHc#gid=5

Pushing this till next week.

Comment 9

[Kat Braybrooke [:codekat]]

Hi all - will be sending email out, but Paula and I have realised we don't fully understand what will be lost and what will stay during this migration - and we're also realising an email will need to be sent to mofo-all to ensure nothing is lost that we've missed in the migration spreadsheet.

Comment 10

[Brett Gaylor [:brett]]

Pomax, we've made a list here:
https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AkvvpcilLIOndFE1MURBQjRFcjV3cHlpVElDVmhGRHc#gid=0

However, one thing I'd like to do is keep the thimble landing page at thimble.webmaker.org and just leave the existing links, so that people who use that can still depend on that list.

I understand from your comment that published makes will be fine as is, but that editing urls for legacy content will not, ie https://thimble.webmaker.org/en-US/projects/o2_helloworld/edit

What would be the best solution, then, for ensuring that these legacy links still work?  There are orgs that actively use these URLS (the one above is an example) and we can't have them dissapear.

Is there a simple redirection strategy that would work for everything in the repo?

Comment 11

[Ross Bruniges [:boozeniges]]

:jp - as it seems like we know the URLs we want to redirect and where we want them to go is this something that could be set up at the load balancer level?

Failing that could we set up something like this for the Thimble app - https://github.com/paulosman/batucada/blob/master/apps/projects/views.py#L33-L53

Comment 12

[Jon Buckley]

Unfortunately, AWS ELB isn't that smart :(

Why we should try to go to all this trouble to have two copies of thimble running indefinitely? Why not just have thimble-node do everything that thimble-django does? We can even import the old data.

Comment 13

[JP Schneider :jp]

+1 to that idea jbuck.  I'd love to see us figure out a conversion path for these projects and allow ourselvesa chance to sunset old thimble.

Comment 14

[Pomax]

We don't need a "conversion path", we already have all those projects in new thimble, in their own directory as dedicated templates. We had that working 2 pretty much on week one. So: we can just make the new instance accept the old URL routes, and then load up the relevant project using new thimble if we want, quite easily.

However, I'm not quite sure what you mean with keeping the old landing page (were there any designs for that?). Do we need a landing page for thimble.webmaker.org that lists all makes with tag "super special we-approved-these projects" that can then be clicked through? Because right now the base url opens up Thimble itself.

Comment 15

[Brett Gaylor [:brett]]

OK, was just confused by this original comment: 

(In reply to Mike "Pomax" Kamermans [:pomax] from comment #2)
> existing links no longer work, though. However, the learning/content team
> mentioned they'll be curating the projects to determine which to keep and
> which to prune....

If we can just load 'em in thimble node we are fine.

The problem we're solving here is that there are an unknown # of orgs using thimble as curriculum, and we don't know which projects they use.  The likely answer is "not many", but its the edge cases that would be the problem.

We can leave it designed as is for June 15th, and do some simple cleanup that indicates there are a list of "legacy projects".  But we won't point to this UI within webmaker.org and we'll sunset this landing page over time.

If by leaving those projects in the repo, and simply building as is, we get new links to these projects, we're good.

Comment 16

[Pomax]

yeah, we got that covered (there's a /projects link on new thimble that lists all the "learning projects" we had)

Comment 17

[Pomax]

that said, we're not surfacing that link atm, but we can trivially make the old style "/en-US/..." links point to the new project locations and have everything work as far as the users/orgs are concerned.

Comment 18

[Pomax]

Attachment: https://github.com/mozilla/thimble.webmaker.org/pull/102

this adds the legacy route from current thimble, using the /en-US/projects/{name}/edit URI fragment.

Comment 19

[Pomax]

landed the patch that enables the old style URLs so that they resolve correctly under new Thimble. I think that's all we really needed from this ticket?

Comment 20

[Pomax]

resolved.