Does not seem like this works off the box. One of our customers tweeted with a stipe buyable product link [1] (from stripe relay) and the buy buttons are not there on twitter.
Support from stripe on this has not been great either with one of their support staff confirming and the other asking us to write to twitter about it.
Has anyone else had success with buyable tweets and stripe relay ?
sadly democracy in India only has the voting part implemented fairly well. It's a monarch until the next election. Even the voting is neck deep in corruption [1]
What do you mean its a monarch until next election. Head of state is often elected for the term period. Also it maybe one of the cases reported, it doesn't imply voting is entirely corrupt.
My guess is that he meant "dictatorship" rather than "monarchy". You took umbrage with his mistake rather than forgiving that and recognizing his intent, which is that the PM role in India has way too much power.
Solid foundation is a joke. OpenERP is probably one of the shittiest pieces of code every written in Python. Take a look at their ORM code. And, of course they still use floating points for accounting [1].
It doesn't even have a screenshot, and the main description does not tell clearly what it is. The only apparent link beside the menu bar is "Validate HTML". There is no link on the items such as "Accounting" in the description.
We have thought about this every waking moment and then dreamt about it as well. We all knew what we had to do and it was high time that somebody put their hands up and decided it was enough. The Sorry OpenERP campaign is our way of declaring freedom from the cradle of filth, that we all know as Open ERP.
* OpenERP is written in python (great) but the code is not readable. They do not follow any coding standards (like pep008) and don't even have a code review process. Give it a try [1]. At my company we say "Unlearn python before you start working on openerp".
* Yes OpenERP is easy to extend and modify and has a good modular architecture. However, the API is badly broken, have a look at an on_change event handler on the server side [2]. Think of modifying this in your extended module!
* Extending/Configuring without code is marketing speak. It sounds and looks great for a demo, but is impractical to be used in any business. For example, you modify how a product view looks like by changing it without code and it works, then next time you
upgrade the product module, you will lose all the changes. It is also a quick recipe to making your ERP a 800lbs gorilla which cannot be maintained.
* They have a long list of modules. Most of the modules are crap uploaded by OpenERP partners who implemented some specific business case for a customer of theirs and is not generic. In most failed OpenERP implementations, the primary reason is almost always these extra modules which introduce dangerous bugs. I would not blame the developers alone, because OpenERP itself lacks a culture of testing and lacks sufficient tools to test the software. Be sure to evaluate every module with real world business cases. For example, purchasing in a different currency could be a feature on the "wishlist" [3]. And BTW.. they have a module which can order " sandwiches, pizzas, prepared meals, etc." for the 2500 employees :P (i am not joking [4])
* Postgresql - it's a great database, but badly misused in Open ERP [5] (it is from the core stock module which keeps track of your inventory). I will personally not trust any software which uses "distinct" [6] in a query as important as that. It also shows how OpenERP will not scale and how Open ERP developers lack the basic knowledge of SQL (not that they know better python).
* Open ERP is far from stable. Memory leaks are pretty common and add to that poorly written python. We have been maintaining production instances for a really long time and I would not find it a stable software.
* As for AGPL - it may not be the right license for an ERP. AGPL requires you to make the source of the software available as a downloadable link to all users of the software. Would you be willing to do that for all your employees ? And moving a bit more back - they switched overnight from GPL to AGPL claiming OpenERP SA owns all the copyright. Even if we assume they really do, you have an "open source" software which has no community contributions or you have a software which has a license which stands to be sued by any previous contributor some day.
* Success Stories: There may not be many actually. I personally know several of the companies in the openerp success cases page who do not use OpenERP anymore.
* Partners/Implementors of Open ERP: Here you will find the good, bad and the ugly. There are some great implementors who understand OpenERP well but may not necessarily be the partners in the spotlight. The gold, silver and ready partnership levels are just a matter of how much money you paid Open ERP SA (the company behind openerp). Chose your implementor very carefully. If they say, it has everything you want and works just like that - they are lying to you. I recommend reading a recent article a community member has written, it's pretty detailed and in french (but google translate seems to translate it well) [7].
And finally, the recent fuss about "sorry sap". It looks more like an ambitious plan to have a negative social campaign about SAP and hope that SAP would fork out a few million dollars to acquire them. Venture capitalists who invested in OpenERP surely have an exit plan ?
I have an extensive experience as an OpenERP implementer (it's now over) and agree with all of the above points.
By any mean, any communication coming from OpenERP (and partners) must be taken with a grain of salt. It's not that it's PR stunt level but it's often not very far.
That said, there's not better OpenSource alternative.
Also, don't be lured by the OpenSource term.
Also, disclaimer: Sharoon Thomas (if that's actually him) is involved in Tryton (http://www.tryton.org/en/) which is an OpenERP fork. Better in some ways, worse in other ways.
I should have put in a disclaimer myself (though my information is there on the HN profile)
Anyway:
* I work for Openlabs (http://openlabs.co.in)
* I am a board member of the Tryton Software Foundation (http://foundation.tryton.org/) (The entity behind Tryton a fork of Open ERP)
* But, all the above views and opinions are personal.
Your comments, if accurate, are definitely concerning. So how is Tryton different? Have you righted the wrongs that OpenERP has made? And if not, what do you recommend as an alternative to OpenERP?
No worries. I've kept an eye on you for a long time (through Tryton mostly) so when I read your name, I felt I had to mention your involvement in Tryton.
That said, I think your remarks are that of anybody who has expertise in OpenERP and who finally feel free to criticize the software. Me an several of my ex-coworkers share the same.
OpenERP has a bunch of license crap (read violations). They switched from GPLv3 to AGPL overnight claiming that "OpenERP SA" (the company behind OpenERP) owns the entire codebase. Looking at it from many sides:
* the product is NOT open source if a single company owns the entire copyright ? why will they not call it proprietary tomorrow ? (they don't have a contributor agreement either)
* AGPL is the wrong license to have for an ERP system. In addition to all its ambiguity, AGPL software "must offer an ... opportunity for all users interacting with your Program through a computer network to request immediate transmission by HTTP of the complete source code of your modified version or other derivative work" [1]. Does that mean that 2500 users of the software in your company should be able to download the source code of your ERP to comply ?
For me, the license switch was to make the software impractical to use for any serious business and offer a "private use" license at a price as a vendor lock in.
Not sure I agree with you here. The AGPL keeps the code completely open and free to use...the only thing it does is insure that you have to pay OpenERP for a commercial license if you want to keep any customizations or custom modules you've developed private.
What's wrong with that? First, I'm free to use the code at no charge to me. I'm even free to customize it as much as I'd like...I just have to make a link available to those customizations that my users can access. I have no problem personally doing this...none of our users would have any interest in the code we develop. If I do decide downstream that I'd like to develop a private module, I can approach OpenERP and subscribe. I've already received pricing, and their cost for 1000 users annually is cheaper than what I pay for our commercial ERP for 100 users.
The way I see it, the AGPL insures that OpenERP (the company) gets their due for giving away the code. Nothing more. Seems fair.
Support from stripe on this has not been great either with one of their support staff confirming and the other asking us to write to twitter about it.
Has anyone else had success with buyable tweets and stripe relay ?
[1] https://twitter.com/lienielsen/status/646708462043402240