AAF: AAOBloggers

:)

a Pythonic Linux Sharepoint Services?

leave a comment »

السلام عليكم…

summery

WSS is great but it likes people with deep pockets (MS IIS License). Go open source instead 😄

I guess one of the benefits of working for a company that is very close to Microsoft is getting to know all their “solutions” first hand. One of these solutions is Windows Sharepoint Service. basically, it’s an application suite that allows people who are working on a project to work better with one another by organizing the way information is managed and accessed while providing methods to organize team work and increase team efficiency.

How did they do it? will it’s simple really, they just jam a blogging platform, a forum, subversion control, and a wiki into on system and provide exceptional integration with MS Office.. thats all.

Why should i give a *? will for starters, this can be the perfect solution for developing software. as you may have noticed, almost all major projects have a Sharepoint like system, one way or another. sourceforge, gnome live, and so on.

OK, now two problems remain: It’s proprietary and it costs money. I’ve searched the net and found an open source sharepoint clone released by Alfresco (google it) but it’s more oriented towards replacing microsoft’s sharepoint technology than providing a platform for POSIX servers. it even integrates with Office!

One solution is to write my one tailored sharepoint system. that, or wait until someone else writes one. I’m probably going to write one myself (most likly using python since it’s very convenient for web applications) if i get the chance.

i’ll probably design it for technical projects rather then general purpose, it might include:

• a bug tracking tool
• a Mailing list/forum
• a basic file management system

you might wonder why i intend to write the previous tools all over again appose to using will established tool already available. the answer is simple:

Better integration with the system
no need for separate passwords for each system and so on
Each tool instance would be specific to the project it serves
No more overcrowded forums/bug trackers. when you access the tool it will only represent the it’s parent project.

In conclusion, I hope I don’t need to write the thing. but if no other sutable choices exist, i’ll probably have to write it anyways. as usual, any feedback is appreciated 🙂

SIGTERMer

PS: I might also integrate OO.o if it provides the necessary functionality, and if i have enough time to read on the subject.

Advertisements

Written by seininn

May 24, 2009 at 12:52 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: