getting set up for developing / contributing

[Taylor Gautier <tg...@tagged.com>]

Hi,

We might embark upon some Kafka hacking.  And it may end up turning into
something worth contributing back.  I'd like to know how we should start.
 The SVN URL listed on the apache site seems to not have any branches or
tags in it, and this makes me think it's a dup of an internal svn repo -
which means possible merging issues if we start from there, and obviously
the git repo is RO so not the way to go.

Please advise.

Thx.

Re: getting set up for developing / contributing

[Neha Narkhede <ne...@gmail.com>]

Hi Taylor,

I'm not sure if you've seen this earlier, but the process of contributing is
documented here <http://incubator.apache.org/kafka/contributing.html>
If some things are not clearly explained there, please let us know how we
can improve the instructions.

Thanks,
Neha

On Thu, Sep 22, 2011 at 8:28 AM, Taylor Gautier <tg...@tagged.com> wrote:

> Hi,
>
> We might embark upon some Kafka hacking.  And it may end up turning into
> something worth contributing back.  I'd like to know how we should start.
>  The SVN URL listed on the apache site seems to not have any branches or
> tags in it, and this makes me think it's a dup of an internal svn repo -
> which means possible merging issues if we start from there, and obviously
> the git repo is RO so not the way to go.
>
> Please advise.
>
> Thx.
>

Re: getting set up for developing / contributing

[Chris Burroughs <ch...@gmail.com>]

Hi Taylor http://incubator.apache.org/kafka/code.html is the right place
with the authoritative repo.  The reason there arn't any tags or
branches is because kafka has not had any official releases as an Apache
Podling, and there was no good way to import the pre ASF tags from github.

On 09/22/2011 11:28 AM, Taylor Gautier wrote:
> Hi,
> 
> We might embark upon some Kafka hacking.  And it may end up turning into
> something worth contributing back.  I'd like to know how we should start.
>  The SVN URL listed on the apache site seems to not have any branches or
> tags in it, and this makes me think it's a dup of an internal svn repo -
> which means possible merging issues if we start from there, and obviously
> the git repo is RO so not the way to go.
> 
> Please advise.
> 
> Thx.
> 

Re: getting set up for developing / contributing

[Taylor Gautier <tg...@tagged.com>]

Thanks!

Well, I think you saw what we plan to do - write to an auxiliary topic with
the offsets that are generated so that we reading from that topic can easily
get us the nth message from the top.

Does that make sense?  Knowing the code do you foresee any gotchas with that
approach?

On Thu, Sep 22, 2011 at 12:28 PM, Jay Kreps <ja...@gmail.com> wrote:

> Welcome! We do all development in the open, there are no secret company
> repos (or at least not at linkedin).
>
> Our branching strategy so far is basically that we do development on trunk
> and create branches for releases. We have only been in apache/svn for a
> very
> short time so this is new. In git we had lots of branches flying around all
> over the place. This is a little slower but I think we are getting much
> better review on code that goes in. We will see how it goes.
>
> We would love to add docs to help people get started, but we don't have
> much
> now. If you write anything down and feel willing to add a page to the site
> (its in svn) or the wiki or your personal blog that would be wonderful.
>
> One thing that can be helpful when starting on a project is to spend some
> time talking through ideas, mysterious code, or whatever else with the
> existing contributors. If you are interested in chatting about stuff I (and
> probably others) would be totally happy to do so. If you are in the bay
> area
> we can do it in person and if not maybe just by phone. Obviously this is
> not
> necessarily, but might help you out if you have questions.
>
> Also feel free to discuss any ideas around your usage on the user or dev
> mailing lists. I am happy to compare and contrast with how we have done
> things at linkedin and how that worked out for us.
>
> -Jay
>
> On Thu, Sep 22, 2011 at 8:28 AM, Taylor Gautier <tg...@tagged.com>
> wrote:
>
> > Hi,
> >
> > We might embark upon some Kafka hacking.  And it may end up turning into
> > something worth contributing back.  I'd like to know how we should start.
> >  The SVN URL listed on the apache site seems to not have any branches or
> > tags in it, and this makes me think it's a dup of an internal svn repo -
> > which means possible merging issues if we start from there, and obviously
> > the git repo is RO so not the way to go.
> >
> > Please advise.
> >
> > Thx.
> >
>

Re: getting set up for developing / contributing

[Jay Kreps <ja...@gmail.com>]

Welcome! We do all development in the open, there are no secret company
repos (or at least not at linkedin).

Our branching strategy so far is basically that we do development on trunk
and create branches for releases. We have only been in apache/svn for a very
short time so this is new. In git we had lots of branches flying around all
over the place. This is a little slower but I think we are getting much
better review on code that goes in. We will see how it goes.

We would love to add docs to help people get started, but we don't have much
now. If you write anything down and feel willing to add a page to the site
(its in svn) or the wiki or your personal blog that would be wonderful.

One thing that can be helpful when starting on a project is to spend some
time talking through ideas, mysterious code, or whatever else with the
existing contributors. If you are interested in chatting about stuff I (and
probably others) would be totally happy to do so. If you are in the bay area
we can do it in person and if not maybe just by phone. Obviously this is not
necessarily, but might help you out if you have questions.

Also feel free to discuss any ideas around your usage on the user or dev
mailing lists. I am happy to compare and contrast with how we have done
things at linkedin and how that worked out for us.

-Jay

On Thu, Sep 22, 2011 at 8:28 AM, Taylor Gautier <tg...@tagged.com> wrote:

> Hi,
>
> We might embark upon some Kafka hacking.  And it may end up turning into
> something worth contributing back.  I'd like to know how we should start.
>  The SVN URL listed on the apache site seems to not have any branches or
> tags in it, and this makes me think it's a dup of an internal svn repo -
> which means possible merging issues if we start from there, and obviously
> the git repo is RO so not the way to go.
>
> Please advise.
>
> Thx.
>