You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Yingda Chen <yd...@gmail.com> on 2018/10/04 19:30:52 UTC
Design doc for new feature?
Hi all,
We are interested in contributing a few new features to Tez and some of
these new features should ideally be preceded with design doc and
discussions.
Is JIRA (possibly with external Google Doc link) sufficient for that?
Thanks all,
-Yingda
Re: Design doc for new feature?
Posted by Yingda Chen <yd...@gmail.com>.
It is working now.Thanks a lot Jon.
Have a great weekend,
Best,
Yingda
On Sat, Oct 6, 2018 at 6:53 AM Jonathan Eagles <je...@gmail.com> wrote:
> Ok. I have added Chyler to tez contributors as well. Please verify accounts
> can now assign Jiras to themselves.
>
> Regards,
> Jon Eagles
>
> On Fri, Oct 5, 2018, 5:21 PM Yingda Chen <yd...@gmail.com> wrote:
>
> > Sorry my bad, it should be Chyler.
> >
> > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Chyler
> >
> > Thanks,
> > -Yingda
> >
> > On Sat, Oct 6, 2018 at 6:17 AM Jonathan Eagles <je...@gmail.com>
> wrote:
> >
> > > Yingda, I added yingdachen as contributor but was unable to find user
> > name
> > > for Chryler. Can you verify the username for this account?
> > >
> > > Regards,
> > > jeagles
> > >
> > > On Fri, Oct 5, 2018 at 5:11 PM Yingda Chen <yd...@gmail.com> wrote:
> > >
> > > > Hi Jon,
> > > >
> > > > We have created the first batch of JIRAs that we plan to work on,
> under
> > > the
> > > > new proposed feature TEZ-3998.
> > > >
> > > > Just a gentle ping, could you please add our JIRA accounts
> (yingdachen
> > > and
> > > > Chryler) to contributor list so that we can assign things to
> ourselves?
> > > >
> > > > Thanks,
> > > > -Yingda
> > > >
> > > > On Fri, Oct 5, 2018 at 6:19 AM Yingda Chen <yd...@gmail.com> wrote:
> > > >
> > > > > Sounds good and Thanks Jon. We have signed up for the dev mailing
> > > list,
> > > > > and will be creating new JIRAs shortly. Lets go from there.
> > > > >
> > > > > In the mean time, could you please add the following two accounts
> to
> > > the
> > > > > contributors list first (we may have more folks join later as
> well)?
> > > > >
> > > > > yingdachen
> > > > > Chyler
> > > > >
> > > > > Thanks,
> > > > > -Yingda
> > > > >
> > > > > On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> Welcome and thank you for reaching out, Yingda.
> > > > >>
> > > > >> Here is a sample of the process. Feel free to create a new JIRA
> for
> > > each
> > > > >> feature. You can attach a design doc to the JIRA and request for
> > > > comments
> > > > >> on the dev list. After design discussions, usually the design
> takes
> > > one
> > > > of
> > > > >> two paths. For smaller projects, subtasks are added to the
> > > > JIRA(umbrella)
> > > > >> and are added in pieces. For larger projects, a feature branch is
> > > > created
> > > > >> and sub-jiras are committed directly to the feature branch and
> later
> > > > >> merged
> > > > >> back to the main line.
> > > > >>
> > > > >> As far as google doc link versus other formats, I feel this is ok
> as
> > > it
> > > > >> does not require certain software to read and contribute to the
> > design
> > > > >> discussion. However, versioning and history of changes are part
> of a
> > > > >> separate application as opposed to being stand alone in the JIRA.
> > I'm
> > > ok
> > > > >> with google doc as well as PDF.
> > > > >>
> > > > >> Please have a look at
> > > > >>
> > > >
> > https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> > > > >> for
> > > > >> some process.
> > > > >>
> > > > >> Get signed up for tez development and let me know what apache jira
> > > > account
> > > > >> (others welcome as well) to add to the contributors list, so that
> > you
> > > > are
> > > > >> able to assign jiras to yourself.
> > > > >>
> > > > >> Regards,
> > > > >> Jon Eagles
> > > > >> Tez PMC Chair
> > > > >>
> > > > >> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com>
> > wrote:
> > > > >>
> > > > >> > Hi all,
> > > > >> >
> > > > >> > We are interested in contributing a few new features to Tez and
> > some
> > > > of
> > > > >> > these new features should ideally be preceded with design doc
> and
> > > > >> > discussions.
> > > > >> >
> > > > >> > Is JIRA (possibly with external Google Doc link) sufficient for
> > > that?
> > > > >> >
> > > > >> > Thanks all,
> > > > >> > -Yingda
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: Design doc for new feature?
Posted by Jonathan Eagles <je...@gmail.com>.
Ok. I have added Chyler to tez contributors as well. Please verify accounts
can now assign Jiras to themselves.
Regards,
Jon Eagles
On Fri, Oct 5, 2018, 5:21 PM Yingda Chen <yd...@gmail.com> wrote:
> Sorry my bad, it should be Chyler.
>
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Chyler
>
> Thanks,
> -Yingda
>
> On Sat, Oct 6, 2018 at 6:17 AM Jonathan Eagles <je...@gmail.com> wrote:
>
> > Yingda, I added yingdachen as contributor but was unable to find user
> name
> > for Chryler. Can you verify the username for this account?
> >
> > Regards,
> > jeagles
> >
> > On Fri, Oct 5, 2018 at 5:11 PM Yingda Chen <yd...@gmail.com> wrote:
> >
> > > Hi Jon,
> > >
> > > We have created the first batch of JIRAs that we plan to work on, under
> > the
> > > new proposed feature TEZ-3998.
> > >
> > > Just a gentle ping, could you please add our JIRA accounts (yingdachen
> > and
> > > Chryler) to contributor list so that we can assign things to ourselves?
> > >
> > > Thanks,
> > > -Yingda
> > >
> > > On Fri, Oct 5, 2018 at 6:19 AM Yingda Chen <yd...@gmail.com> wrote:
> > >
> > > > Sounds good and Thanks Jon. We have signed up for the dev mailing
> > list,
> > > > and will be creating new JIRAs shortly. Lets go from there.
> > > >
> > > > In the mean time, could you please add the following two accounts to
> > the
> > > > contributors list first (we may have more folks join later as well)?
> > > >
> > > > yingdachen
> > > > Chyler
> > > >
> > > > Thanks,
> > > > -Yingda
> > > >
> > > > On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com>
> > > wrote:
> > > >
> > > >> Welcome and thank you for reaching out, Yingda.
> > > >>
> > > >> Here is a sample of the process. Feel free to create a new JIRA for
> > each
> > > >> feature. You can attach a design doc to the JIRA and request for
> > > comments
> > > >> on the dev list. After design discussions, usually the design takes
> > one
> > > of
> > > >> two paths. For smaller projects, subtasks are added to the
> > > JIRA(umbrella)
> > > >> and are added in pieces. For larger projects, a feature branch is
> > > created
> > > >> and sub-jiras are committed directly to the feature branch and later
> > > >> merged
> > > >> back to the main line.
> > > >>
> > > >> As far as google doc link versus other formats, I feel this is ok as
> > it
> > > >> does not require certain software to read and contribute to the
> design
> > > >> discussion. However, versioning and history of changes are part of a
> > > >> separate application as opposed to being stand alone in the JIRA.
> I'm
> > ok
> > > >> with google doc as well as PDF.
> > > >>
> > > >> Please have a look at
> > > >>
> > >
> https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> > > >> for
> > > >> some process.
> > > >>
> > > >> Get signed up for tez development and let me know what apache jira
> > > account
> > > >> (others welcome as well) to add to the contributors list, so that
> you
> > > are
> > > >> able to assign jiras to yourself.
> > > >>
> > > >> Regards,
> > > >> Jon Eagles
> > > >> Tez PMC Chair
> > > >>
> > > >> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com>
> wrote:
> > > >>
> > > >> > Hi all,
> > > >> >
> > > >> > We are interested in contributing a few new features to Tez and
> some
> > > of
> > > >> > these new features should ideally be preceded with design doc and
> > > >> > discussions.
> > > >> >
> > > >> > Is JIRA (possibly with external Google Doc link) sufficient for
> > that?
> > > >> >
> > > >> > Thanks all,
> > > >> > -Yingda
> > > >> >
> > > >>
> > > >
> > >
> >
>
Re: Design doc for new feature?
Posted by Yingda Chen <yd...@gmail.com>.
Sorry my bad, it should be Chyler.
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Chyler
Thanks,
-Yingda
On Sat, Oct 6, 2018 at 6:17 AM Jonathan Eagles <je...@gmail.com> wrote:
> Yingda, I added yingdachen as contributor but was unable to find user name
> for Chryler. Can you verify the username for this account?
>
> Regards,
> jeagles
>
> On Fri, Oct 5, 2018 at 5:11 PM Yingda Chen <yd...@gmail.com> wrote:
>
> > Hi Jon,
> >
> > We have created the first batch of JIRAs that we plan to work on, under
> the
> > new proposed feature TEZ-3998.
> >
> > Just a gentle ping, could you please add our JIRA accounts (yingdachen
> and
> > Chryler) to contributor list so that we can assign things to ourselves?
> >
> > Thanks,
> > -Yingda
> >
> > On Fri, Oct 5, 2018 at 6:19 AM Yingda Chen <yd...@gmail.com> wrote:
> >
> > > Sounds good and Thanks Jon. We have signed up for the dev mailing
> list,
> > > and will be creating new JIRAs shortly. Lets go from there.
> > >
> > > In the mean time, could you please add the following two accounts to
> the
> > > contributors list first (we may have more folks join later as well)?
> > >
> > > yingdachen
> > > Chyler
> > >
> > > Thanks,
> > > -Yingda
> > >
> > > On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com>
> > wrote:
> > >
> > >> Welcome and thank you for reaching out, Yingda.
> > >>
> > >> Here is a sample of the process. Feel free to create a new JIRA for
> each
> > >> feature. You can attach a design doc to the JIRA and request for
> > comments
> > >> on the dev list. After design discussions, usually the design takes
> one
> > of
> > >> two paths. For smaller projects, subtasks are added to the
> > JIRA(umbrella)
> > >> and are added in pieces. For larger projects, a feature branch is
> > created
> > >> and sub-jiras are committed directly to the feature branch and later
> > >> merged
> > >> back to the main line.
> > >>
> > >> As far as google doc link versus other formats, I feel this is ok as
> it
> > >> does not require certain software to read and contribute to the design
> > >> discussion. However, versioning and history of changes are part of a
> > >> separate application as opposed to being stand alone in the JIRA. I'm
> ok
> > >> with google doc as well as PDF.
> > >>
> > >> Please have a look at
> > >>
> > https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> > >> for
> > >> some process.
> > >>
> > >> Get signed up for tez development and let me know what apache jira
> > account
> > >> (others welcome as well) to add to the contributors list, so that you
> > are
> > >> able to assign jiras to yourself.
> > >>
> > >> Regards,
> > >> Jon Eagles
> > >> Tez PMC Chair
> > >>
> > >> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > We are interested in contributing a few new features to Tez and some
> > of
> > >> > these new features should ideally be preceded with design doc and
> > >> > discussions.
> > >> >
> > >> > Is JIRA (possibly with external Google Doc link) sufficient for
> that?
> > >> >
> > >> > Thanks all,
> > >> > -Yingda
> > >> >
> > >>
> > >
> >
>
Re: Design doc for new feature?
Posted by Jonathan Eagles <je...@gmail.com>.
Yingda, I added yingdachen as contributor but was unable to find user name
for Chryler. Can you verify the username for this account?
Regards,
jeagles
On Fri, Oct 5, 2018 at 5:11 PM Yingda Chen <yd...@gmail.com> wrote:
> Hi Jon,
>
> We have created the first batch of JIRAs that we plan to work on, under the
> new proposed feature TEZ-3998.
>
> Just a gentle ping, could you please add our JIRA accounts (yingdachen and
> Chryler) to contributor list so that we can assign things to ourselves?
>
> Thanks,
> -Yingda
>
> On Fri, Oct 5, 2018 at 6:19 AM Yingda Chen <yd...@gmail.com> wrote:
>
> > Sounds good and Thanks Jon. We have signed up for the dev mailing list,
> > and will be creating new JIRAs shortly. Lets go from there.
> >
> > In the mean time, could you please add the following two accounts to the
> > contributors list first (we may have more folks join later as well)?
> >
> > yingdachen
> > Chyler
> >
> > Thanks,
> > -Yingda
> >
> > On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com>
> wrote:
> >
> >> Welcome and thank you for reaching out, Yingda.
> >>
> >> Here is a sample of the process. Feel free to create a new JIRA for each
> >> feature. You can attach a design doc to the JIRA and request for
> comments
> >> on the dev list. After design discussions, usually the design takes one
> of
> >> two paths. For smaller projects, subtasks are added to the
> JIRA(umbrella)
> >> and are added in pieces. For larger projects, a feature branch is
> created
> >> and sub-jiras are committed directly to the feature branch and later
> >> merged
> >> back to the main line.
> >>
> >> As far as google doc link versus other formats, I feel this is ok as it
> >> does not require certain software to read and contribute to the design
> >> discussion. However, versioning and history of changes are part of a
> >> separate application as opposed to being stand alone in the JIRA. I'm ok
> >> with google doc as well as PDF.
> >>
> >> Please have a look at
> >>
> https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> >> for
> >> some process.
> >>
> >> Get signed up for tez development and let me know what apache jira
> account
> >> (others welcome as well) to add to the contributors list, so that you
> are
> >> able to assign jiras to yourself.
> >>
> >> Regards,
> >> Jon Eagles
> >> Tez PMC Chair
> >>
> >> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com> wrote:
> >>
> >> > Hi all,
> >> >
> >> > We are interested in contributing a few new features to Tez and some
> of
> >> > these new features should ideally be preceded with design doc and
> >> > discussions.
> >> >
> >> > Is JIRA (possibly with external Google Doc link) sufficient for that?
> >> >
> >> > Thanks all,
> >> > -Yingda
> >> >
> >>
> >
>
Re: Design doc for new feature?
Posted by Yingda Chen <yd...@gmail.com>.
Hi Jon,
We have created the first batch of JIRAs that we plan to work on, under the
new proposed feature TEZ-3998.
Just a gentle ping, could you please add our JIRA accounts (yingdachen and
Chryler) to contributor list so that we can assign things to ourselves?
Thanks,
-Yingda
On Fri, Oct 5, 2018 at 6:19 AM Yingda Chen <yd...@gmail.com> wrote:
> Sounds good and Thanks Jon. We have signed up for the dev mailing list,
> and will be creating new JIRAs shortly. Lets go from there.
>
> In the mean time, could you please add the following two accounts to the
> contributors list first (we may have more folks join later as well)?
>
> yingdachen
> Chyler
>
> Thanks,
> -Yingda
>
> On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com> wrote:
>
>> Welcome and thank you for reaching out, Yingda.
>>
>> Here is a sample of the process. Feel free to create a new JIRA for each
>> feature. You can attach a design doc to the JIRA and request for comments
>> on the dev list. After design discussions, usually the design takes one of
>> two paths. For smaller projects, subtasks are added to the JIRA(umbrella)
>> and are added in pieces. For larger projects, a feature branch is created
>> and sub-jiras are committed directly to the feature branch and later
>> merged
>> back to the main line.
>>
>> As far as google doc link versus other formats, I feel this is ok as it
>> does not require certain software to read and contribute to the design
>> discussion. However, versioning and history of changes are part of a
>> separate application as opposed to being stand alone in the JIRA. I'm ok
>> with google doc as well as PDF.
>>
>> Please have a look at
>> https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
>> for
>> some process.
>>
>> Get signed up for tez development and let me know what apache jira account
>> (others welcome as well) to add to the contributors list, so that you are
>> able to assign jiras to yourself.
>>
>> Regards,
>> Jon Eagles
>> Tez PMC Chair
>>
>> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com> wrote:
>>
>> > Hi all,
>> >
>> > We are interested in contributing a few new features to Tez and some of
>> > these new features should ideally be preceded with design doc and
>> > discussions.
>> >
>> > Is JIRA (possibly with external Google Doc link) sufficient for that?
>> >
>> > Thanks all,
>> > -Yingda
>> >
>>
>
Re: Design doc for new feature?
Posted by Yingda Chen <yd...@gmail.com>.
Sounds good and Thanks Jon. We have signed up for the dev mailing list,
and will be creating new JIRAs shortly. Lets go from there.
In the mean time, could you please add the following two accounts to the
contributors list first (we may have more folks join later as well)?
yingdachen
Chyler
Thanks,
-Yingda
On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <je...@gmail.com> wrote:
> Welcome and thank you for reaching out, Yingda.
>
> Here is a sample of the process. Feel free to create a new JIRA for each
> feature. You can attach a design doc to the JIRA and request for comments
> on the dev list. After design discussions, usually the design takes one of
> two paths. For smaller projects, subtasks are added to the JIRA(umbrella)
> and are added in pieces. For larger projects, a feature branch is created
> and sub-jiras are committed directly to the feature branch and later merged
> back to the main line.
>
> As far as google doc link versus other formats, I feel this is ok as it
> does not require certain software to read and contribute to the design
> discussion. However, versioning and history of changes are part of a
> separate application as opposed to being stand alone in the JIRA. I'm ok
> with google doc as well as PDF.
>
> Please have a look at
> https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> for
> some process.
>
> Get signed up for tez development and let me know what apache jira account
> (others welcome as well) to add to the contributors list, so that you are
> able to assign jiras to yourself.
>
> Regards,
> Jon Eagles
> Tez PMC Chair
>
> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com> wrote:
>
> > Hi all,
> >
> > We are interested in contributing a few new features to Tez and some of
> > these new features should ideally be preceded with design doc and
> > discussions.
> >
> > Is JIRA (possibly with external Google Doc link) sufficient for that?
> >
> > Thanks all,
> > -Yingda
> >
>
Re: Design doc for new feature?
Posted by Jonathan Eagles <je...@gmail.com>.
Welcome and thank you for reaching out, Yingda.
Here is a sample of the process. Feel free to create a new JIRA for each
feature. You can attach a design doc to the JIRA and request for comments
on the dev list. After design discussions, usually the design takes one of
two paths. For smaller projects, subtasks are added to the JIRA(umbrella)
and are added in pieces. For larger projects, a feature branch is created
and sub-jiras are committed directly to the feature branch and later merged
back to the main line.
As far as google doc link versus other formats, I feel this is ok as it
does not require certain software to read and contribute to the design
discussion. However, versioning and history of changes are part of a
separate application as opposed to being stand alone in the JIRA. I'm ok
with google doc as well as PDF.
Please have a look at
https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez for
some process.
Get signed up for tez development and let me know what apache jira account
(others welcome as well) to add to the contributors list, so that you are
able to assign jiras to yourself.
Regards,
Jon Eagles
Tez PMC Chair
On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <yd...@gmail.com> wrote:
> Hi all,
>
> We are interested in contributing a few new features to Tez and some of
> these new features should ideally be preceded with design doc and
> discussions.
>
> Is JIRA (possibly with external Google Doc link) sufficient for that?
>
> Thanks all,
> -Yingda
>