It's a pretty huge deal choosing the same namespace as the also very popular ckeditor module. It's not an "incompatibility", it's a poor engineering and design choice that needs to be remedied asap.

Comments

reubenavery’s picture

reubenavery CreditAttribution: reubenavery commented

I'd be happy to do this for you and make it a 2.0 branch.. but I'm somehow expecting resistance to this.

why fellas, why???? why you do this???

jenlampton’s picture

jenlampton
she / her
CreditAttribution: jenlampton commented

I don't really see the problem here. No one would ever have both the ckeditor module and this module on their site at the same time, so, where's the issue?

The reason this module is named ckeditor is because it was the starting point for the ckeditor module that's now in Drupal 8. Keeping the same name for both will mean backporting/forward porting of features and bugfixes goes much faster.

davidneedham’s picture

davidneedham
he/him
CreditAttribution: davidneedham commented
Category: Bug report » Task
Priority: Critical » Normal
Status: Active » Closed (works as designed)

It's probably moot at this point, but I don't see a problem either for the same reasons. I've been using this module extensively and have never run into an issue with the name.

Since this name was intentional for migration, and given the time since last comment, I'm going to go ahead and close this with works as designed.