Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EABBA2009F3 for ; Fri, 20 May 2016 13:15:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E962F160A0E; Fri, 20 May 2016 11:15:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3AA941609AF for ; Fri, 20 May 2016 13:15:23 +0200 (CEST) Received: (qmail 54044 invoked by uid 500); 20 May 2016 11:15:20 -0000 Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.incubator.apache.org Delivered-To: mailing list dev@asterixdb.incubator.apache.org Received: (qmail 53664 invoked by uid 99); 20 May 2016 11:15:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2016 11:15:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 228E9180545 for ; Fri, 20 May 2016 11:15:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ELy-enlKsh-m for ; Fri, 20 May 2016 11:15:16 +0000 (UTC) Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9B7675F560 for ; Fri, 20 May 2016 11:15:15 +0000 (UTC) Received: by mail-wm0-f50.google.com with SMTP id a17so521918wme.0 for ; Fri, 20 May 2016 04:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=m0v+B1CB1StweiMkw1SHpEWXytqJtdA7NbvEOeUTJyQ=; b=REij4UPIMx+iqIfgqA73BYmixo10xJnZ0090ss7IBcIcnYFcJp517mTKA6TmH16y8a XckrVlX4DImkGBfaLce5qIyQ1TB6HB/0XXPS5K5Gdu5+Lqdqij96+DfEJg4XH/KFovUt ds70gGeRuFC0XXkxfNtENdi23orwohdBlV5dE7KIgcSypqsm6/bqGX1UsrsF3CNbYlZe aUj6Vs1Pp60XzrzEj+cG+yTaREwR284RnrY4aLSoaIUsi30ejgTl7fUVNsHoZvgoyvII jHeJqAiucEYXXBpQkTLMQeBGJ40UW3NJOy/jALxhlF6c3s+nLYZNeSSxla+0eFQja9eR PZfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=m0v+B1CB1StweiMkw1SHpEWXytqJtdA7NbvEOeUTJyQ=; b=Wu8I1hW6iM29LKxB6+C6YgeiGeC4a9zR5BXpFDmRcmSUKehmlXaKRWwY4Rc0IHP7YW lOvS+2RtZlYVih5LQOEdinDgnG8VWHmvqTTEvJGAxg4Ps/gUIABM/f/IcpVj3S7XsaFV 7sRTAu/rzTM9rGlcW4wKSk9D2eXvgTPniEmO2jAEqiiHQvuFNPulW2Wx9Ann9odu4smr 2W1V7kBTkLwDIFjWHqnkF6Pqa3TWXTaH4NPmVhHKN49ry58Ihb6id1kefKX/izJf0B87 9WYETFdrbXVZ5QLeqzpBfMBa+P+p94iXLuh9vkZfjswMtY1hCub4Q2qJTFPVVeOa+3Jz gPzw== X-Gm-Message-State: AOPr4FXgF70k7fNFnqVutHzE8M0se7uvE1Trd02KZTxZOflXDpJHgmCnDO73qhio+YhI5XcW8A3Gdhsou5UaKQ== MIME-Version: 1.0 X-Received: by 10.28.31.73 with SMTP id f70mr3313657wmf.77.1463742914057; Fri, 20 May 2016 04:15:14 -0700 (PDT) Received: by 10.194.148.101 with HTTP; Fri, 20 May 2016 04:15:13 -0700 (PDT) In-Reply-To: References: <98B478C0-167B-4584-A5D9-312012DD5847@apache.org> <2B382C91818C51E9.d1d88564-a987-4615-ba44-540ccb995e1e@mail.outlook.com> <2B382C91818C51E9.58f6e315-8fbd-4f49-ac57-2cee04c33b66@mail.outlook.com> Date: Fri, 20 May 2016 16:45:13 +0530 Message-ID: Subject: Re: Commencing work on ASTERIXDB-1375 : Revise web UI From: Kaveen Rodrigo To: dev@asterixdb.incubator.apache.org, chillery@hillery.land Content-Type: multipart/alternative; boundary=001a114b415c6f5e7805334434cc archived-at: Fri, 20 May 2016 11:15:24 -0000 --001a114b415c6f5e7805334434cc Content-Type: text/plain; charset=UTF-8 Thanks Chris, that cleared a lot of things, thanks again. I will be pulling from upstream and rebasing frequently, even if not I don't think it would be fine since I will be working on the static files for the webui therefore it won't be a big issue. cheers, Kaveen On 20 May 2016 at 13:22, Chris Hillery wrote: > On Fri, May 20, 2016 at 12:34 AM, wrote: > > > > > > > Hello Chris, > > > > > > I was planning to do the incremental commits to my fork and then at the > > end of the summer to push my branch upstream, > > > > > > Will this be a problem? > > > If you rebase your work regularly, then you shouldn't have a problem > proposing your changes all at once at the end of the summer. However I > still think it will be easier both for you and for your reviewers if you > propose smaller changes for review more often rather than saving everything > up. > > > > > Or should I work on the main repo (in a branch) and commit there, > > > You won't be able to literally commit to the main repository, even in a > branch. (I'm assuming that you're not an Apache Committer on the AsterixDB > project - correct me if I'm wrong.) You should clone the Apache GitHub > mirror instead. > > You could fork that mirror if you want, but if you do so, you'll need to > keep the fork up to date in addition to rebasing your work. It's possibly > worth doing if you are going to be batching up a lot of work before > committing, because the fork then serves as an off-site backup of your work > in progress. It's not really *necessary* to have a fork unless you intend > to collaborate frequently with other developers, though. > > > I did setup a Gerrit account, that's only for review right? > > > > It's for review, yes, but a successful review is a pre-requisite for the > code to actually get committed to the main repository. If you've never used > Gerrit before, there's a bit of a learning curve and setup necessary. > That's another reason I suggested more frequent commits - that way you > figure out how to work with Gerrit in, say, June, instead of having to deal > with those problems for the first time right at the end of the summer. > > Ceej > aka Chris Hillery > -- Kaveen Rodrigo Personal Website - (lifeofenigma.com) Software Engineering Undergraduate, Informatics Institute of Technology Sri Lanka (Affiliated with University of Westminster, UK) *Contact Information* *Mobile* +94779684740 *E-Mail* kaveen.2013175@iit.ac.lk | u.k.k.rodrigo@gmail.com --001a114b415c6f5e7805334434cc--