Cosmos: Inconsistent "Case" of names of different sections.

Created on 10 Oct 2017  路  10Comments  路  Source: OpenGenus/cosmos

Example: graph-algorithms is spinal case while computational_geometry is snake Case.

Most helpful comment

We have a naming convention in the Contributing guideline wiki which very few contributors have complied to.

We have impose simple rules in the guidelines which are not so important but it has been seen that contributors had difficulty adjusting to it. In such a scenario, coding guidelines will only discourage contributions. For instance, even @kapillamba4's code does not comply to present guidelines.

As I already mentioned to others previously, guidelines impose restrictions which discourage almost all contributors which is detrimental for our community.

Ensuring code quality is certainly on our future roadmap and when considering copying code, it is difficult to track down the source of a code to a person. This is another restriction which cannot be checked. Despite that, we have some quality contributions and contributors. 鉂わ笍

This has come far away negatively from the vision.

I hope you will corporate in keeping the community intact 馃憤

All 10 comments

This is the kind of problem that comes up when there is no coding standard. (Yet)

@arnavb Maybe we can just add a link to the google style guide.

@kapillamba4 That's a pretty good idea, but it is just _one_ possibility. Right now, someone has to be willing to actually go and refactor _every_ single file so it conforms to the style guide. A bigger problem than this right now is the actual organization of this project, which is inconsistent.

For those who are curious: Google Style Guide on Github

@arnavb The bigger problem is people copy pasting code from geeksforgeeks (and some other sites) which has alot of poorly written code.

@kapillamba4 Their code is not poorly written, it's just that they have their own style.

@arnavb yes and @AdiChat i have an idea which can help improve code quality, can you integrate this project with travis ci?

I see what you are trying to say @kapillamba4, but what would a "build" for this repo be?

@arnavb @AdiChat I believe we can use code linters and google style checking "scripts" for different languages for continuous integration. Although i don't have time to search for those on the web and I don't know if travis ci supports such a thing.

Travis CI does support this, but it is a automated build system. Thus it would not be appropriate for this purpose.

We have a naming convention in the Contributing guideline wiki which very few contributors have complied to.

We have impose simple rules in the guidelines which are not so important but it has been seen that contributors had difficulty adjusting to it. In such a scenario, coding guidelines will only discourage contributions. For instance, even @kapillamba4's code does not comply to present guidelines.

As I already mentioned to others previously, guidelines impose restrictions which discourage almost all contributors which is detrimental for our community.

Ensuring code quality is certainly on our future roadmap and when considering copying code, it is difficult to track down the source of a code to a person. This is another restriction which cannot be checked. Despite that, we have some quality contributions and contributors. 鉂わ笍

This has come far away negatively from the vision.

I hope you will corporate in keeping the community intact 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

qoo2p5 picture qoo2p5  路  4Comments

ms10398 picture ms10398  路  4Comments

arthurlacoste picture arthurlacoste  路  3Comments

arnavb picture arnavb  路  3Comments

rhendz picture rhendz  路  4Comments