We have sharepoint and we use it as a document management system/wiki. I would argue that trac is totally different.
However, if they are Microsoft oriented they'll probably bring along Microsoft project and Team system. Those systems would cover most of trac's functionality. But you will lose the light weight extensibility of trac. Good luck. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Sent: Wednesday, December 06, 2006 11:49 AM To: Trac Users Subject: [Trac] Re: Any experience with SharePoint - arguments for still running Trac (side by side maybe) Ilias Lazaridis wrote: > Mark wrote: > > Hi, > > > > I set up a Trac site recently for our organization (team of about 20 > > people, in a division of about 150 in a company of about 3000). > > > > This company is supremely Microsoft oriented, and are looking at > > implementing SharePoint for the Division. I don't even consider the > > possibility of suggesting Trac INSTEAD of SharePoint - but I would > > still like to keep Trac (as it would be nice to have a usable, open > > technology). > > > > Anybody have any ideas how I could go about convincing this team to at > > least keep a Trac instance around (if only for the original 20 > > people?). > > > > Note - we may not be the exact target audience for Trac (it is not a > > development team - though we do produce some scripts). > > The main innovative point is the integration of the wiki with the > issue-tracking-system. This was the reason that I selected trac (in > addition to it's BSD2 license, usage of python and nice & simple UI > look). > This is probably not the killer point for our organization - as we already have a defect tracker for our 'real' projects. My main reason for installing Trac was because our TWIKI installation was a) Perl b) Slow c) Ugly :-) The extra features (over and above Wiki) of Trac are a help for some places. (most other users here find Trac to be so much nicer!) > Although both systems (wiki, ticket-system) have their deficits > stand-alone, their combination enables you to do creative work nicely > (e.g. pointing from the wiki to the open tickets) > > this looks like this (ticket numbers embedded into a working-plan): > > http://dev.lazaridis.com/base/wiki/PlanTicketQueryMacro > > or like this (query embedded into the wiki document): > > http://case.lazaridis.com/wiki/TracAudit > I love the way I can extend it and read the database easily, and I am using it as a platform for dynamic information that could be done with any web server - but Trac gives me everything and all I have to do is retrieve information from somewhere else :-) I had a discussion with my manager today - and I am not so negative about things now - we may have a SharePoint server - but if I can put enough functionality into the Trac instance before then (probably a year away) it might just live :-) > . > > -- > http://dev.lazaridis.com/base Thanks for your reply and help, Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
