+1
On Sat, Jun 4, 2016 at 7:25 PM, Jignesh Patel wrote:
> Great to hear from our resident marketing guru. Awesome suggestion Greg!
>
> Here is another design. It has the logo and the word art with the full
> system name in it. Comments Greg? I may have misunderstood what you were
> suggesting.
>
Word art + cute animal mascot has worked well for a lot of Apache projects.
This guy (a Basilisk lizard) seems appropriate:
https://i.ytimg.com/vi/PgSvN70lJ6w/hqdefault.jpg
The swoop of his tail could be incorporated into the flourish of the
capital 'Q'.
On Sat, Jun 4, 2016 at 7:25 PM, Jignesh
Great to hear from our resident marketing guru. Awesome suggestion Greg!
Here is another design. It has the logo and the word art with the full system
name in it. Comments Greg? I may have misunderstood what you were suggesting.
Powerpoint is also attached if someone is feeling adventurous. No
Cool logos Jignesh!
Personally I'm a fan of word art that says what the brand is, so that
everyone will know without requiring much education.
So I would consider "Quickstep" in the logo. You can also choose an icon
to be part, or not.
Having branded 3 Apache projects now, I will tell you that
Hello Quickstep-pers: I think it would be good to have a logo for the project.
I created three simple ones for us to consider.
Ideally a logo is distinctive, renders well (so needs to be simple), and
reflects the project theme. As many of you may recall, when we started this
project, we had a
Github user zuyu commented on the issue:
https://github.com/apache/incubator-quickstep/pull/5
There is the only one gcc test killed by the Travis.
https://travis-ci.org/apache/incubator-quickstep/jobs/133990216#L5810
If we could somehow run it with 2 concurrent jobs li
Github user zuyu commented on the issue:
https://github.com/apache/incubator-quickstep/pull/5
@zuyu: Ok so we now reduce the configurations that we try. This seems bad
in general. I understand Travis is timing out. Do we know why?
---
If your project is set up for it, you can reply t
Github user pateljm commented on a diff in the pull request:
https://github.com/apache/incubator-quickstep/pull/6#discussion_r65807621
--- Diff: storage/StorageBlock.cpp ---
@@ -91,57 +91,30 @@ StorageBlock::StorageBlock(const CatalogRelationSchema
&relation,
all_indices
Intersting that when one comments on a PR the email to this list has the name
of the original author of the PR (in this case hbdeshmukh) rather than the
person who created the comment. Somewhat misleading.
Any tips on how to fix this?
Cheers,
Jignesh
> On Jun 4, 2016, at 3:55 PM, hbdeshmukh
Github user hbdeshmukh commented on the issue:
https://github.com/apache/incubator-quickstep/pull/7
@zuyu You are right, and we can undo that if needed. You are also right
that in the future, we must be careful to keep PRs focused.
---
If your project is set up for it, you can reply
Github user zuyu commented on a diff in the pull request:
https://github.com/apache/incubator-quickstep/pull/6#discussion_r65807414
--- Diff: storage/StorageBlock.cpp ---
@@ -91,57 +91,30 @@ StorageBlock::StorageBlock(const CatalogRelationSchema
&relation,
all_indices_in
Github user hbdeshmukh commented on the issue:
https://github.com/apache/incubator-quickstep/pull/7
@pateljm But the second commit is not related to this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user pateljm commented on a diff in the pull request:
https://github.com/apache/incubator-quickstep/pull/6#discussion_r65805554
--- Diff: storage/StorageBlock.cpp ---
@@ -91,57 +91,30 @@ StorageBlock::StorageBlock(const CatalogRelationSchema
&relation,
all_indices
Github user hbdeshmukh commented on the issue:
https://github.com/apache/incubator-quickstep/pull/7
Looks good @hbdeshmukh. Merged. I know clang is failing, but that appears
to be related to the ongoing LLVM issue.
---
If your project is set up for it, you can reply to this email an
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-quickstep/pull/7
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feat
15 matches
Mail list logo
