🇺🇸United States @ultimike

ultimike → created an issue.

rachel_norfolk → credited ultimike → .

ultimike → created an issue.

@avpaderno all valid questions to which I have no answers.

But, we need to collect input and samples before deciding the best path forward.

-mike

Here's the text of an AI disclosure that will appear on a future DrupalEasy blog post that will go to Drupal Planet:

AI was used to create the initial outline for this blog post using DrupalEasy's Professional Module Development curriculum as the source material. We support AI disclosure statements on all content that is posted to Drupal Planet ✨ Should content appearing on Planet Drupal have content notices if they are generated using AI such as ChatGPT? Active .

-mike

Updated status to Needs Review.

ultimike → created an issue.

Woot! Ready for a review.

Before and after screenshots added.

-mike

nicxvan → credited ultimike → .

An initial task would be to go through all the current feeds and send some emails to figure out who the listed owner of each should be...

Seems like maybe a good no-code task for a contribution day at a future Drupal event...

-mike

That is all very disappointing, but I understand. ☹️

This is now a much bigger task than I imagined....

-mike

@avpaderno - I'm not sure if it should be automatic, or more like a quarterly newsletter with different content each time reminding feed owners of the quality standards for posting on Drupal Planet.

As a first step, sure, an automatic reminder each quarter is fine, but I think we should aim higher.

Also - I wouldn't be against temporarily removing publishers whose current emails bounce. Being on Drupal Planet is a privilege, and should be treated as such.

-mike

I think it should be a requirement of posting on Drupal Planet - publishers should have to disclose any use of AI in the authoring of the post and/or images used in the post.

We (the Drupal community) could even provide suggested text or badging that publishers could use.

-mike

@ressa - I agree wholeheartedly, but I think that your idea should be spun off into a different issue.

I chose the two items in the issue description because I think they are easily achievable in the short term.

Thinking about the "AI disclosure" a bit more - we (the Drupal community) could even provide suggested text or badging to make it easier for authors to comply.

-mike

ultimike → created an issue.

Wow - this is all super-helpful. Huge kudos to @pdureau for taking this on.

As someone new to SDC, this discussion has been especially helpful in filling in some knowledge gaps for me.

-mike

ultimike → created an issue.

Initial best practices document published: https://www.drupal.org/node/3516295 →

Is there any reason not to close this issue?

-mike

I have been working on this in a separate Google Doc and will publish very soon - if anyone would like access to the doc, just ask.

-mike

If we focus on the title of this issue, I think that https://www.drupal.org/ixp → is actually complete enough for launch. Anyone feel differently?

-mike

@swirt Understood. I definitely think we need to somehow include content from your comment 3 above, and the Contrib First link, in our best practices document.

I might just copy/paste parts of your comment directly into the draft version of the best practices doc for now...

-mike

This issue feels overly broad to me.

Regarding @swirt's comments, I've responded to them in 📌 Develop IXP Best Practices Documentation Active

@chrisck - what do you are feel the short-term, achievable tasks for this issue? Maybe we can break those into individual issues?

You wrote:

Could the IXP initiative find a way to engage public organizations?

This is absolutely a goal for us (along with engaging other types of organizations), but I think it all comes down to messaging, correct? Do you feel that there are any structural additions we can make to the program to make it easier for government agencies to participate?

One of my goals is definitely for the IXP to have some visibility at every "summit" event at DrupalCons and other Drupal events - at the very least, maybe just a few minutes to introduce the program to summit attendees.

Thoughts?

thanks,
-mike

@flux423 - focusing only on the "IXP Survey" tab of the GoogleDoc, I think it is a no-brainer to move this along.

My main question to everyone is this: how do we use the resultant data? I think we need specific answers to this, including who will be doing the work to utilize the data. I don't think we should start this effort until we have a "realistic in a reasonable time frame" plan in place.

Some initial ideas:

