Hello potential Gophers!

Spurred by several simultaneous and wholly unrelated requests for "how can
I help contribute to make streaming with the Go SDK happen?", I've written
a bunch of things down to answer them. While I'm very pleased with these
offers, I don't scale that well, and so I've written it all down so that a)
I don't need to repeat myself, and b) can look it up myself for future
reference.

First, I've added to the Go Tips
<https://cwiki.apache.org/confluence/display/BEAM/Go+Tips> page a
contribution recommendations section, linking to specific JIRAs or other
pages on how to contribute, and a section on recommendations on developing
the Go SDK.

Second, one of those pages is a guide to Supporting Streaming in the Go SDK
<https://cwiki.apache.org/confluence/display/BEAM/Supporting+Streaming+in+the+Go+SDK>
with
a biased overview of what needs to be done, and a general task breakdown,
task ordering, along with associated JIRAs.  The JIRAs have a rough set of
links and guides for how to add any of the given features and what parts of
the SDK are important.

The JIRAs are not 100% comprehensive, nor are they "starter" tasks, and nor
are they "good things to learn Go with", or even "good to learn beam with",
but if you already know Beam, or you know Go, you might be the right person
to give it a try. The JIRAs should be enough for folks to start reading the
right places in the SDK so these features can be added, and more specific
questions can be asked. Some even have certain approaches recommended for
Go, but these will need to be handled on a case by case basis.

This is not the entirely of available "work surface" on the Go SDK, but
just the aspects beneficial to streaming. It does cover a lot of the
remaining feature surface though.

It's important to emphasize:* I do not plan on doing all this work myself*.
This is free for the community to contribute to, if streaming Go is
something you'd like. Unless someone's assigned the JIRA, it's safe to
assume it's not yet spoken for. I'll be around to lend a hand or review
code though.

I hope to have a few other updates about the Go SDK for you in the next few
months, but those will wait until their time.

Thank you for your attention, and do let me know if you have questions or
suggestions, or that you're jumping in!
Robert Burke
Defacto TL of Beam Go (until someone better comes along)
[email protected]

Reply via email to