-RE: Wiki pages clean-up
Yash Sharma 2013-09-20, 10:22
Good work Harri.
The wiki is much more neater. Don't worry about #2 :) :)
From: Harri Kinnunen [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 20, 2013 1:52 PM
To: <[EMAIL PROTECTED]>
Subject: Re: Wiki pages clean-up
I've put the pruned wiki pages into production:
The rationale was to split the on content on "use case basis" (i.e. 'install', 'use', 'compile', 'contribute', ...) and eliminate the duplicate (and sometimes conflicting) content.
Couple of items:
1) Credit where it's due: Snatched parts of the "Installing Binaries" from Ben's github page.
2) Overrode Yash's changes in the wiki homepage. (Sorry...)
3) I'm having trouble compiling on Eclipse based on the instructions in https://cwiki.apache.org/confluence/display/DRILL/Sources+and+Setting+Up+Development+Environment .. Left it like that anyways as it could just be me and my setup. I'll test a bit further and get back to this one.
On 18.9.2013, at 20.11, Jacques Nadeau <[EMAIL PROTECTED]> wrote:
> Much better, I think you should make it the new home.
> On Mon, Sep 16, 2013 at 5:05 PM, Harri Kinnunen
> <[EMAIL PROTECTED]>wrote:
>> the currently the wiki pages contain lots of overlapping (and
>> conflicting) items. Mostly this is on the "getting the source" and
>> "building it" areas. Some of the top-level items ("Use Cases", for
>> example) point to empty pages.
>> I did some cleaning up on the one, but didn't quite finish it yet.
>> A draft version:
>> Still to do:
>> 1) Grab the "Sample queries" from the current Demo How-to and/or
>> Ben's work on the github.
>> 2) Figure out how to make the eclipse build work and document it in
>> "Setting up the dev env."
>> Comments? Wrong direction/right direction?
NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.