Open Raynos opened 10 years ago
@substack
We are building a web GUI for publishing npm modules. With this we can make npm so dead easy that nothing else makes sense.
You should join us. It would be sweet to get some nice test / testling / tape integration in the publishing work flow.
@maxogden
We both know frontend people don't use command line tools. We need to cater to that. What better then a GUI for npm itself. Let's start with publishing.
You should join us. I would love feedback on how to really tailor this to people that know nothing about browserify, npm & node.
@thlorenz
Remember nstart? Now imagine it had a web GUI. Now imagine you don't have to enter passwords in a terminal. This is going to be amazing.
You should join us. I would love some help making sure the publishing flow isn't too opinionated and caters to multiple people. I'll also finish nstart up this week, love feedback on that too.
i'm not available for knockout hacking but perhaps requirebin.com, browserify-cdn and the associated modules that I worked on would be helpful
On Mon, Nov 4, 2013 at 10:14 AM, Raynos (Jake Verbaten) < notifications@github.com> wrote:
@maxogden https://github.com/maxogden
We both know frontend people don't use command line tools. We need to cater to that. What better then a GUI for npm itself. Let's start with publishing.
You should join us. I would love feedback on how to really tailor this to people that know nothing about browserify, npm & node.
— Reply to this email directly or view it on GitHubhttps://github.com/Raynos/npm-the-wizard/issues/13#issuecomment-27675012 .
@creationix
Authoring and publishing modules through a web gui designed to work on a chrome book & offline. That's just the start. We are building a module publishing GUI aimed at publishing browserify/npm style modules.
You should join us. It would be amazing to have something work offline creating a full git repo. It would also love to set up a publishing system that isn't coupled to npm. Maybe we can just upload the git tarball somewhere.
@maxogden browserify-cdn is going to help so much. A lot of the requirebin machinery is going to help a bunch too.
@hij1nx
You are right, a terminal vs a GUI makes such a difference for uptake. We can make it easy & appealing to the masses. Plus would love to educate people with the right defaults for simplicity.
I know your busy, but if you have a change of heart, you should totally join us. We want to make this really easy for everyone.
@williamcotton
Love your ideas on corsLIT, really inspirational to this concept. We want to build a way to publish & author modules that focuses on the bare essentials, the code, the tests & the examples. All the other artifacts (files, git repos, package managers) should be automated transparently.
You should join us. I can really use some radical ideas before we pave the standard npm cow path.
Awesome stuff. I'm available Friday and the first half of Saturday to help. So is this a node-knockout entry or something?
(@raynos in case that wasn't clear. I'm saying that I could join the KO team if you're willing to have me for only part of the competition.)
Not sure if I can join, since I'm already part of another knockout team, but in any case the UI tool should be driving a CLI tool. In other words there should be a way to interact with the tool on the command line and to script it.
However having a UI on top of that to support uptake is an awesome idea.
Hey, this sounds like a fun project to hack on for a weekend! I'm in! What other steps should I take? Do I need to register? @Raynos can you email me some details at williamcotton@gmail.com?
Ok, since it looks like I'm not gonna make it, I'm gonna list the modules I created to support the implementation @Raynos and I were gonna do a while back:
Good luck guys!
@creationix yeah this nodeknockout entry. I added you to the team.
You should do the whole node knockout dance. If you happen to be near SF it would be cool to hang out here aswell. We should sync up on IRC & you can PR / comment / issue / commit this repo
@thlorenz good luck in your team! We will definitely re-use the stuff you build last time and get a command line nstart up and running.
@williamcotton awesome. Totally join us.
At this point we can use help with focus & features. We outlined some ideas & motiviations, got a few sketches. Next we need to figure out the MVP and the non trivial parts. Join in the conversation with issues / comments / PRs / commits.
We currently have two members ( http://nodeknockout.com/teams/team-mad-science )
We should convince some people to join us.
Check out the README for the concept and get involved in discussions either way.