To clarify: We will not erase any projects from github.
Status quo & pain points:
The current database of projects on codefor.de is outdated and incomplete. It would be very time consuming to review and update all of it. Even with our best efforts, we would not produce a complete list of projects.
Many labs have their own websites. They do not want to add projects more than once, and they already add them to their own website.
Some labs use the codefor.de/nameoftheirlab subpage as the only place to refer to their work. Currently, the database is the only way they can showcase their projects.
Digifarm Münster has built a solid database that features many CFG projects. In many community discussions we conceded that we should build on it/ integrate it, instead of keeping up our own.
How we should display projects in future:
on subpage codefor.de/projects:
make it clear that we are not showing a complete project list of everything CFG has done, because many things are on the labs' own websites.
highlight some (ca. 3) projects with images and short text
link to digifarm with a big button or integrate digifarm (maybe link to first, integrate at a later date as a seperate project)
rest of projects, everything that should not be displayed, gets moved to "Projektarchiv"
"Projektarchiv" gets a disclaimer that information might be incomplete/ outdated, and once again link to digifarm
on subpages for labs, eg. codefor.de/flensburg
show all the lab's projects that are registered in database (stays as is)
labs are encouraged to write blogposts that highlight their projects (which will also be added to their lab subpage, if they add the relevant tag "labname")
To clarify: We will not erase any projects from github.
Status quo & pain points:
How we should display projects in future:
on subpage codefor.de/projects:
on subpages for labs, eg. codefor.de/flensburg
==
[1] (https://github.com/okfde/codefor.de/tree/main/content/projekte) or (codefor.de/projekte) inkl. project archive