🇺🇸United States @p.ayekumi

alexpott → credited p.ayekumi → .

Sorry about posting my edit on the discuss page:

I made a couple of minor grammar changes.

Here are a few minor changes:

#Creation

When a file is uploaded using the Drupal API, it becomes a "managed file," and Drupal keeps track of it (through the File API) in the database.

• Uploaded files are placed in a wrapper scheme and directory (by default: public://).
• Drupal automatically creates a File entity with permanent status and sets its usage counter to 1.
• These files are displayed in the admin list of files (Content > Files, path: /admin/content/files) under the "at least one use" category.

Files are uploaded immediately upon addition to a field. They undergo analysis through hook_file_validate() and receive a temporary status. However, they only become permanent if the form is submitted and validated.

#Cleaning

Drupal natively incorporates a (physical) file deletion system. Here are the rules used by Drupal:

• Any file in temporary status and which is no longer attached to an entity (usage at 0 or entry absent in the file_usage table) is considered deletable.
   
• Any file in temporary status, that has not been altered (modified) since temporary_maximum_age (see system.file configuration) will be deleted the next time the Drupal cron runs (see file_cron() method). This property is set at "6 hours" by default, if set top 0 deletion is disabled. It is possible to modify it in Back Office in Configuration > Media > File system (/admin/config/media/file-system).

An alternate way to force the deletion of these files:

In file.settings set make_unused_managed_files_temporary property to true (default is 0) to activate the automatic deletion system for permanent files with a usage of 0.

This operation is only possible by modifying the configuration file, there is no Back Office interface to modify this property.

The activation of this property is not retroactive, already created files in permanent status with 0 usage will therefore not be deleted despite the activation of this property.

I have sent the email to order the 100 and I am just waiting for a reply.

I have put the proof in the midcamp organizer's slack channel!
Check it out and place your vote!!

I have just received the proofs I will share them with the team.

I sent out an email and cc @ midcamp.
Currently just waiting on response.

Here

froboy → credited p.ayekumi → .

froboy → credited p.ayekumi → .

I really like/and approve of the logo.
Great work!! @urvashi_vora!

@lostcarpark
I actually like the rabbit_hole_symbols-fs8.png if it has to be between that and the rabbit_hole_plain-fs8.png, because it explains the denied access.

I like the idea of making it more simple to understand like @chrisfromredfin, maybe something like this

"Introduces a new field type for postal addresses that is compatible with all countries."

I agree with @Ravi Kant. I feel that the Draggable_Views_1.png → describes the flexibility of a view being draggable in different directions.

I like that is a clean design, as long as there is a description of the module name. I think this would be a great choice.

I like the GTM-logo-1 design. The image of it being an actual tag is cool and I think will make more sense for a first-time user of the app over the other logo.

Great work!!

I really like this logo, it is pretty clear the options that this module helps with.

I personally like option #3 or #4. Primarily because I think it is easier to see with the contrasting background.

I personally like version 3.1 as well. It gives the feeling that there are different components but they are all equally important in their own light.

I agree with the comments above and I believe that we have come to a consensus to use Version 3.1.

I really like this logo, it is really simple and clean.

These changes look to be valid.