That's a great idea. Since you recently ran into such issues, please feel free to add that in to the User Guide and I would be happy to review it.
The RST source code for the User and Dev guides can be found here:
How about adding a "common errors and possible solutions"
section?? Many of the newbies like me faced a few hiccups while trying
to build and use Flume-NG for the first time. It would be pretty
useful for people like me. But it's just a suggestion from my side.
Pardon me if it sounds too childish. I am actually very new to the
open source world. Many thanks.
On Mon, Jul 2, 2012 at 11:02 PM, Mike Percy <firstname.lastname@example.org> wrote:
> Hi Flume users & devs,
> Now that we have branched in preparation for a Flume 1.2.0 release, we have
> one week to improve the documentation coverage and find any major issues
> before RC0.
> Looking at the docs, we are missing coverage on several key components, so
> this is a ripe opportunity for new contributors come in and submit a patch
> or two. The plan is still to begin the release vote on Monday, July 9, and I
> know some folks in the U.S. plan on taking a few days off this week for
> Independence Day, so if you want to contribute, please get them in early so
> the available committers can review the patches and commit them.
> Committers - please commit any changes to the trunk as usual, and I'll be
> happy to backport applicable doc updates, build fixes, or any critical bug
> fixes to the release branch. Just send a note to the list.
> Looking forward to a great 1.2.0 release!