i didn't say they couldn't learn a new sustem, i said they wouldn't want to.
last time i checked there was no option to connect to any other groupware product other than exchange in the default install of linux. thus there is no "native" support for kolab. if they developed the server to accept connections from outlook by simply selecting "Microsoft Exchange" in the account setup wizard, that would be native support. yeah, i did read the articles.
some of the replies imply that it is the cost of the software that i am concerned about.
far from it.
i see that the connectors are all very well priced, but they are still connectors.
the trouble is not the cost, the trouble is the idea that the user has another piece of software to install on their desktop. if cost was the concern, then any of the groupware packages out there would be a no brainer. transparency is the issue here. obviously the developers have done a bang up job of cloning the value adding features of exchange in their projects, but they are still neglecting the most widely implemented client software.
what the orgainzations that are willing to use oss server technology want is a drop in solution... this is not a drop in solution.
for those/.'ers who said "write one yourself", i am not going to lie, i can't... wouldn't have the first clue where to start. but what i do know is what consumers want. and i also know what business purchasing and it departments want; and that's a replacement for exchange, that installs and functions like exchange.
once again the open source community releases an exchange killer, and once again it is missing the most important component...
native integration with outlook.
i said this before in another post, but i am going to say it again. businesses aren't ready for desktop linux, which means server side solutions (no matter how brilliant) MUST work with the desktop apps that employees use. no one wants to relearn their e-mail client; and yes i am aware that evolution is almost identical to outlook at the interface level. but the truth of it is, the perception of any new desktop software is "now i have to learn everything all over again". it's the illusion of difficulty, so we as developers (and by we i mean you:) ) should make it our primary goal to lessen the difficulty of the intgration with newer, oss technology where ever we can
Re:when are we going to learn?
on
Opengroupware
·
· Score: 1
so there is no other application that has to be installed on the client machine... no connector software at all. you just go through the setup and tell the outlook client to find an exchange server that is really OGo?
somehow i don't think that is correct.
perhaps you and i have different opinions on what "natively connecting" is.
when are we going to learn?
on
Opengroupware
·
· Score: 2, Insightful
you want to replace exchange, there is only one way:
make the server talk to outlook natively
no connectors, no webdav to mapi, no nothing
the simple truth is that outlook rules corporate email... not because it syncs with handhelds, because it is what everyone in the office, that isn't us, is used to using.
build a groupware server that works with outlook without any additional plug-ins, and exchange will disappear in time
no one cares about any other mail/groupware client but outlook... when linux is ready to be deployed to all the desktops in an organization (which it isn't yet, and don't try to tell me otherwise) a groupware server that supports "not-outlook" will be viable.
i think that canada, the us, britain... most of the mid-east, asia, africa and australia (although i may be reaching there) are all fucked.
the world's kind of a mess all around, mainly because of imaginary global economics that ensure that hungry people stay that way while we (including me, i'm no better) get fat and whine about anything we can from the comfort of our clean, disease free homes clicking and typing ona piece of electronics with a pricetag that looks like some families yearly income.
we're all guilty, and we're all making it worse day by day.
good plan... i would add that leaving them in less conspicuos(sp?) places, like near a coffee machine, in the boardroom or on the back of a toilet would be more effective. this will make it seem that employees are reading them amongst themselves as if gearing up for something big... like a class action or a petition.
not only does the revised plan have fear, but it does not forget uncertainty and doubt. read a little tzu, make a little meme... presto, you're calling the shots without calling a thing.
there's more to it than that
on
Ageism in IT?
·
· Score: 1
i think the bottom line is, old people are a financial liability... they get sick, they are really close to pension, they have developed lives for themselves that often come before work...
youth is wasted on the young, and wisdom is wasted on the old.
640k is more than anyone will ever need.
- Microsoft
why would any normal person want a computer in their home?
- HP
you want xerox to market a product called a "mouse"?
- Xerox
well i don't see a problem with that, all the money is in the hardware anyway, not this "software" stuff
- IBM
Slashdot Mirror
ouch.
the learning curve is not difficult, i never said it was... getting users to believe that is another thing entirely.
last time i checked there was no option to connect to any other groupware product other than exchange in the default install of linux. thus there is no "native" support for kolab. if they developed the server to accept connections from outlook by simply selecting "Microsoft Exchange" in the account setup wizard, that would be native support. yeah, i did read the articles.
far from it.
i see that the connectors are all very well priced, but they are still connectors.
the trouble is not the cost, the trouble is the idea that the user has another piece of software to install on their desktop. if cost was the concern, then any of the groupware packages out there would be a no brainer. transparency is the issue here. obviously the developers have done a bang up job of cloning the value adding features of exchange in their projects, but they are still neglecting the most widely implemented client software.
what the orgainzations that are willing to use oss server technology want is a drop in solution... this is not a drop in solution.
for those /.'ers who said "write one yourself", i am not going to lie, i can't... wouldn't have the first clue where to start. but what i do know is what consumers want. and i also know what business purchasing and it departments want; and that's a replacement for exchange, that installs and functions like exchange.
native integration with outlook.
i said this before in another post, but i am going to say it again. businesses aren't ready for desktop linux, which means server side solutions (no matter how brilliant) MUST work with the desktop apps that employees use. no one wants to relearn their e-mail client; and yes i am aware that evolution is almost identical to outlook at the interface level. but the truth of it is, the perception of any new desktop software is "now i have to learn everything all over again". it's the illusion of difficulty, so we as developers (and by we i mean you :) ) should make it our primary goal to lessen the difficulty of the intgration with newer, oss technology where ever we can
somehow i don't think that is correct.
perhaps you and i have different opinions on what "natively connecting" is.
make the server talk to outlook natively
no connectors, no webdav to mapi, no nothing
the simple truth is that outlook rules corporate email... not because it syncs with handhelds, because it is what everyone in the office, that isn't us, is used to using.
build a groupware server that works with outlook without any additional plug-ins, and exchange will disappear in time
no one cares about any other mail/groupware client but outlook... when linux is ready to be deployed to all the desktops in an organization (which it isn't yet, and don't try to tell me otherwise) a groupware server that supports "not-outlook" will be viable.
you'd think that she would be happy that she was getting paid for downloaded songs period.
http://macteens.com/news_more.php?id=122_0_3_0_C
i'm gonna get placebo'd i just know it.
i think that canada, the us, britain... most of the mid-east, asia, africa and australia (although i may be reaching there) are all fucked. the world's kind of a mess all around, mainly because of imaginary global economics that ensure that hungry people stay that way while we (including me, i'm no better) get fat and whine about anything we can from the comfort of our clean, disease free homes clicking and typing ona piece of electronics with a pricetag that looks like some families yearly income. we're all guilty, and we're all making it worse day by day.
good plan... i would add that leaving them in less conspicuos(sp?) places, like near a coffee machine, in the boardroom or on the back of a toilet would be more effective. this will make it seem that employees are reading them amongst themselves as if gearing up for something big... like a class action or a petition.
not only does the revised plan have fear, but it does not forget uncertainty and doubt. read a little tzu, make a little meme... presto, you're calling the shots without calling a thing.
i think the bottom line is, old people are a financial liability... they get sick, they are really close to pension, they have developed lives for themselves that often come before work... youth is wasted on the young, and wisdom is wasted on the old.
640k is more than anyone will ever need. - Microsoft why would any normal person want a computer in their home? - HP you want xerox to market a product called a "mouse"? - Xerox well i don't see a problem with that, all the money is in the hardware anyway, not this "software" stuff - IBM
well, when SGI lays you off this week, you're going to have plenty of time to learn how to create programs in binary, just like your friends.