Renaming discuss.neos.io

The Neos Project Tools & Operations
#1

In todays General Meeting we briefly discussed about reconsidering “discuss.neos.io”. It is somewhat inconsistent as discuss it is a verb unlike other subdomains we use.
Personally I’d prefer to use “<tool>.neos.io” for infrastructure as it seems to be the most flexible solution (imagine, we’ve had “issues.typo3.org” instead of “forge.typo3.org”).

We already renamed the discourse subdomain recently, but now would be the chance to re-consider so please vote:

0 voters

Show results
#2

Even thoughI’m not looking forward to the work involved, I agree that discourse.neos.io is more consistent.

1 Like
#3

@bwaidelich ah, again: we can’t see who voted and we can’t make sure that only team members vote. What to do about that? Could you check if there’s some way to realize that in Discourse?

Polls for a closed group of voters
#4

Hey everybody,

I personally like “discuss” more than discourse :slight_smile: But don’t know why :wink:

All the best,
Sebastian

#5

What bugged me while using “discuss” was that sentences like “yeah, just let’s continue the conversation on discuss” didn’t come naturally. On “Discuss”? Or “discuss.neos.io”? “Let’s discuss it on discuss”? That’s where a tool-name is a much better fit.

1 Like
#6

I personally dislike tool.domain as it locks you to the tool, that’s imho a bad naming scheme. Even though we already use that, and switching all of them would be too much work :wink:

So I like discuss tbh, but won’t block any change as I rather see a consistent scheme.

#7

Tool names are not my favorit either. Purpose would be nicer :wink:

So either, discuss, discussion or conversation.neos.io

My 2cnts. :wink:

#8

I agree, but what if we decide to swap the tool (like we did with mantis > redmine > jira)?

#9

To me that wouldn’t make a difference: it is about the user experience, not about the tooling :wink:
You expect discussions / conversations, tooling should be as much in the background as possible and design should give a user the feeling of improvement when switching tooling…

Again: my opinion :wink:

#10

Henjo, Rens, I agree from a users POV high-level subdomains are much nicer.
But in any case we should have a consistent scheme which would mean that we’d have to move jira.neos.io, too.
And, more importantly: when we change tools or add complementary ones for the same purpose, we’d run into problems. Remember, we used to have bugs.typo3.org and had to add forge.typo3.org with the move from Mantis to Redmine. That was even more confusing to the user IMO.
And just replacing the domain is no option IMO because it would break all links. Well, maybe that could be worked around with some very clever redirects but mostly you want to have some kind of grace period with both tools working side-by-side (like we had with mantis, redmine & jira)…

1 Like
#11

Right, it seems there is no such feature currently for the discourse polls (and they’re lacking some other important features). In this case I didn’t see it as a problem that non-members can share their opinion though.

#12

The ideal situation and reality seems to be in conflict more often :wink:
Let’s take the best pragmatic approach we can think of - eyes ahead!

#13

that’s the key argument: as we experienced with Forge, we’ll need some transition time sometimes when two tools need to be accessible at the same time. So, while I agree with “discussions.*” etc being the nicer names, I still think that “discourse.neos.io” is better in this case and is consistent with the subdomains we already have. To be honest, I also wouldn’t like to invest the work at the moment to rename jira.*, crowd.* etc.

#14

So I guess this is decided with 45%:40% !?

#15

Not sure what to make of it. But I think, considering that there is no clear vote in favour of one alternative and looking the work involved, it would be fine to leave it as it is now.

4 Likes