🇹🇳Tunisia @Ahmed Aziz ABBASSI

hestenet → credited azizos → .

I was busy last weekend by work and family plans. I will dedicate this weekend for testing @Aditiup work.

@vlad.dancer As her mentor for GSoC (Google Summer of Code) 2024, I would like to dedicate time this weekend to review and test her work. If you have any other suggestions or ideas, I would be happy to hear them.

@Aditiup I will try to test it ASAP and set RTBC.

@Aditiup Please do not mark your MR as a draft, as it will be automatically blocked.

@Aditiup Could you please provide a patch file?

Here’s an example of how to create one: git diff > filename.patch

I've tested it and it looks good to me too.

azizos → created an issue.

azizos → created an issue.

azizos → created an issue.

@mohitrai6236 Thanks for creating the issue!

@tedbow Welcome 🥰!

@mohitrai6236 Please write it into a seperate issue as it is an other proposal idea.

Hi folks! I am interesting to be a mentor for this project too. As I am the primary mentor for the Drupal 10 Newsletter Module, I could be a backup mentor working aside with @ayushmishra206.

@SiddhantGupta Could you please specify which repository you cloned?

@SiddhantGupta Please read the previous comments carefully!

@roman7 While a deep understanding of Drupal 7 architecture is not mandatory for our current project, having knowledge of it can significantly boost your capabilities, especially when delving into the Mail Tracking module's source code referenced in the previous comment. This foundational understanding can empower you to navigate the complexities of the codebase more effectively, identify opportunities for optimization, and contribute valuable insights to our project. Feel free to explore Drupal 7 architecture further to enhance your skills and gain a deeper insight into the Mail Tracking implementation. Your effort in expanding your knowledge base will undoubtedly benefit our project in the long run.

I wanted to share some insights with you regarding essential tracking tools for Drupal 10. According to this guide on DrupalTeam.com , the following tracking tools are highly recommended:

• Google Analytics: This powerful tool provides comprehensive website analytics, helping you track user behavior, traffic sources, and more.
• Clicky: Another popular analytics tool that offers real-time monitoring, heatmaps, and detailed reports to optimize your website's performance.
• Crazy Egg: This tool specializes in visualizing user behavior through heatmaps, scroll maps, and click tracking.

Additionally, I came across a module called Mail Tracking on Drupal.org that implements a tracking feature for reading mail engagement. Exploring this module could provide you with valuable insights on how to enhance the tracking capabilities of your project.

Don't hesitate to reach out if you have any questions or need further assistance!

: https://drupalteam.com/drupal-10-analytics-tools-guide/
: https://www.drupal.org/project/mail_tracking →

@dineshchhantyal This is an overview of my thoughts:

1. Standardize APIs: You can design your mailing feature to interact with mailing service providers using standardized APIs such as SMTP, IMAP, or OAuth. This can help in achieving compatibility with a wider range of providers.
2. Support Popular Providers: You can prioritize integrating with popular providers (such as google, outlook, yahoo, zoho, etc...) first and then gradually expand to include others based on user demand.

This is a project I'd be interested in mentoring, if it is selected and I am selected as a mentor.

azizos → created an issue.

I've did the steps described above in the issue summary.

Ahmed Aziz ABBASSI → created an issue.

name: Hello World
description: Creates a page showing "Hello World".
package: Custom
type: module
version: 1.0
core: 8.x

I wanted to provide an update regarding the configuration of the Hello World module in the GitHub repository shared (https://github.com/sidharrell/D8HWexample.git). 

Previously, the YAML settings were as shown in the first code snippet provided. This configuration worked fine only with Drupal 8.

To ensure compatibility with major versions of Drupal, I have made the following changes to the YAML settings:

name: Hello World
description: Creates a page showing "Hello World".
package: Custom
type: module
version: 1.0
core_version_requirement: ">=8"

I have forked the original GitHub repository and implemented these necessary changes in the YAML settings. As a result, the module will now work with different major versions of Drupal.

I have also updated the tutorial to reflect the new GitHub repository link of the forked version.

Thank you for your attention to this matter.

Best regards,
Aziz
 

Ahmed Aziz ABBASSI → made their first commit to this issue’s fork.

This issue attracts me the most: https://www.drupal.org/project/automatic_updates/issues/3159920#comment-14990083 ✨ Add a PHP Memory Readiness checker Needs work

I would like to work mainly on it.
I would start integrating it in my proposal.

Yes, this postponed issue caught my eye and I was extremely interested in solving it: https://www.drupal.org/project/automatic_updates/issues/3343721#comment-14975655 🐛 rsync compatibility with version 2.x Closed: outdated .

When I was trying to solve it, I was completely lost.

@rivimey
You make a good point about not needing to worry about bootstrap memory needs for a usable site. However, there are still many other factors that can affect memory usage during in-place updates, as you mentioned.

I agree that memory profiling is a good approach to determine the factors that affect memory needs. By profiling the memory usage during different types of updates and configurations, we can identify the patterns and factors that contribute to higher memory usage.

Regarding the memory limit check, checking if the memory_limit value is greater than a certain threshold is a good start. As you mentioned, a value like 200MB could be a reasonable threshold, but it may need to be adjusted based on the specific needs of the site.

The second version you suggested, attempting to allocate blobs of memory until you run out, is not a good approach due to the potential problems it can cause on the host and in the PHP process. Instead, a more accurate approach would be to simulate the update process using a sample of the site's data and modules and measure the memory usage during the simulation. This would give us a more accurate estimate of the peak memory usage during an actual update.

Overall, a combination of approaches, including memory profiling and simulation, can help us develop a more accurate and effective PHP memory readiness check for in-place updates.

Hi Tim, could I have interest in a postponed issues or should I limit myself for active issues?

Hello @hestenet
I've read the materials in the attached links above. I've got more familiar with the project's road map. The main architecture of automatic updates is more clear now. But, I've lost with links. I need to be guided. I hope you get my wanted-contribution as serious as you could. Thanks in advance.

this is the version of rsync. How to see the path of the bin?
I've tried looking under /usr/bin and I haven't found anything.
Could you explain more please?

Good afternoon, I'm trying to solve this issue. In my local machine, I've php 8.2.2. Is that ok? or I've to install php 8.1.16?