My intent was for it to be scoped to #1 in this summary
smustgrave → credited hestenet → .
smustgrave → credited hestenet → .
hestenet → created an issue.
hestenet → created an issue.
I've updated the button. Thank you!
hestenet → created an issue.
Closing this issue for now - can be reopened the next time an active educational message or warning is needed.
That isn't necessarily a final opinion btw - just the initial feedback I received, will circle back if I hear more.
This has been raised to the provisional new DA Innovation Working Group lead for input and consideration - but the current thinking is that it doesn't necessarily add value for the DA itself - as we already have tools and process for fundraising in more traditional ways. Folks are not convinced that it would really increase the overall engagement in fundraising, but possibly just create a confusing landscape of where to do fundraising.
This might be better served with an experimental, community organized kick-off to see if it has legs.
This has been raised to the provisional new DA Innovation Working Group lead for input and consideration for the DA's engineering roadmap. I will let this group know when I hear back.
gusaus → credited hestenet → .
I agree with the bump to major.
There is an option issue in Mozilla's tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1925236
gábor hojtsy → credited hestenet → .
gábor hojtsy → credited hestenet → .
This would be helpful for Drupal.org's site migrations and the time period that we have Modern Drupal and D7 running in parallel.
rachel_norfolk → credited hestenet → .
hestenet → created an issue.
hestenet → created an issue.
Thanks folks! As @fjgarlin mentioned - part of de-emphasizing the all organizations view was to further emphasize the service providers who are part of the DCP program. The integrity and magnitude of the reward for being both project and financial contributors is important
... but of course - the all organizations view doesn't just show service providers, it also shows end-users and a variety of other types of organizations.
There's good reason for people to want to be able to see how those types of organizations are contributing, to evaluate potential employers, or to find providers in countries that don't have any DCPs.
Navigating that isn't necessarily difficult but it is delicate - so I may need to regroup with some of the board stakeholders involved in managing the DCP program and with some of the other leadership folks on the DA side.
Either of the proposals above (a more prominent button/link - or - a placement in the main menu somewhere) might work - just want to make sure everyone who has put thought into that program has thought it through and weighed in.
I'll report back.
hestenet → created an issue.
gábor hojtsy → credited hestenet → .
This user has been temporarily suspended until they respond to my outreach:
https://www.drupal.org/u/sunil-jolapara →
I have also applied a negative 200 credit penalty for a minimum of 30 days and sent a notification to the company.
I will work with them from here based on their next reply.
@deviantintegral
Thanks for the several points of feedback.
Re: # of Drupal sites, we have more reliable data than any of the web crawler based tools like BuiltWith or Wappalyzer in the form of the usage stats we get when sites phone home for updates:
https://www.drupal.org/project/usage/Drupal →
Lots of great feedback from many people in this thread. I won't respond to each one here, but will pass on to everyone involved and create child issues where needed.
Thank you all!
I'm very glad to see that most feedback is 'this is great, but we can make it better' instead of in fundamental disagreement with the direction.
@e0ipso - Thanks for the feedback.
I'll quickly address 2 points, but I think it'd be prudent for larger discussions of any feedback items to branch off until full child issues if needed.
Re: the companies we choose to represent Drupal, esp Nestlé. On a personal level I have similar concerns, and I think it's important to question who we choose to associate the Drupal brand with. On a technical level it's a hugely impressive case study in scale, editorial process, and internationalization - so I can understand why it was chosen. I think this is worth escalating to folks working on content for additional thoughts. Appreciate it being mentioned.
Re: "Fortune 500" and the implied emphasis on the enterprise. It's interesting b/c I've been fending off concerns recently that somehow the Starshot/DrupalCMS means Drupal is not for the enterprise anymore. From both ends folks seem to think it's mutually exclusive, which is missing the forest for the trees, IMO.
But I do believe we can probably find a way to speak to both audiences, and importantly, give community contributors a reason to be proud to participate.
Maybe something like... "putting the power demanded by the fortune 500 in the hands of non-profits, community organizers, higher education, government, and small business alike."
@rkoller, thank you very much for investing so much time in giving feedback.
CTA buttons should accommodate longer text
In CTA buttons, any text longer than about 8-12 characters has weird line wrapping behavior.
From @b_man →
Image overlap: positioning should be adaptable to more image sizes
Images in the standard dimensions expected for the hero component break properly at various desktop widths and mobile sizes, however, images that fall outside of those dimensions can end up with content overlap.
Feedback from @pameeela
Content: Use consistent sentence case
We should be using consistent sentence case in the content:
Overall scale
The current overall scale of heading sizes, text sizes, images, etc is perhaps a little bit too big. (However, in general it's really nice to be fully utilizing more screen space - and we should lean into that! With basic content types even moreso than landing pages).
I'm benchmarking based on the standard 14inch Macbook Pro, which I think is a pretty good representative sample of the current standard laptop screen size.
Here's what it looks like at 67% zoom, where the full first component is above the fold:
→
hestenet → created an issue.
Ready for an initial deployment of this MR for (very rough) demo content for: /home, /get-started, /drupal-cms, /downloads, /try-hosting
hestenet → made their first commit to this issue’s fork.
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
Re: breadcrumbs
There is a mock for a 'standard' page (non-landing page) in the Figma with breadcrumbs - not needed for the first target pages, but...
In terms of including the responsible parties in this:
So from a technical point of view:
- The announcement feed content is posted as a blog entry to: https://www.drupal.org/about/announcements/blog →
- So either a DA staff member or core team member could do that part.
BUT
- There is an extra step to publish the JSON feed (an extra safety net) - that only a DA engineering team member can do <-- so that's probably the role we should mention.
Historically I've been doing all this, but I'm not the only empowered to do so.
kristen pol → credited hestenet → .
With the approval of another co-maintainer given, I'm going to make an exception and proceed with this change a few days early.
@acbramley - you are added! Congratulations/Thank you!
+1 to @quietone's documentation idea of adding it to the release process.
+1 approval from DA side, if we can get core approval
hestenet → created an issue.
Can we get some delicious screenshots or a tugboat link or something to review? 🙂
From @saldeak at Packagist: https://github.com/composer/packagist/issues/1464
Ok I've enabled it, and force-updated all packages using this GitLab instance. So you should have dists everywhere now. Please check everything works as expected.. One possible improvement would be getting me a readonly auth token I can set up on our end so as to ensure we don't get rate-limited, but given the small amount of packages maybe it's fine as is too.
So another option would be to replace LD with ND.
I'm inclined in this direction, I think.
hestenet → created an issue.
hestenet → created an issue.
+1 from the DA side.
Technically our governance states we need one DA rep and one Core rep - so I think this is RTBC.
However, some additional +1's wouldn't hurt since this is not about a single post.
I have swapped the package namespaces around - watch out for support requests related to the change.
-
https://www.drupal.org/project/vipps_mobilepay →
- Old submodule namespace:
vipps_mobilepay_commerce - New submodule namespace:
vipps_mobilepay-vipps_mobilepay_commerce
- Old submodule namespace:
-
https://www.drupal.org/project/graphql_compose_fragments →
- Old package namespace:
vipps_mobilepay_commerce-vipps_mobilepay_commerce - New package namespace
vipps_mobilepay_commerce
- Old package namespace:
I have swapped the package namespaces around - watch out for support requests related to the change.
-
https://www.drupal.org/project/graphql_compose →
- Old submodule namespace:
graphql_compose_fragments - New submodule namespace:
graphql_compose-graphql_compose_fragments
- Old submodule namespace:
-
https://www.drupal.org/project/graphql_compose_fragments →
- Old package namespace:
graphql_compose_fragments-graphql_compose_fragments - New package namespace
graphql_compose_fragments
- Old package namespace:
Note that the prefixing of a project with its own name was not an error, but rather a way to prevent a namespace collision with the first project created.
Updating the namespaces is a manual process on the DA's part - I've gone ahead and made the following change now:
-
https://www.drupal.org/project/psi →
- Submodule old namespace:
published_state_indicator - Submodule new namespace:
psi-published_state_indicator
- Submodule old namespace:
-
https://www.drupal.org/project/published_state_indicator →
- Old package namespace:
published_state_indicator-published_state_indicator - New package namespace:
published_state_indicator
- Old package namespace:
I've swapped around the composer namespaces for the packages as follows:
-
tarte_au_citron_addtoany →
- old package namespace:
tarte_au_citron_addtoany-tarte_au_citron_addtoany - new package namespace:
tarte_au_citron_addtoany
- old package namespace:
-
tarte_au_citron_googletagmanager →
- old package namespace:
tarte_au_citron_googletagmanager-tarte_au_citron_googletagmanager - new package namespace:
tarte_au_citron_googletagmanager
- old package namespace:
-
tarte_au_citron_media_remote_video →
- old package namespace:
tarte_au_citron_media_remote_video-tarte_au_citron_media_remote_video - new package namespace:
tarte_au_citron_media_remote_video
- old package namespace:
-
tarte_au_citron_recaptcha →
- old package namespace:
tarte_au_citron_recaptcha-tarte_au_citron_recaptcha - new package namespace:
tarte_au_citron_recaptcha
- old package namespace:
I have passed this on to our Marcomm team (@tanishakalia and @christina.lockhart) to add to their work plan. Thank you @joachim namyslo!
That is possible. It's not something we do very often, but we have a couple requests in the backlog, so I can see about doing a batch pretty soon.