hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
Thanks for gathering all these together @ressa.
This will be postponed until Planet Drupal is ported over to the new site (don't want to invest time on the old site) - and then we will need to do a review and triage of these issues to see which make sense for the majority of planet drupal users.
mradcliffe → credited hestenet → .
jurgenhaas → credited hestenet → .
Could you provide draft changes in a Google doc or similar? I could give you direct edit access as well, I suppose, and we have revision history - I'd just like to be able to easily track what changes we're making. (Though, as you say, this page is pretty out of date).
hestenet → created an issue.
matthews → credited hestenet → .
hestenet → created an issue.
griffynh → credited hestenet → .
This charter has been reviewed and accepted by the Drupal Association.
hestenet → made their first commit to this issue’s fork.
mradcliffe → credited hestenet → .
hestenet → created an issue.
hestenet → created an issue.
I've gone ahead and upgraded @johnpicozzi to have administer maintainers as well so that he can add @murz to assist.
hestenet → created an issue.
mradcliffe → credited hestenet → .
Explanation of how to publish recipes on d.o
Strengthening the escalation process for abuse.
fixing 'enrollment to community tier coming soon' to 'open now'
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
avpaderno → credited hestenet → .
Fixed some aliases on published pages.
hestenet → created an issue.
I am going to proceed with the policy change as proposed, given the clarification about what is included in the role and what is not. However, feel free to add additional discussion if desired.
I have sent a formal educational message and warning to the users referenced above and several others who appear to be senior members of the TATA Drupal team.
More maintainership is good, so hopefully they can respond by engaging more senior contributors, and/or starting by having the new folks establish a track record.
@jdleonard - thank you - looks like that page wasn't ready yet - so I've linked directly the trial instead
@krishnarp - the prevailing accessibility best practice for screen readers and keyboard navigation that we've followed for the last decade plus has actually been to make all links load in the same window rather than extra windows. If there is new documented accessibility research about that being different for external links like social links specifically, please let me know.
@poker10 - move the comparison cards to the top, and will make further edits in the child issue - thanks.
@everyone-concerned-with-page scale - you hopefully noticed some iterative, but targeted improvements to header, text, and margins on especially the top level hero components, but in a couple other places as well. My MR for this was merged by fjgarlin on my team this morning. Didn't want to do anything more dramatic, but now any individual component should fully fit on a 13" macbook screen at 100% zoom.
A top-level primary navigation bar, with non-navigable menu items... ugh. Instead these appear to be hover-triggered, animated mega menus or some such... might as well start taking side bets on whether these are going to result in seizures, or merely headaches.
🤔 The old D7 drupal.org menu (which we have had since at least 2017?) - is the same on all the points you reference here, though we are doing another pass on keyboard nav and looking at non-js fallback. You can still see this here: https://www.drupal.org/documentation →
I'm sad to see Drupal keeps doubling down on a destructive focus on neo-marxist "wokeism".
As a member of this community for the nearly 19 years, and CTO of the Drupal Association for the last 10, I will wear this xenophobic word salad as a badge of honor for the rest of my days. 🥇
To everyone who has been respectful, or even harsh but fair, thank you for your feedback. Many community members (with full time design, user experience, and accessibility backgrounds) have been involved through the whole process - and will continue to help our very small staff iterate and improve on this work in the open source spirit.
I appreciate the patience and encouragement from those who have offered it.
Once I complete an issue summary update - I expect to close this mega-issue in favor of focused child issues on the concrete feedback we can work to resolve.
@andrew.wang - I don't think that is related. Timeouts do happen sometimes, but we're not seeing alerts in our monitors that suggest it should be more frequent. If it's just happening on your dashboard and not on other areas of the site, maybe open a separate issue.
Some of the relevant permissions of the site moderator role include:
- Administer comments and comment settings
- Fasttoggle: Moderate comments
- Fasttoggle: Moderate posts
- Fasttoggle: Moderate users (no user data access)
- Delete contents of any file attachment
- Use the Full HTML text format
- Administer content
- Access the content overview page
Some less relevant, but not enough to justify a whole new role - especially as if they are maliciously updated with abusive content being able to edit them is in fact relevant:
- Administer all documentation guides
- Administer news feeds
- Book listing: View any unpublished content
- Book listing: Create /Edit any/ Delete
- Case study: Create /Edit any/ Delete
- Page: Create /Edit any/ Delete
- Contributor skill: delete
- Contributor role: delete
- Documentation Guide: Create /Edit any/ Delete
- Documentation Page: Create /Edit any/ Delete
- Hosting listing: Create /Edit any/ Delete
- Organization: Create /Edit any/ Delete
- Projects: Create /Edit any/ Delete
- Forum topics: Create /Edit any/ Delete
- Taxonomy terms: Create /Edit any/ Delete
Importantly it has no elevated user administrator permissions, and therefore no access to PII that might be on user profiles.
@kimble - a second round of scale adjustments is definitely very high on the priority list, after some key functional issues and bug fixes, and now that we're back from holidays and are going to have Drupal CMS launched next week.
hestenet → created an issue.
Added a 'how to support ddev' message
hestenet → created an issue.
Latest policy addition may be adjusted pending: https://www.drupal.org/project/site_moderators/issues/3498008 🌱 Policy: Grant Site Moderator role to CWG Conflict Resolution Team Active
Updating to add policy proposed in: https://www.drupal.org/project/site_moderators/issues/3498008 🌱 Policy: Grant Site Moderator role to CWG Conflict Resolution Team Active
hestenet → created an issue.
Thank you everyone for your additional comments. I'll provide another update of recent and in-progress fixes as well as triage the additional feedback here in the new year.
hestenet → created an issue.
Thank you @thursday_ bw - every couple months I try to get the transcripts all caught up. Would like to do it more often.
mradcliffe → credited hestenet → .
mradcliffe → credited hestenet → .
mradcliffe → credited hestenet → .
mradcliffe → credited hestenet → .
mradcliffe → credited hestenet → .
mradcliffe → credited hestenet → .
lostcarpark → credited hestenet → .
Made a provisional MR for the change - which currently fails check-versions, but I guess we see after this release happens and other things are branched: https://git.drupalcode.org/issue/gitlab_templates-3493016/-/pipelines/36...
hestenet → made their first commit to this issue’s fork.
phenaproxima → credited hestenet → .
hestenet → created an issue.
hestenet → created an issue.
Specbee's work to improve their internal contribution standards seems to have been working - I haven't had an escalated issue from one of their staff since this discussion 5 months ago.
Closing this issue for now. It can be re-opened if and when that is necessary.
Thanks to everyone involved, and especially @shefali for leading the internal charge on contribution strategy.
I have sent an updated nudge to org leadership.
I have sent both an individual education and a message to organization leadership.
seantwalsh → credited hestenet → .
seantwalsh → credited hestenet → .
In reviewing some of the recent issue history for Innoraft here: https://www.drupal.org/node/2145877/issue-credits →
Contribution practices look like they are much improved!
Thanks to the Innoraft team for working on their internal processes.
We can re-open this issue if we discover any other issues that need further education or support.
Update
The following pages are now live:
- https://www.drupal.org
- https://www.drupal.org/download →
- https://www.drupal.org/drupal-cms →
- https://www.drupal.org/about/11 →
- https://www.drupal.org/get-started →
- https://www.drupal.org/about/overview/technical →
- https://www.drupal.org/why-drupal →
We have made a *quite a few* updates based on the feedback in this issue and elsewhere, both large and small. There are also still some issues outstanding that we are working to improve.
Our general philosophy is:
Each page won't be perfect as it goes live, but as long as we feel it is an improvement on what it is replacing we'll proceed with the roll out and make iterative improvements.
I have updated the issue summary with notes on what we've worked on so far.
There has been additional feedback that I have yet to triage into the IS. I do intend to do that.
This is actually deliberate, for a couple of reasons:
There are some technical reasons why new.drupal.org will run in parallel with www.drupal.org for a while - while content exists in both places.
We’re definitely concerned about the ranking of the new site as pages move. Having both D7 & modern Drupal coexist on www.drupal.org was our first choice, but routing the asset & API paths to make the pages complete is not something we can do on the timeline we’re being asked to deliver. For example, I think D7 & modern Drupal have the same Views autocomplete API path, so that can’t be routed reliably. A subdomain is more straightforward than a subdirectory for us
You can think of it a bit like the old.reddit.com vs new.reddit.com, except we are avoiding duplicated content, for example:
eg:
https://www.drupal.org/about/11 →
now redirects to https://new.drupal.org/about/11, so there aren’t two pages with the same content.
As sections are migrated they are being 302 redirected and we're managing this in Google Site Owner Tools. Once all the content areas are fully migrated www. will take over fully.
nicxvan → credited hestenet → .
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.