Issue support credits [#2712493]

As the creator and maintainer of this project, I must admit there are a LOT of things about Drupal, php coding, and theming that I do NOT know.

It's kind of paradox if you ask me, because I am not aware of all the things that I do not know.

Sometimes (if not often) I do become aware of something that has been staring me in the face for years, but I just never really gave it any notice. But once I begin to understand 'that thing', then it begs the question 'What should I do about it'?

Its kind of emabarrasing in a way, to acknowledge these things publicly. But one advantage of doing so is that it can serve as a commitment to learn from the experience and in so doing, make a change.

Issuing support credit is 'that thing' in this case.

So, I'm opening this issue to walk thru all the resolved issues in this queue and make sure credit is awarded properly, and even log a few comments reflective of new things I learn along the way.

Comments

Comment #1

24 April 2016 at 14:49

dbt102 created an issue. See original summary.

Comment #2

dbt102 CreditAttribution: dbt102 commented 24 April 2016 at 15:13

I've read thru many project issue queues for many years now to better understand why certain modules are behaving the way that they do. I guess it was my presumption that to resolve an issue I needed to submit a patch. And, if that patch was accepted, then some magic would happen in the background and I might be awarded credit for actually help resolve the issue.

But, 'good grief' if you just help whoever created the issue to think through it and get it resolved, you can get 'official' credit for that. No code required.

Comment #3

dbt102 CreditAttribution: dbt102 commented 24 April 2016 at 15:07

Issue summary:

View changes

Comment #4

dbt102 CreditAttribution: dbt102 commented 24 April 2016 at 16:05

So, I've been kind of focused on "Help" issues this last week. It started with the issue Create a README or HELP plugin created by jonreid. My initial thought was to just push up a new release to include the readme file. But then it lead me eventually to looking for 'official' direction on d.o. providing 'help' on contributed projects.

Then, this last week, Drupal 8.1.0 was released, and I began reading thru the release notes, and right there at the top of the list was a note related to D8 help. I began digging into that to discover that this is quite an involved item, and its being addressed in core. And user jhodgdon has really stepped up to help make help something special in D8.

I decided somewhere along the line (if not just now) that the best way to lead the implementation of youtube_block help, was to implement the Help text standard (for core and contrib) one step at a time.

Each step that I'm following is defined by the four different places on a site where help and explanatory texts can be displayed to users. The "Help text standard" does a good job giving direction about implenting help in each of these places.

Also, since i've learned a lot about contributing to the Drupal Community thru this issue (Issue Support Credits), and then researching jhodgdon work on the larger HELP issue, i'm thinking she's become a kind of vitual mentor, wether she knows it or not. So as a follow-up to this issue. I need to look into the d.o guidelines for recognizing mentors.

Going to close out this issue now though, because I have completed review of the queue to make sure proper attibution has been given to all the resolved issues.

Comment #5

dbt102 CreditAttribution: dbt102 commented 24 April 2016 at 16:32

Also note, there is a "giving credit" link at the bottom of each issue do give specific direction. Its a great help, but gets pretty involved making it a long read