simcha-vos-from-tu-delft opened a new issue, #136:
URL: https://github.com/apache/airavata-mft/issues/136

   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'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/airavata-mft_chart.png)
   
   | Level of maturity | Basic | Intermediate | Advanced |
   |--------------------|-------|-------------|----------|
   | Collaboration | ‎ <br>✅ ***Completed this level!*** <br><br> |  |  |
   | | ✔️ [Generate documentation from source 
code](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-documentation-from-source-code)<br>✔️
 [Prepare or create documentation 
artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Prepare-or-create-documentation-artifacts)<br>
 | ❌ [Commit 
validation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Commit-validation)<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>❌
 [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>
 | ❌ [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>❌
 [Static code quality 
analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-quality-analysis)<br>❌
 [Static code style 
analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-style-analysis)<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-Thesi
 s-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>⚠️ ***Still working on this level!*** <br><br> |  |  |
   | | ❌ [Package 
management](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Package-management)<br>❌
 [Build environment 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-environment-configuration)<br>
 | ✔️ [Build files 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-files-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>✔️
 [Source code version 
control](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Source-code-version-control)<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>✔️
 [Generate source and metadata 
artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-source-and-metadata-artifacts)<br>✔️
 [Release 
tagging](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Release-tagging)<br>✔️
 [Publish artifacts to a registry](htt
 
ps://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Publish-artifacts-to-a-registry)<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>❌
 [Push container to 
remote](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Push-container-to-remote)<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 **[Build environment 
configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-environment-configuration);**
 implemented by 49% of GitHub repositories
   - Implement **[Package 
management](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Package-management);**
 implemented by 36% 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!**


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to