-
Notifications
You must be signed in to change notification settings - Fork 0
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
Is it PloneIntranet, plone.intranet, ploneintranet or Plone Intranet? #10
Comments
Depends on the context. I think PloneIntranet and plone.intranet should never be used. "ploneintranet" makes sense in the context of package names. Otherwise "Plone Intranet". |
Agreed. I would use "Plone Intranet" where ever possible. |
It's unfortunate that the IRC channel is #plone.intranet (and not #ploneintranet), I guess that introduces some confusion. |
blame @mattss for the IRC channel name |
Should we change the IRC channel? I'll fix up the docs. |
+1 for changing channel name, but we'll need to have everyone informed. |
#10 Use consistent naming for Plone Intranet
All variants are currently used in the docs.
The text was updated successfully, but these errors were encountered: