Sure Binal. It will be great if you can help potential contributors as early as possible.
Closing ticket, after successful completion of project in gsoc 2024. @stanzin if you want further discussion please create child issue of this ticket.
This project is completed by @aditi_upadhyay in gsoc_2024. Closing the ticket
Bringing 2024 unsolved issue to 2025
Closing ticket, after successful completion of project in gsoc 2024. All project aspects were covered under another ticket https://www.drupal.org/project/gsoc/issues/3425856 🌱 Proposal 2024: Enhancing Drupal SEO with AI for Drupal 8, 9, and 10 Active
Updating project metadata from 2024 to 2025. Hope this year we get any contributor working on this issue.
Closing ticket, after successful completion of project in gsoc 2024
Closing ticket, after successful completion of project in gsoc 2024
Closing ticket, after successful completion of project in gsoc 2024
Removing duplicate ticket. @narashimha05 please refer to this ticket https://www.drupal.org/project/gsoc/issues/3506603 🌱 Proposal 2025: Appwrite Integration Module for Drupal Active
Aditya4478 → created an issue.
Marking unassigned because GSoC program has not declared contributor/assignee yet.
Marking unassigned because GSoC program has not declared contributor/assignee yet.
LGTM !
Try to attach screenshot too Stan
Patch LGTM !
All tests are passed,
LGTM ! :-)
#17 shows unrelated JS failure.
#12 Patch is working for D11. LGTM !
Restoring Status, ready to be merged.
LGTM ! Keep going for other issues with same patch format.
LGTM !
I will remind @stanzin about the patch 👍
patch needed for 11.x
@smustgrave I think, it should be comitted on github. Can you say why it was postponed please ?
thanks @hestenet
LGTM !
Hello everyone!
I am thrilled and grateful to the ORG Admins for entrusting me with the opportunity to mentor this project. After carefully reviewing all the conversations above, I am thrilled to see the tremendous enthusiasm and positivity surrounding this project. This level of enthusiasm is very encouraging, and it's great to see that we have a fantastic team in place, as evidenced by your impressive profiles and introductions.
I would like to invite you all to join the Drupal-google channel in Slack. We can discuss more freely there and exchange ideas. While only one person may be selected as a GSOC contributor, I encourage everyone to maintain a contributing nature. Even if you are not selected, your will rewarded with a great knowledge by remaining in the Drupal network. So expecting the same Strength even after GSoC :)
Here are replies to few question :-
- @Kareem Elshafee , @Harshita_Gupta , @smit_raval_ : The project is open, you can participate.
- @Yuvraj_Singh_5519 , @Aryan2004 , @Md_Athar , @Durgesh4993 , @Sayan2908, @Saurabh_Shukla, @kiran, @shravani_kaware : See here to know about how you can start.
- @Ritesh77 : You can search project issues here →
- @AnshumanDhiman : This → can help you for direct slack registration. Just follow the links !!
- @Shatmanyu Gupta : Start understanding Drupal Codebase, & see the issues attached in the summary of this page (aka "Project Resources"). Follow the contributor's guidance link attached in GSoC Drupal Page
- @CHANDU_19 , @smit_raval_: You can visit here → to understand about the project. Also, This 🌱 [PLAN] Drupal CSS Modernization Initiative Active issue have discussion on how the things need to be get done.
- @dbold03 , @stanzin : Refer
here →
. Else, you can also follow these steps :
(Note: You must have PHP & Composer pre-installed in your System Globally.)- Run
git clone https://git.drupalcode.org/project/drupal.git - from within the repository's root (top level) directory, Run
composer install - change directories into the
core/directory & runyarn install
- Run
Overall, I am excited to collaborate with all of you and can't wait to see what we can accomplish together. Let's approach this project with a positive attitude and a determination to succeed!
trying different status
i think, issue is very outdated...