<div dir="ltr">Hi, Michael<div><br></div><div>As you are no longer alone now, we'd better to put things in your head onto documents so that everybody who wish to contribute will know where to go.</div><div><br></div><div>Besides the technical roadmap, I think we shall need a space for issue tracking and proposal discussion. After we make the project more open to the community, it won't be long that more developers join this project.</div><div><br></div><div>That's my basic thoughts for the moment.</div><div><br></div><div>--</div><div>Yujun </div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, May 21, 2016 at 1:10 AM Michael Krotscheck <<a href="mailto:krotscheck@gmail.com">krotscheck@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi there!<div><br></div><div>Well, the first thing we need is other reviewers, which is the fastest way to become a core :). <span style="line-height:1.5">The project page right now is the README.md file in the project itself. The main reason for this is that the target audience - javascript engineers - usually find that first via NPM. Most of the Todo items there have already been done, actually, so the next step would be to really identify what this project needs to accomplish, group it into major categories, and start working on it. Off the top of my head, here's a list:</span></div><div><span style="line-height:1.5"><br></span></div><div><ol><li><span style="line-height:1.5">Dependency synchronization: Keep a list of semver global-dependencies.json at the root of the project, and update a project's dependencies if the versions are out of sync.</span><br></li><li><span style="line-height:1.5">Eslint invocation. Infra's Common Testing Interface states that all javascript projects must support 'npm run lint', using eslint-config-openstack. The generator should add/update this to any project it's run in.</span></li><li><span style="line-height:1.5">nsp invocation. Not strictly necessary, but a postinstall scan of the project for publicly known vulnerabilities is always a good thing.</span></li></ol><div>After these pieces, the next step becomes more complicated, as we need to choose whether the user is creating a web application, or a node application. This then allows us to switch out which test harness and runner we're using, so that the `npm test` command can be consistent. Once this lands, we can start talking about project src/dist directories, how to best use gulp in each project type, and actual project templates :).</div></div><div><br></div><div>Is there something in particular you'd like to work on?</div></div><div dir="ltr"><div><br></div><div>Michael</div></div><div dir="ltr"><div><span style="line-height:1.5"><br></span></div><div><br></div><div><div class="gmail_quote"><div dir="ltr">On Thu, May 19, 2016 at 12:39 AM Zhang Yujun <<a href="mailto:zhangyujun%2Bzte@gmail.com" target="_blank">zhangyujun+zte@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, Michael,<div><br></div><div>I have several project experience in JavaScript and please let me know how I could help on this project?</div><div><br></div><div>Is there a project page?</div><div><br></div><div>Or we shall getting started with gerrit review?</div><div><br></div><div>--</div><div>Yujun<br><br><div class="gmail_quote"></div></div></div><div dir="ltr"><div><div class="gmail_quote"><div dir="ltr">On Wed, May 18, 2016 at 11:45 PM Michael Krotscheck <<a href="mailto:krotscheck@gmail.com" target="_blank">krotscheck@gmail.com</a>> wrote:<br></div></div></div></div><div dir="ltr"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello everyone!<div><br></div><div>The js-generator-openstack project has been incubated under openstack-infra, and is seeking contributors (and cores). The purpose of the project is as follows:</div><div><ul><li><span style="line-height:1.5">Help manage common project configuration aspects, such as licenses, gerrit, authors, and more.</span><br></li><li><span style="line-height:1.5">Assist in keeping dependencies up-to-date and synchronized across javascript projects (JS equivalent of global requirements).</span></li><li><span style="line-height:1.5">Provide all the necessary hooks for OpenStack's JavaScript Common Testing Interface.</span></li><li>Suggest common tools to use for tasks such as linting, unit testing, functional testing, and more.</li><li><span style="line-height:1.5">(Newton Stretch) Provide a quick way of bootstrapping a new CORS-consuming OpenStack UI.</span></li></ul><div><span style="line-height:1.5">I'm looking for help- firstly, because right now I'm the only person who's willing to review JavaScript amongst the various infra cores, and I'd really like more eyeballs on this project. Secondly, because I know that I'm not the only person who has opinions about how we should be doing JavaScript things.</span><br></div></div><div><br></div><div>Come on over to <a href="https://review.openstack.org/#/q/project:openstack-infra/js-generator-openstack+status:open" target="_blank">https://review.openstack.org/#/q/project:openstack-infra/js-generator-openstack+status:open</a> and help me out, would ya? If you've got questions, I'm active in the #openstack-javascript channel.</div><div><br></div><div>Michael</div></div></blockquote></div></div></div><div dir="ltr"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>