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

Add baby_fto. #144

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Add baby_fto. #144

merged 1 commit into from
Jan 9, 2025

Conversation

lgarron
Copy link
Member

@lgarron lgarron commented Jan 9, 2025

I'm currently using the name baby_fto in Twizzle / scramble.cubing.net / timer.cubing.net, because:

  • I don't think the historical name (Skewb Diamond) is particularly intuitive if you're not a puzzle builder, and having the full prefix "Skewb" might cause UX/coding issues.
  • "2×2 FTO" isn't quite fully established, and it's unclear if this will match generalizations for other puzzles in the future.

But we may want to figure out a scheme for the latter, e.g. 2x2_fto or fto_2_layer

@jfly
Copy link
Member

jfly commented Jan 9, 2025

I don't have any useful feedback on the slug, sorry. I don't feel bad about having to change this in the future.

@lgarron
Copy link
Member Author

lgarron commented Jan 9, 2025

I don't have any useful feedback on the slug, sorry. I don't feel bad about having to change this in the future.

Alright, I'm okay with that as well, thanks!

Aliases are easy to implement, and I think we can figure out braking name change releases in the future if needed.

@lgarron lgarron merged commit 0774d53 into main Jan 9, 2025
2 checks passed
@lgarron lgarron deleted the baby_fto branch January 9, 2025 09:03
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.

2 participants