manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: GSoC 2015 Tasks
Date Thu, 12 Feb 2015 15:11:05 GMT
Hi Rafa,

I'm willing to support *both* development efforts, but I can't do this in
anything like an official capacity.  So one way forward would be for you to
handle the GSoC processes, and some development questions, but have the
students work with the list for most of their technical direction.  What do
you think?


On Thu, Feb 12, 2015 at 9:51 AM, Rafa Haro <> wrote:

> Hi devs,
> I have created two issues (CONNECTORS-1161 and CONNECTORS-1162) labeled
> with gsoc2015 label. The first one is about developing a Confluence
> repository and authority connector and the second one is about creating an
> Apache Kafka output connector. I have created them because I already know,
> at least, one student which is interested in both and he has some
> experience with ManifoldCF. Once the issues are public, others students can
> also send their proposals and everyone interested in mentoring this year
> can review them and decide which one is better.
> I was mentoring two GSoC projects last year, both for Apache Stanbol
> project. The experience was great, but even taking into account that both
> students were also experienced in Apache Stanbol, it normally takes a lot
> of time for the mentor. So this year I wouldn’t mind to be mentor again,
> but would take only one project. I aim all committers to register as
> mentors this year and of course, if you think there are more tasks that
> could fit with a great GSoC project for Manifold, don’t hesitate to create
> them in Jira. In my opinion, GSoC, in most of the occasions, is also a
> great way to contribute to the project, specially for committers like for
> instance me that currently don’t have the opportunity to have a regular
> contact with the project in my daily work and need to find the time and the
> way to make contributions.
> Cheers,
> Rafa

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message