• Additions to "best practices for IXPs" and "best practices for employers" pages (neither exists as of this moment, but I'm currently working on the latter.)
• A blog post suitable for general (Drupal) audiences.

-mike

mradcliffe → credited ultimike → .

@swirt - I'm putting together a "case studies" page for IXP. Is there any chance that you can turn your comment 3 above into a blog post somewhere? Ideally, it would be on https://medium.com/civicactions...

I would love to see the link to https://guidebook.civicactions.com/en/latest/common-practices-tools/cont... highlighted as well.

Thoughts?

thanks,
-mike

ultimike → created an issue.

Thanks!

-mike

swirt → credited ultimike → .

Following up on @kappaluppa's comment...

This was a bit of a tricky issue to reproduce as the form validation doesn't allow us to add an invalid link from an add/edit page that triggers the exception that needs to be logged. To get around this, we created a node with a link field with a valid URL, and then modified the uri value directly using SQL (see values in previous comment.)

Invalid values like this can be created via data migrations with malformed urls (as migrated link uri values are not always validated.)

Tests are still needed for this issue.

-mike

volkswagenchick → credited ultimike → .

This doesn't feel like a novice issue to me - I'm removing the tag.

-mike

Tim - this is all very exciting!

A couple of requested text changes/additions:

Developer hub

On https://jobs.drupal.org/ixp-developer-hub, please change:

The IXP Fellowship Program exists to promote opportunities for inexperienced developers to level up their Drupal skills by working for participating Drupal agencies.

To:

The IXP Fellowship Program → exists to promote opportunities for inexperienced developers to level up their Drupal skills by working for participating Drupal organizations . In exchange, once the mentoring engagement is complete, the participating organization is awarded contribution credits → .

IXP developers are inexperienced, but trained Drupal developers. If you have less than three months of paid Drupal experience, then you qualify for this program.

Contribution credits

Do we want to add the IXP hiring organization credit reward here and link back to the /ixp page?

thank you!

-mike

Wow - really great work so far - thanks so much!

I think the main page → , the What is an IXP? → , and IXP for new developers → are all ready to go - I made relatively minor changes to each of them.

That leaves IXP for organizations → and IXP for volunteers/reviewers → .

@anilu@ @camoa, do either of you have the content for either of these pages ready-to-go somewhere or will it need to be created (mainly from our "process" Google doc?)

I think the "IXP for organizations" page has a much higher priority, as that's what we want to be focusing on at DrupalCon next week - finding participating organizations.

-mike

ultimike → created an issue.

mradcliffe → credited ultimike → .

mradcliffe → credited ultimike → .

mradcliffe → credited ultimike → .

ultimike → made their first commit to this issue’s fork.

ultimike → created an issue.

@camoa and I have information from @horncologne and @flux423 that needs to be synthesized and added here.

-mike

ultimike → created an issue.

ultimike → created an issue.

I'm changing the title of this issue so that we have separate issues for best practices documentation for employers and employees (IXPs.)

-mike

ultimike → created an issue.

Maybe we want to build out the IXP home and sub-pages from https://www.drupal.org/ixp → ?

Regardless, IMHO, the near-term goal is to determine a hierarchy of pages that we'll need for launch. How about:

https://www.drupal.org/ixp → - main page that includes overview, summary of requirements, and links to sub-pages
https://www.drupal.org/ixp/employer-requirements → - employer requirements for contribution credit
https://www.drupal.org/ixp/employee-requirements → - who can apply for IXP positions
https://www.drupal.org/ixp/case-studies → - see 📌 Collect case studies from existing programs Active
https://www.drupal.org/ixp/best-practices-employers → - see 📌 Develop IXP Best Practices Documentation Active
https://www.drupal.org/ixp/best-practices-employees →

Much of the information for the main page and two requirements pages can come from 🌱 IXP Phase 2 proposed process Active

-mike

I think this is a duplicate of 📌 Develop IXP Best Practices Documentation Active - marking as such.

-mike

@chrisck - thanks for the kind words.

@swirt and I spoke at Florida DrupalCamp and he told me about his idea about how agencies who work on government projects might be able to hire IXPs outside of a big contract by utilizing the "contribute first" idea ( more info 📌 Develop IXP Best Practices Documentation Active .)

I absolutely encourage this discussion to continue, but at this point in time, I'm focused on what can we do in the short term to get the IXP program launched.

I think @swirt's idea should be part of the " IXP Best Practices 📌 Develop IXP Best Practices Documentation Active " for hiring organizations documentation. @swirt and/or @chrisck - would one/both of you be willing to do that?

-mike

Should we split this issue into two issues, one for hiring organizations and one for the IXP themselves? (I think so.)

-mike

mradcliffe → credited ultimike → .

Screenshots added.

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

@nicxvan - just to clarify, are you saying that all that is currently needed is a before-and-after screenshot (and perhaps some better information in the issue template)?

-mike

I'm aware of the AI Image Alt Text module, but this issue can also be considered a bug because if the prompt used to generate the image is longer than 255 characters, then an error occurs because the alt text field can't handle that.

-mike

@nicxvan, @cilefen,

Wow - thanks so much for hopping on this so quickly!

Some background on this request: each year at Florida DrupalCamp, during lightning talks, I share my list of "Drupal grievances" from the previous 12 months. The lack of the "Status Report" link was one of my original grievances a few years ago. At the time, I found a different core issue (which I have been unable to find again) that mentioned this, but its scope was bigger and never went anywhere.

Fast-forward to a few days ago, and I decided that this would not only make a good item for my "grievance rewind" for this year's lightning talk, but also a good issue to tackle (and possibly mentor someone new on) for Florida Drupal Camp's contribution day. Imagine my surprise (and joy!) when I opened this issue a few minutes ago to see the MR!

Hopefully, the narrow scope of this issue will allow this MR to be merged.

Marking as RTBC.

-mike

ultimike → created an issue.

ultimike → created an issue.

nicxvan → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

volkswagenchick → credited ultimike → .

I've just updated this fork with the following changes:

1. Changed the name of the new flavor to "Markdown Smörgåsbord"
2. Added a new hook_markdown_easy_environment_modify() that will allow folks to add additional extensions. I also added a supporting test.
3. (scope creep alert!) While working on the new hook, I discovered that the way I implemented hook_markdown_easy_config_modify() was bad. So very bad (because it would force the developer to recreate the entire converter - including the extensions - in the hook's implementation.) So, I changed the hook to fire a bit earlier (and this is the breaking part) I changed its input parameter from the $converter to just the $config array. This is a breaking change (so sorry!) for anyone who has already implemented this hook. But, the code is much better for the long haul now. Once this is merged, I will update the documentation (I have already updated the README in this issue fork.)

I'm going to let this sit for a week or so for feedback before merging. Will dance for feedback.

-mike

Another couple of ideas:

• Markdown Smörgåsbord
• Markdown Extras

After much discussion and difficulty in (my) figuring out the correct spelling, I'm going to go with "Markdown Smörgåsbord".

-mike

Heh - I think the discussion here has outgrown the title of the issue 😂

Anyway, @kreynen, your hierarchy makes sense.

-mike