On 17 June 2013 17:08, David Galligani <[email protected]> wrote: > On 06/17/2013 06:02 PM, [email protected] wrote: > >> Thanks, David. >> >> So Products is the same as Projects? >> > I can't say ... > I don't know what you mean for Project :) > But I think that's what you want . >
Yes, we decided to call them Products some time back. They're the same thing currently as Projects were in Trac, with the major difference to Trac being of course that you can have more than one (read: many) of them. "Product" better reflects how many organisations develop software: They sell it (or give it away) as products, or they use it internally as products to do jobs. They are reasonably permanent and many iterations, versions, milestones, and projects may improve a product over time. A project is something you do to achieve an aim, like create introduce a major change to a product or create a product in the first place. Or take on a project for a client if you're in a consultancy. By definition they are more transient. We may re-introduce projects in the future for those purposes. I hope that helps to explain some of the reasoning behind our decision. You can change the label to project if you prefer in the TracIni file: https://issues.apache.org/bloodhound/wiki/TracIni wiki.label = Wiki tickets.label = Tickets products.label = Products Cheers, Joe > > I'm a simple user and quite a noob here , but if I'm wrong I think some of > the devs > will correct me . > > Hope it helps > > D, > > -- Joachim Dreimann | *User Experience Manager* WANdisco // *Non-Stop Data* e. [email protected] twitter @jdreimann <https://twitter.com/jdreimann>
