0.4 feature freeze

[luisivan]

According to the Development Plan, 0.4 should include:

• Economic abstraction: Orgs should be able to hold and interact with any standard value-holding token
• Improved budgeting and accounting
• Dividends for the organization token holders
• Fundraising with tokens, not only ether
• Funds vault: The only part of the company that is not expected to change, making upgradeability easy while maintaining the access to the funds.

0.4 is crucial, because it will be the first release that gets deployed to the mainnet.

[luisivan]

As @izqui and I discussed, postponing this release and merging it with 0.5 would be a great idea in terms of timing. Now, 0.5 should include:

• Front-end modules API: A way for devs to create interfaces for their modules

• Core modules API: Something higher in the stack that just calling the contracts, more sugary

• Module developer incentives plan: Incentivizing developers

• Organization-wide encrypted datastores: Give organizations their own data store using IPFS/Swarm/etc.

We will discuss what we can include and what not, but feels like modularizing as early as possible is a good move, since we will be touching very fundamental parts of the codebase.

Regarding the developer incentive plan, we can probably think about it later when we see how devs create and maintain modules.

And regarding the organization datastores, since a lot of the work on modules will probably be directed towards storage (e.g. modules will be upgradeable and fetcheable using IPFS/Swarm/etc.), we could postpone it to 0.6 and learn from the modularization process first.

Finally, something that we didn't include in the development plan, but that is crucial: Refactoring the app with Vue. In my opinion we should start ASAP, @harshjv is already looking into it to see how complex that would be.

[izqui]

For me the crucial question we need to ask is whether we split the current app in modules this version or we do it in 0.5, while still maintaining a reasonable release date. We need to do a good estimation, but I would like to try to target end of July as our internal deadline, so 0.4 alpha gets publicly released in August or very early September.

My current state of mind would be: all new code (accounting & dividend sharing) is coded in Vue and we start thinking about this part as a standalone module. All other code of the dapp gets refactored and modularized in 0.5.

The thing is that 0.5 will make very little changes in the smart contracts, so the audits that will start on 0.4 will be able to be run with 0.5.

[izqui]

Notes from v0.4 locking meeting.

• Refactor to Vue and modularization of the app is moved to v0.5 (as v0.5 frontend will be able to work with v0.4 contracts, locked for mainnet). @harshjv to start planning refactor for v0.5 soon.
• v0.4 will maintain mostly the current design. v0.5 will have more design changes. @owisixseven to start thinking about v0.5 redesign now.

Main work needed for v0.4:

• 9: Accounting module to be thrown away and starting from scratch.

• 10: Fundraising module to be updated for multitoken

Given that 0.4 won't be a huge frontend workload, July deadline doesn't seem to crazy.