πŸ‡ΊπŸ‡ΈUnited States @ivanstegic

Account created on 21 May 2008, over 16 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

@mindaugasd Please https://ten7.com/blog/post/just-say-drupal for rebuttal to your comments. I'll say though that the post now feels a little outdated with this conversation, so please take it with general intention of simplification.

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

We are bike shedding this without a wide view of the world.

I keep coming back to the idea that this is meaningful for our community only.

Why isn't this as simple as calling our product "Drupal" and having it be powered by "Drupal Core" ? We might not need to replace the Starshot name, maybe we just need to remove it.

I am still in favor of

  • Drupal Starshot -> Drupal
  • Drupal 8, 9, 10, 11, etc -> Drupal Core
  • Drupal 7 -> Legacy Drupal
πŸ‡ΊπŸ‡ΈUnited States ivanstegic

@nicxvan you said "Someone new to Drupal landing on this page would only see the product Drupal CMS" and I think it's herein that lies the problem.

Someone new to this page should be introduced to "Drupal" and not to "Drupal CMS"

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

I think we are painting ourselves into a really problematic hole by adding the label "CMS" and bifurcating our product even further. Additional thoughts here on the related post: https://www.drupal.org/project/starshot/issues/3452281#comment-15634164 β†’

I think this issue should be blocked until a real decision on the final product name is made.

If Starshot launches as "Drupal CMS" then we will have all of these:

  • Drupal CMS
  • Drupal Core
  • Drupal 7
  • Drupal 10.2 (and 9, and 8 ofcourse)
  • Next iteration of Drupal 11

Adding "Drupal CMS" to the mix just causes additional confusion and we really should be simplifying as a product.

If Starshot launches as "Drupal" that uses "Drupal Core" and "Legacy Drupal" is Drupal 7, then the story becomes so much easier to tell.

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

Can we just use the word Drupal to describe our product and be done? This post applies now more than ever: https://ten7.com/blog/post/just-say-drupal

Here is what I think we need to do:

  • Use the Starshot moniker as a way to rally around a temporary push
  • When time runs out, launch Starshot as the "default download" as @Dries put it and just call it Drupal
  • Tweak packagist.org/packages/drupal/drupal to NOT say abandoned
  • Continue to THINK of the HEAD of Drupal right now as "Drupal Core" (easy)
  • Realize that Starshot uses "Drupal Core" AND "Drupal Contrib" and that calling it "Drupal" is just fine and people in the real world won't care

I also think we need to rethink the marketing page in the wireframes that @Gabor posted about. Here is how I would frame it: https://ten7.im/2zyds1rL

(My edited image is uploaded here too.)

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

@Gabor I think that means we are splitting Drupal into two things. You can't have "the new default download of Drupal" and "Drupal" at the same time.

πŸ‡ΊπŸ‡ΈUnited States ivanstegic

I was wondering if there was a technical reason why `drupal/drupal` would not be possible, and it seems to me that this is the perfect thing to call it. When you go to https://packagist.org/packages/drupal/drupal the first thing you see is a page that says the "This package is abandoned and no longer maintained." -- this is really awful for us, I think. From a marketing perspective, `drupal/drupal` should be our best and brightest. And the `drupal/core-recommended` should be the underlying power of the product.

πŸ‡ΊπŸ‡ΈUnited States ivanstegic
  1. If this is the new "default download" of Drupal, then the name should be just "Drupal", see @Dries LinkedIn Post here https://www.linkedin.com/posts/buytaert_starshot-activity-72015734272273...
  2. "Core" means nothing to the outside world, and "CMS" is redundant.
  3. I agree that Starshot should not be mentioned
  4. I think as technical folk, we like to categorize and label things and so ofcourse we want to go down the road of naming it "Core" or "CMS"
  5. I also think it's OK to have it be "Drupal" and "Drupal" and not "Drupal CMS" and "Drupal Core" or "Drupal API" or "Drupal Framework"
  6. Maybe think about this as "Drupal for Marketing" and it uses "Drupal for Devs" but it's all "Drupal"

One more thing... if this is the and it's just a package of certain things that we deem best in class, then it SHOULD be called Drupal. Otherwise, when this launches, we will have done ourselves a disservice and bifurcated our beloved product into two. I see no other option but that "Drupal Starshot" is just "Drupal"

πŸ‡ΊπŸ‡ΈUnited States ivanstegic
  • This would be an easy, unobtrusive addition to core
  • There's already a module that could be used, why complicate this issue?
  • I propose it's just a text file with an agreed upon format
  • If you want to keep it up to date, or build it automatically, let's create another issue for it?
  • I'm sorry if I am missing something, it feels like this is an easy change.
Production build 0.71.5 2024