# Fortran index hackathon 22nd July **URL:** \ **Category:** Announcements\ **Created:** [May 13, 2026, 10:27am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898 "2026-05-13T10:27:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jwallwork23](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jwallwork23](https://fortran-lang.discourse.group/u/jwallwork23)\ **Post date:** [May 13, 2026, 10:27am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/1 "2026-05-13T10:27:21Z")
The next [Fortran index](https://fortran-index.github.io) hackathon will be hosted online on **22nd July 14:00-16:30 BST (UTC+1)**. We’ll be continuing work on improving [fortran-lang](https://fortran-lang.org/ "https://fortran-lang.org/")’s [package index](https://fortran-lang.org/packages/ "https://fortran-lang.org/packages/") so that it’s more useful for the community. Register below if you’re interested in contributing! > **[Fortran index hackathon 7 registration form](https://docs.google.com/forms/d/e/1FAIpQLScXfxx5Ns7Z7E973aplmc1-aq97Oz-B5b3YLLVgQLdNrJHUmg/viewform?usp=send_form)** > > Registration for the 7th Fortran index hackathon on Wednesday 22nd July 2026 from 14:00-16:30 BST (13:00-15:30 UTC). > > This hackathon will focus on overhauling Fortran-lang's package index to make it more useful for the community. > > Please read the... ---
**Author:** ![jorgeg](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jorgeg/32/6835_2.png) [@jorgeg](https://fortran-lang.discourse.group/u/jorgeg)\ **Post date:** [May 13, 2026, 11:00am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/2 "2026-05-13T11:00:10Z")
can a source available code base be featured? ---
**Author:** ![jwallwork23](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jwallwork23](https://fortran-lang.discourse.group/u/jwallwork23)\ **Post date:** [May 13, 2026, 11:23am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/3 "2026-05-13T11:23:48Z")
Sorry, I’m not sure I understand your question. Are you asking if certain packages could have a ‘featured’ status on fortran-lang? Or something else? ---
**Author:** ![jorgeg](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jorgeg/32/6835_2.png) [@jorgeg](https://fortran-lang.discourse.group/u/jorgeg)\ **Post date:** [May 13, 2026, 11:32am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/4 "2026-05-13T11:32:42Z")
yep! in the index ---
**Author:** ![jwallwork23](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jwallwork23](https://fortran-lang.discourse.group/u/jwallwork23)\ **Post date:** [May 13, 2026, 11:51am UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/5 "2026-05-13T11:51:02Z")
Interesting idea! I’ll create an issue ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [May 13, 2026, 9:11pm UTC](https://fortran-lang.discourse.group/t/fortran-index-hackathon-22nd-july/10898/6 "2026-05-13T21:11:18Z")
Some type of rating system like “Rotten Tomatoes” has for people to rate a package on a scale, with perhaps a “critics” rating, although how someone would be designated as a “critic” or subject expert is somewhat ambigious would be nice, or a checklist of desired attributes and some stats like “lines of code” and some information on how many packages might use the code if it a library or how many users use the code if an application would be nice and far more useful than “number of downloads” (could just be because used in a CD/CI script, etc) or “stars” (too Boolean) . A list of mine I use to try to motivate me to clean up a github repo includes git repository on WWW (github) annotated source files with an open license unit test make(1) build fpm(1) build user manual (on-line) man-page app program demo program for public procedures developer documents (ford(1)) CI/CD(Continious Integration/Development) verification (github actions) registered in fpm(1) repository Maintenance Level (actively maintained, abandoned, bug fixes only, … last date changed, … would be useful too. An actual repo (like Netlib if it were more organized) so code is available over extended periods and appears as a “release” would be even more ideal. Display of logos is appealing and can be informative, not just eye candy (see [fortran-package-manager · GitHub Topics · GitHub](https://github.com/topics/fortran-package-manager)) is useful. The human eye can scan through images very efficiently compared to text and AI image generates make it easier to supply such images.