Skip to content

Where should we go with this project? #2

@ETHproductions

Description

@ETHproductions

See also: js-org/js.org#786

Basically the consensus there is that a project called "tools" should focus mainly on dev tools, and libraries do not really fall into this category. There's also a library-searching site already: http://javascripting.com

One suggestion was to set up a system where you can select the tools you want, then download a .zip containing everything you need:

I was thinking about something like yeoman to make it easy to setup a new project (I do this quite often and it always costs me a lot of time because they are often quite different). In contrast to a complete boilerplate I would enjoy a toolbox of modules to pick from and combine.

To me, this idea sounds awesome, but I'm not sure exactly how we would create something like that. Any thoughts about this, or other ideas?

Also, I'm moving into a very busy time in my life (my first job and lots of schoolwork are just the first two items on the list). Because of this, I'm going to have much less time to devote to maintaining this project. @vihanb, you can keep working on it if you would like, but I don't care if you don't want to.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions