You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by dong wang <el...@gmail.com> on 2015/03/18 04:56:09 UTC
curious about the kylin github website
as we know, we have 2 urls to get Kylin
1, https://github.com/apache/incubator-kylin
2, https://github.com/KylinOLAP/Kylin
and as watched, it seems that staging of https://github.com/KylinOLAP/Kylin
can always keep the latest changes, thus if one wants to keep up with
kylin's developing process, we should get codes from staging of
https://github.com/KylinOLAP/Kylin instead of staging of
https://github.com/apache/incubator-kylin, is it right?
Re: curious about the kylin github website
Posted by Luke Han <lu...@gmail.com>.
New committer votes already there actually, soon these will not be the
issue. Please help to vote.
As I mentioned, that "staging" repo just for temporary purpose to keep it
as simple as possible to avoid additional efforts, but definitely will
switch to the main repo soon.
Thanks.
Luke
Best Regards!
---------------------
Luke Han
2015-03-18 16:02 GMT-07:00 Ankur Bansal <an...@gmail.com>:
> +1 on Git Pull Requests.
> We should use same process for regular contributors as the one we advocate
> for new contributors.
> Pull request should be a standard practice for the very purpose.
> I suggest getting rid of https://github.com/KylinOLAP/Kylin all together.
>
> - Ankur
>
> On Wed, Mar 18, 2015 at 1:35 PM, Julian Hyde <ju...@hydromatic.net>
> wrote:
>
> > How do people feel about pull requests and the github mode of
> development?
> > I agree with Ted that regular contributors should become committers, but
> > for others, or even for committers who are not ready to commit to trunk,
> > github forks and pull requests are a good way of working in public and
> > getting feedback early. Anyone who wants to contribute to kylin could
> > easily create a github account.
> >
> > Julian
> >
> >
> > On Mar 18, 2015, at 10:55 AM, Ted Dunning <te...@gmail.com> wrote:
> >
> > > On Tue, Mar 17, 2015 at 10:09 PM, Luke Han <lu...@gmail.com> wrote:
> > >
> > >> The other one is our staging code repo to simplify development since
> > many
> > >> of our team members do not have push privileges to Apache one yet
> (This
> > >> approach will be changed anytime without notification).
> > >>
> > >
> > > This is not a good practice. Effectively, what is happening is that
> > > development is happening in private with occasional burps to the public
> > > repo.
> > >
> > > If you have lots of people that you trust to be committers, you should
> > > start a vote to make them committers. Having more committers is not a
> > > problem... it is a good thing.
> >
> >
>
Re: curious about the kylin github website
Posted by Ankur Bansal <an...@gmail.com>.
+1 on Git Pull Requests.
We should use same process for regular contributors as the one we advocate
for new contributors.
Pull request should be a standard practice for the very purpose.
I suggest getting rid of https://github.com/KylinOLAP/Kylin all together.
- Ankur
On Wed, Mar 18, 2015 at 1:35 PM, Julian Hyde <ju...@hydromatic.net> wrote:
> How do people feel about pull requests and the github mode of development?
> I agree with Ted that regular contributors should become committers, but
> for others, or even for committers who are not ready to commit to trunk,
> github forks and pull requests are a good way of working in public and
> getting feedback early. Anyone who wants to contribute to kylin could
> easily create a github account.
>
> Julian
>
>
> On Mar 18, 2015, at 10:55 AM, Ted Dunning <te...@gmail.com> wrote:
>
> > On Tue, Mar 17, 2015 at 10:09 PM, Luke Han <lu...@gmail.com> wrote:
> >
> >> The other one is our staging code repo to simplify development since
> many
> >> of our team members do not have push privileges to Apache one yet (This
> >> approach will be changed anytime without notification).
> >>
> >
> > This is not a good practice. Effectively, what is happening is that
> > development is happening in private with occasional burps to the public
> > repo.
> >
> > If you have lots of people that you trust to be committers, you should
> > start a vote to make them committers. Having more committers is not a
> > problem... it is a good thing.
>
>
Re: curious about the kylin github website
Posted by Julian Hyde <ju...@hydromatic.net>.
How do people feel about pull requests and the github mode of development? I agree with Ted that regular contributors should become committers, but for others, or even for committers who are not ready to commit to trunk, github forks and pull requests are a good way of working in public and getting feedback early. Anyone who wants to contribute to kylin could easily create a github account.
Julian
On Mar 18, 2015, at 10:55 AM, Ted Dunning <te...@gmail.com> wrote:
> On Tue, Mar 17, 2015 at 10:09 PM, Luke Han <lu...@gmail.com> wrote:
>
>> The other one is our staging code repo to simplify development since many
>> of our team members do not have push privileges to Apache one yet (This
>> approach will be changed anytime without notification).
>>
>
> This is not a good practice. Effectively, what is happening is that
> development is happening in private with occasional burps to the public
> repo.
>
> If you have lots of people that you trust to be committers, you should
> start a vote to make them committers. Having more committers is not a
> problem... it is a good thing.
Re: curious about the kylin github website
Posted by Ted Dunning <te...@gmail.com>.
On Tue, Mar 17, 2015 at 10:09 PM, Luke Han <lu...@gmail.com> wrote:
> The other one is our staging code repo to simplify development since many
> of our team members do not have push privileges to Apache one yet (This
> approach will be changed anytime without notification).
>
This is not a good practice. Effectively, what is happening is that
development is happening in private with occasional burps to the public
repo.
If you have lots of people that you trust to be committers, you should
start a vote to make them committers. Having more committers is not a
problem... it is a good thing.
Re: curious about the kylin github website
Posted by Li Yang <li...@apache.org>.
Agree with PR against https://github.com/apache/incubator-kylin.
Leveraging https://github.com/KylinOLAP/Kylin is only a temporary
workaround. There are a few non-committer who is contributing heavily at
the moment. We tried PR against https://github.com/apache/incubator-kylin
at first and the result was me being the team bottleneck, doing fetching,
merging, pushing whole day long.
The situation will change soon once they are raised to committers.
Cheers
Yang
On Fri, Mar 20, 2015 at 7:02 AM, Luke Han <lu...@gmail.com> wrote:
> Ok, will work on it ASAP.
>
> Thanks.
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> 2015-03-19 11:46 GMT-07:00 Henry Saputra <he...@gmail.com>:
>
> > Luke,
> >
> > Please do not use https://github.com/KylinOLAP/Kylin anymore and to
> > move dev to the one under Apache mirror..
> > Need to make it READ only ASAP before making a release under Apache.
> >
> > New contributors send PR against
> https://github.com/apache/incubator-kylin
> > .
> >
> > There is no reason that contributors cannot contribute without commit
> > or push access.
> > Committers just one of the members of community that could commit code
> > to repo. Reviews still need to happen even for committers to help
> > maintain quality of code.
> >
> >
> > - Henry
> >
> > On Tue, Mar 17, 2015 at 9:09 PM, Luke Han <lu...@gmail.com> wrote:
> > > Please go with https://github.com/apache/incubator-kylin as primary
> > source
> > > of Apache Kylin code repo.
> > >
> > > The other one is our staging code repo to simplify development since
> many
> > > of our team members do not have push privileges to Apache one yet (This
> > > approach will be changed anytime without notification).
> > >
> > > We are keeping push to Apache Repo with a little bit delay, but please
> go
> > > with Apache Kylin Repo.
> > >
> > >
> > > Thanks.
> > >
> > > Luke
> > >
> > >
> > > Best Regards!
> > > ---------------------
> > >
> > > Luke Han
> > >
> > > 2015-03-17 20:56 GMT-07:00 dong wang <el...@gmail.com>:
> > >
> > >> as we know, we have 2 urls to get Kylin
> > >> 1, https://github.com/apache/incubator-kylin
> > >> 2, https://github.com/KylinOLAP/Kylin
> > >>
> > >> and as watched, it seems that staging of
> > >> https://github.com/KylinOLAP/Kylin
> > >> can always keep the latest changes, thus if one wants to keep up with
> > >> kylin's developing process, we should get codes from staging of
> > >> https://github.com/KylinOLAP/Kylin instead of staging of
> > >> https://github.com/apache/incubator-kylin, is it right?
> > >>
> >
>
Re: curious about the kylin github website
Posted by Luke Han <lu...@gmail.com>.
Ok, will work on it ASAP.
Thanks.
Best Regards!
---------------------
Luke Han
2015-03-19 11:46 GMT-07:00 Henry Saputra <he...@gmail.com>:
> Luke,
>
> Please do not use https://github.com/KylinOLAP/Kylin anymore and to
> move dev to the one under Apache mirror..
> Need to make it READ only ASAP before making a release under Apache.
>
> New contributors send PR against https://github.com/apache/incubator-kylin
> .
>
> There is no reason that contributors cannot contribute without commit
> or push access.
> Committers just one of the members of community that could commit code
> to repo. Reviews still need to happen even for committers to help
> maintain quality of code.
>
>
> - Henry
>
> On Tue, Mar 17, 2015 at 9:09 PM, Luke Han <lu...@gmail.com> wrote:
> > Please go with https://github.com/apache/incubator-kylin as primary
> source
> > of Apache Kylin code repo.
> >
> > The other one is our staging code repo to simplify development since many
> > of our team members do not have push privileges to Apache one yet (This
> > approach will be changed anytime without notification).
> >
> > We are keeping push to Apache Repo with a little bit delay, but please go
> > with Apache Kylin Repo.
> >
> >
> > Thanks.
> >
> > Luke
> >
> >
> > Best Regards!
> > ---------------------
> >
> > Luke Han
> >
> > 2015-03-17 20:56 GMT-07:00 dong wang <el...@gmail.com>:
> >
> >> as we know, we have 2 urls to get Kylin
> >> 1, https://github.com/apache/incubator-kylin
> >> 2, https://github.com/KylinOLAP/Kylin
> >>
> >> and as watched, it seems that staging of
> >> https://github.com/KylinOLAP/Kylin
> >> can always keep the latest changes, thus if one wants to keep up with
> >> kylin's developing process, we should get codes from staging of
> >> https://github.com/KylinOLAP/Kylin instead of staging of
> >> https://github.com/apache/incubator-kylin, is it right?
> >>
>
Re: curious about the kylin github website
Posted by Henry Saputra <he...@gmail.com>.
Luke,
Please do not use https://github.com/KylinOLAP/Kylin anymore and to
move dev to the one under Apache mirror..
Need to make it READ only ASAP before making a release under Apache.
New contributors send PR against https://github.com/apache/incubator-kylin.
There is no reason that contributors cannot contribute without commit
or push access.
Committers just one of the members of community that could commit code
to repo. Reviews still need to happen even for committers to help
maintain quality of code.
- Henry
On Tue, Mar 17, 2015 at 9:09 PM, Luke Han <lu...@gmail.com> wrote:
> Please go with https://github.com/apache/incubator-kylin as primary source
> of Apache Kylin code repo.
>
> The other one is our staging code repo to simplify development since many
> of our team members do not have push privileges to Apache one yet (This
> approach will be changed anytime without notification).
>
> We are keeping push to Apache Repo with a little bit delay, but please go
> with Apache Kylin Repo.
>
>
> Thanks.
>
> Luke
>
>
> Best Regards!
> ---------------------
>
> Luke Han
>
> 2015-03-17 20:56 GMT-07:00 dong wang <el...@gmail.com>:
>
>> as we know, we have 2 urls to get Kylin
>> 1, https://github.com/apache/incubator-kylin
>> 2, https://github.com/KylinOLAP/Kylin
>>
>> and as watched, it seems that staging of
>> https://github.com/KylinOLAP/Kylin
>> can always keep the latest changes, thus if one wants to keep up with
>> kylin's developing process, we should get codes from staging of
>> https://github.com/KylinOLAP/Kylin instead of staging of
>> https://github.com/apache/incubator-kylin, is it right?
>>
Re: curious about the kylin github website
Posted by Luke Han <lu...@gmail.com>.
Please go with https://github.com/apache/incubator-kylin as primary source
of Apache Kylin code repo.
The other one is our staging code repo to simplify development since many
of our team members do not have push privileges to Apache one yet (This
approach will be changed anytime without notification).
We are keeping push to Apache Repo with a little bit delay, but please go
with Apache Kylin Repo.
Thanks.
Luke
Best Regards!
---------------------
Luke Han
2015-03-17 20:56 GMT-07:00 dong wang <el...@gmail.com>:
> as we know, we have 2 urls to get Kylin
> 1, https://github.com/apache/incubator-kylin
> 2, https://github.com/KylinOLAP/Kylin
>
> and as watched, it seems that staging of
> https://github.com/KylinOLAP/Kylin
> can always keep the latest changes, thus if one wants to keep up with
> kylin's developing process, we should get codes from staging of
> https://github.com/KylinOLAP/Kylin instead of staging of
> https://github.com/apache/incubator-kylin, is it right?
>