Hello Darrell,
To prevent development from slowing to
an absolute crawl at times when I get
stuck or too busy I pass issues to
contractors. This is not a regular
occurrence but still my biggest
out-of-pocket expense related to the
project.
I'd actually like to do this more often
to get things done faster. Also, it
seems that we will have to start
working with Microsoft support in the
near future. I haven't had to do this
in the past but things are settling
down and the more difficult
compatibility problems remain. An MS
incident is about $250 each I believe.
None of this would be needed if we
had a few capable volunteer developers
though. But I'm not holding my breath
at this point :)
Though for the project to become a
viable Open Source project, we will
have to find a way to attract those
volunteers. I honestly do not know
why we have done so badly in this
area. But for the almost 4 years of
existence as a Sourceforge project
we have attracted 3 developer
contributions outside my own.
Unpaid developer work probably adds
up to about 200 lines of code.
Excluding external projects but
including rewrites Open Connector
has definitely had 10+ _thousand_
lines of code written. Most likely
a lot more, haven't checked.
Is there something in particular
that makes that project unattractive
to get into?
So to see this project to completion
I'd say choose one of those in that
order...
1. Volunteer development time if you
have the relevant background.
2. Bribe, blackmail or otherwise
convince someone with that skill-
set to help out with the project :)
3. Consider donating any amount to
the project to offset expenses.
To give an idea of the work needed...
Most estimates and accounts I've
received suggest that an Outlook
connector project requires 3-6 full-
time developers 6-12 months to
complete. Also, that is considering
that they do not write the entire
project from scratch. We are writing
from scratch given that the code is
LGPL.
The upside is though that we already
have a working connector. But there
is still work to get it to finished
and optimized.
Best regards,
Kervin
--- Darrell McGuire [EMAIL PROTECTED] wrote:
Kervin-
You mention ...access to funds... give me some
perspective if you
would please as to what amounts of money might be
helpful/relevant to
different tasks. If someone can throw in a couple
hundred here and
there is that actually useful, or are you only
talking about relevant
amounts only being in the thousands or tens of
thousands of dollars?
Thanks,
Darrell McGuire
Pegasys Computer Technologies, Inc.
Kervin L. Pierre wrote:
Hello Marc,
Thanks for the feedback.
That bug has been fixed in the current
version. Please try Milestone 2 when
that comes out. Thanks.
It's caused by a faulty check on my
part. Your configuration settings are
ok, but the file check fails due to
locking.
Best regards,
Kervin
--- Marc Boschma [EMAIL PROTECTED] wrote:
Hi,
I installed the Alpha connector and tried to
configure a file backed
account but I continually get Please Configure an
Open Connector
How do I get started?
Marc
On 27/09/2006, at 1:21 AM, Kervin L. Pierre wrote:
Hello,
Thanks for your continued interest in Outlook
Connector.
Yes we have been taking our time on this one
haven't we :)
The project is moving forward though. I am
hoping that stable, functioning betas will
attract new resources to the project in the
future. But as you've suspected, as of now,
resources are very limited.
Quick status
1. MAPI Message Storage Provider and MAPI
Transport provider both work. There hasn't
been _any_ performance optimization on those
yet, so expect a first run of 3mins and
subsequent startups may take that long as
well. Performance optimization is scheduled
for last. But the core functionality for
adding/deleting/modifying CalDAV events on
CalDAV servers work and have been tested
on Cosmo [ http://cosmo.osafoundation.org ]
and Oracle CalDAV [ not released as yet ].
2. The final major component left for
development, The address book provider is
being worked on. This where I've been
spending my dev time lately. This will will
allow the sharing of individual calendars.
I estimate this component can be in Beta
with a solid month on development; but that
depends on our our other/paid projects are
going.
3. Working on getting Bedework CalDAV
[ http://bedework.org ] support done.
4. The MS2 is 'Milestone 2'. The current
build on sourceforge is 'Milestone 1'.
That was the first 'release' build of the
project that would actually do something
useful. It will add/modify/delete CalDAV
events on a CalDAV server. MS2 fixes a
few annoying bugs so that users can test
individual calendars a bit more. It also
introduces a new refactored set of
