Very good idea , who will Implementation this thing .
Taiga looks good, and Atlassian’s JIRA is available free of charge to open-source projects. I think the big question, as @neginy seems to be asking, is how many people are really going to participate in development?
@PeterDF That is an excellent question and on that I don’t know how
the community would react to using taiga. My motivation is for two reasons.
@rmehta what do you think?
When I find an erpnext/ frappe app on GitHub I have
no ideas of what it truly is and how it functions. When people write an app
they are writing it to solve their problems and not really anyone else. This usually
leads to an app not having any documentation of how it functions or how to
install it. For a new comer this can be intimating.
I could write an app that is truly awesome that
the whole community app could use and one that erpnext team would take and
manage for the project but it’s easier for apps to get lost in github. It could
still happen if we impletment something like Taiga.
As a business owner myself and having work with
few manufactures/ retailers most of them leaned to odoo to solve their issues. On
the outside odoo looks slick and feature rich with all of their plugins.
A business owner that is looking for an ERP
this is all of the extensions that I am going to think that exsist for the
project. At least that is how it is in my area… Most SME can’t afford a IT
manager.
Now let’s take a look at odoos apps Odoo Apps | Odoo Apps Store. If I hadn’t have
worked with odoo in the past I would go with this solution based on this alone.
Disclaimer: I have worked with both ERPnext and Odoo. Odoo I
feel is crap and the coding is not pythonic in the least. I also don’t like the
way they have switch to a LGPL license. With doing so they now have a proprietary
version one that that is better than the community. In my option once they did
that they told the community that they are only interested in making money and
not the people that made that project what it is. They already had one fork
Tryon and I’m waiting for another one. Look at SugarCRM. This is why I chose
frappe. The creator really understand what the true meaning of open source
software really is. I don’t have to worry that they will pull the same crap that
Odoo, sugar, and countless others have. Frappe is really a paradigm shift
customization take one time at all and that means it is a lower Total cost of
ownership.
Sorry for the rant guys.
also the reason i recommed taiga and not Atlassian’s JIRA is because it fits into the current eco system and would be faster to implement and is not forcing people to use it. Its just a nice option. If people really want somthing like this we should have it done though frappe or the erpnext foundation when it is up and running. I would be willing to install it.
I’ve tried Odoo as well. It was too slow on our server, amongst other problems.
gitHub is a great tool for developers but doesn’t work at all for community input and participation, especially when many people in the community are not programmers. Does Taiga allow voting on issues/features as well as bug tracking?
I brought up JIRA last year, but there didn’t appear to be much interest.
It allows up-voting and down-voting of issues. Jira would requite a lot of work to implement and would in my option would be to disrupting. Something like taiga provides a middle ground
@woakes070048 Thanks for sharing your thoughts!
Integrations are a great idea but what is the use case? Will you be using them yourself?
Our goal is to keep making ERPNext better. Like I have said other places, what really separates us from Odoo is that we are sustaining via hosting & support at the moment and are not dependant on partner networks, so our goal will be to get as many people use ERPNext is the most efficient manner.
What we have observed is that most cloud users are looking for more complete set of features and even more simplicity in the UI. So that will be our general directions.
We will also be working on connectors either directly or via other contributors. So we would be happy to help you too.
Also we are happy to help anyone wanting to make open source apps.
i also moved out of odoo sorry but their POS is unbeatable compare to erpnext
@woakes070048 when you said taiga, this one https://taiga.io/ ?
i am comparising jira vs trello vs favor … taiga is better?
but taiga is a bit expensive
There’s nothing saying Taiga can’t be forked though, right?
We should not fork it. Taiga is opensource so we are welcome to host it ourselves. I have it internal at my company and it gives me a better over view of everything that we are working on.
didn’t know it’s open source, sweet
I think Erpnext will greatly benefit from integration with either Rocket.Chat or Mattermost. The thing is that the integration should be approached in smart way with different DocTypes. Maybe if we can outline how the integration should work, then we can put a bounty on it
These are all tempting things to do, but the key is getting the core product right. If someone from the community is willing to work on this, we are happy to support!
Btw Foundation is coming soon, so we will have a formal forum to discuss this.
@ganas i came across this https://github.com/getsmarter/rocketchat-api-rest… might be useful
@woakes070048 thanks,s I’ve been going through Rocket.Chat documantation and already convinced it’s better solution than MatterMost (mainly disappointed that mattermost don’t support LDAP and encryption in the open source version) overall Rocket.Chat have more open source culture also mattermost licence quite shady u can take a look at it.
The integration with Erpnext should be generic that apply to any doctype just like email notification, but user can define the list of triggers and action, things like:
- Reminders from CRM (e.g contact customer follow up …)
- Submissions (e.g. Leave Application,Material Request,Purchase Receipt…)
- Approval/Rejections (e.g. Leave Application)
- used as live support for website
- notification when assigned or shared
and the list can go on and on…
However, as I said the integration should be generic for any doctype but need and easy interface to define the tigers, I am after a while the community will start finding new use cases which can be feed back to the integration app where the user can activate/disable them
@Muthu while i respect you option I strongly disagree. I think Rocket.chat is a better platform and the team behind it is very open. The rocketchat team has made it compatible with slacks api so you can use most slack intergrations. I also like the fact that it is written on meteor vs go (mattermost). Now the only thing that i like mattermost for is the groups but that will be added to rocketchat soon. Why do you think that mattermost is better? Maybe i missed something about the platform
@woakes070048 . Yes you are right rocket-chat is the better option , I agree with you, I was insisting matter-most just for the groups as you said , but if that is going to be added to rocket-chat certainly it will be the best . .
Thanks
Hey guys a fiend of mine showed me this and wanted to know what you think. It seams to be the best of both worlds. it called https://vector.im/ and it is also compatible with slacks api. Matrix ∙ Vector. I am going to try it out and it works as it claims i might migrate my Rocketchat instance to it
@woakes070048 I don’t know I tried it and for me it looks like more of an IRC replacement for adhoc communication more than business oriented communication, you test it and let us know. For now lets not get lost for specific app, lets look at them in bigger functions like (creating and deleting public and private channels, adding participant to channels and removing them, posting a massage to a channel, sending direct messages, file sharing, help disk …) and based on this functions we can have the blueprints for our integration as follows:
From administrator perspective:
- When the system admin assign a role to a user, he also can checkbox to add this user to the respective channel. for example, when assigned user A a sales person role, he will be added to sales team channel, and vice versa when the role is revoked .
- the Admin can assign the users for the Help desk channel.
.
.
…
From user perspective, something like a single page setting where the user can change default values, like: - get direct messages if assigned a doctype, shared, …
- get messages for reminders for entries in the calendar, task, project …
- single place where he can define triggers on the doctypes that he has access to ( the triggers can be defined the same we define filters). for example, the user can put a trigger on “Next Contact Date” for the opportunity he’s assigned to receive a direct message reminder ahead of scheduled time.
- manny triggers will be added by default in the integration based on the user assigned roles, and the user can enable or disable these triggers (I believe the community will come up with new triggers and use case for each role, which will in return increase the number of predefined default triggers for each role in the app, and reduce the need for the user to define his own triggers).
.
.
…
Those are some of the ideas I got so far on how the integration should be, I’m looking forward for the inputs from you guys. for example one place that I still have no idea how to integrate it is comments on doctype
@woakes070048 did you do any work on WSO2 integration?