It might turn out to be long post, but trying to attempt placing my insight worth $0.02.
It is delightful to know and indeed blissful that people at FlectraHQ are open for communication to take forward Flectra the FLOSS way.
On deciding the path forward we must take caveats from what has worked AND what has not worked in past…
Foundation mode working has given boost to many projects from Linux to ERPNext… Unless we consider and safeguard the interest of FlectraHQ, developers and members of the community, it would be difficult to ensure the sustainability of the project.
Few more insights about delayed open-sourcing experiments with MariaDB Maxwell proxy can be followed, which was in turn helped by Bruce Perens in forming Business Source License 1.1 had gone well.
With earlier discussions as prelude on Foundation Formation, following points for consideration might be worth:
Foundation formation with minimum 3 rolling members from community and 2 lifetime membership from FlectraHQ as governing council.
It forms community/committees for Users / Developers - Contributors.
Foundation gets the show running with Conferences, Seminars, Training workshop etc… (as starting point as well for first meet)…
It forms the delayed open-sourcing licensing mechanism and builds trust circle with time and Revenues as limiting factor for functional modules and may take help from external sources and create even customized licensing for Flectra.
Initially Foundation shall represent Contributors of code and convey their concerns on architectural changes, core development, refactoring needs etc… to FlectraHQ and Later at some stage, when Community can afford monetarily and with sufficient nos of contributors, it can take Open Core development under its wings wide LGPL /existing licensing.
In no case Foundation shall involve in programs such as partner programs or app store, let that remain a domain under FlectraHQ if at all required till their sustenance.
Foundation shall reward donors/members in promotions but equal rewards to be created for Contributors i.e. equal space for knowledge, code, monetary contributors( Or else ratio between Contributors and Users would not be healthy e.g ERPNext is yet short of Contributors compared to large user base)
Foundation not to intervene in development of Functional modules, but if any module contributed towards delayed release and found to be important then would porpose and set priorities for monetary contribution and convert to LGPL (or even request members to sponsor fund with possibility to enlist them as contributors).
In consultation with FlectraHQ should provide feedback mechanism to avoid /de-list (One Model, five functions, 5$ price kind of modules i.e. which are not real contribution towards advancement of Flectra growth but are disruption by spoiling real copyright issues), and provide strict guidelines towards real functional improvement rather than mix an match of code(OR at right stage can enforce all modules to be under Delayed release mechanism)
These would be points to ponder for initial agreement only and might be worked at elaboration once initial agreement is reached and ball starts rolling…