Hey all, the beman.dump standard library proposal was rejected last week by Library Evolution Incubator (LEWGI) meaning it no longer qualifies for listing as an official Beman library.
This opens the question of what to do with the beman.dump repository. One option that has worked for me in this past is moving it to a different org (bemanproject-junkyard?).
What do y’all think?
Could we just archive it but leave it as part of the Beman org? Or do you think that will be confusing?
That makes sense. I wasn’t aware of that GitHub feature.
Sounds good.
Will the original author take back “ownership” of the project/library? Or are they abandoning it?
What do you think @foonathan?
I would say that we should merge the PR, and archive it. Then it serves as another example project people can look at.
Do we still need to make the repo beman standard compliant before archiving?
I don’t think so. Our time is better spent on improving listed libraries.
I suggest a small grace period (e. g. a week/ half a week) so we can have the repo in an acceptable level for future reference, iron out a couple TODOs, and document the library a little bit.
Unless if we are going to delete it outright of course.
Given we are lacking experience with release cycles. Maybe this repo could be a good exercise on releasing a library?? Just need to include a note on “oh btw the paper is rejected”.
Usually, we do experiments like this in exemplar, but I think dump would be more appropriate.
Why wouldn’t we use something like optional26 that probably deserves a release? My feeling is that we should deprecate dump asap.
hum that’s a good point.
Exactly!
Related to dump, I would just merge the PR today. Immediately do the archive. We have other things to do in Beman.
@leads , what’s the conclusion on this thread?
I just realized I should have said
we should dump dump
That would have been way funnier 
I agree with @Jeff-Garland here. @neatudarius feel free to go ahead with the PR merge/archive.
Done:
Issue: Retire beman.dump · Issue #5 · bemanproject/dump · GitHub
CC: @leads @foonathan
Thanks @foonathan for contribution!
