Tweet
Hey Team Espo!
It is with much gratitude and respect for what we have here so far, that I need to ask and understand from you something on the development, for managing our expectations and systems development and introduction planning.
I see a number of developments that are essential for users, because they cost large amounts of time for users working with the current way, and the developments to improve this would be small amounts of work in comparison - but I get the impression there is an amount of persuasion or resources necessary with yourselves to pick up on these requests.
The point of choosing open-source is that, yes, we can commission developments privately if needed.
The problem though is these are core developments, so I need to understand what is the best way to get these things done, without causing ourselves divergence problems.
I just would not ask for anything that does not add benefit for the whole platform, so I see these developments as value added to the platform and user needs for speed and intuition.
However, I do not know what you see, need or want if these requests aren't being adopted.
What do you prefer?
1. Requests here and debate them?
2. Requests on GitHub and debate them?
3. We discuss privately commissioning or sponsoring some developments where you don't want to add them to the core?
4. We must work with 3rd party development? In which case, are we going to have an increasing number of Extensions or is there a path for core contributions through GitHub Pull Requests?
5. What is the preferred method of persuasion? We promote Espo? We sponsor features? We find developer time ourselves for commissioning?
I'll give you a classic example:
I look at the Documents Object, and it is 2 very minor features away from being time-efficient in daily use:
1. The Document Categories on the left should filter a list of files on the right, with the main view being all files where the user has viewing permissions.
2. The Documents List View should accept drag & drop to add Documents.
I look at every Details Read / Edit page, and it should have a "Create {Record Name}" button in the top-right, because every single time I need to click back to the List view to get that button. It makes no sense to me, or the users I have to onboard having that button missing by design.
I see these things as just obvious needs, that every user I show the system to will expect to work that way because it matches every other system they use, and it is obviously a faster way to get more from EspoCRM and save precious time for business.
Now, I need this to happen if I am not to spend a lot of time, and ask for a lot of time from users for not having these simple things to save us all time every single day.
What is the official and preferred approach to Team Espo to make these things happen?
Can I be confident that the development and evolution appetite remains strong for the user experience?
Should we talk on the phone or email or here in the spirit of open collaboration?
What can I do to help?
How do we make EspoCRM even better every day?
Many thanks,
Marcus
It is with much gratitude and respect for what we have here so far, that I need to ask and understand from you something on the development, for managing our expectations and systems development and introduction planning.
I see a number of developments that are essential for users, because they cost large amounts of time for users working with the current way, and the developments to improve this would be small amounts of work in comparison - but I get the impression there is an amount of persuasion or resources necessary with yourselves to pick up on these requests.
The point of choosing open-source is that, yes, we can commission developments privately if needed.
The problem though is these are core developments, so I need to understand what is the best way to get these things done, without causing ourselves divergence problems.
I just would not ask for anything that does not add benefit for the whole platform, so I see these developments as value added to the platform and user needs for speed and intuition.
However, I do not know what you see, need or want if these requests aren't being adopted.
What do you prefer?
1. Requests here and debate them?
2. Requests on GitHub and debate them?
3. We discuss privately commissioning or sponsoring some developments where you don't want to add them to the core?
4. We must work with 3rd party development? In which case, are we going to have an increasing number of Extensions or is there a path for core contributions through GitHub Pull Requests?
5. What is the preferred method of persuasion? We promote Espo? We sponsor features? We find developer time ourselves for commissioning?
I'll give you a classic example:
I look at the Documents Object, and it is 2 very minor features away from being time-efficient in daily use:
1. The Document Categories on the left should filter a list of files on the right, with the main view being all files where the user has viewing permissions.
2. The Documents List View should accept drag & drop to add Documents.
I look at every Details Read / Edit page, and it should have a "Create {Record Name}" button in the top-right, because every single time I need to click back to the List view to get that button. It makes no sense to me, or the users I have to onboard having that button missing by design.
I see these things as just obvious needs, that every user I show the system to will expect to work that way because it matches every other system they use, and it is obviously a faster way to get more from EspoCRM and save precious time for business.
Now, I need this to happen if I am not to spend a lot of time, and ask for a lot of time from users for not having these simple things to save us all time every single day.
What is the official and preferred approach to Team Espo to make these things happen?
Can I be confident that the development and evolution appetite remains strong for the user experience?
Should we talk on the phone or email or here in the spirit of open collaboration?
What can I do to help?
How do we make EspoCRM even better every day?
Many thanks,
Marcus
Comment