hestenet → created an issue.
xjm → credited hestenet → .
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue. See original summary → .
Going to try moving this to the parent /project/ai and see if it can find the right home from there.
lostcarpark → credited hestenet → .
@mpotter - a staff engineer at GitLab chimed in about 11 months ago to say they didn't think it would be too difficult to add, but it seems to have stalled out from there.
I think it wouldn't hurt to leave a comment to +1
https://gitlab.com/gitlab-org/gitlab/-/issues/217206#note_1941172559
@bertboerland is correct that it is not necessarily 'fair use' to use any kind of trademark without permission of the organization. However, in many cases brands will implicitly allow this in the case of demonstrating integrations or support. The most common example is the use of logos/trademarks when showing if software can be hosted on a particular hosting provider, for example.
After some legal consultation and research - we were recommended that generally speaking most third party technology providers will allow and may even encourage use of a logo to indicate that integrations are available, so long as they are *not* made to appear official. With the extra text on this page we think this should be okay.
However, if we receive a request directly from any of these trademark holders we would absolutely comply with their wishes.
Furthermore - this page will likely be replaced with the new.d.o redesign anyway
I'm going to wont-fix this particular issue for the moment.
hestenet → created an issue.
hestenet → created an issue.
smustgrave → credited hestenet → .
nicxvan → credited hestenet → .
Comments #11 and #12 offer good suggestions about places to make things more visible.
And yes - GitLab does present the git terms of service when they need to accept that - but it's a good point that it can be quite a long time since the last time someone looked at it.
We can probably slightly update the language on: https://www.drupal.org/drupal-security-team/security-advisory-process-an... → (or a related page) with a very simple statement about the security team's discretion to revoke based on the requirement for co-operation.
hestenet → created an issue.
Added more specifics about case study weight
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
hestenet → created an issue.
rachel_norfolk → credited hestenet → .
Assigning credit. Thank you for preparing the issue!
Assigning credit. Thank you for preparing the issue!
Assigning credit. Thank you for preparing the issue!
Assigning credit. Thank you for preparing the issue!
hestenet → created an issue.
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 → .