Should we archive this repository?

[jan-janssen]

I have the feeling the dependabot is the only one contributing to this repository recently, so I would suggest we should archive it, unless there is more active development planned for this repository in future. In particular, people might confuse the pyiron_gui with ironflow https://github.com/pyiron/ironflow .

[liamhuber]

ironflow uses pyiron gui as a tab in the ironflow gui. My understanding is that this won't cause any problems since right now we only pin lower bounds. So then I would not expect archiving this to create any dependency conflict in ironflow. Based on this understanding I don't object to archiving it.

I might want to un-archive it once ironflow is rebased onto the contrib workflow stuff and we start selling that more actively (assuming the pyiron gui tab is still a part of ironflow, which seems likely).

[niklassiemer]

I lean against archiving this repo, actually due to the dependabot PRs checking that the code is working after all with the newest software stack.

However, if we decide to start archiving repos which are not actively developed right now, pyiron_gpl sounds like the next candidate to me.

[niklassiemer]

Bringing this to more life, I think I will convert some of the nice widgets here to nodes for the pyiron_workflow infrastructure.