Based on Add issue comment attribution credits can be given to organizations and clients in addition the individual developer. Most of the modules are already doing this.

I think it would be great if we can do the same for Entity Browser module as well. It would encourage more organizations to participate in making this module a stable one before the Drupal 8 release.

I am thinking that since we are following a Github workflow it might add challenges. But I think its worth looking into if it is not too much of work.

Comments

gokulnk created an issue. See original summary.

slashrsm’s picture

slashrsm CreditAttribution: slashrsm at Examiner.com commented
Status: Needs work » Active

Since it is all based on commit comments we're already able to do that. Even on Github (people working on issues need to be aware how to properly provide attribution). Am I something missing here? Is this issue actionable in any way?

gokulnk’s picture

gokulnk CreditAttribution: gokulnk at Azri Solutions for CyberSafe commented

I am a little confused here. Let me know if the below workflow would fix this issue.

  1. Create a issue on drupal.org with proper Attributions
  2. Copy the commit message from the Git Command Section
  3. Use that command for Git commit, in the forked repo
slashrsm’s picture

slashrsm CreditAttribution: slashrsm as a volunteer commented

Exactly. Our policy is to use pull requests on Github while always opening an issue on d.o. This is a bit confusing and might change in the future, but it allows us to leverage GitHub PR workflow while still keeping record using standard Drupal tools (d.o. issue queue).

gokulnk’s picture

gokulnk CreditAttribution: gokulnk at Azri Solutions for CyberSafe commented
Status: Active » Closed (works as designed)

Thanks for the confirmation. It makes sense now.