Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # user >> Re: Call for documentation


Copy link to this message
-
Re: Call for documentation
Thanks a lot for the pointers Mike. Since it is the first time I am
trying something like this, so I needed these.

Regards,
    Mohammad Tariq
On Tue, Jul 3, 2012 at 4:19 AM, Mike Percy <[EMAIL PROTECTED]> wrote:
> By the way - if you want guidance on how to submit a patch, this page should
> help:
> https://cwiki.apache.org/confluence/display/FLUME/How+to+Contribute#HowtoContribute-ProvidingPatches
>
> Regards,
> MIke
>
>
> On Mon, Jul 2, 2012 at 2:50 PM, Mike Percy <[EMAIL PROTECTED]> wrote:
>>
>> Hi Mohammad,
>> 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:
>>
>> https://svn.apache.org/viewvc/incubator/flume/trunk/flume-ng-doc/sphinx/
>>
>> Regards,
>> Mike
>>
>>
>> On Mon, Jul 2, 2012 at 1:53 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:
>>>
>>> Hello Mike,
>>>
>>>          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.
>>>
>>> Regards,
>>>     Mohammad Tariq
>>>
>>>
>>> On Mon, Jul 2, 2012 at 11:02 PM, Mike Percy <[EMAIL PROTECTED]> 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!
>>> >
>>> > Regards,
>>> > Mike
>>> >
>>
>>
>