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

Document Repository Map #2859

Open
jasnell opened this issue Jan 19, 2016 · 4 comments
Open

Document Repository Map #2859

jasnell opened this issue Jan 19, 2016 · 4 comments
Labels

Comments

@jasnell
Copy link

@jasnell jasnell commented Jan 19, 2016

One of the more significant complaints I've seen is the confusion caused by all the individual repositories being so spread out across three different github organizations. While there are conversations happening about how those repos should be organized, one interim step is to provide a roadmap that outlines all of the relevant repositories, where they live, and how they relate to one another. This can either be done as a separate doc or added to the contributing guide (which is likely best)

/cc @tunniclm @ritch

@jasnell
Copy link
Author

@jasnell jasnell commented Jan 19, 2016

@tunniclm
Copy link
Contributor

@tunniclm tunniclm commented Jan 19, 2016

@dougwilson check me on this, are these:

  expressjs  "Organization for HTTP utilities and anything Connect/Express related."
  jshttp     "Low-Level JavaScript HTTP-related Modules"
  pillarjs   "The BYO HTTP Framework Framework"
  strongloop "StrongLoop Inc."
    express
    expressjs.com
@tunniclm
Copy link
Contributor

@tunniclm tunniclm commented Jan 19, 2016

I did some investigation, here's some analysis of dependencies (not complete): https://gist.github.com/tunniclm/17bb1a909bacf2bb37e0

@crandmck
Copy link
Member

@crandmck crandmck commented Jan 22, 2016

Would it also make sense to add some information to http://expressjs.com on what's in jshttp, pillarjs, and expressjs? If there's agreement, I'll open an issue in https://github.com/strongloop/expressjs.com to add it to the site.

@Fishrock123 Fishrock123 added the meta label Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.