Change repositories naming convention to be consistent

[BOLT04]

Description

In our EddieJaoudeCommunity organization, we have many repositories where some use Pascal case and others use kebab-case. We could choose one naming convention and use that across all present and future repositories 😃.

Context Being consistent with the naming convention was mentioned on this live stream. I searched on this repo's issues and discussions and didn't find something already opened for this topic.

What does everyone think about this and what naming convention should we adopt 😃?

[github-actions[bot]]

It's great having you contribute to this project

Thank you for raising an Issue! Welcome to the community :nerd_face:

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

[vinzvinci]

I agree with kebab-case :)

[eddiejaoude]

thanks @BOLT04 for raising 👍 - yep I want to be consistent, not sure why I was not 🤦‍♂️

[chryzcode]

I don't really understand what this is all about!

[BOLT04]

I don't really understand what this is all about!

Hi @chryzcodez 😃, this issue was a question to see if the community agrees we should keep the repositories naming consistent. Meaning, we change this (current naming):

to this (kebab-case):

That is only an example, this issue is supposed to also decide which convention to choose.

Hope that clears your doubts.

[chryzcode]

ok, I get now, thanks @BOLT04

I feel that would be nice!

[chryzcode]

I think this can be done by the community members with special privileges and freedom.

[Vyvy-vi]

I think it's best if Eddie or someone from the @EddieHubCommunity/coreteam does this, after the community agrees

[Vyvy-vi]

I think kebab_case is fine but some ppl here might like Camel case :P (looks at js people)

[BOLT04]

kebab-case is fine by me too 👍 Not sure if only @eddiejaoude has permissions to do this, but yeah let's agree on a convention first 😃

[chryzcode]

kebab-case is fine by me too 👍 Not sure if only @eddiejaoude has permissions to do this, but yeah let's agree on a convention first 😃

Yeah!

[eddiejaoude]

Thanks everyone 👍 - I will do this soon 🤓

[chryzcode]

Okay!

[eddiejaoude]

This is still on my to do list 🤓

[github-actions[bot]]

Stale issue message

[schmelto]

@eddiejaoude a friendly reminder 🙈

[ghost]

Why do we even have stalebot, it makes important issues/hacktoberfest prs stale 🤔

[kaiwalyakoparkar]

Why do we even have stalebot, it makes important issues/hacktoberfest prs stale thinking

We need it. Because you are looking from the perspective of a contributor while the teams are looking from the maintainer's perspective. It would be really hard to get back to the issues which are not active for a long time. I agree that sometimes it marks important issues as stale but I guess there was discussion about the same in the community and they would be coming up with a different solution than removing it.

[eddiejaoude]

@eddiejaoude a friendly reminder 🙈

thanks @schmelto I need to do this asap 🤦‍♂️

[eddiejaoude]

I really need to do this 🤦‍♂️

[mikeysan]

No pressure (and get that green square), When will you do this? :smile:

[BOLT04]

perhaps we could mention this on the next live stream and do it live. It's a chance to learn for those who don't know how to do it 😃

[eddiejaoude]

Great idea @BOLT04 👍 I will do it on a live and show people how to update their git remotes too

[gptkrsh]

No pressure (and get that green square), When will you do this? 😄

Do we get a 🟩 for this? 😅

[gptkrsh]

Great idea @BOLT04 👍 I will do it on a live and show people how to update their git remotes too

Awesome!

[highfrezh]

interesting.👊

[highfrezh]

Agree with kebab_case