Open Stack

Good idea. Since we've already got a storyboard project, let's start there.

Michael

On Fri, May 20, 2016 at 4:02 PM Zhang Yujun <zhangyujun+zte at gmail.com>
wrote:

> Hi, Michael
>
> 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.
>
> 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.
>
> That's my basic thoughts for the moment.
>
> --
> Yujun
>
> On Sat, May 21, 2016 at 1:10 AM Michael Krotscheck <krotscheck at gmail.com>
> wrote:
>
>> Hi there!
>>
>> Well, the first thing we need is other reviewers, which is the fastest
>> way to become a core :). 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:
>>
>>
>>    1. 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.
>>    2. 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.
>>    3. nsp invocation. Not strictly necessary, but a postinstall scan of
>>    the project for publicly known vulnerabilities is always a good thing.
>>
>> 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 :).
>>
>> Is there something in particular you'd like to work on?
>>
>> Michael
>>
>>
>> On Thu, May 19, 2016 at 12:39 AM Zhang Yujun <zhangyujun+zte at gmail.com>
>> wrote:
>>
>>> Hi, Michael,
>>>
>>> I have several project experience in JavaScript and please let me know
>>> how I could help on this project?
>>>
>>> Is there a project page?
>>>
>>> Or we shall getting started with gerrit review?
>>>
>>> --
>>> Yujun
>>>
>>> On Wed, May 18, 2016 at 11:45 PM Michael Krotscheck <
>>> krotscheck at gmail.com> wrote:
>>>
>>>> Hello everyone!
>>>>
>>>> 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:
>>>>
>>>>    - Help manage common project configuration aspects, such as
>>>>    licenses, gerrit, authors, and more.
>>>>    - Assist in keeping dependencies up-to-date and synchronized across
>>>>    javascript projects (JS equivalent of global requirements).
>>>>    - Provide all the necessary hooks for OpenStack's JavaScript Common
>>>>    Testing Interface.
>>>>    - Suggest common tools to use for tasks such as linting, unit
>>>>    testing, functional testing, and more.
>>>>    - (Newton Stretch) Provide a quick way of bootstrapping a new
>>>>    CORS-consuming OpenStack UI.
>>>>
>>>> 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.
>>>>
>>>> Come on over to
>>>> https://review.openstack.org/#/q/project:openstack-infra/js-generator-openstack+status:open and
>>>> help me out, would ya? If you've got questions, I'm active in the
>>>> #openstack-javascript channel.
>>>>
>>>> Michael
>>>>
>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160523/18a0bc0d/attachment.html>