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

Portland, OR πŸ‡ΊπŸ‡Έ
Account created on 25 March 2006, almost 18 years ago
#

Merge Requests

Recent comments

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

@fabianx and I both like the suggestion of enabling the module by default,
but having an opt-out variable documented in the release notes.

We can canvass a few other opinions, but I think that's pretty close to a
consensus on the approach.

+1 - that works for me.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

@dqd - I appreciate that quotation! That's a very important message in order for us all to be sure we are working towards a solution that helps Drupal be more sustainable for the people who contribute so much, while at the same time avoiding certain minefields.

I have to agree with @rszrama that allowing maintainers to include certain kinds of commercial interest is not only reasonable, but perhaps important for the long term health and support of their modules.

That said - I totally agree that we should have certain standards. I don't think anyone wants to take people by surprise, risk compromising PII, or create a negative user experience. But there is room to improve the options for promoting fiscal support without having to do any of those things.

I think @rszrama and team are being thoughtful in hearing the feedback, and I trust that they'll work out an improved solution - and we can use this experience to understand and update our general governance for this.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

@jweowu - users will still be able to attach accepted file types to issues (even when they move to GitLab) so that may include patch files. They won't have any automated features or testing associated, but they will be attachable.

However we have *never* recommended hot-linking to patch files on a remote server. That is a really bad/dangerous development practice. We know people have been doing it for years, but it has always been against Drupal.org recommendations.

It has always been much safer and more reliable to host copies of patches you are using locally.

There is a feature request (actually multiple feature requests) open requesting GitLab add stable urls for diffs:

We absolutely agree this is a feature GitLab needs to add. However it won't block the migration, and we still won't recommend hot linking to them in any deployment process.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

Over the past weeks and months we've added quite a few updates to the Owner Tools page to work on making it more relevant and useful to organization profile owners.

We'll continue to make ongoing improvements - but at least for the initial scope of this issue I think I'll call this fixed.

Example from the DA's profile:

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

Let’s go ahead and say July 1st for Disable DrupalCI testing.

For no new testing schedules, DrupalCon Portland is May 6-9. We might as well pick a date around then.

We should send emails to people with DrupalCI testing set up. Maybe 2 weeks before each date, so we’re sending at most 2 emails.

I agree with this plan.

For no new testing schedules, DrupalCon Portland is May 6-9. We might as well pick a date around then.

I would say disable around a week before - that will again encourage folks to keep moving over to GitLabCI at contribution day.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

Updating with explanation of credit scale

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

The latest changes as discussed and as represented in the MR have a +1 from me. RTBC.

We may want a second +1 from @drumm

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

I think for the scope of Drupal it makes more sense for the DEI.md to be in core and to be understood to apply to all of the ecosystem under its governance.

I am not so much considered about prioritizing this against the innovation and other code projects, because we have talented folks in the community for whom this is a strength area, moreso than code.

The template can also be pretty light weight:
https://github.com/badging/badging/blob/main/Template.DEI.md?plain=1

For the upcoming announcement:
https://gitlab.com/gitlab-com/marketing/developer-relations/open-source-...

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

Does someone from the core side want to raise their hand to help define what would need to be in the composer.json data structure in order to make this happen?

Or perhaps even to propose the larger example of what else might be needed to fully replace info.yml files?

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

@ultimike

Right now that would be equivalent to 3 core contributions a month, or 3 case studies on the latest version of Drupal every month - the annual total of 360 credits would be about equivalent of $36,000 of financial contribution to the DA.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

My initial thoughts here:

The Drupal Association has a 'special programs' credit field we can use to grant credit to organizations without needing to build something extra or file a bunch of issues.

We could set a rubric for the value training/hiring an IXP dev. Maybe it's 30 credits a month for example - so in one year, they'd gain 360 credits per IXP. And that credit would last for an additional 12 months if that person left the IXP program.

The question is whether that's quite enough to make that incentive worth while.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

@gusaus - bumped you to an admin again so you can prototype out what creating a Fund looks like. Once it exists we can regroup about in the new year and decide if/how we want to use it more specifically. Thank you for offering to set it up so we can see how it might work.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

Announcements feed was including in standard profile/enabled by default in Drupal 10.2!

Hoping that will help us build confidence towards doing this in D7. The longer time horizon we have to communicate with D7 site owners before EOL the more resources we can provide to them and the better we can shepherd them into a good experience with the EOL process.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

My suggestion after reading the comments would be as follows:

For a maintainership offer (or one of the automatically created bot issues) on a project that is truly out of date/replaced by another module:

  • Close the issue 'won't-fix', with a comment that says "This project is obsolete due to [other module] or [core]. If you believe there is a reason to revive this module anyway, please reopen this issue with a detailed explanation the purpose this project would serve that is not met by the existing options that replaced it."
  • Perhaps the issue title should have the word [Obsolete] added in front
  • The project page should be edited to mark obsolete status and add a link to the replacement to the description.
  • If the user does re-open and the explanation is good, proceed as normal with adding maintainership.
  • If the user does re-open, but with no explanation or a bad explanation, we close again with a denial.

I feel like that will let us help key the queue clean and not spend too many resources on unneeded projects, and leaves enough discretion to you all as moderators to judge how special cases might fall.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

I believe this is RTBC - and ready for project announcements to be marked Stable.

There are follow ups for Dashboard but they can happen as part of the Dashboard work directly.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ
πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

This is an exceptionally old issue to be necro-ing. However, it's relevant to a page I just put together...

As we start doing more with GitLabCI we want to enable people to do more with Peronal Access Tokens, which is more API access. This is a subset of all the ways people could automate/script/use bots on Drupal.org, but it's a concrete one I was at least able to write an initial policy for.

We should keep updating as specific use cases arise, and not be afraid to iterate on it if the language isn't perfect.

Also - the requirement to open an issue for approving an automation allows us to request things like a unique user agent string and some of the other requirements discussed above, where appropriate.

https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... β†’

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

The post is now available in the feed:
https://www.drupal.org/announcements.json β†’

"id": "3398477",
"title": "Drupal 9 is end of life",
"content_html": "<p>It's time to update your Drupal 9 sites to Drupal 10.</p>",
"url": "https://www.drupal.org/about/announcements/blog/drupal-9-is-end-of-life",
"date_modified": "2023-11-01T19:11:48+00:00",
"date_published": "2023-11-01T19:09:06+00:00",
"_drupalorg": {
"featured": false,
"version": "^9.0.0"
}

Who has a handy site to check? 😊

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

hestenet β†’ created an issue.

Production build https://api.contrib.social 0.61.6-2-g546bc20