suggestion for a new structure

[frectonz]

i was gonna submit a pr but i am facing a problem,
i want to list myself as a rust and javascript developer (i am assuming we are not listing niche stuff like elm, ocaml, nix).

since people are bound to have multiple skills and languages they work with, the current structure of the list should be changed

one suggestion would be that a structure where

each developer will have a single .md file in the repo, where they will have their name, github, website, bio stuff like that
and the README.md will contain links each developer's .md file

the directory structure would be

| README.md
| LICENSE
| devs/
|         frectonz.md
|         chapi.md
|         robi.md
|         beka.md

and the README.md would look like

# codenight-developers

...

## Python Developers

- [chapi](./devs/chapi.md)
- [beka](./devs/beka.md)
- [robi](./devs/robi.md)

## Javascript Developers

- [chapi](./devs/chapi.md)
- [beka](./devs/beka.md)
- [robi](./devs/robi.md)
- [frectonz](./devs/frectonz.md)

## Rust Developers

- [frectonz](./devs/frectonz.md)

plus this will also decrease the number of merge conflicts that might happen since each contributor will just create a new file for themselves

[chapimenge3]

Hi @frectonz yeah thanks for the suggestion

Since people are bound to have multiple skills and languages they

So i think the best solution would be to write the name twice the reason for this is even tho with your structure the merge conflict will still happen because of the read me will always updated .

Another thing is to make it easy for other people to find dont you think putting all the developer in one place easy to find and look around ?

[frectonz]

Another thing is to make it easy for other people to find dont you think putting all the developer in one place easy to find and look around ?

yes, having one large file is good for various reasons,

1. it's good for SEO
2. people can easily ctrl+f to search for what they are looking for

... with your structure the merge conflict will still happen because of the read me will always updated .

yes, but they will be one line merge conflicts, they will be easier to fix than blocks of text.

So i think the best solution would be to write the name twice ...

that's also one way of solving this issue, ok then i will be doing that 🤝

[chapimenge3]

We can create a github action that will generate the correct READ me file and let the people add a file and then the github action will read that file and add it to the read me too ?

[frectonz]

that would be very cool

[chapimenge3]

I think we need to settle this before i accept the next Merge conflict

[chapimenge3]

@frectonz The best approach now is to have a form external form and we will automatically add the name and also if there is a new category we will add that one too the read me too > what do you think ?

@Bekacru

[chapimenge3]

@frectonz

But they will lose the perk of being a contributors.: 🤔 ?

[baydisng13]

let's use table on /readme.md

[chapimenge3]

Table looks wise may be good but Merge conflict is gonna kill us @baydisng13 don't you think ?

What do you think we have external form but the people lose the perks of being contributors.

[chapimenge3]

let's use table on /readme.md

I was thinking of automating the number-assigning part and strictly explain the contribution guide too .

[Bekacru]

I think keeping it simple is fine for now. Let's use the current format as it's. then we can do the github action thing later and generate tables as @baydisng13 suggested.