Possible renaming of three Python lecture series

[jstac]

The names are now

1. Python Programming for Quantitative Economics
2. Introductory Quantitative Economics with Python
3. Advanced Quantitative Economics with Python

@thomassargent30 suggests we replace "Introductory" with "Basic".

That's option A:

1. Python Programming for Quantitative Economics
2. Basic Quantitative Economics with Python
3. Advanced Quantitative Economics with Python

Option B is to simply drop the word, so the three series are then

1. Python Programming for Quantitative Economics
2. Quantitative Economics with Python
3. Advanced Quantitative Economics with Python

Option C is

1. Python Programming for Economics and Finance
2. Quantitative Economics with Python
3. Advanced Quantitative Economics with Python

If we go with option C, we could put some material on option pricing into series 1, which would be fun. For example, Monte Carlo methods using GPUs!

[thomassargent30]

Dear John, I like options B and C. You choose please. I see your argument for adding finance. Ok with me. Thanks, Tom

…

On Sat, Apr 25, 2020, 5:33 PM John Stachurski ***@***.***> wrote: The names are now 1. Python Programming for Quantitative Economics 2. Introductory Quantitative Economics with Python 3. Advanced Quantitative Economics with Python @thomassargent30 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_thomassargent30&d=DwMCaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=hV4qLWg4zodvX-YQ-ETIbA&m=R5mmxQL8ZBXZUzBFTnPZ-RtDoRuwgHIhQko9w6Wf0_g&s=8ExG-3-lckoF4lq9aiY7L8fHEnJaxLWSQMlbmkNVXnU&e=> suggests we replace "Introductory" with "Basic". That's option A: 1. Python Programming for Quantitative Economics 2. Basic Quantitative Economics with Python 3. Advanced Quantitative Economics with Python Option B is to simply drop the word, so the three series are then 1. Python Programming for Quantitative Economics 2. Quantitative Economics with Python 3. Advanced Quantitative Economics with Python Option C is 1. Python Programming for Economics and Finance 2. Quantitative Economics with Python 3. Advanced Quantitative Economics with Python If we go with option C, we could put some material on option pricing into series 1, which would be fun. For example, Monte Carlo methods using GPUs! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_QuantEcon_meta_issues_2&d=DwMCaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=hV4qLWg4zodvX-YQ-ETIbA&m=R5mmxQL8ZBXZUzBFTnPZ-RtDoRuwgHIhQko9w6Wf0_g&s=Tx3re6s4G6OYqQWxlv5Ka5mSSNucXlVyNZtPqr6icyE&e=>, or unsubscribe <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AA63MTQQZZHDSIKYJ33OB2TRONXMRANCNFSM4MQ6X2MA&d=DwMCaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=hV4qLWg4zodvX-YQ-ETIbA&m=R5mmxQL8ZBXZUzBFTnPZ-RtDoRuwgHIhQko9w6Wf0_g&s=a3lR9D09tbOhcbrT5Tbh5I1SfYwWrIyge39h0fl4IQA&e=> .

[jstac]

Hi @mmcky @shlff @Harveyt47 @DrDrij @najuzilu, yet another of many recent changes, but -- unless any of you have strong objections -- we're going to go with option C.

@Harveyt47, would you mind to take the lead on this? It's just a matter of figuring out all the places where the names appear. Please do a careful search over all html / md / rst files in each of the three repos. @mmcky and @DrDrij can assist. I'll review the PRs too. Many thanks.

[mmcky]

@jstac can the url prefixes stay the same:

python-programing
python-intro
python-advanced

the issue with python-intro to python is that the python.quantecon.org currently hosts the landing page to unify the three linked to lecture-python-website. If you want to simplify that prefix in line with the title Andrij and I will need to review the infrastructure site for deployments.

[jstac]

Ah, yes, that's an issue. I would prefer to change it but I I feel like we've done a lot of chopping and changing. Let's leave it as is for now and then review some time down the road.

[DrDrij]

Good point @mmcky. Restoring the python.quantecon.org could fix some of the traffic and SEO - but we wouldn't have anywhere to house our landing page for the 3 lectures (unless it went on the org site homepage).

[jstac]

Well, if restoring python.quantecon.org would be helpful, then we could shift python-intro there and then the landing page for the 3 lectures could sit at quantecon.org/python-lectures?

[mmcky]

@DrDrij do you think this will help a lot given the current google search results I am getting now? Does google keep history like that? For me it makes sense to host the landing page at python.quantecon.org as it unifies the python pages together but I am happy to be overruled. python-intro won't make as much sense when we change the titles. I am a bit worried that people will go to python.quantecon.org and not find programming and advanced from the top symbol based navbar.

[jstac]

