Crystal: [RFC] Create crystal-lang/crystal-rfcs

[asterite]

The main crystal repository is full with issues that suggest features or functionality. This clutters the repository with issues that are not issues at all.

I suggest we create another repository, crystal-rfcs, for submitting RFCs and discussing them there. RFCs should probably also follow some guideline, specially if they are about language features, but for now we can simply not require anything special.

This would be similar to how Rust handles this.

Thoughts?

[asterite]

One example: https://github.com/crystal-lang/crystal/issues/4754

[Sija]

crystal-lang/rfcs seems 'nuff, moar DRY

[sdogruyol]

I say, let's go for it :+1: It's easier and simpler to handle discussions / suggestions in a separate repository.

[Fryguy]

Alternate idea: What about a label on the issue? Then with GitHub search just tack on a label:rfc if you want to see that label and a -label:rfc if you don't want to see that label.

One reason I don't like a separate repo is that casual contributors won't be aware of it (even if it's in an ISSUE_TEMPLATE.md, they don't read it), and they will make the issue here anyway, meaning a core contributor has to transfer it. Not really a huge deal, but it does add some overhead.

e.g.
features: https://github.com/crystal-lang/crystal/issues?q=is%3Aissue+is%3Aopen+label%3Akind%3Afeature
non-features: https://github.com/crystal-lang/crystal/issues?q=is%3Aissue+is%3Aopen+-label%3Akind%3Afeature

[Sija]

@Fryguy we already have too many of those, IMO introducing a new one would only make things worse.

[ensoxyz]

why not just do the reverse crystal-issues and let this be the report for request. This would allow a clean slate and clear up all the clutter and confusion instantly.

[lbguilherme]

@ensoxyz then commits won't be able to close issues so easily. And it is better to have issues about the code near the code itself.

Something like a hosted discourse could also be considered. Either way, seems good to move proposals apart from actual actionable and specific issues. +1

[ghost]

can the scope of this expanded to not only code/ implementation but also usage/ best practice (e.g.) because I think the documentation could still benefit by keeping such issues closer to the language/ incorporating them than outsourcing to stack overflow?

Searching for crystal questions is a bit of a pain although I think many have already been asked.
A central place may be the best until crystal gains further adoption/ spread.

[akzhan]

Core team should be extended to handle more infrastructure as I suppose.

[asterite]

Nevermind, compared to other repos of other languages we still have very low traffic, so this is not an issue.

[luislavena]

On a personal note, I would love people submit issues to discuss possible
API addition or changes instead of direct work on a PR that might generate
lot of back and forth and consuming more time and effort.

Sorry for top posting. Sent from mobile.

On Oct 15, 2017 21:55, "Ary Borenszweig" [e-mail] wrote:

Nevermind, compared to other repos of other languages we still have very
low traffic, so this is not an issue.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/crystal-lang/crystal/issues/4944#issuecomment-336755163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAQVli4RHxEyargLxKi_mcsq3Y8UP7Tks5ssqmMgaJpZM4PSWId
.