Define how Cordova handles package-lock.json

[janpio]

npm introduced package-lock.json some time ago. Apache Cordova never decided how this file should be handled in our packages (commit to git? not commit to git? .gitignore?).

We should define that and make the necessary changes.

[raphinesse]

I thought we decided to commit it some time ago. It's on the ToDos for the next major.

[janpio]

Well, then there should be an issue here to track the progress.

(Creating that issue now)

[raphinesse]

It's in "planned" on the board for the next major.

So do we put meta issues here now?

[janpio]

Yep, those "cards" should be converted to issues anyway (at least that's how I understood @erisu's intent - please correct me if I'm wrong) - and here is the only place that matches.

[janpio]

The card has now been converted to an issue.
Should have checked the board first before creating this issue, but well...

[erisu]

Yes, all note cards needs to be converted into issues. I was not confident in which repo these issues were to be created. If we decided this repo then I can go head and start converting them all.

All items on that board, especially in the planned column, was decided for this coming next major.

The items in the planning/ideas column might need more discussion but the title and content can be written as if its an actual task that will be implemented but add the discussion label.

Once moved to the planned column, we can remove the discussion label.

@janpio @raphinesse

Sorry I hadn't had time to send out an official email to the mailing list or bing up any of these questions.

[brodycj]

FYI we had already reached agreement in [1], would have liked a cross-reference.