This is a tough one.

I'm feeling more and more @DrDrij 's point that the existing set up is too nested --- too many clicks to get down to one lecture. So what we could do is have python.quantecon.org point to the middle one, which is the page now at https://python-intro.quantecon.org/. From there, readers can either go ahead or switch to programming or advanced using the navigation bar with the Greek letters.

Now, as for @mmcky 's point, which is a very good one, we have to abandon these Greek letters and put in something more descriptive :-)

So how about "Programming", "Basic" and "Advanced" on that nav bar.

The three titles are still as per option C.

Finally, the existing landing page, currently at python.quantecon.org, gets moved to quantecon.org/python-lectures.

Are well all OK with this plan? The URL python-intro.quantecon.org will no longer be needed, but perhaps we can route everything heading to that URL or below into python.quantecon.org.

I'm sorry I didn't plan this better guys...

Oh yeah, and one separate thing, which I know I shouldn't put here: I wrote somewhere -- no idea where now -- that I'd like those big GH buttons down the bottom of each of the three lecture landing pages ("The source files for these lectues are blah blah") to be terminated. Instead, we'll just have "View source" to the left of "View commits" on each of the three pages. "View source" points at the corresponding GH repo.

[mmcky]

Roger that. Just a couple of questions:

1. The current landing page will just be linked from quantecon.org as an entry point right?
2. should the repo be renamed from lecture-python-intro to lecture-python to maintain conventions?

Here is a checklist of things that need to be updated and changed.

Infrastructure:

• update QuantEcon.aws.admin for build scripts for publishing (@mmcky)
• setup PR on org site to migrate python landing page (@DrDrij)
• redirect front page python lecture link to new landing page location (@DrDrij). This will be done implicitly when we sync lecture-python for the first time which will replace the index.html file.
• update python landing page with new link location for python-intro (@DrDrij)
• update top quantecon navbar with new location for python intro lectures (@DrDrij).
• update lecture-python-intro repository name to lecture-python (@mmcky)
• update lecture-python-intro.theme repository name to lecture-python.theme (@mmcky)
• update themes for all python repos to move from symbols to text (as above) (@DrDrij)
• archive lecture-python-website and migrate relevant issues to meta or org site is currently supporting the landing page once moved to the org site (@mmcky)

Lecture Repo:

• update lecture-python with any internal changes needed to remove Introductory (@Harveyt47)
• update lecture-python-programming with internal changes need for title change with Finance (i.e. conf.py, index.rst etc) (@Harveyt47)

Deployment:

• update sitemap.xml files and inform google (@DrDrij)
• add redirects from python-intro bucket to python

[Harveyt47]

Hey @mmcky should I hold off on Lecture Repo tasks until after Infrastructure tasks are complete. Not certain if order matters here.

There are four files in the lecture repo's which require the name changes.

1. conf.py which I believe is used for the naming of the pdf and its url
2. index.rst which the name is used for the title on the index page.
3. home.html which is the python.quantecon.org page we are changing.
4. about.md which is a file documenting the history of the project.

These are the only files that come up for me upon a name search for

1. Python Programming for Quantitative Economics
2. Introductory Quantitative Economics with Python
   in their respective repos.

[mmcky]

Thanks @Harveyt47. Please feel free to go ahead with setting up PR's that I can review. There shouldn't be many collisions with other changes so if the PR's stay open for a couple days that will be fine.

[jstac]

Really sorry @mmcky to be creating all that work 😬 . I hate to use your hugely valuable time on these changes but I think the name change is necessary and I'm glad we'll end up with a less nested set of pages.

The current landing page will just be linked from quantecon.org as an entry point right?

I'm not sure what the question is. Would you mind to rephrase?

should the repo be renamed from lecture-python-intro to lecture-python to maintain conventions?

I hate to say it but yes, I think we should bite the bullet and do it. Thanks @mmcky

[mmcky]

No problem @jstac - just getting some structure in place for the migration.

Would you mind to rephrase?

Sure. We have a current landing page hosted at https://python.quantecon.org which will be migrated to be a page on the org site https://quantecon.org/python-lectures. I guess my question is will that page only be linked from:

1. The quantecon.org front page from the "Quantitative Economics with Python" button
2. the Lectures -> Quantitative Economics with Python button in the top QuantEcon navbar.

Are you still happy with those as entry points?

Other uses will no doubt go directly to python.quantecon.org and then navigate sideways to either Programming or Advanced.

[jstac]

Yes, I'm happy with that. My hope is that users will visit the upper level landing page currently at python.quantecon.org only once. In that way we avoid the deep nesting.

[mmcky]

@DrDrij when you are free can we link up to review Infrastructure tasks for this migration. Thanks.