Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swapping the order of episodes on lists and loops #926

Merged
merged 7 commits into from
Jun 8, 2021

Conversation

maxim-belkin
Copy link
Contributor

See #496 for more info.

maxim-belkin and others added 4 commits April 6, 2021 12:42
It has been decided (#453)
that it is better to describe Python lists before loops. This is
the first commit that simply renames the episodes to achieve the
desired order.

Further work is necessary to ensure that concepts from the
episode on loops are not used in the episode on lists.
@maxim-belkin maxim-belkin requested review from annefou and ldko May 31, 2021 18:10
Copy link
Contributor

@ldko ldko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the swap looks good. I noticed a few minor things that we might want to change.

_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/04-lists.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/04-lists.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
_episodes/05-loop.md Outdated Show resolved Hide resolved
maxim-belkin and others added 2 commits June 4, 2021 09:22
Co-authored-by: Lauren Ko <lauren.ko@unt.edu>
Co-authored-by: Lauren Ko <lauren.ko@unt.edu>
@maxim-belkin
Copy link
Contributor Author

Thank you, Lauren. All good suggestions/edits.

Copy link
Contributor

@ldko ldko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I see the there is a build failure, but it doesn't look specifically relevant to the changes here. make lesson-check-all outputs what I would expect locally.

Thanks very much for wrapping this up @maxim-belkin ! I imagine a lot of people will be glad to have this change in the lesson. Thanks to everyone who worked on it!

Copy link

@annefou annefou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is excellent! I also don't know why build fails: it works well for me locally.

I am really looking forward to be teaching this "new" lesson!!! thanks @maxim-belkin

@maxim-belkin
Copy link
Contributor Author

The build fails because of the missing github-pages gem in Travis. I guess the fix is to add github-pages to the list of Gems we install on line 10 in .travis.yml

- gem install json kramdown jekyll bundler

but that's not critical because the main test -- GitHub Action "Website" -- passes.

As we discussed previously, we need to announce this change. Do you think we should do it before or after merging this PR?

@ldko
Copy link
Contributor

ldko commented Jun 4, 2021

As we discussed previously, we need to announce this change. Do you think we should do it before or after merging this PR?

On the issue you mention announcing it on the Carpentries' Discuss channel. I am not sure what that refers to :D. Will a lot of people see it there? It does make sense to give notice though, in particular because of the accounts mentioned in this recent RFC. It seems to me not waiting too long to merge it though would be good, so we don't lose hold of it again. Does it also make sense to do a tag/release for the version before we merge the change?

@annefou
Copy link

annefou commented Jun 4, 2021

It is a good idea to do a tag/release for the version before merging. For announcing it: I am not sure what is best but announcing it in the Carpentries' Discuss channel seems a good idea (I guess many people will be reached).

@maxim-belkin
Copy link
Contributor Author

Does it also make sense to do a tag/release for the version before we merge the change?

My understanding is that lesson releases are coordinated across The Carpentries org(s) and are performed by The Carpentries' staff.

@fmichonneau, what are our options here?

@maxim-belkin
Copy link
Contributor Author

maxim-belkin commented Jun 5, 2021

On the issue you mention announcing it on the Carpentries' Discuss channel. I am not sure what that refers to :D

I was talking about https://carpentries.topicbox.com/ . For example, this is our previous Request (Call) for Contributions: https://carpentries.topicbox.com/groups/discuss/Tb9e8878a4c4c4fa8-M281b5e6b472544bacf432926/call-for-contributions-visuals-images-figures-plots-charts-etc

@maxim-belkin maxim-belkin changed the title Swap the order of episodes on lists and loops Swapping the order of episodes on lists and loops Jun 8, 2021
@maxim-belkin maxim-belkin merged commit 90446c5 into gh-pages Jun 8, 2021
@maxim-belkin maxim-belkin deleted the lists-loops branch June 8, 2021 19:38
zkamvar pushed a commit that referenced this pull request Apr 21, 2023
Swapping the order of episodes on lists and loops
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants