Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove cruft from bin/ #82

Open
coke opened this issue Oct 14, 2021 · 6 comments
Open

Remove cruft from bin/ #82

coke opened this issue Oct 14, 2021 · 6 comments

Comments

@coke
Copy link
Contributor

coke commented Oct 14, 2021

bin/ has many files which don't appear to belong in examples, esp. bin/perldoc, which mentions parrot, and has its own entire repo at https://github.com/raku/rakudoc (formerly raku/doc).

@coke
Copy link
Contributor Author

coke commented Oct 15, 2021

Additionally lib has some modules which aren't used (anymore?) Removed some, but all need to be verified.

@Altai-man
Copy link
Member

Doesn't this repo should be simply archived as something historical?

@coke
Copy link
Contributor Author

coke commented Oct 15, 2021

I'm trying to bring it up to date as it's still live at examples.raku.org - if the plan is to shut it down, please point me at the discussion.

@Altai-man
Copy link
Member

#73 is the discussion ticket, I think.
Arguments noted there (just improve docs instead!) still stand strong IMO. Improving weak bits of our docs is blocked now, but efforts toward smaller bits are maybe still more effective than updating the repo,

@coke
Copy link
Contributor Author

coke commented Oct 15, 2021

I appreciate you trying to save me some work here; if there's consensus on shutting down the site, that's fine, but it's been a year and there's been no movement on removing it, so if I can make incremental progress on cleanup, I'll do so.

@Altai-man
Copy link
Member

if there's consensus on shutting down the site, that's fine

I am not sure any consensus can be reached on this matter at all. People opinions tend to differ and as we (as "folks who contribute to Raku" umbrella) have no governance on how to decide what to do, if one decides to ignite such a conversation, I'm afraid it'll produce a lot of bikeshedding resulting in no consequent actions done and so maintaining the status quo (what people really despise is something they are not used to yet).

Thus acting on the de facto basis (the repo serves no purpose argument etc) is maybe more preferable to the de jure state of things ("some people are afraid of changes and doing nothing maintains status quo better than shutting down the site, so let's keep it around").

If you are still keen on working on it, at least use the https://github.com/Raku/examples/commits/enchance branch with extensions updated, a lot of scripts fixed, partial rewriting of the server part etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants