Add ForaLABS.json for extension catalog entry

[HarlleyHauradou]

New extension

Tier 1

Any extension that is listed in the Extensions Catalog must fulfill these requirements.

• Extension has a reasonable name (not too general, not too narrow, suggests what the extension is for). The extension name should not start with Slicer (unless it explicitly provides a bridge between Slicer and a tool or library), because it would make it more difficult to find extensions if the name of many started with the same word.
• Repository name is Slicer+ExtensionName (except if the repository that hosts the extension can be also used without Slicer)
• Repository is associated with 3d-slicer-extension GitHub topic so that it is listed here. To edit topics, click the settings icon in the right side of "About" section header and enter 3d-slicer-extension in "Topics" and click "Save changes". To learn more about topics, read https://help.github.com/en/articles/about-topics
• Extension description summarizes in 1-2 sentences what the extension is usable (should be understandable for non-experts)
• Any known related patents must be mentioned in the extension description.
• LICENSE.txt is present in the repository root and the name of the license is mentioned in extension homepage. We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. MIT (https://choosealicense.com/licenses/mit/) or Apache (https://choosealicense.com/licenses/apache-2.0/) license is recommended. Read here to learn more about licenses. If source code license is more restrictive for users than MIT, BSD, Apache, or 3D Slicer license then describe the reason for the license choice and include the name of the used license in the extension description.
• Extension URL and revision (scmurl, scmrevision) is correct, consider using a branch name (main, release, ...) instead of a specific git hash to avoid re-submitting pull request whenever the extension is updated
• Extension icon URL is correct (do not use the icon's webpage but the raw data download URL that you get from the download button - it should look something like this: https://raw.githubusercontent.com/user/repo/main/SomeIcon.png)
• Screenshot URLs (screenshoturls) are correct, contains at least one
• Content of submitted json file is consistent with the top-level CMakeLists.txt file in the repository (dependencies, etc. are the same)
• Homepage URL points to valid webpage containing the following:
  • Extension name
  • Short description: 1-2 sentences, which summarizes what the extension is usable for
  • At least one nice, informative image, that illustrates what the extension can do. It may be a screenshot.
  • Description of contained modules: at one sentence for each module
  • Publication: link to publication and/or to PubMed reference (if available)
• Hide unused github features (such as Wiki, Projects, and Discussions, Releases, Packages) in the repository to reduce noise/irrelevant information:
  • Click Settings and in repository settings uncheck Wiki, Projects, and Discussions (if they are currently not used).
  • Click the settings icon next to About in the top-right corner of the repository main page and uncheck Releases and Packages (if they are currently not used)
• The extension is safe:
  • Does not include or download binaries from unreliable sources
  • Does not send any information anywhere without user consent (explicit opt-in is required)

Tier 3

Community-supported extensions.

• Documentation, tutorial, and test data are provided for most modules. A tutorial provides step-by-step description of at least the most typical use case, include a few screenshots. Any sample data sets that is used in tutorials must be registered with the Sample Data module to provide easy access to the user.
• Follows programming and user interface conventions of 3D Slicer (e.g., GUI and logic are separated, usage of popups is minimized, no unnecessary custom GUI styling, etc.)
• The extension can be successfully built and packaged on all supported platforms (Windows, macOS, Linux)
• Maintainers respond to issues and pull request submitted to the extension's repository.
• Maintainers respond to questions directly addressed to him/her via @mention on the Slicer Forum.
• Permissive license is used for the main functions of the extension (recommended Apache or MIT). The extension can provide additional functionality in optional components that are distributed with non-permissive license, but the user has to explicitly approve those before using them (e.g., a pop-up can be displayed that explains the licensing terms and the user has to acknowledge them to proceed).
• All requirements of tiers < 3.

Tier 5

Critically important extensions, supported by Slicer core developers. New Slicer Stable Release is released only if all Tier 5 extension packages are successfully created on all supported platforms.

• Slicer core developers accept the responsibility of fixing any issues caused by Slicer core changes; at least one Slicer core developer (anyone who has commit right to Slicer core) must be granted commit right to the extension's repository.
• Automated tests for all critical features.
• Maintainers respond to questions related to the extension on the Slicer Forum.
• All requirements of tiers < 5.

[Copilot]

Pull request overview

This pull request adds a new extension catalog entry for the ForaLABS extension to the 3D Slicer Extensions Index. The extension is submitted at Tier 1 (experimental) level and includes the minimum required fields to be listed in the extensions catalog. The repository URL points to SlicerForaLABS on GitHub, using the main branch for the extension source code.

Changes:

• Added ForaLABS.json catalog entry with schema v1.0.1, empty build dependencies, ForaLABS category, and main branch reference

Comments suppressed due to low confidence (1)

ForaLABS.json:3

• The extension JSON file is missing the "build_subdirectory" field. While this field is optional (defaults to "."), the vast majority of extension catalog entries explicitly include it for clarity and consistency. Consider adding "build_subdirectory": "." after the "build_dependencies" field to follow the established convention in the codebase.

  "build_dependencies": [],

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[HarlleyHauradou]

Hello! Thank you for reviewing this pull request.

I would like to kindly ask about the next steps in the process. Since all checks have passed, please let me know if there is anything else I should do on my side, or if I should simply wait for the review and possible merge.

Thank you very much for your time and help.

[lassoan]

Thanks for your patience. There are just a few things to sort out:

• The extension packaging will fail, as the list of files in https://github.com/HarlleyHauradou/SlicerForaLABS/blob/main/ForaLABS/CMakeLists.txt is incorrect. Please follow the standard module template to avoid complications (one module per folder, folder name matches module name). You can also try adding this experimental github action, which automatically tests your CMakeLists.txt files: https://github.com/lassoan/SlicerMONAIAuto3DSeg/pull/105/changes
• The extension name is difficult to change later (you want to avoid rebranding), so it is worth spending some time on it now. I don't see anything specific to foraminifera, but the module can be used for any porous structure analysis. Instead of "ForaLABS", Would you consider using a more generic name, such as "PoroLab", "PoroQuant", ...?
• No test data is provided. This makes it difficult for others to test your extension and makes user support more difficult for you (if something does not work as expected then you will not know if it is because there was something unusual about the user's input data). Recommendation: add a section like "Sample Data" with links to publicly available foraminifera micro-CT datasets (e.g., from repositories like Zenodo, Dryad, or institutional archives) or include a minimal example dataset in the repository (e.g., a small NRRD/STL file).
• Using non-ASCII characters in the source code (e.g., nível de módulo) may cause problems on some systems