On 9 March 2012 15:11, Stefan Krecher <[email protected]> wrote: > Am 9. März 2012 15:01 schrieb Stéphane Ducasse <[email protected]>: >>> A simple and good looking Ticketing-System for use in an agile team >>> would be a good thing - it's a CRUD-Application with some Reporting >>> and maybe some eye candy. >> >> Why don't you start based on experience to build a tool and share with us. > > i guess, that's what i'm going to do - my problem is, that i'm quite > new too seaside and have no experience with building "eyecandy". I > work at the server-side ... or deal with projectmanagement-stuff > >>> Is anyone interested in creating some OpenSource-Projects for use in a >>> wider range? Those Tools should look "sexy" and should be easy to try >>> (OneClick) or to install as a Service. >> >> Yes we are lot of people interested in that. Just quite busy. > > that's a problem. > > But let me dream: > If pharo was organized as a scrum-project and if i was the product > owner, i would suspend the current pharo development and instruct the > team to work the complete next sprint (e.g. 4 weeks) on an > OpenSource-Project for some general use. > Imagine what a bunch of pharo developers could create in 4 weeks ... > And if companies start to evaluate and use the new software, this > would be a big boost for pharo/ smalltalk. > It would be a complete new way of pushing an Open Source Project.
Um. That makes no sense. Pharo developers should develop Pharo, not something that merely uses Pharo. Or: "Pharo's not being developed fast enough! Let's make the devs work on something else!" frank
