The-turing-way: Enabling GitHub Discussions in the Turing way repo

[BatoolMM]

I'm thinking that maybe enabling GitHub Discussions tab could be pretty useful and beneficial for the Turing way community especially for first-timers who are intimidated to open new issues.

The problem is that we gonna have some overlap with Issues which could cause confusion 😕 . This idea is open for discussion.

[KirstieJane]

I think this is a super useful issue - thank you @BatoolMM!

I think the discussion about enabling GitHub Discussions needs to focus on whether we want to be forward looking - adopting new features that GitHub have brought in - or whether we want to work in a way that _at the moment_ is most similar to how many open source projects work.

One of my big goals for The Turing Way is to build a space that makes folks feel more confident and able to contribute to lots of other open source projects. But I don't know which way to go on the Discussions tab!

Voting isn't perfect but maybe give this comment a 🚀 reaction if you think we should should lean into activating the Discussions tab or a 🎉 reaction if you think we're best to stick with issues for now.

And - as Batool says - please keep the discussion going!

[martinagvilas]

Thanks @BatoolMM for opening this issue!

On the one hand, I really like the idea of @KirstieJane of making The Turing Way as similar as possible to other open-source projects to facilitate learning how to contribute to open-source in general. I do have a question on waiting until the feature becomes mainstream (open to discussion): When do we consider that the feature has become standard use and is ready to be added to The Turing Way? Do we select a couple of open-source projects that need to put the feature into practice before we do? Do we wait until X number of open-source projects implement it? Or what else?

On the other hand, I personally like the Github Discussions feature and I think it would be super useful for The Turing Way in particular for cases where people want to suggest new chapters or have any other big and novel idea for the book or the community. However, if Discussions are enabled I would add a guide for users detailing when to open an issue and when to open a discussion.

For now, I lean into the waiting option (🎉 ) since the majority of open-source projects I'm familiar with haven't implemented discussions yet (or they are currently trying them out)

[malvikasharan]

This is a fantastic discussion. Agree with everything that’s been said.

I would lean towards using the feature for two reasons that’s been said in this thread already: 1) making it easier for new users to join/open a discussion which is indeed more friendly than issues. 2) be the example of open source community that adapts to new changes (maybe we test this and if this doesn’t work we stop the feature and report why we made that decision).

I agree that we need to have a clear guidance for when to open an issue and when to open a discussion.

My personal reason for discussion feature is to actually get some discussions that have been opened in issue going. Most of the issues are not paid enough attention and though the number keeps increasing, it isn’t that effective after a few months have passed without any action.