public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Konrad Djimeli <djkonro35@gmail.com>,
	kawa@sourceware.org, summer-of-code@gnu.org
Subject: Re: Interest in contributing to Kawa
Date: Wed, 15 Mar 2017 00:02:00 -0000	[thread overview]
Message-ID: <28ee97f2-49ce-df65-cdbf-ed25074945f3@bothner.com> (raw)
In-Reply-To: <CAK3i8CyUi0muKnwqc=k0xYjX_ZJOVk1UazSmu+01qqjdhD_pag@mail.gmail.com>

On 03/14/2017 01:04 PM, Konrad Djimeli wrote:
> My name is Konrad Djimeli a third year Computer Science Student at the
> University of Buea, Cameroon. I am interested in contributing to the
> Kawa project and I would like to work on the Google Summer of Code
> project "Update XQuery implementation ". I am very comfortable working
> with Java and XML and I have experience developing an X3D(XML base
> file format) importer for BRLCAD during the Google Summer of Code
> 2015.

Welcome!

> I have successful build and compiled the Kawa source code and have
> tested the XQuery functionalities.
>
> Please I would like to know what functionalities are priorities to the
> community that need to be added. I would also appreciate any
> suggestion on how to better familiarize myself with the project.

Unfortunately, I don't believe many people are using Kawa's XQuery implementation.
I don't get a lot of feedback (or bug reports) relating to XQuery.
I myself use it for the script I use to generate my photo-album web-pages,
plus it's part of Kawa's testsuite, but I don't spend much time enhancing it.
So XQuery enhancement is an ok project if someone is interested in it,
but if we have to choose between proposals (as seems likely), we're more likely
to prioritize another proposal.

If you do submit a proposal to work on Kawa-XQuery, I recommend you also
submit at least one other proposal.

Personally, I'd be more supportive if you wanted to work on one of the
GNU TexInfo-projects, which are also XML/HTML-related. However, texinfo(1)
requires facility with Perl and texinfo(2) requires facility with JavaScript.

-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

      reply	other threads:[~2017-03-15  0:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 20:04 Konrad Djimeli
2017-03-15  0:02 ` Per Bothner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28ee97f2-49ce-df65-cdbf-ed25074945f3@bothner.com \
    --to=per@bothner.com \
    --cc=djkonro35@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=summer-of-code@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).