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

Standardize Pod name #1923

Closed
JJ opened this issue Apr 13, 2018 · 13 comments
Closed

Standardize Pod name #1923

JJ opened this issue Apr 13, 2018 · 13 comments
Labels
good first issue If you want to dive in, this would be a good place to start

Comments

@JJ
Copy link
Contributor

JJ commented Apr 13, 2018

Let's try and call it Pod 6 everywhere, including the non-breaking space before the 6

JJ added a commit that referenced this issue Apr 13, 2018
@JJ JJ added the good first issue If you want to dive in, this would be a good place to start label Apr 14, 2018
@JJ
Copy link
Contributor Author

JJ commented Apr 21, 2018

Also #1948. Use it in the page that describes it.

@AlexDaniel
Copy link
Member

From my comment here:

Uh, actually, maybe not yet. At least not without a deep discussion.

Some random thoughts:

The thing is that we will have an alias eventually. Let's say it'll be “AAA”. With current naming of pod, it'll then be “Perl 6 Pod” and “AAA Pod” depending on context. Yes, two different names for the same thing, but that's what we want (sort of).

So if we rename it to “Pod 6”, then I guess it'll stay “Pod 6” in both cases, which is nice… But then, what is “6”?

I guess “pod6” will work nicely with “6lang”, but then why not “6pod”? :)

@AlexDaniel
Copy link
Member

But we're using Pod 6 pretty much everywhere else.

Well, maybe that's not right? I don't know.

@JJ
Copy link
Contributor Author

JJ commented Apr 21, 2018 via email

@AlexDaniel
Copy link
Member

Well, the point is that maybe we should be calling it “Perl 6 Pod” for now.

@AlexDaniel
Copy link
Member

(because that leaves enough room for the upcoming alias)

@JJ
Copy link
Contributor Author

JJ commented Apr 21, 2018

I'd like to hear more opinions about this. Even if we leave the page title that way, it's kind of cumbersome to say Perl 6 Pod every time you mention it on the documents. We can clarify in the documentation that when we say "Pod 6" we actually mean "Perl 6 Pod" and then change that last thing to whatever, when (or if) that change happens.

@JJ
Copy link
Contributor Author

JJ commented May 4, 2018

This probably should remain open.

@JJ JJ removed the JJ TPF Grant label May 14, 2018
@JJ
Copy link
Contributor Author

JJ commented Jun 7, 2018

So will everyone agree on Perl 6 Pod?

@Kaiepi
Copy link
Collaborator

Kaiepi commented Jun 7, 2018

I'm ok with Perl 6 Pod

@JJ
Copy link
Contributor Author

JJ commented Aug 7, 2019

Should we open this back now? Pod6 or Pod(non-breaking-spce)6?

@AlexDaniel
Copy link
Member

This is related, but there I propose some crazy changes.

@AlexDaniel
Copy link
Member

Also, I think it is universally POD6 right now and nobody writes it with a nbsp, so there's no point in trying to force that. But as I mentioned, maybe the “pod” part of the name needs to be rethought too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue If you want to dive in, this would be a good place to start
Projects
None yet
Development

No branches or pull requests

3 participants