[Pharo-project] Increase populatity of Pharo by doing some Killer-OpenSource-Tools

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Mar 9 09:01:29 EST 2012


On Mar 9, 2012, at 1:05 PM, Stefan Krecher wrote:

> Hi,
> 
> i suspect, that the popularity of Pharo (or Smalltalk in general)
> could be increased by developing some "Killer-OpenSource-Tools".
> By "Killer-OpenSource-Tools" i think of Tools, e.g. for supporting the
> Software-Development-Process in general. Moose of course could become
> such a tool.
> But i think of some standard Tools like Bug-Tracking/ Project Management.

I agree

> Let me explain by a short example.
> In a lot of projects i needed to use Trac (http://trac.edgewall.org/)
> as a Ticketing system.  Trac is a "simple" Python script to manage
> Tasks/ Tickets, it is customizable and can be enhanced. But it is very
> very ugly, configuration is very unhandy. We like to print tickets to
> pin them to a whiteboard for use in daily scrum meetings. This and
> additional reports are made by BIRT-Reports. Everything feels very
> unstable but a lot of companies prefer Trac because of licensing
> issues (e.g. Jira is better but commercial).
> 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. 

> Another idea could be a Tool for organizing activities regarding
> Softwaretests, e.g. generation of Testspecifications/ -plans and
> reports on test-runs. I used TestLink (http://www.teamst.org/) but it
> is ugly and unhandy too ...
> 
> Pier CMS could be a good solution for Intranets or Websites, but the
> lack of Documentation keeps people from using it.
> 
> 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.

> 
> regards,
> Stefan
> 





More information about the Pharo-dev mailing list