Think of a way to merge the core and periphery dirs

[andreivladbrg]

Ref sablier-labs/v2-core#979

[andreivladbrg]

Idea:

└── deployments
    ├── lockup
    │  ├── v1.0.0 // both core and periphery
    │  └── v1.1.0 // both core and periphery 
    └── flow
       ├── v1.0.0 
       └── v1.1.0 

[smol-ninja]

Looks good to me.

[PaulRBerg]

Wouldn't it be better to rename periphery to airdrops, and add a warning in <v1.2.0 that the npm package hsed to be called @sablier/v2-periphery?

[andreivladbrg]

this issue was created in august, at that time there was no discussion about airdrop repo (will update the OP)

[PaulRBerg]

OK, so you agree with my proposal?

[andreivladbrg]

Wouldn't it be better to rename periphery to airdrops, and add a warning in <v1.2.0 that the npm package hsed to be called @sablier/v2-periphery?

@PaulRBerg just realized that this wouldn’t work, as the periphery used to contain the proxy contract in the earlier versions. so, IMO naming it “airdrops” would be misleading. wdyt?

we will have airdrops only for the new versions, and we can mention “previously known as periphery.”

[smol-ninja]

How about moving previously deployed merkle campaign contracts to airdrops and keep rest (batch, proxy) etc in core?

[andreivladbrg]

How about moving previously deployed merkle campaign contracts to airdrops and keep rest (batch, proxy) etc in core?

even more confusing IMO :))

[PaulRBerg]

good point @andreivladbrg

we will have airdrops only for the new versions, and we can mention “previously known as periphery.”

Sounds good