simcha-vos-from-tu-delft opened a new issue, #605:
URL: https://github.com/apache/maven-jlink-plugin/issues/605

   I'm with the Software Engineering Research Group at the TU Delft, and I am 
investigating automations. I have looked at your repository and which GitHub 
workflows and Maven plugins you are using. I hope to provide you with some 
interesting insights about your repository! I'll give you a quick summary of 
what I found, and the automation tasks I recommend you to focus on next (:
   
   
   
![Image](https://simchavos.com/assets/thesis/output/apache/maven-jlink-plugin_chart.png)
   
   | Level of maturity | Basic | Intermediate | Advanced |
   |--------------------|-------|-------------|----------|
   | Collaboration | ‎ <br>✅ ***Completed this level!*** <br><br> |  |  |
   | | ✔️ [Prepare or create documentation 
artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Prepare-or-create-documentation-artifacts)<br>
 | ✔️ [Generate documentation from source 
code](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-documentation-from-source-code)<br>❌
 [Bot 
commits](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Bot-commits)<br>
 | ✔️ [Publish 
documentation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Publish-documentation)<br>❌
 [Commit 
validation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Commit-validation)<br>❌
 [Issues or PRs 
management](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Issues-or-PRs-management)<br>
 |
   | Code quality | ‎ <br>✅ ***Completed this level!*** <br><br> |  |  |
   | | ✔️ [Run 
tests](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Run-tests)<br>✔️
 [Static code style 
analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-style-analysis)<br>
 | ✔️ [Static code quality 
analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-quality-analysis)<br>❌
 [Test coverage and 
validity](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Test-coverage-and-validity)<br>❌
 [Generate test 
reports](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-test-reports)<br>❌
 [Automatic code 
formatting](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Automatic-code-formatting)<br>
 | ✔️ [Verify packaging 
correctness](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Verify-packaging-correctness)<br>✔️
 [Sign artifacts](https://github.com/simchavos/automations/wiki/Automation
 -Thesis-Wiki#Sign-artifacts)<br>✔️ [License 
checks](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#License-checks)<br>❌
 [Vulnerability 
scans](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Vulnerability-scans)<br>
 |
   | Development |  | ‎ <br>✅ ***Completed this level!*** <br><br> |  |
   | | ✔️ [Build files 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-files-configuration)<br>
 | ✔️ [Build environment 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-environment-configuration)<br>
 | ❌ 
[Optimization](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Optimization)<br>
 |
   | Artifacts |  | ‎ <br>✅ ***Completed this level!*** <br><br> |  |
   | | ✔️ [Code 
compilation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Code-compilation)<br>✔️
 [Dependency management of 
artifact](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Dependency-management-of-artifact)<br>
 | ✔️ [Build tasks, resources and 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-tasks,-resources-and-configuration)<br>✔️
 
[Packaging](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Packaging)<br>✔️
 [Release 
tagging](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Release-tagging)<br>✔️
 [Publish artifacts to a 
registry](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Publish-artifacts-to-a-registry)<br>
 | ✔️ [Generate source and metadata 
artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-source-and-metadata-artifacts)<br>✔️
 [Source control management
 
](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Source-control-management)<br>❌
 [Generate release 
notes](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-release-notes)<br>❌
 
[Containerization](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Containerization)<br>
 |
   
   # And now? Next steps!
   It is not always clear which automation tasks should be prioritized. It is 
however important to balance your automation efforts, as a uniform level of 
maturity is most productive. I'm here to help! Below is a list of tasks that 
you can work on to help level up your maturity across the automation domains: 
   
    - Implement **[Generate test 
reports](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-test-reports);**
 implemented by 10% of GitHub repositories
   - Implement **[Automatic code 
formatting](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Automatic-code-formatting);**
 implemented by 10% of GitHub repositories
   # What do you think?
   Do you think my analysis is correct, do these recommendations help you? Or 
have I missed something?
   
   For my master's thesis I'm doing research into the use of automations in 
GitHub repositories. With my findings, I want to see if I can help out 
developers with what automations they could focus on. Do you want to help me 
out? **Leaving a response is much appreciated!**
   
   If you have any other Java/Maven projects you'd like analyzed, you can send 
me the repositories and I can analyze them for you!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to