Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future of Uzume #17

Open
7h3730B opened this issue May 9, 2020 · 1 comment
Open

Future of Uzume #17

7h3730B opened this issue May 9, 2020 · 1 comment

Comments

@7h3730B
Copy link

7h3730B commented May 9, 2020

Describe your issue.

We don't have many guild members who are contributing to this Project.
So it is basically dead right now.

Describe what you were expecting instead.

Maybe we can get this to life again when using another programming language.
I would suggest node js, because lots of people on the guild are using it.

Additional context.

For the base we could use my Project Boto then we are going with node and get the message handler or other stuff from it.

@zekroTJA
Copy link
Member

zekroTJA commented May 9, 2020

Yeah sure, but I guess, the project would also be dead if we don't create an active team of people who can feel responsible for this projekt and also may promote and show new features about this project to motivate people to contribute.

And yes, a lot of people may know how to write stuff for Node / with JavaScript. The thing is, that, especially people which are new to JS and coding in general, often don't have that much knowledge about general conventions and "Do's/Don'ts" when using JS.

Here are some proposals how we should manage the project to prevent this:

  1. We should use TypeScript instead of JS. Yes, it adds another layer of tool-chaning but makes the whole code base more reliable and understandable for contributors and it can be simpified by using NPM build scripts in the package.json.
  2. We need to force contributors to use tools like ESLint/TSLint. This can be enforced by using CI pipelines checking the code quality with these tools.
  3. As same as this, we should also enforce the usage of a formatter like Prettier, which should also be checked by a CI pipeline.

But in general, I think this is a good idea. In my opinion, discord.js is still one of the best documented and maintained wrappers for the Discord API and also node provides a huge base of packages which we can use and which people might be comfortable with (i.e. express).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants