# Fortran tools on GitHub **URL:** \ **Category:** Uncategorized\ **Created:** [July 18, 2021, 3:52am UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570 "2021-07-18T03:52:21Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Beliavsky](https://avatars.discourse-cdn.com/v4/letter/b/ba8739/32.png) [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)\ **Post date:** [July 18, 2021, 3:52am UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/1 "2021-07-18T03:52:21Z")
[Fortran tools on GitHub](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md) lists tools in the categories below - [Automatic Documentation](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#automatic-documentation) - [Build Tools](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#build-tools) - [Compilers](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#compilers) - [Emacs Plugins](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#emacs-and-plugins) - [Fixed to Free Source Form Conversion](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#fixed-to-free-source-form-conversion) - [Indentation and Formatting](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#indentation-and-formatting) - [Interoperability](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#interoperability) - [Parallel Programming](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#parallel-programming) - [Preprocessors](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#preprocessors) - [Refactoring](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#refactoring) - [Static Analysis](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#static-analysis) - [Text Editors, Integrated Development Environments, and Plugins](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#text-editors-integrated-development-environments-and-plugins) - [Translation from Fortran](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#translation-from-fortran) - [Translation to Fortran](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#translation-to-fortran) - [Unclassified](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#unclassified) - [Unit Testing](https://github.com/Beliavsky/Fortran-tools-on-GitHub/blob/main/README.md#unit-testing) ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [July 18, 2021, 10:39am UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/2 "2021-07-18T10:39:17Z")
Thanks @Beliavsky ! We should figure out how to maintain this as a community and present at [fortran-lang.org](http://fortran-lang.org) for greater visibility. ---
**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\ **Post date:** [July 18, 2021, 4:06pm UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/3 "2021-07-18T16:06:23Z")
I think submitting to the [Package Index](https://fortran-lang.org/packages/) is the way to go. ---
**Author:** ![Beliavsky](https://avatars.discourse-cdn.com/v4/letter/b/ba8739/32.png) [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)\ **Post date:** [July 18, 2021, 5:14pm UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/4 "2021-07-18T17:14:43Z")
> [@milancurcic](#): > > I think submitting to the [Package Index](https://fortran-lang.org/packages/) is the way to go. Most of the Fortran tools are not written in Fortran. The Package Index is more suitable for items in the [Fortran codes on GitHub](https://github.com/Beliavsky/Fortran-code-on-GitHub) list. ---
**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\ **Post date:** [July 18, 2021, 7:31pm UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/5 "2021-07-18T19:31:41Z")
We currently don’t limit to Fortran as the implementation language, e.g. ford, fypp, fprettify are all implemented in Python, and listed. The current scope for the package index is “written in Fortran or for use with Fortran”. ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [July 18, 2021, 9:12pm UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/6 "2021-07-18T21:12:24Z")
My original idea for the package index is indeed codes written in Fortran. If it is not written in Fortran, hopefully it is a tool, and in that case it can go into the tools section. I have noticed that we put in some tools that are just a simple Python script. I don’t like that, I would prefer if the package section contains high quality maintained Fortran codes, hopefully with several contributors etc. Perhaps we could clearly mark “for use with Fortran”, written in any langauge. In that case, I think LFortran, GFortran and Flang should all be also listed. ---
**Author:** ![milancurcic](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/milancurcic/32/2_2.png) [@milancurcic](https://fortran-lang.discourse.group/u/milancurcic)\ **Post date:** [July 18, 2021, 10:38pm UTC](https://fortran-lang.discourse.group/t/fortran-tools-on-github/1570/7 "2021-07-18T22:38:16Z")
If people prefer that, it would work as well.