Let's discuss joint projects in the editor - why and where they are going
When setting up projects that are designed to sell on the market, will it be possible to share the profits from the sales between the project participants?
If so, how do the project participants agree before the start of sales (or even before working on a joint project) so that no one ends up being cheated?
- Let's add MQPROJ projects to be linked to a product in the marketplace or kodobase to make it easier to publish new versions in one click
The validation will remain of course.
It's just that a lot of the requirements will be checked on the editor side. That is, most of the warnings and tips will be seen from the meta-editor, not the moderator.
We will finally increase the scope of product requirements by offering tools for automated verification and preparation of materials.
Verification will remain of course.
It's just that a lot of the requirements will be checked on the editor's side. That is, most of the warnings and advice will be seen from the meta-editor rather than the moderator.
We will finally increase the scope of product requirements by offering a means of automated verification and material preparation.
thanks a lot. Going to completely update my code from the new year. Already wrote my classes... will gradually translate to new, clean code.
And I want to try a repository with projects because I work from different parts of the world. I need mobility. it's inconvenient to keep my laptop and computers in sync all the time...
When setting up projects that are designed to sell on the market, will it be possible to share the profits from the sales between the project participants?
If so, how do the project participants agree before the sales start (or even before they start working on a joint project) so that no one ends up being cheated?
Yes, that idea has been floating around for a long time.
We will most likely include it, but the project owner will still have control there. That is, he, as the owner, may overbid the shares. And here it is not clear how to solve the problem, as the right to edit should always work.
The check will remain, of course.
How is it possible if EAs are encrypted and copy-protected? Even employees of Metaquotes cannot copy EAs if they want to?
You could also consider how to connect participants from the Freelance service according to the scheme "complete a task in the project - get paid by the project owner".
When implementing such a scheme, is it possible to limit the visibility of a part of the project for one participant or another?
Yes, you can make a private project and include any number of participants with different rights.
Very convenient for freelancing, where you can save all history of file modifications of the work. And you won't need to send files to each other.
Most likely, we'll add a link to the freelance task to the projects, like for kodobase and marketplace.
How is it possible if EAs are encrypted and copy-protected? Even Metaquotes employees cannot copy EAs if they want to?
Check the stated functionality, design and general product requirements.
With the implementation of projects in the editor, we will be able to increase the amount of technical requirements for products and allow them to be easily checked on their side before publication.
Yes, that idea has been floating around for a long time.
We will most likely include it, but the project owner still has control there. That is, he, as the owner, can override the shares.
And here it is not clear how to solve the problem, as the right to edit should always work.
Maybe, as an option, to connect arbitration to this scheme to resolve disputes?
Another option. We could try to distribute shares from the volume of work done. The system could automatically calculate the contribution of each participant, and everyone will immediately see how much he has done and what his share will be.
Several schemes could be devised, and before starting work on a joint project a participant would know which scheme has been adopted, that is, they would understand what they are doing and when the shares can be reallocated.
Such ready-made templates could simplify the contractual process between the participants and reduce the time needed to resolve such issues.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
We have now released the first version of projects, collaborative projects and a new repository.
A huge change has taken place with the introduction of project files in the form of MQPROJ projects. Large projects with many included files can now be easily organised and handled conveniently. Particularly nice is that the system completes all project subdirectories and related inclusions itself, making life easier for developers. Intellisense has also grown to suit project needs.
The data warehouse had to be completely redesigned to properly support the project work. That is, each project became independent with its own participants, access rights, statistics and related information.
Own projects can be maintained in a private area, while Shared Projects with the possibility of involving other developers/users are better suited for collaborative work. The project owner has full control over the project type (personal, public and join-on-demand) and the rights of its participants. He can change the project mode at any time.
The list of public projects is shown in a separate tab in MetaEditor from where you can easily join projects.
You can already fully work with personal and group projects, but this is only the first version.
What we'll do next:
What issues would you like to discuss?