ecosystem refactoring

[fabienjuif]

This issue trace the strategy of refactoring for this two issues:

• Documentation
• Lerna uses

The workflow I would like to see is this one:

• 1 standby PR, this like a master, should be named refactoring - protected
  • We can't commit in this PR, we should use branches and PR
  • We will rebase merge it to master when it will be stable and OK for us
• n PR to complete the two issues above
  • Will be squash merge into the refactoring - protected PR
  • Will be named after this convention : <emoji> <text> (#pr) (1 emoji, and the text should be lowercase)

FYI: @frinyvonnick

[frinyvonnick]

Remaining work on lerna :

• Set up publishing logic
• Don't forget to copy root LICENSE and README.md in hoc-react-loader package when publishing

[fabienjuif]

• Move to lerna
• Move to yarn workspaces
• Try to move to microbundle

[fabienjuif]

@frinyvonnick Why should we move LICENSE in each package ? It seems that npmjs look into package.json to retrieve the license

[frinyvonnick]

Babel seems to have only one LICENSE file but repeat the license acronym in each package.json, we maybe should find other examples ?

[fabienjuif]

What I try to say is:

1. I think this is necessary to add it to each package.json, and I think this is the case?
2. I think this is NOT necessary to copy the whole LICENSE file in each package, what is your though?

[frinyvonnick]

I agree with the two statements 👍

[fabienjuif]

Thank you,
=> I close the issue
=> Both packages have LICENSE field :)