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
Comments
|
Also #1948. Use it in the page that describes it. |
|
From my comment here:
|
Well, maybe that's not right? I don't know. |
|
We kind of have to agree on a name. Pod 6 rhymes nicely with Perl 6. We
can't keep calling it Pod or Perl 6 Pod, as in, you know, this thing we use
with, you know, this thing.
Pod 6 I guess is as good as any other; it's better than POD or Pod, better
than Pod6 and better than Perl 6 Pod, which is what was being used so far.
We can't just delay naming things until the Perl 6 naming debate is
settled, which might be never. And when it's done, it will be the time to
reckon... and refactor.
|
|
Well, the point is that maybe we should be calling it “Perl 6 Pod” for now. |
|
(because that leaves enough room for the upcoming alias) |
|
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. |
|
This probably should remain open. |
|
So will everyone agree on Perl 6 Pod? |
|
I'm ok with Perl 6 Pod |
|
Should we open this back now? Pod6 or Pod(non-breaking-spce)6? |
|
This is related, but there I propose some crazy changes. |
|
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. |
Let's try and call it
Pod 6everywhere, including the non-breaking space before the 6The text was updated successfully, but these errors were encountered: