Fair enough, Guy - I understand and accept your point. I also personally don't accept that proprietary software can really be compatible with transparency of any sort... or at the very least, it always creates another barrier to transparency somewhere down the track, so it might allow a small increment of better internal collaboration, but it inevitably creates new problems related to loss of community data control, imposing a 3rd party's Ts&Cs on your staff and/or customers (the next logical step, of course, is to get your customers using the solution). Anyway, glad to you made an improvement in your proprietary software business, but of course, I'll continue to avoid using Autodesk products because they similarly impose upon the freedoms of your users... ;) (for what it's worth, I used to use AutoCAD way back in the DOS days, but stopped using proprietary software in about 1994). I can't really see why your article was posted on OpenSource.com... because it didn't really have anything to do with open source that I could see.
We've used WeKan for quite a while, and it's pretty impressive, but it errs on the site of being a bit too basic (easy for new users, frustrating for more experienced ones). We've also used the FOSS Kanban tools Taiga.io (which is functionally comprehensive but harder to run your own - it's based on the Django framework) and KanBoard.net (which isn't as "pretty" but is far more functional and thoughtful in its capabilities - we currently use the reference instance by the software's main author, so not sure how hard it is to self-host - I think it's custom from the ground up, written in PHP). So, if WeKan is too basic for you, those other two are worth a look. I certainly endorse both over the proprietary Trello.
Fair enough, Guy - I understand and accept your point. I also personally don't accept that proprietary software can really be compatible with transparency of any sort... or at the very least, it always creates another barrier to transparency somewhere down the track, so it might allow a small increment of better internal collaboration, but it inevitably creates new problems related to loss of community data control, imposing a 3rd party's Ts&Cs on your staff and/or customers (the next logical step, of course, is to get your customers using the solution). Anyway, glad to you made an improvement in your proprietary software business, but of course, I'll continue to avoid using Autodesk products because they similarly impose upon the freedoms of your users... ;) (for what it's worth, I used to use AutoCAD way back in the DOS days, but stopped using proprietary software in about 1994). I can't really see why your article was posted on OpenSource.com... because it didn't really have anything to do with open source that I could see.