sorry for the late reply. Thank you for your interest in GSoC and
Camel! If you'd like we have some issues in the JIRA labeled
`help-wanted` (and I'll go through the JIRA and mark more issues).
You can have a look at those and pick a smaller one to get started and
learn about how the project is structured/built and how to contribute.
For the new components you mentioned it would be good to write a
comment in the issue tracker that you're considering contributing the
implementation to let anyone else know that you might be working on
For GSoC in particular, be aware of the timeline, now is the time
to discuss the ideas, so if you have any further ideas you can bring
those to our attention now, we can create JIRA issues for those and
mention that you'll be working on them. This would be a good
opportunity for you to work on something that you find interesting and
something that the Camel project can benefit from as well.
I have taken a brief look at the project and its structure. And now have questions about the proposals.
- Implementing a single component doesn’t seem to be really 3-months project to me (for now I think it may take maybe about a month). So consequently following question appears: how to make a project proposal? Should I take several components? Or what is the best way to come up with proposal and to whom should I send it?
- What is the best way to communicate on a particular issue? In Jira?
(make sure you're subscribed to the dev list, I had to approve your
last email from the moderation queue).
On Thu, Feb 27, 2020 at 3:17 AM Kirill Yankov <[hidden email]> wrote:
> - Implementing a single component doesn’t seem to be really 3-months project to me (for now I think it may take maybe about a month). So consequently following question appears: how to make a project proposal? Should I take several components? Or what is the best way to come up with proposal and to whom should I send it?
If you think you can take on several components that's very welcome,
bare in mind that each component should also include component
documentation, Spring Boot starter, preferably an example and also
preferably OSGi support. For the OSGi support in particular you might
need to contribute to whichever library you might be using to add the
necessary OSGi metadata, or define a wrapper bundle at
Servicemix/Karaf. Adding OSGi support is not a showstopper, we have
some components that do not have it, but we have users relying on OSGi
and it would be nice to have.
Previous years we discussed the ideas with the students on the dev
mailing list, they noted on the JIRA that they're interested in
working on it -- so that other GSoC students also see. Then the
student prepared a proposal and shared with us on the dev mailing
list for comments. Writing the proposal ahead of time and including
the Camel comitters increases your chances of getting accepted, as we
can assure that all the necessary information is in the proposal
before submission to Google.
> - What is the best way to communicate on a particular issue? In Jira?
The way we usually do it is, for more impactful changes we discuss on
the mailing list, for smaller/not-as-impactful changes we just use the
JIRA comments. We usually also point from JIRA to the mailing list
thread from the mailing list archives.
For example, a new component would be just a few comments on the JIRA,
whereas adding a new reactive engine to Camel-core would start first
as a discussion on the mailing list.
Feel free to ask specific questions if this doesn't cover everything
you were curious about.