>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2944651. --> Reported by: [bserem](https://www.drupal.org/user/388753) >>> <p>Recently a module called "<a href="https://www.drupal.org/project/contribute">Contribute</a>" made its appearance, and with it, a huge discussion has risen, mainly because it is now a <a href="https://www.drupal.org/project/webform/issues/2936020">dependency of the famous Webform module</a>.</p> <p>In the aforementioned discussion, it became clear (very clear some might say), that most developers do like the idea of contribute and it would be a good idea for inclusion in Drupal Core. What most people object to is to make "contribute" module a dependency of other modules, which kind of makes sense.</p> <p>My suggestion and I hope that people will back me on that, is to include contribute in Core and even install it in the standard installation profile.</p> <p>This way it is highly probably some people will join the community and get more active in it, like the author and maintainer of the module intend, while we will avoid issues where more and more project add a dependency that it not really a dependency.</p> <h3>Problem/Motivation</h3> <p>Everyone's first and most significant impression of Drupal begins when they first install Drupal using the standard or the demo installation profile. Within Drupal (the software) there is no mention of Open Source, core and project contributors, the Drupal Association, and how to get involved in the Drupal community.</p> <p>To build a growing and sustainable ecosystem, we should encourage participation and acknowledge contributions within Drupal (the software).</p> <p>We need to discuss and decide&hellip;</p> <ul> <li>Should encouraging participation and acknowledging contributions be added to Drupal core?</li> <li>What should the overall message and user engagement be with in Drupal core?</li> <li>What is the best approach implement this type of messaging in Drupal core?</li> </ul> <h3>Proposed resolution</h3> <p>TBD</p> <h3>Remaining tasks</h3> <ul> <li>Get people's opinion in the below comments</li> <li>Determine who are the key and final decisions makers for this type of improvement/feature</li> <li>See what other Open Source projects are doing? WordPress, Joomla, etc&hellip;</li> <li>Decide on an MVP (Minimum viable product) and long term solution.</li> <li>Decide how or who is going to lead the messaging?</li> <li>Determine the level of effort needed to complete these tasks.</li> <li>Decide if initial development/prototyping can be done using the Contribute module.</li> </ul> <h3>User interface changes</h3> <p>There are few possible opportunities where this type of message could/should be integrated.</p> <ul> <li>During the installation process.</li> <li>Immediately after the site is installed and a user is redirect to the front page.</li> <li>On the 'Status Report'</li> <li>On the 'Extend' page'</li> <li>Dedicated page (linked from admin toolbar)</li> </ul> <h3>Notes</h3> <ul> <li>The Contribute module could be used to quickly prototype the overall message and approach.</li> </ul> <h3>API changes</h3> <ul> <li>There might need to be some update to Drupal.org's APIs</li> <li>Messaging could be handled via a dedicated core module.</li> </ul> <h3>Data model changes</h3> <ul> <li>User data from Drupal.org needs to be enhanced.</li> <li>Composer.json files could be updated to include extra data about project's status and maintainers.</li> </ul> <h3>Related Issues/Discussions</h3> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/webform/issues/2936020" title="Status: Closed (fixed)">#2936020: Add Contribute module as a dependency</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupal/issues/2282537" title="Status: Closed (won't fix)">#2282537: Create a mechanism for modules to announce funding campaigns through the Update module</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupalorg/issues/2138397" title="Status: Active">#2138397: Highlight Flattr, Paypal or Whatever Opportunities on Issue Pages</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/drupalorg/issues/2138411" title="Status: Postponed">#2138411: Highlight Gratipay, Flattr, Paypal or Whatever Opportunities on Documentation Pages</a></span></li> </ul> <h3>References</h3> <ul> <li><a href="https://www.jrockowitz.com/blog/contribute">https://www.jrockowitz.com/blog/contribute</a></li> <li><a href="https://www.jrockowitz.com/blog/contribute-statement">https://www.jrockowitz.com/blog/contribute-statement</a> </li> <li><a href="https://www.drupal.org/governance/d8accelerate">https://www.drupal.org/governance/d8accelerate</a> </li> <li><a href="https://www.acquia.com/blog/acquia-blog/accelerating-drupal-8-adoption/27/01/2016/3291486">https://www.acquia.com/blog/acquia-blog/accelerating-drupal-8-adoption/27/01/2016/3291486</a> </li> <li><a href="http://d8rules.org/">http://d8rules.org/</a></li> </ul> > Related issue: [Issue #2940739](https://www.drupal.org/node/2940739) > Related issue: [Issue #2945263](https://www.drupal.org/node/2945263) > Related issue: [Issue #2936020](https://www.drupal.org/node/2936020)