[sip-comm-dev] Re: SIP: Spell Checker Implementation


#1

Since I wasn't the mentor of the Spell Checker Google Summer of Code
project, I'm not sure what's blocking its merging into trunk (i.e. the
build) and I guess it's a matter of committer priorities.

···

On Thu, Jul 22, 2010 at 12:41 PM, Nitish Upreti <nitishupreti@gmail.com> wrote:

If a spell checker exist at branches/gsoc08/spellcheck , why is it yet
not integrated with the alpha buid?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Thanks for the information. I was working on this thing for some time
now.(Learning loads during the process) :slight_smile:
Should I continues with the left over work and release an another
patch?

As you said, you've already invested time and effort in your
implementation. So my advice is to at least compare your
implementation to the one we have and weigh the advantages and
disadvantages of the two in order to produce an implementation which
is superior to the one we have.

Do you think it will be worthy to the SIP community or should I
just pick up something else?

While I cannot answer on behalf of the SIP Communicator community, I
do want a spell checker - it's such a basic feature.

As lots of stuff seems pending! What
would you recommend?

For starters, don't contact a developer in private - write to the
mailing lists so that the whole SIP Communicator community knows you
need help.

Then, before starting work on something you intend to contribute to
SIP Communicator, write to the mailing lists so that you know
beforehand whether there's interest in it, whether it stands a chance
of being integrated into SIP Communicator and, as in your case,
whether there's a competing implementation.

···

On Thu, Jul 22, 2010 at 12:51 PM, Nitish Upreti <nitishupreti@gmail.com> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

As you said, you've already invested time and effort in your
implementation.

I was the gsoc student that did the spell checker and keybinding chooser
patches that never got integrated. At the time there were competing
priorities due to working up toward a new release and since has been
forgotten. The screenshots and code for the project are also available at:
http://www.atagar.com/misc/gsocBlog/

For starters, don't contact a developer in private - write to the

mailing lists so that the whole SIP Communicator community knows you
need help.

This was a public discussion, the thread's available at:
http://osdir.com/ml/voip.sip-communicator.devel/2008-08/msg00078.html

I pinged Yana occasionally afterward and after a few months without any sign
becoming a priority I moved on, and now work with the tor community. The
branch is a couple of years old so integration will now be nontrivial,
however I'd be happy to answer questions if you have any. Cheers! -Damian

···

On Thu, Jul 22, 2010 at 3:00 AM, Lubomir Marinov <lubo@sip-communicator.org>wrote:

On Thu, Jul 22, 2010 at 12:51 PM, Nitish Upreti <nitishupreti@gmail.com> > wrote:
> Thanks for the information. I was working on this thing for some time
> now.(Learning loads during the process) :slight_smile:
> Should I continues with the left over work and release an another
> patch?

As you said, you've already invested time and effort in your
implementation. So my advice is to at least compare your
implementation to the one we have and weigh the advantages and
disadvantages of the two in order to produce an implementation which
is superior to the one we have.

> Do you think it will be worthy to the SIP community or should I
> just pick up something else?

While I cannot answer on behalf of the SIP Communicator community, I
do want a spell checker - it's such a basic feature.

> As lots of stuff seems pending! What
> would you recommend?

For starters, don't contact a developer in private - write to the
mailing lists so that the whole SIP Communicator community knows you
need help.

Then, before starting work on something you intend to contribute to
SIP Communicator, write to the mailing lists so that you know
beforehand whether there's interest in it, whether it stands a chance
of being integrated into SIP Communicator and, as in your case,
whether there's a competing implementation.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net