@svendecabooter It's fine to update the suggested short description as long as you followed the convention of 200 characters or less and non-technical. Also that you didn't use the project name in this summary - for example - we don't recommend "The External Authentication module ..."
For the categories we did not recommend those two additional categories, however if you feel they should be used for your module then it's fine to leave them.
This can be marked as RTBC if it adheres to those recommendations. Thanks for checking.
The logo meets the requirements of 512x512, file size is close to 10k and the logo is correctly named logo.png. The file is in the root folder of the repository. (note - this need to be in the default branch). Also the existing logo needs to be removed as the first image on the d.o project. Please check that @zaporylie
@carsoncho. The new categories for projects(modules) on D.O with their descriptions, can be found at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →
chrisfromredfin → credited leslieg → .
Thanks for the update. We did an automated mapping of categories and were just letting maintainers know which new category was selected in case they felt their module belonged in another category. This issue can be marked as fixed,
seantwalsh → credited leslieg → .
seantwalsh → credited leslieg → .
seantwalsh → credited leslieg → .
seantwalsh → credited leslieg → .
This years trainers were Rod Martin (rodmartin), Mike Anello (ultimike), April Sides (weekbeforenext) and Jennifer Smith (not on Drupal.org)
Moving to RTBC
Hi @camhoward. Thanks for the inquiry. The Project Browser team did not introduce the dump truck. That was part of the existing logo for Backup_migrate. We resized the logo, etc to make it comptable with Project Browser. The logo we provided is a suggestion, your team is welcome to change the logo to better reflect the module if you wish. The requirements for the logo can be found at bit.ly/maintpb. Let us know if you have any questions.
johnpicozzi → credited leslieg → .
Moving back to "Needs work" for the changes to the "staging" language that @hrisfromredfin added to the MR.
After manaull testimg I can confirm that the wrench icon appear on the correct place on the card when the Project is maintained and does not display when the project is unsupported.
Needs a code review
hi @ty. Thanks for your thoughtful questions and apologies for delay in responding.
This issue was created when there were 55 categories that could be added to a module on the drupal.org project page. After listening to community concerns and evaluating the best way forwrd to endure that categories would be a beneficial filter for Project Browser's target audience (sitebuilders and those new to Drupal), the decision was made to take a step back and take a good look at the categories that existed, the number of categories that could be selected, etc. We spent quite a bit of time working with the Drupal community on this and made the decision to reduce the number of categories from 55 down to 19 and to limit the number of categories that could be selected for a mudule to three.
We understood that this was a major change. Before we reopened all the category issues for rework, we worked with the Drupal Association the implementation of a migration plan to map and automatically update the existing categories. https://www.drupal.org/project/drupalorg/issues/3383004 🌱 Migrating "Categories" on Drupal.org Project pages Fixed
We also creating a document outlining the suggested use of the various categories. A document with category descriptions was created and added to the Maintainers page on Drupal.org https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → .
The "Security" category was defined as: Help protect the website from attackers or bad actors, by identifying, preventing, or mitigating security vulnerabilities.
All modules previously using the Spam category were migrated to the new Security category.
As the module maintainer you can select two additional categories if you feel that Honeypot falls under categories in addition to Security. Please review the definitions while making your decisions.
Please reach out if you have additional questions or concerns.
While we were doing discovery. this was added as a sort due to people asking - how do I find modules that were added recently so I can decide if there is something newer than what I am currently using. Not sure how many foks would actualy use it. Maybe we start with "sort by relevance" only and then re-address this option if folks start asking for it. Interested in @chrisfromredfin thoughts
Thanks @chrisfromredfin. That's an interesting question. I'll bring this up for discussion at next Tuesday's Sitebuilder Subcommittee meeting.
My personal opinion is to use creation date of the project on drupal.org. Since the default filters are "Covered by Security Policy" and "Maintained", then the list of newest projects should eliminate projects that aren't ready for prime time yet. (Advanced filters would still allow this option if someone wanted to see all new projects.)
I think using "last_updated" as the sort would always promote the largest modules as they are constantly updating their codebases. Maybe that isn't true all the time, however I don't think it's what people have asked for when using this sort.
Will update here after we meet on Tuesday.
Additional comments from today's Project Browser slack meeting:
rkoller: ah no then it is like in claro i was refering to. just styled slightly different.
the claro one is just easier to recognize in black
rkoller: in comparison gin has a black box for the bul operations. that has a clear color contrast against the white background while gins light blue makes it disappear against the white background has a color contrast of 1.1:1 in gin compared to 15.5:1 in claro.
but the pattern is identical just different styling.
in gin it just breaks with SC1.4.11 that way. but that is the point utilizing already existing ui patterns. and that bulk operations bar went through a lot of discussions
see attached file - claro_bulkoperationsbar.jpg
Adding comment from @chrisfromredfin in slack:
"Yeah I am preferring it as a banner all the way across the bottom, the way gin does bulk operations"
Adding comment from @rkoller from Sitebuilder Subcommittee call on 10/15:
"ui wise i would orient to the ui pattern used on admin/content for bulk operations. at the moment the add and install button for project browser is just a free hovering button at the button at the bottom of the page."
Adding comment from @lostcarpark from Sitebuilder Subcommittee call on 10/15:
"Another approach might be to have a sidebar with the install queue always visible in the sidebar. When there's nothing queued, it could contain a message like "Items queued for install will be shown here. Use 'Add' and 'Remove' buttons to select modules to install, and press 'Install' when ready."
Wouldn't using the term "install" also make it clearer? "Add to install queue" or "Remove from install queue" .
Explaining that the number of available categories has been reduced from 55 down to 19
I was a speaker on the "Project Browser: making Starshot's in-browser feature composition a reality" session on Tuesday at 17:30
Assigned credit and marked as fixed.
Moving back to RTBC as the issue identified was not for the logo file, but for the svg file which can be larger.
Assigned credit and marked as fixed.
As part of the Project Browser Initiative, the community had recommended "Developer tools" as the sole category to select on your project page for Categories. It is just a suggestion, you can use whatever categories you feel best fir your module. We prefer one, but up to 3 can be selected if you feel the module equally fits into multiple categories. The updated categories with definitions can be found at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →
Assigned credit and marked as fixed.
Currently set to SEO and Auti=omation. While people could generally look for cool things under admministration tools, we decided to leave what the maintainer has.
Assigned credit and marked as fixed.
Using "Enter Module name here" is technical and not something that our target audience would necessarily understand.
After discussing with Chris, I suggest keeping it simple and using a few examples as the placeholder.. (e.g. image gallery, spam protection) to give users an idea of how it can be used.
Also suggest that we change the label from "Search for modules" to just "Search " as it can now search for recipes and eventually themes, etc.
Monitored Drupal Recipes Initiative Update in Auditorium
Monitored Drupal AI in auditorium
I was part of the setup crew on Monday 2-6
I attended the orientation
updated issue summary with proposal, assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
leslieg → created an issue.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
leslieg → created an issue.
@lostcarpark. The file size is 32k. Any chance you can get that closer to 10k?
Assigned credit and marked as fixed.
Assigned credit and marked as fixed. Note - module already had a logo
Assigned credit and marked as fixed.
marking as rtbc
Assigned credit and marked as fixed.
leslieg → created an issue.
Assigned credit and marked as fixed.
This ticket was created but never finished. Members of the community have created an alternate logo for you to consider.
See attached logo.png.
I updated the issue summary with the instructions for adding a logo compatible with Project Browser. These instruction should be followed regardless of which logo you choose to use.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
leslieg → created an issue.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.
Assigned credit and marked as fixed.