You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hudi.apache.org by Vinoth Chandar <vi...@apache.org> on 2021/07/02 03:40:51 UTC
[DISCUSS] Consolidate all dev collaboration to Github
Hi all,
When we incubated Hudi, we made some initial choices around collaboration
tools of choice. I am wondering if there are still optimal, given the scale
of the community at this point.
Specifically, two points.
A) Our issue tracker is JIRA, while we just use Github Issues for support
triage. While JIRA is pretty advanced and gives us the ability to track
releases, versions and kanban boards, there are few practical operational
problems.
- Developers often open bug fixes/PR which all need to be continuously
tagged against a release version (fix version)
- Referencing JIRAs from Pull Requests is great (we cannot do things like
`fixes #1234` to close issues when PR lands, not an easy way to click and
get to the JIRA)
- Many more developers have a github account, to contribute to Hudi though,
they need an additional sign-up on jira.
So wondering if we should just use one thing - Github Issues, and build
scripts/hubot or something to get the missing project management from
boards.
B) Our design docs are on cWiki. Even though we link it off the site, from
my experience, many do not discover them.
For large PRs, we need to manually enforce that design and code are in sync
before we land. If we can, I would love to make RFC being in good shape a
pre-requisite for landing the PR.
Once again, separate signup is needed to write design docs or comment on
them.
So, wondering if we can move our process docs etc into Github Wiki and RFCs
to the master branch in a rfc folder, and we just use github PRs to raise
RFCs and discuss them.
This all also makes it easy for us to measure community activity and keep
streamlining our processes.
personally, these different channels are overwhelming to me at-least :)
Love to hear thoughts. Please specify if you are for,against each of A and
B.
Thanks
Vinoth
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
Thanks all. Started a VOTE around this.
If you can chime in with your +1s there as well, it will be great!
On Fri, Jul 16, 2021 at 8:31 PM Gary Li <ga...@apache.org> wrote:
> +1 for option B.
>
> On Sat, Jul 17, 2021 at 9:51 AM Udit Mehrotra <ud...@apache.org> wrote:
>
> > +1 for option B. For A, I will need more data points to convince myself
> if
> > GitHub issues will provide all the issue tracking functionality that Jira
> > provides today.
> >
> > Thanks,
> > Udit
> >
> > On Fri, Jul 16, 2021 at 2:33 PM Vinoth Chandar <vi...@apache.org>
> wrote:
> >
> > > Looks like we can start with B has a lot of support.
> > > I will start a VOTE on B alone and we can proceed if the VOTE passes.
> > >
> > > On Fri, Jul 16, 2021 at 8:05 AM Nishith <n3...@gmail.com> wrote:
> > >
> > > > +1 for option B.
> > > >
> > > > > On Jul 15, 2021, at 10:50 PM, Bhavani Sudha <
> bhavanisudhas@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > > Completely agree on B. On A I feel the necessity to centralize
> > > > everything
> > > > > in one place but also without losing the capabilities of Jira. I
> > think
> > > we
> > > > > will have to explore tools in eitherways.
> > > > >
> > > > > Thanks,
> > > > > Sudha
> > > > >
> > > > >> On Thu, Jul 15, 2021 at 10:42 PM vino yang <yanghua1127@gmail.com
> >
> > > > wrote:
> > > > >>
> > > > >> +1 for option B.
> > > > >>
> > > > >> Best,
> > > > >> Vino
> > > > >>
> > > > >> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
> > > > >>
> > > > >>> +1 on B. Not sure on A though. I understand the intent to have
> all
> > in
> > > > >>> one place. but not very sure if we can get all functionality
> > > (version,
> > > > >>> type, component, status, parent- child relation), etc ported over
> > to
> > > > >>> github. I assume labels are the only option we have to achieve
> > these.
> > > > >>> Probably, we should also document the labels in detail so that
> > anyone
> > > > >>> looking to take a look at untriaged issues should know how/where
> to
> > > > look
> > > > >>> at. If we plan to use GH issues for all, I am sure there will be
> a
> > > lot
> > > > of
> > > > >>> proliferation of issues.
> > > > >>>
> > > > >>> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <
> vinoth@apache.org>
> > > > >> wrote:
> > > > >>>
> > > > >>>> Based on this, I will start consolidating more of the cWiki
> > content
> > > to
> > > > >>>> github wiki and master branch?
> > > > >>>>
> > > > >>>> JIRA vs GH Issue still probably needs more feedback. I do see
> the
> > > > >>> tradeoffs
> > > > >>>> there.
> > > > >>>>
> > > > >>>> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com>
> > > wrote:
> > > > >>>>
> > > > >>>>> +1
> > > > >>>>>
> > > > >>>>> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org>
> > wrote:
> > > > >>>>>> Hi all,
> > > > >>>>>>
> > > > >>>>>> When we incubated Hudi, we made some initial choices around
> > > > >>>> collaboration
> > > > >>>>>> tools of choice. I am wondering if there are still optimal,
> > given
> > > > >> the
> > > > >>>>> scale
> > > > >>>>>> of the community at this point.
> > > > >>>>>>
> > > > >>>>>> Specifically, two points.
> > > > >>>>>>
> > > > >>>>>> A) Our issue tracker is JIRA, while we just use Github Issues
> > for
> > > > >>>> support
> > > > >>>>>> triage. While JIRA is pretty advanced and gives us the ability
> > to
> > > > >>> track
> > > > >>>>>> releases, versions and kanban boards, there are few practical
> > > > >>>> operational
> > > > >>>>>> problems.
> > > > >>>>>>
> > > > >>>>>> - Developers often open bug fixes/PR which all need to be
> > > > >>> continuously
> > > > >>>>>> tagged against a release version (fix version)
> > > > >>>>>> - Referencing JIRAs from Pull Requests is great (we cannot do
> > > > >> things
> > > > >>>> like
> > > > >>>>>> `fixes #1234` to close issues when PR lands, not an easy way
> to
> > > > >> click
> > > > >>>> and
> > > > >>>>>> get to the JIRA)
> > > > >>>>>> - Many more developers have a github account, to contribute to
> > > Hudi
> > > > >>>>> though,
> > > > >>>>>> they need an additional sign-up on jira.
> > > > >>>>>>
> > > > >>>>>> So wondering if we should just use one thing - Github Issues,
> > and
> > > > >>> build
> > > > >>>>>> scripts/hubot or something to get the missing project
> management
> > > > >> from
> > > > >>>>>> boards.
> > > > >>>>>>
> > > > >>>>>> B) Our design docs are on cWiki. Even though we link it off
> the
> > > > >> site,
> > > > >>>>> from
> > > > >>>>>> my experience, many do not discover them.
> > > > >>>>>> For large PRs, we need to manually enforce that design and
> code
> > > are
> > > > >>> in
> > > > >>>>> sync
> > > > >>>>>> before we land. If we can, I would love to make RFC being in
> > good
> > > > >>>> shape a
> > > > >>>>>> pre-requisite for landing the PR.
> > > > >>>>>> Once again, separate signup is needed to write design docs or
> > > > >> comment
> > > > >>>> on
> > > > >>>>>> them.
> > > > >>>>>>
> > > > >>>>>> So, wondering if we can move our process docs etc into Github
> > Wiki
> > > > >>> and
> > > > >>>>> RFCs
> > > > >>>>>> to the master branch in a rfc folder, and we just use github
> PRs
> > > to
> > > > >>>> raise
> > > > >>>>>> RFCs and discuss them.
> > > > >>>>>>
> > > > >>>>>> This all also makes it easy for us to measure community
> activity
> > > > >> and
> > > > >>>> keep
> > > > >>>>>> streamlining our processes.
> > > > >>>>>>
> > > > >>>>>> personally, these different channels are overwhelming to me
> > > > >> at-least
> > > > >>> :)
> > > > >>>>>>
> > > > >>>>>> Love to hear thoughts. Please specify if you are for,against
> > each
> > > > >> of
> > > > >>> A
> > > > >>>>> and
> > > > >>>>>> B.
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> Thanks
> > > > >>>>>> Vinoth
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> Regards,
> > > > >>> -Sivabalan
> > > > >>>
> > > > >>
> > > >
> > >
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Gary Li <ga...@apache.org>.
+1 for option B.
On Sat, Jul 17, 2021 at 9:51 AM Udit Mehrotra <ud...@apache.org> wrote:
> +1 for option B. For A, I will need more data points to convince myself if
> GitHub issues will provide all the issue tracking functionality that Jira
> provides today.
>
> Thanks,
> Udit
>
> On Fri, Jul 16, 2021 at 2:33 PM Vinoth Chandar <vi...@apache.org> wrote:
>
> > Looks like we can start with B has a lot of support.
> > I will start a VOTE on B alone and we can proceed if the VOTE passes.
> >
> > On Fri, Jul 16, 2021 at 8:05 AM Nishith <n3...@gmail.com> wrote:
> >
> > > +1 for option B.
> > >
> > > > On Jul 15, 2021, at 10:50 PM, Bhavani Sudha <bhavanisudhas@gmail.com
> >
> > > wrote:
> > > >
> > > > Completely agree on B. On A I feel the necessity to centralize
> > > everything
> > > > in one place but also without losing the capabilities of Jira. I
> think
> > we
> > > > will have to explore tools in eitherways.
> > > >
> > > > Thanks,
> > > > Sudha
> > > >
> > > >> On Thu, Jul 15, 2021 at 10:42 PM vino yang <ya...@gmail.com>
> > > wrote:
> > > >>
> > > >> +1 for option B.
> > > >>
> > > >> Best,
> > > >> Vino
> > > >>
> > > >> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
> > > >>
> > > >>> +1 on B. Not sure on A though. I understand the intent to have all
> in
> > > >>> one place. but not very sure if we can get all functionality
> > (version,
> > > >>> type, component, status, parent- child relation), etc ported over
> to
> > > >>> github. I assume labels are the only option we have to achieve
> these.
> > > >>> Probably, we should also document the labels in detail so that
> anyone
> > > >>> looking to take a look at untriaged issues should know how/where to
> > > look
> > > >>> at. If we plan to use GH issues for all, I am sure there will be a
> > lot
> > > of
> > > >>> proliferation of issues.
> > > >>>
> > > >>> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org>
> > > >> wrote:
> > > >>>
> > > >>>> Based on this, I will start consolidating more of the cWiki
> content
> > to
> > > >>>> github wiki and master branch?
> > > >>>>
> > > >>>> JIRA vs GH Issue still probably needs more feedback. I do see the
> > > >>> tradeoffs
> > > >>>> there.
> > > >>>>
> > > >>>> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com>
> > wrote:
> > > >>>>
> > > >>>>> +1
> > > >>>>>
> > > >>>>> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org>
> wrote:
> > > >>>>>> Hi all,
> > > >>>>>>
> > > >>>>>> When we incubated Hudi, we made some initial choices around
> > > >>>> collaboration
> > > >>>>>> tools of choice. I am wondering if there are still optimal,
> given
> > > >> the
> > > >>>>> scale
> > > >>>>>> of the community at this point.
> > > >>>>>>
> > > >>>>>> Specifically, two points.
> > > >>>>>>
> > > >>>>>> A) Our issue tracker is JIRA, while we just use Github Issues
> for
> > > >>>> support
> > > >>>>>> triage. While JIRA is pretty advanced and gives us the ability
> to
> > > >>> track
> > > >>>>>> releases, versions and kanban boards, there are few practical
> > > >>>> operational
> > > >>>>>> problems.
> > > >>>>>>
> > > >>>>>> - Developers often open bug fixes/PR which all need to be
> > > >>> continuously
> > > >>>>>> tagged against a release version (fix version)
> > > >>>>>> - Referencing JIRAs from Pull Requests is great (we cannot do
> > > >> things
> > > >>>> like
> > > >>>>>> `fixes #1234` to close issues when PR lands, not an easy way to
> > > >> click
> > > >>>> and
> > > >>>>>> get to the JIRA)
> > > >>>>>> - Many more developers have a github account, to contribute to
> > Hudi
> > > >>>>> though,
> > > >>>>>> they need an additional sign-up on jira.
> > > >>>>>>
> > > >>>>>> So wondering if we should just use one thing - Github Issues,
> and
> > > >>> build
> > > >>>>>> scripts/hubot or something to get the missing project management
> > > >> from
> > > >>>>>> boards.
> > > >>>>>>
> > > >>>>>> B) Our design docs are on cWiki. Even though we link it off the
> > > >> site,
> > > >>>>> from
> > > >>>>>> my experience, many do not discover them.
> > > >>>>>> For large PRs, we need to manually enforce that design and code
> > are
> > > >>> in
> > > >>>>> sync
> > > >>>>>> before we land. If we can, I would love to make RFC being in
> good
> > > >>>> shape a
> > > >>>>>> pre-requisite for landing the PR.
> > > >>>>>> Once again, separate signup is needed to write design docs or
> > > >> comment
> > > >>>> on
> > > >>>>>> them.
> > > >>>>>>
> > > >>>>>> So, wondering if we can move our process docs etc into Github
> Wiki
> > > >>> and
> > > >>>>> RFCs
> > > >>>>>> to the master branch in a rfc folder, and we just use github PRs
> > to
> > > >>>> raise
> > > >>>>>> RFCs and discuss them.
> > > >>>>>>
> > > >>>>>> This all also makes it easy for us to measure community activity
> > > >> and
> > > >>>> keep
> > > >>>>>> streamlining our processes.
> > > >>>>>>
> > > >>>>>> personally, these different channels are overwhelming to me
> > > >> at-least
> > > >>> :)
> > > >>>>>>
> > > >>>>>> Love to hear thoughts. Please specify if you are for,against
> each
> > > >> of
> > > >>> A
> > > >>>>> and
> > > >>>>>> B.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> Thanks
> > > >>>>>> Vinoth
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Regards,
> > > >>> -Sivabalan
> > > >>>
> > > >>
> > >
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Udit Mehrotra <ud...@apache.org>.
+1 for option B. For A, I will need more data points to convince myself if
GitHub issues will provide all the issue tracking functionality that Jira
provides today.
Thanks,
Udit
On Fri, Jul 16, 2021 at 2:33 PM Vinoth Chandar <vi...@apache.org> wrote:
> Looks like we can start with B has a lot of support.
> I will start a VOTE on B alone and we can proceed if the VOTE passes.
>
> On Fri, Jul 16, 2021 at 8:05 AM Nishith <n3...@gmail.com> wrote:
>
> > +1 for option B.
> >
> > > On Jul 15, 2021, at 10:50 PM, Bhavani Sudha <bh...@gmail.com>
> > wrote:
> > >
> > > Completely agree on B. On A I feel the necessity to centralize
> > everything
> > > in one place but also without losing the capabilities of Jira. I think
> we
> > > will have to explore tools in eitherways.
> > >
> > > Thanks,
> > > Sudha
> > >
> > >> On Thu, Jul 15, 2021 at 10:42 PM vino yang <ya...@gmail.com>
> > wrote:
> > >>
> > >> +1 for option B.
> > >>
> > >> Best,
> > >> Vino
> > >>
> > >> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
> > >>
> > >>> +1 on B. Not sure on A though. I understand the intent to have all in
> > >>> one place. but not very sure if we can get all functionality
> (version,
> > >>> type, component, status, parent- child relation), etc ported over to
> > >>> github. I assume labels are the only option we have to achieve these.
> > >>> Probably, we should also document the labels in detail so that anyone
> > >>> looking to take a look at untriaged issues should know how/where to
> > look
> > >>> at. If we plan to use GH issues for all, I am sure there will be a
> lot
> > of
> > >>> proliferation of issues.
> > >>>
> > >>> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org>
> > >> wrote:
> > >>>
> > >>>> Based on this, I will start consolidating more of the cWiki content
> to
> > >>>> github wiki and master branch?
> > >>>>
> > >>>> JIRA vs GH Issue still probably needs more feedback. I do see the
> > >>> tradeoffs
> > >>>> there.
> > >>>>
> > >>>> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com>
> wrote:
> > >>>>
> > >>>>> +1
> > >>>>>
> > >>>>> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> > >>>>>> Hi all,
> > >>>>>>
> > >>>>>> When we incubated Hudi, we made some initial choices around
> > >>>> collaboration
> > >>>>>> tools of choice. I am wondering if there are still optimal, given
> > >> the
> > >>>>> scale
> > >>>>>> of the community at this point.
> > >>>>>>
> > >>>>>> Specifically, two points.
> > >>>>>>
> > >>>>>> A) Our issue tracker is JIRA, while we just use Github Issues for
> > >>>> support
> > >>>>>> triage. While JIRA is pretty advanced and gives us the ability to
> > >>> track
> > >>>>>> releases, versions and kanban boards, there are few practical
> > >>>> operational
> > >>>>>> problems.
> > >>>>>>
> > >>>>>> - Developers often open bug fixes/PR which all need to be
> > >>> continuously
> > >>>>>> tagged against a release version (fix version)
> > >>>>>> - Referencing JIRAs from Pull Requests is great (we cannot do
> > >> things
> > >>>> like
> > >>>>>> `fixes #1234` to close issues when PR lands, not an easy way to
> > >> click
> > >>>> and
> > >>>>>> get to the JIRA)
> > >>>>>> - Many more developers have a github account, to contribute to
> Hudi
> > >>>>> though,
> > >>>>>> they need an additional sign-up on jira.
> > >>>>>>
> > >>>>>> So wondering if we should just use one thing - Github Issues, and
> > >>> build
> > >>>>>> scripts/hubot or something to get the missing project management
> > >> from
> > >>>>>> boards.
> > >>>>>>
> > >>>>>> B) Our design docs are on cWiki. Even though we link it off the
> > >> site,
> > >>>>> from
> > >>>>>> my experience, many do not discover them.
> > >>>>>> For large PRs, we need to manually enforce that design and code
> are
> > >>> in
> > >>>>> sync
> > >>>>>> before we land. If we can, I would love to make RFC being in good
> > >>>> shape a
> > >>>>>> pre-requisite for landing the PR.
> > >>>>>> Once again, separate signup is needed to write design docs or
> > >> comment
> > >>>> on
> > >>>>>> them.
> > >>>>>>
> > >>>>>> So, wondering if we can move our process docs etc into Github Wiki
> > >>> and
> > >>>>> RFCs
> > >>>>>> to the master branch in a rfc folder, and we just use github PRs
> to
> > >>>> raise
> > >>>>>> RFCs and discuss them.
> > >>>>>>
> > >>>>>> This all also makes it easy for us to measure community activity
> > >> and
> > >>>> keep
> > >>>>>> streamlining our processes.
> > >>>>>>
> > >>>>>> personally, these different channels are overwhelming to me
> > >> at-least
> > >>> :)
> > >>>>>>
> > >>>>>> Love to hear thoughts. Please specify if you are for,against each
> > >> of
> > >>> A
> > >>>>> and
> > >>>>>> B.
> > >>>>>>
> > >>>>>>
> > >>>>>> Thanks
> > >>>>>> Vinoth
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Regards,
> > >>> -Sivabalan
> > >>>
> > >>
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
Looks like we can start with B has a lot of support.
I will start a VOTE on B alone and we can proceed if the VOTE passes.
On Fri, Jul 16, 2021 at 8:05 AM Nishith <n3...@gmail.com> wrote:
> +1 for option B.
>
> > On Jul 15, 2021, at 10:50 PM, Bhavani Sudha <bh...@gmail.com>
> wrote:
> >
> > Completely agree on B. On A I feel the necessity to centralize
> everything
> > in one place but also without losing the capabilities of Jira. I think we
> > will have to explore tools in eitherways.
> >
> > Thanks,
> > Sudha
> >
> >> On Thu, Jul 15, 2021 at 10:42 PM vino yang <ya...@gmail.com>
> wrote:
> >>
> >> +1 for option B.
> >>
> >> Best,
> >> Vino
> >>
> >> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
> >>
> >>> +1 on B. Not sure on A though. I understand the intent to have all in
> >>> one place. but not very sure if we can get all functionality (version,
> >>> type, component, status, parent- child relation), etc ported over to
> >>> github. I assume labels are the only option we have to achieve these.
> >>> Probably, we should also document the labels in detail so that anyone
> >>> looking to take a look at untriaged issues should know how/where to
> look
> >>> at. If we plan to use GH issues for all, I am sure there will be a lot
> of
> >>> proliferation of issues.
> >>>
> >>> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org>
> >> wrote:
> >>>
> >>>> Based on this, I will start consolidating more of the cWiki content to
> >>>> github wiki and master branch?
> >>>>
> >>>> JIRA vs GH Issue still probably needs more feedback. I do see the
> >>> tradeoffs
> >>>> there.
> >>>>
> >>>> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
> >>>>
> >>>>> +1
> >>>>>
> >>>>> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> >>>>>> Hi all,
> >>>>>>
> >>>>>> When we incubated Hudi, we made some initial choices around
> >>>> collaboration
> >>>>>> tools of choice. I am wondering if there are still optimal, given
> >> the
> >>>>> scale
> >>>>>> of the community at this point.
> >>>>>>
> >>>>>> Specifically, two points.
> >>>>>>
> >>>>>> A) Our issue tracker is JIRA, while we just use Github Issues for
> >>>> support
> >>>>>> triage. While JIRA is pretty advanced and gives us the ability to
> >>> track
> >>>>>> releases, versions and kanban boards, there are few practical
> >>>> operational
> >>>>>> problems.
> >>>>>>
> >>>>>> - Developers often open bug fixes/PR which all need to be
> >>> continuously
> >>>>>> tagged against a release version (fix version)
> >>>>>> - Referencing JIRAs from Pull Requests is great (we cannot do
> >> things
> >>>> like
> >>>>>> `fixes #1234` to close issues when PR lands, not an easy way to
> >> click
> >>>> and
> >>>>>> get to the JIRA)
> >>>>>> - Many more developers have a github account, to contribute to Hudi
> >>>>> though,
> >>>>>> they need an additional sign-up on jira.
> >>>>>>
> >>>>>> So wondering if we should just use one thing - Github Issues, and
> >>> build
> >>>>>> scripts/hubot or something to get the missing project management
> >> from
> >>>>>> boards.
> >>>>>>
> >>>>>> B) Our design docs are on cWiki. Even though we link it off the
> >> site,
> >>>>> from
> >>>>>> my experience, many do not discover them.
> >>>>>> For large PRs, we need to manually enforce that design and code are
> >>> in
> >>>>> sync
> >>>>>> before we land. If we can, I would love to make RFC being in good
> >>>> shape a
> >>>>>> pre-requisite for landing the PR.
> >>>>>> Once again, separate signup is needed to write design docs or
> >> comment
> >>>> on
> >>>>>> them.
> >>>>>>
> >>>>>> So, wondering if we can move our process docs etc into Github Wiki
> >>> and
> >>>>> RFCs
> >>>>>> to the master branch in a rfc folder, and we just use github PRs to
> >>>> raise
> >>>>>> RFCs and discuss them.
> >>>>>>
> >>>>>> This all also makes it easy for us to measure community activity
> >> and
> >>>> keep
> >>>>>> streamlining our processes.
> >>>>>>
> >>>>>> personally, these different channels are overwhelming to me
> >> at-least
> >>> :)
> >>>>>>
> >>>>>> Love to hear thoughts. Please specify if you are for,against each
> >> of
> >>> A
> >>>>> and
> >>>>>> B.
> >>>>>>
> >>>>>>
> >>>>>> Thanks
> >>>>>> Vinoth
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Regards,
> >>> -Sivabalan
> >>>
> >>
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Nishith <n3...@gmail.com>.
+1 for option B.
> On Jul 15, 2021, at 10:50 PM, Bhavani Sudha <bh...@gmail.com> wrote:
>
> Completely agree on B. On A I feel the necessity to centralize everything
> in one place but also without losing the capabilities of Jira. I think we
> will have to explore tools in eitherways.
>
> Thanks,
> Sudha
>
>> On Thu, Jul 15, 2021 at 10:42 PM vino yang <ya...@gmail.com> wrote:
>>
>> +1 for option B.
>>
>> Best,
>> Vino
>>
>> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
>>
>>> +1 on B. Not sure on A though. I understand the intent to have all in
>>> one place. but not very sure if we can get all functionality (version,
>>> type, component, status, parent- child relation), etc ported over to
>>> github. I assume labels are the only option we have to achieve these.
>>> Probably, we should also document the labels in detail so that anyone
>>> looking to take a look at untriaged issues should know how/where to look
>>> at. If we plan to use GH issues for all, I am sure there will be a lot of
>>> proliferation of issues.
>>>
>>> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org>
>> wrote:
>>>
>>>> Based on this, I will start consolidating more of the cWiki content to
>>>> github wiki and master branch?
>>>>
>>>> JIRA vs GH Issue still probably needs more feedback. I do see the
>>> tradeoffs
>>>> there.
>>>>
>>>> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> When we incubated Hudi, we made some initial choices around
>>>> collaboration
>>>>>> tools of choice. I am wondering if there are still optimal, given
>> the
>>>>> scale
>>>>>> of the community at this point.
>>>>>>
>>>>>> Specifically, two points.
>>>>>>
>>>>>> A) Our issue tracker is JIRA, while we just use Github Issues for
>>>> support
>>>>>> triage. While JIRA is pretty advanced and gives us the ability to
>>> track
>>>>>> releases, versions and kanban boards, there are few practical
>>>> operational
>>>>>> problems.
>>>>>>
>>>>>> - Developers often open bug fixes/PR which all need to be
>>> continuously
>>>>>> tagged against a release version (fix version)
>>>>>> - Referencing JIRAs from Pull Requests is great (we cannot do
>> things
>>>> like
>>>>>> `fixes #1234` to close issues when PR lands, not an easy way to
>> click
>>>> and
>>>>>> get to the JIRA)
>>>>>> - Many more developers have a github account, to contribute to Hudi
>>>>> though,
>>>>>> they need an additional sign-up on jira.
>>>>>>
>>>>>> So wondering if we should just use one thing - Github Issues, and
>>> build
>>>>>> scripts/hubot or something to get the missing project management
>> from
>>>>>> boards.
>>>>>>
>>>>>> B) Our design docs are on cWiki. Even though we link it off the
>> site,
>>>>> from
>>>>>> my experience, many do not discover them.
>>>>>> For large PRs, we need to manually enforce that design and code are
>>> in
>>>>> sync
>>>>>> before we land. If we can, I would love to make RFC being in good
>>>> shape a
>>>>>> pre-requisite for landing the PR.
>>>>>> Once again, separate signup is needed to write design docs or
>> comment
>>>> on
>>>>>> them.
>>>>>>
>>>>>> So, wondering if we can move our process docs etc into Github Wiki
>>> and
>>>>> RFCs
>>>>>> to the master branch in a rfc folder, and we just use github PRs to
>>>> raise
>>>>>> RFCs and discuss them.
>>>>>>
>>>>>> This all also makes it easy for us to measure community activity
>> and
>>>> keep
>>>>>> streamlining our processes.
>>>>>>
>>>>>> personally, these different channels are overwhelming to me
>> at-least
>>> :)
>>>>>>
>>>>>> Love to hear thoughts. Please specify if you are for,against each
>> of
>>> A
>>>>> and
>>>>>> B.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Vinoth
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> -Sivabalan
>>>
>>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Bhavani Sudha <bh...@gmail.com>.
Completely agree on B. On A I feel the necessity to centralize everything
in one place but also without losing the capabilities of Jira. I think we
will have to explore tools in eitherways.
Thanks,
Sudha
On Thu, Jul 15, 2021 at 10:42 PM vino yang <ya...@gmail.com> wrote:
> +1 for option B.
>
> Best,
> Vino
>
> Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
>
> > +1 on B. Not sure on A though. I understand the intent to have all in
> > one place. but not very sure if we can get all functionality (version,
> > type, component, status, parent- child relation), etc ported over to
> > github. I assume labels are the only option we have to achieve these.
> > Probably, we should also document the labels in detail so that anyone
> > looking to take a look at untriaged issues should know how/where to look
> > at. If we plan to use GH issues for all, I am sure there will be a lot of
> > proliferation of issues.
> >
> > On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org>
> wrote:
> >
> > > Based on this, I will start consolidating more of the cWiki content to
> > > github wiki and master branch?
> > >
> > > JIRA vs GH Issue still probably needs more feedback. I do see the
> > tradeoffs
> > > there.
> > >
> > > On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
> > >
> > > > +1
> > > >
> > > > On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> > > > > Hi all,
> > > > >
> > > > > When we incubated Hudi, we made some initial choices around
> > > collaboration
> > > > > tools of choice. I am wondering if there are still optimal, given
> the
> > > > scale
> > > > > of the community at this point.
> > > > >
> > > > > Specifically, two points.
> > > > >
> > > > > A) Our issue tracker is JIRA, while we just use Github Issues for
> > > support
> > > > > triage. While JIRA is pretty advanced and gives us the ability to
> > track
> > > > > releases, versions and kanban boards, there are few practical
> > > operational
> > > > > problems.
> > > > >
> > > > > - Developers often open bug fixes/PR which all need to be
> > continuously
> > > > > tagged against a release version (fix version)
> > > > > - Referencing JIRAs from Pull Requests is great (we cannot do
> things
> > > like
> > > > > `fixes #1234` to close issues when PR lands, not an easy way to
> click
> > > and
> > > > > get to the JIRA)
> > > > > - Many more developers have a github account, to contribute to Hudi
> > > > though,
> > > > > they need an additional sign-up on jira.
> > > > >
> > > > > So wondering if we should just use one thing - Github Issues, and
> > build
> > > > > scripts/hubot or something to get the missing project management
> from
> > > > > boards.
> > > > >
> > > > > B) Our design docs are on cWiki. Even though we link it off the
> site,
> > > > from
> > > > > my experience, many do not discover them.
> > > > > For large PRs, we need to manually enforce that design and code are
> > in
> > > > sync
> > > > > before we land. If we can, I would love to make RFC being in good
> > > shape a
> > > > > pre-requisite for landing the PR.
> > > > > Once again, separate signup is needed to write design docs or
> comment
> > > on
> > > > > them.
> > > > >
> > > > > So, wondering if we can move our process docs etc into Github Wiki
> > and
> > > > RFCs
> > > > > to the master branch in a rfc folder, and we just use github PRs to
> > > raise
> > > > > RFCs and discuss them.
> > > > >
> > > > > This all also makes it easy for us to measure community activity
> and
> > > keep
> > > > > streamlining our processes.
> > > > >
> > > > > personally, these different channels are overwhelming to me
> at-least
> > :)
> > > > >
> > > > > Love to hear thoughts. Please specify if you are for,against each
> of
> > A
> > > > and
> > > > > B.
> > > > >
> > > > >
> > > > > Thanks
> > > > > Vinoth
> > > > >
> > > >
> > >
> >
> >
> > --
> > Regards,
> > -Sivabalan
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by vino yang <ya...@gmail.com>.
+1 for option B.
Best,
Vino
Sivabalan <n....@gmail.com> 于2021年7月16日周五 上午10:35写道：
> +1 on B. Not sure on A though. I understand the intent to have all in
> one place. but not very sure if we can get all functionality (version,
> type, component, status, parent- child relation), etc ported over to
> github. I assume labels are the only option we have to achieve these.
> Probably, we should also document the labels in detail so that anyone
> looking to take a look at untriaged issues should know how/where to look
> at. If we plan to use GH issues for all, I am sure there will be a lot of
> proliferation of issues.
>
> On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org> wrote:
>
> > Based on this, I will start consolidating more of the cWiki content to
> > github wiki and master branch?
> >
> > JIRA vs GH Issue still probably needs more feedback. I do see the
> tradeoffs
> > there.
> >
> > On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
> >
> > > +1
> > >
> > > On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> > > > Hi all,
> > > >
> > > > When we incubated Hudi, we made some initial choices around
> > collaboration
> > > > tools of choice. I am wondering if there are still optimal, given the
> > > scale
> > > > of the community at this point.
> > > >
> > > > Specifically, two points.
> > > >
> > > > A) Our issue tracker is JIRA, while we just use Github Issues for
> > support
> > > > triage. While JIRA is pretty advanced and gives us the ability to
> track
> > > > releases, versions and kanban boards, there are few practical
> > operational
> > > > problems.
> > > >
> > > > - Developers often open bug fixes/PR which all need to be
> continuously
> > > > tagged against a release version (fix version)
> > > > - Referencing JIRAs from Pull Requests is great (we cannot do things
> > like
> > > > `fixes #1234` to close issues when PR lands, not an easy way to click
> > and
> > > > get to the JIRA)
> > > > - Many more developers have a github account, to contribute to Hudi
> > > though,
> > > > they need an additional sign-up on jira.
> > > >
> > > > So wondering if we should just use one thing - Github Issues, and
> build
> > > > scripts/hubot or something to get the missing project management from
> > > > boards.
> > > >
> > > > B) Our design docs are on cWiki. Even though we link it off the site,
> > > from
> > > > my experience, many do not discover them.
> > > > For large PRs, we need to manually enforce that design and code are
> in
> > > sync
> > > > before we land. If we can, I would love to make RFC being in good
> > shape a
> > > > pre-requisite for landing the PR.
> > > > Once again, separate signup is needed to write design docs or comment
> > on
> > > > them.
> > > >
> > > > So, wondering if we can move our process docs etc into Github Wiki
> and
> > > RFCs
> > > > to the master branch in a rfc folder, and we just use github PRs to
> > raise
> > > > RFCs and discuss them.
> > > >
> > > > This all also makes it easy for us to measure community activity and
> > keep
> > > > streamlining our processes.
> > > >
> > > > personally, these different channels are overwhelming to me at-least
> :)
> > > >
> > > > Love to hear thoughts. Please specify if you are for,against each of
> A
> > > and
> > > > B.
> > > >
> > > >
> > > > Thanks
> > > > Vinoth
> > > >
> > >
> >
>
>
> --
> Regards,
> -Sivabalan
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Sivabalan <n....@gmail.com>.
+1 on B. Not sure on A though. I understand the intent to have all in
one place. but not very sure if we can get all functionality (version,
type, component, status, parent- child relation), etc ported over to
github. I assume labels are the only option we have to achieve these.
Probably, we should also document the labels in detail so that anyone
looking to take a look at untriaged issues should know how/where to look
at. If we plan to use GH issues for all, I am sure there will be a lot of
proliferation of issues.
On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar <vi...@apache.org> wrote:
> Based on this, I will start consolidating more of the cWiki content to
> github wiki and master branch?
>
> JIRA vs GH Issue still probably needs more feedback. I do see the tradeoffs
> there.
>
> On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
>
> > +1
> >
> > On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> > > Hi all,
> > >
> > > When we incubated Hudi, we made some initial choices around
> collaboration
> > > tools of choice. I am wondering if there are still optimal, given the
> > scale
> > > of the community at this point.
> > >
> > > Specifically, two points.
> > >
> > > A) Our issue tracker is JIRA, while we just use Github Issues for
> support
> > > triage. While JIRA is pretty advanced and gives us the ability to track
> > > releases, versions and kanban boards, there are few practical
> operational
> > > problems.
> > >
> > > - Developers often open bug fixes/PR which all need to be continuously
> > > tagged against a release version (fix version)
> > > - Referencing JIRAs from Pull Requests is great (we cannot do things
> like
> > > `fixes #1234` to close issues when PR lands, not an easy way to click
> and
> > > get to the JIRA)
> > > - Many more developers have a github account, to contribute to Hudi
> > though,
> > > they need an additional sign-up on jira.
> > >
> > > So wondering if we should just use one thing - Github Issues, and build
> > > scripts/hubot or something to get the missing project management from
> > > boards.
> > >
> > > B) Our design docs are on cWiki. Even though we link it off the site,
> > from
> > > my experience, many do not discover them.
> > > For large PRs, we need to manually enforce that design and code are in
> > sync
> > > before we land. If we can, I would love to make RFC being in good
> shape a
> > > pre-requisite for landing the PR.
> > > Once again, separate signup is needed to write design docs or comment
> on
> > > them.
> > >
> > > So, wondering if we can move our process docs etc into Github Wiki and
> > RFCs
> > > to the master branch in a rfc folder, and we just use github PRs to
> raise
> > > RFCs and discuss them.
> > >
> > > This all also makes it easy for us to measure community activity and
> keep
> > > streamlining our processes.
> > >
> > > personally, these different channels are overwhelming to me at-least :)
> > >
> > > Love to hear thoughts. Please specify if you are for,against each of A
> > and
> > > B.
> > >
> > >
> > > Thanks
> > > Vinoth
> > >
> >
>
--
Regards,
-Sivabalan
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
Based on this, I will start consolidating more of the cWiki content to
github wiki and master branch?
JIRA vs GH Issue still probably needs more feedback. I do see the tradeoffs
there.
On Fri, Jul 9, 2021 at 2:39 AM wei li <lw...@gmail.com> wrote:
> +1
>
> On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> > Hi all,
> >
> > When we incubated Hudi, we made some initial choices around collaboration
> > tools of choice. I am wondering if there are still optimal, given the
> scale
> > of the community at this point.
> >
> > Specifically, two points.
> >
> > A) Our issue tracker is JIRA, while we just use Github Issues for support
> > triage. While JIRA is pretty advanced and gives us the ability to track
> > releases, versions and kanban boards, there are few practical operational
> > problems.
> >
> > - Developers often open bug fixes/PR which all need to be continuously
> > tagged against a release version (fix version)
> > - Referencing JIRAs from Pull Requests is great (we cannot do things like
> > `fixes #1234` to close issues when PR lands, not an easy way to click and
> > get to the JIRA)
> > - Many more developers have a github account, to contribute to Hudi
> though,
> > they need an additional sign-up on jira.
> >
> > So wondering if we should just use one thing - Github Issues, and build
> > scripts/hubot or something to get the missing project management from
> > boards.
> >
> > B) Our design docs are on cWiki. Even though we link it off the site,
> from
> > my experience, many do not discover them.
> > For large PRs, we need to manually enforce that design and code are in
> sync
> > before we land. If we can, I would love to make RFC being in good shape a
> > pre-requisite for landing the PR.
> > Once again, separate signup is needed to write design docs or comment on
> > them.
> >
> > So, wondering if we can move our process docs etc into Github Wiki and
> RFCs
> > to the master branch in a rfc folder, and we just use github PRs to raise
> > RFCs and discuss them.
> >
> > This all also makes it easy for us to measure community activity and keep
> > streamlining our processes.
> >
> > personally, these different channels are overwhelming to me at-least :)
> >
> > Love to hear thoughts. Please specify if you are for,against each of A
> and
> > B.
> >
> >
> > Thanks
> > Vinoth
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by wei li <lw...@gmail.com>.
+1
On 2021/07/02 03:40:51, Vinoth Chandar <vi...@apache.org> wrote:
> Hi all,
>
> When we incubated Hudi, we made some initial choices around collaboration
> tools of choice. I am wondering if there are still optimal, given the scale
> of the community at this point.
>
> Specifically, two points.
>
> A) Our issue tracker is JIRA, while we just use Github Issues for support
> triage. While JIRA is pretty advanced and gives us the ability to track
> releases, versions and kanban boards, there are few practical operational
> problems.
>
> - Developers often open bug fixes/PR which all need to be continuously
> tagged against a release version (fix version)
> - Referencing JIRAs from Pull Requests is great (we cannot do things like
> `fixes #1234` to close issues when PR lands, not an easy way to click and
> get to the JIRA)
> - Many more developers have a github account, to contribute to Hudi though,
> they need an additional sign-up on jira.
>
> So wondering if we should just use one thing - Github Issues, and build
> scripts/hubot or something to get the missing project management from
> boards.
>
> B) Our design docs are on cWiki. Even though we link it off the site, from
> my experience, many do not discover them.
> For large PRs, we need to manually enforce that design and code are in sync
> before we land. If we can, I would love to make RFC being in good shape a
> pre-requisite for landing the PR.
> Once again, separate signup is needed to write design docs or comment on
> them.
>
> So, wondering if we can move our process docs etc into Github Wiki and RFCs
> to the master branch in a rfc folder, and we just use github PRs to raise
> RFCs and discuss them.
>
> This all also makes it easy for us to measure community activity and keep
> streamlining our processes.
>
> personally, these different channels are overwhelming to me at-least :)
>
> Love to hear thoughts. Please specify if you are for,against each of A and
> B.
>
>
> Thanks
> Vinoth
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
Any more strong opinions around these?
On Mon, Jul 5, 2021 at 7:43 AM Vinoth Chandar <vi...@apache.org> wrote:
> I had similar views on A actually. JIRA is pretty powerful, queryable.
> But, I convinced myself on labelling and then building out dashboards using
> SQL (for reports/analytics).
> Still having one place for issues/prs. For releases, we can
> directly leverage milestones.
>
> We can definitely prioritize B first. Seems like everyone is on-board for
> that.
>
> @raymond : I am not sure if we will be able to install this on to the
> apache organization. Has been an issue for many of these github related
> services.
>
>
> On Sat, Jul 3, 2021 at 1:00 PM Raymond Xu <xu...@gmail.com>
> wrote:
>
>> Just to mention there are some GitHub plugin brings JIRA features to GH
>> issues. This one for example is free for open source.
>> https://www.zenhub.com/pricing
>>
>>
>>
>> On Fri, Jul 2, 2021 at 8:58 PM Navi Brar <navinder_brar@yahoo.com
>> .invalid>
>> wrote:
>>
>> > Hi,
>> >
>> >
>> > +1 on B
>> >
>> >
>> > But I have a slightly orthogonal view on A. I think jira should stay. It
>> > provides a lot more visibility on the issue management. You can link
>> PRs,
>> > wikis, releases etc easily which everyone will have to dig through the
>> > comments in github or every github issue might end up having too many
>> > labels that they might loose the significance. I recently landed a jira
>> on
>> > Hudi and I think the integration with github was pretty seamless.
>> >
>> >
>> > Happy either ways though.
>> >
>> >
>> > Thanks,
>> >
>> > Navinder
>> >
>> > >
>> > > On 03-Jul-2021, at 8:12 AM, vbalaji@apache.org wrote:
>> > >
>> > > +1 for both A and B. Makes sense to centralize bug tracking and RFCs
>> > in github.
>> > > Balaji.V
>> > >
>> > >
>> > > On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar <
>> > vinoth@apache.org> wrote:
>> > >
>> > > Raymond - +1 on your thoughts.
>> > >
>> > > Once we have more voices and alignment, we can do one final RFC on
>> cWiki
>> > > covering everything.
>> > >
>> > > Can more people please chime in. Ideally we will put this to a VOTE
>> > >
>> > >> On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <
>> xu.shiyan.raymond@gmail.com
>> > >
>> > >> wrote:
>> > >>
>> > >> +1 for both A and B
>> > >>
>> > >> Also a related suggestion:
>> > >> we can put the release notes and new feature highlights in the
>> release
>> > >> notes section in GitHub releases instead of separately writing them
>> in
>> > the
>> > >> asf-site
>> > >>
>> > >>
>> > >> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason
>> <pwason@uber.com.invalid
>> > >
>> > >> wrote:
>> > >>
>> > >>> +1 for complete Github migration. JIRA is too cumbersome and
>> painful to
>> > >>> use.
>> > >>>
>> > >>> Github PRs and wiki also improve visibility of the project and I
>> think
>> > >> may
>> > >>> increase community feedback and participation as its simpler to use.
>> > >>>
>> > >>> Prashant
>> > >>>
>> > >>>
>> > >>>> On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org>
>> > wrote:
>> > >>>
>> > >>>> Hi all,
>> > >>>>
>> > >>>> When we incubated Hudi, we made some initial choices around
>> > >> collaboration
>> > >>>> tools of choice. I am wondering if there are still optimal, given
>> the
>> > >>> scale
>> > >>>> of the community at this point.
>> > >>>>
>> > >>>> Specifically, two points.
>> > >>>>
>> > >>>> A) Our issue tracker is JIRA, while we just use Github Issues for
>> > >> support
>> > >>>> triage. While JIRA is pretty advanced and gives us the ability to
>> > track
>> > >>>> releases, versions and kanban boards, there are few practical
>> > >> operational
>> > >>>> problems.
>> > >>>>
>> > >>>> - Developers often open bug fixes/PR which all need to be
>> continuously
>> > >>>> tagged against a release version (fix version)
>> > >>>> - Referencing JIRAs from Pull Requests is great (we cannot do
>> things
>> > >> like
>> > >>>> `fixes #1234` to close issues when PR lands, not an easy way to
>> click
>> > >> and
>> > >>>> get to the JIRA)
>> > >>>> - Many more developers have a github account, to contribute to Hudi
>> > >>> though,
>> > >>>> they need an additional sign-up on jira.
>> > >>>>
>> > >>>> So wondering if we should just use one thing - Github Issues, and
>> > build
>> > >>>> scripts/hubot or something to get the missing project management
>> from
>> > >>>> boards.
>> > >>>>
>> > >>>> B) Our design docs are on cWiki. Even though we link it off the
>> site,
>> > >>> from
>> > >>>> my experience, many do not discover them.
>> > >>>> For large PRs, we need to manually enforce that design and code
>> are in
>> > >>> sync
>> > >>>> before we land. If we can, I would love to make RFC being in good
>> > >> shape a
>> > >>>> pre-requisite for landing the PR.
>> > >>>> Once again, separate signup is needed to write design docs or
>> comment
>> > >> on
>> > >>>> them.
>> > >>>>
>> > >>>> So, wondering if we can move our process docs etc into Github Wiki
>> and
>> > >>> RFCs
>> > >>>> to the master branch in a rfc folder, and we just use github PRs to
>> > >> raise
>> > >>>> RFCs and discuss them.
>> > >>>>
>> > >>>> This all also makes it easy for us to measure community activity
>> and
>> > >> keep
>> > >>>> streamlining our processes.
>> > >>>>
>> > >>>> personally, these different channels are overwhelming to me
>> at-least
>> > :)
>> > >>>>
>> > >>>> Love to hear thoughts. Please specify if you are for,against each
>> of A
>> > >>> and
>> > >>>> B.
>> > >>>>
>> > >>>>
>> > >>>> Thanks
>> > >>>> Vinoth
>> > >>>>
>> > >>>
>> > >>
>> >
>> >
>>
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
I had similar views on A actually. JIRA is pretty powerful, queryable. But,
I convinced myself on labelling and then building out dashboards using SQL
(for reports/analytics).
Still having one place for issues/prs. For releases, we can
directly leverage milestones.
We can definitely prioritize B first. Seems like everyone is on-board for
that.
@raymond : I am not sure if we will be able to install this on to the
apache organization. Has been an issue for many of these github related
services.
On Sat, Jul 3, 2021 at 1:00 PM Raymond Xu <xu...@gmail.com>
wrote:
> Just to mention there are some GitHub plugin brings JIRA features to GH
> issues. This one for example is free for open source.
> https://www.zenhub.com/pricing
>
>
>
> On Fri, Jul 2, 2021 at 8:58 PM Navi Brar <na...@yahoo.com.invalid>
> wrote:
>
> > Hi,
> >
> >
> > +1 on B
> >
> >
> > But I have a slightly orthogonal view on A. I think jira should stay. It
> > provides a lot more visibility on the issue management. You can link PRs,
> > wikis, releases etc easily which everyone will have to dig through the
> > comments in github or every github issue might end up having too many
> > labels that they might loose the significance. I recently landed a jira
> on
> > Hudi and I think the integration with github was pretty seamless.
> >
> >
> > Happy either ways though.
> >
> >
> > Thanks,
> >
> > Navinder
> >
> > >
> > > On 03-Jul-2021, at 8:12 AM, vbalaji@apache.org wrote:
> > >
> > > +1 for both A and B. Makes sense to centralize bug tracking and RFCs
> > in github.
> > > Balaji.V
> > >
> > >
> > > On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar <
> > vinoth@apache.org> wrote:
> > >
> > > Raymond - +1 on your thoughts.
> > >
> > > Once we have more voices and alignment, we can do one final RFC on
> cWiki
> > > covering everything.
> > >
> > > Can more people please chime in. Ideally we will put this to a VOTE
> > >
> > >> On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <
> xu.shiyan.raymond@gmail.com
> > >
> > >> wrote:
> > >>
> > >> +1 for both A and B
> > >>
> > >> Also a related suggestion:
> > >> we can put the release notes and new feature highlights in the release
> > >> notes section in GitHub releases instead of separately writing them in
> > the
> > >> asf-site
> > >>
> > >>
> > >> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason
> <pwason@uber.com.invalid
> > >
> > >> wrote:
> > >>
> > >>> +1 for complete Github migration. JIRA is too cumbersome and painful
> to
> > >>> use.
> > >>>
> > >>> Github PRs and wiki also improve visibility of the project and I
> think
> > >> may
> > >>> increase community feedback and participation as its simpler to use.
> > >>>
> > >>> Prashant
> > >>>
> > >>>
> > >>>> On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org>
> > wrote:
> > >>>
> > >>>> Hi all,
> > >>>>
> > >>>> When we incubated Hudi, we made some initial choices around
> > >> collaboration
> > >>>> tools of choice. I am wondering if there are still optimal, given
> the
> > >>> scale
> > >>>> of the community at this point.
> > >>>>
> > >>>> Specifically, two points.
> > >>>>
> > >>>> A) Our issue tracker is JIRA, while we just use Github Issues for
> > >> support
> > >>>> triage. While JIRA is pretty advanced and gives us the ability to
> > track
> > >>>> releases, versions and kanban boards, there are few practical
> > >> operational
> > >>>> problems.
> > >>>>
> > >>>> - Developers often open bug fixes/PR which all need to be
> continuously
> > >>>> tagged against a release version (fix version)
> > >>>> - Referencing JIRAs from Pull Requests is great (we cannot do things
> > >> like
> > >>>> `fixes #1234` to close issues when PR lands, not an easy way to
> click
> > >> and
> > >>>> get to the JIRA)
> > >>>> - Many more developers have a github account, to contribute to Hudi
> > >>> though,
> > >>>> they need an additional sign-up on jira.
> > >>>>
> > >>>> So wondering if we should just use one thing - Github Issues, and
> > build
> > >>>> scripts/hubot or something to get the missing project management
> from
> > >>>> boards.
> > >>>>
> > >>>> B) Our design docs are on cWiki. Even though we link it off the
> site,
> > >>> from
> > >>>> my experience, many do not discover them.
> > >>>> For large PRs, we need to manually enforce that design and code are
> in
> > >>> sync
> > >>>> before we land. If we can, I would love to make RFC being in good
> > >> shape a
> > >>>> pre-requisite for landing the PR.
> > >>>> Once again, separate signup is needed to write design docs or
> comment
> > >> on
> > >>>> them.
> > >>>>
> > >>>> So, wondering if we can move our process docs etc into Github Wiki
> and
> > >>> RFCs
> > >>>> to the master branch in a rfc folder, and we just use github PRs to
> > >> raise
> > >>>> RFCs and discuss them.
> > >>>>
> > >>>> This all also makes it easy for us to measure community activity and
> > >> keep
> > >>>> streamlining our processes.
> > >>>>
> > >>>> personally, these different channels are overwhelming to me at-least
> > :)
> > >>>>
> > >>>> Love to hear thoughts. Please specify if you are for,against each
> of A
> > >>> and
> > >>>> B.
> > >>>>
> > >>>>
> > >>>> Thanks
> > >>>> Vinoth
> > >>>>
> > >>>
> > >>
> >
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Raymond Xu <xu...@gmail.com>.
Just to mention there are some GitHub plugin brings JIRA features to GH
issues. This one for example is free for open source.
https://www.zenhub.com/pricing
On Fri, Jul 2, 2021 at 8:58 PM Navi Brar <na...@yahoo.com.invalid>
wrote:
> Hi,
>
>
> +1 on B
>
>
> But I have a slightly orthogonal view on A. I think jira should stay. It
> provides a lot more visibility on the issue management. You can link PRs,
> wikis, releases etc easily which everyone will have to dig through the
> comments in github or every github issue might end up having too many
> labels that they might loose the significance. I recently landed a jira on
> Hudi and I think the integration with github was pretty seamless.
>
>
> Happy either ways though.
>
>
> Thanks,
>
> Navinder
>
> >
> > On 03-Jul-2021, at 8:12 AM, vbalaji@apache.org wrote:
> >
> > +1 for both A and B. Makes sense to centralize bug tracking and RFCs
> in github.
> > Balaji.V
> >
> >
> > On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar <
> vinoth@apache.org> wrote:
> >
> > Raymond - +1 on your thoughts.
> >
> > Once we have more voices and alignment, we can do one final RFC on cWiki
> > covering everything.
> >
> > Can more people please chime in. Ideally we will put this to a VOTE
> >
> >> On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <xu.shiyan.raymond@gmail.com
> >
> >> wrote:
> >>
> >> +1 for both A and B
> >>
> >> Also a related suggestion:
> >> we can put the release notes and new feature highlights in the release
> >> notes section in GitHub releases instead of separately writing them in
> the
> >> asf-site
> >>
> >>
> >> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason <pwason@uber.com.invalid
> >
> >> wrote:
> >>
> >>> +1 for complete Github migration. JIRA is too cumbersome and painful to
> >>> use.
> >>>
> >>> Github PRs and wiki also improve visibility of the project and I think
> >> may
> >>> increase community feedback and participation as its simpler to use.
> >>>
> >>> Prashant
> >>>
> >>>
> >>>> On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org>
> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> When we incubated Hudi, we made some initial choices around
> >> collaboration
> >>>> tools of choice. I am wondering if there are still optimal, given the
> >>> scale
> >>>> of the community at this point.
> >>>>
> >>>> Specifically, two points.
> >>>>
> >>>> A) Our issue tracker is JIRA, while we just use Github Issues for
> >> support
> >>>> triage. While JIRA is pretty advanced and gives us the ability to
> track
> >>>> releases, versions and kanban boards, there are few practical
> >> operational
> >>>> problems.
> >>>>
> >>>> - Developers often open bug fixes/PR which all need to be continuously
> >>>> tagged against a release version (fix version)
> >>>> - Referencing JIRAs from Pull Requests is great (we cannot do things
> >> like
> >>>> `fixes #1234` to close issues when PR lands, not an easy way to click
> >> and
> >>>> get to the JIRA)
> >>>> - Many more developers have a github account, to contribute to Hudi
> >>> though,
> >>>> they need an additional sign-up on jira.
> >>>>
> >>>> So wondering if we should just use one thing - Github Issues, and
> build
> >>>> scripts/hubot or something to get the missing project management from
> >>>> boards.
> >>>>
> >>>> B) Our design docs are on cWiki. Even though we link it off the site,
> >>> from
> >>>> my experience, many do not discover them.
> >>>> For large PRs, we need to manually enforce that design and code are in
> >>> sync
> >>>> before we land. If we can, I would love to make RFC being in good
> >> shape a
> >>>> pre-requisite for landing the PR.
> >>>> Once again, separate signup is needed to write design docs or comment
> >> on
> >>>> them.
> >>>>
> >>>> So, wondering if we can move our process docs etc into Github Wiki and
> >>> RFCs
> >>>> to the master branch in a rfc folder, and we just use github PRs to
> >> raise
> >>>> RFCs and discuss them.
> >>>>
> >>>> This all also makes it easy for us to measure community activity and
> >> keep
> >>>> streamlining our processes.
> >>>>
> >>>> personally, these different channels are overwhelming to me at-least
> :)
> >>>>
> >>>> Love to hear thoughts. Please specify if you are for,against each of A
> >>> and
> >>>> B.
> >>>>
> >>>>
> >>>> Thanks
> >>>> Vinoth
> >>>>
> >>>
> >>
>
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Navi Brar <na...@yahoo.com.INVALID>.
Hi,
+1 on B
But I have a slightly orthogonal view on A. I think jira should stay. It provides a lot more visibility on the issue management. You can link PRs, wikis, releases etc easily which everyone will have to dig through the comments in github or every github issue might end up having too many labels that they might loose the significance. I recently landed a jira on Hudi and I think the integration with github was pretty seamless.
Happy either ways though.
Thanks,
Navinder
>
> On 03-Jul-2021, at 8:12 AM, vbalaji@apache.org wrote:
>
> +1 for both A and B. Makes sense to centralize bug tracking and RFCs in github.
> Balaji.V
>
>
> On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar <vi...@apache.org> wrote:
>
> Raymond - +1 on your thoughts.
>
> Once we have more voices and alignment, we can do one final RFC on cWiki
> covering everything.
>
> Can more people please chime in. Ideally we will put this to a VOTE
>
>> On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <xu...@gmail.com>
>> wrote:
>>
>> +1 for both A and B
>>
>> Also a related suggestion:
>> we can put the release notes and new feature highlights in the release
>> notes section in GitHub releases instead of separately writing them in the
>> asf-site
>>
>>
>> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason <pw...@uber.com.invalid>
>> wrote:
>>
>>> +1 for complete Github migration. JIRA is too cumbersome and painful to
>>> use.
>>>
>>> Github PRs and wiki also improve visibility of the project and I think
>> may
>>> increase community feedback and participation as its simpler to use.
>>>
>>> Prashant
>>>
>>>
>>>> On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org> wrote:
>>>
>>>> Hi all,
>>>>
>>>> When we incubated Hudi, we made some initial choices around
>> collaboration
>>>> tools of choice. I am wondering if there are still optimal, given the
>>> scale
>>>> of the community at this point.
>>>>
>>>> Specifically, two points.
>>>>
>>>> A) Our issue tracker is JIRA, while we just use Github Issues for
>> support
>>>> triage. While JIRA is pretty advanced and gives us the ability to track
>>>> releases, versions and kanban boards, there are few practical
>> operational
>>>> problems.
>>>>
>>>> - Developers often open bug fixes/PR which all need to be continuously
>>>> tagged against a release version (fix version)
>>>> - Referencing JIRAs from Pull Requests is great (we cannot do things
>> like
>>>> `fixes #1234` to close issues when PR lands, not an easy way to click
>> and
>>>> get to the JIRA)
>>>> - Many more developers have a github account, to contribute to Hudi
>>> though,
>>>> they need an additional sign-up on jira.
>>>>
>>>> So wondering if we should just use one thing - Github Issues, and build
>>>> scripts/hubot or something to get the missing project management from
>>>> boards.
>>>>
>>>> B) Our design docs are on cWiki. Even though we link it off the site,
>>> from
>>>> my experience, many do not discover them.
>>>> For large PRs, we need to manually enforce that design and code are in
>>> sync
>>>> before we land. If we can, I would love to make RFC being in good
>> shape a
>>>> pre-requisite for landing the PR.
>>>> Once again, separate signup is needed to write design docs or comment
>> on
>>>> them.
>>>>
>>>> So, wondering if we can move our process docs etc into Github Wiki and
>>> RFCs
>>>> to the master branch in a rfc folder, and we just use github PRs to
>> raise
>>>> RFCs and discuss them.
>>>>
>>>> This all also makes it easy for us to measure community activity and
>> keep
>>>> streamlining our processes.
>>>>
>>>> personally, these different channels are overwhelming to me at-least :)
>>>>
>>>> Love to hear thoughts. Please specify if you are for,against each of A
>>> and
>>>> B.
>>>>
>>>>
>>>> Thanks
>>>> Vinoth
>>>>
>>>
>>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by "vbalaji@apache.org" <vb...@apache.org>.
+1 for both A and B. Makes sense to centralize bug tracking and RFCs in github.
Balaji.V
On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar <vi...@apache.org> wrote:
Raymond - +1 on your thoughts.
Once we have more voices and alignment, we can do one final RFC on cWiki
covering everything.
Can more people please chime in. Ideally we will put this to a VOTE
On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <xu...@gmail.com>
wrote:
> +1 for both A and B
>
> Also a related suggestion:
> we can put the release notes and new feature highlights in the release
> notes section in GitHub releases instead of separately writing them in the
> asf-site
>
>
> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason <pw...@uber.com.invalid>
> wrote:
>
> > +1 for complete Github migration. JIRA is too cumbersome and painful to
> > use.
> >
> > Github PRs and wiki also improve visibility of the project and I think
> may
> > increase community feedback and participation as its simpler to use.
> >
> > Prashant
> >
> >
> > On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org> wrote:
> >
> > > Hi all,
> > >
> > > When we incubated Hudi, we made some initial choices around
> collaboration
> > > tools of choice. I am wondering if there are still optimal, given the
> > scale
> > > of the community at this point.
> > >
> > > Specifically, two points.
> > >
> > > A) Our issue tracker is JIRA, while we just use Github Issues for
> support
> > > triage. While JIRA is pretty advanced and gives us the ability to track
> > > releases, versions and kanban boards, there are few practical
> operational
> > > problems.
> > >
> > > - Developers often open bug fixes/PR which all need to be continuously
> > > tagged against a release version (fix version)
> > > - Referencing JIRAs from Pull Requests is great (we cannot do things
> like
> > > `fixes #1234` to close issues when PR lands, not an easy way to click
> and
> > > get to the JIRA)
> > > - Many more developers have a github account, to contribute to Hudi
> > though,
> > > they need an additional sign-up on jira.
> > >
> > > So wondering if we should just use one thing - Github Issues, and build
> > > scripts/hubot or something to get the missing project management from
> > > boards.
> > >
> > > B) Our design docs are on cWiki. Even though we link it off the site,
> > from
> > > my experience, many do not discover them.
> > > For large PRs, we need to manually enforce that design and code are in
> > sync
> > > before we land. If we can, I would love to make RFC being in good
> shape a
> > > pre-requisite for landing the PR.
> > > Once again, separate signup is needed to write design docs or comment
> on
> > > them.
> > >
> > > So, wondering if we can move our process docs etc into Github Wiki and
> > RFCs
> > > to the master branch in a rfc folder, and we just use github PRs to
> raise
> > > RFCs and discuss them.
> > >
> > > This all also makes it easy for us to measure community activity and
> keep
> > > streamlining our processes.
> > >
> > > personally, these different channels are overwhelming to me at-least :)
> > >
> > > Love to hear thoughts. Please specify if you are for,against each of A
> > and
> > > B.
> > >
> > >
> > > Thanks
> > > Vinoth
> > >
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Vinoth Chandar <vi...@apache.org>.
Raymond - +1 on your thoughts.
Once we have more voices and alignment, we can do one final RFC on cWiki
covering everything.
Can more people please chime in. Ideally we will put this to a VOTE
On Fri, Jul 2, 2021 at 12:54 PM Raymond Xu <xu...@gmail.com>
wrote:
> +1 for both A and B
>
> Also a related suggestion:
> we can put the release notes and new feature highlights in the release
> notes section in GitHub releases instead of separately writing them in the
> asf-site
>
>
> On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason <pw...@uber.com.invalid>
> wrote:
>
> > +1 for complete Github migration. JIRA is too cumbersome and painful to
> > use.
> >
> > Github PRs and wiki also improve visibility of the project and I think
> may
> > increase community feedback and participation as its simpler to use.
> >
> > Prashant
> >
> >
> > On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org> wrote:
> >
> > > Hi all,
> > >
> > > When we incubated Hudi, we made some initial choices around
> collaboration
> > > tools of choice. I am wondering if there are still optimal, given the
> > scale
> > > of the community at this point.
> > >
> > > Specifically, two points.
> > >
> > > A) Our issue tracker is JIRA, while we just use Github Issues for
> support
> > > triage. While JIRA is pretty advanced and gives us the ability to track
> > > releases, versions and kanban boards, there are few practical
> operational
> > > problems.
> > >
> > > - Developers often open bug fixes/PR which all need to be continuously
> > > tagged against a release version (fix version)
> > > - Referencing JIRAs from Pull Requests is great (we cannot do things
> like
> > > `fixes #1234` to close issues when PR lands, not an easy way to click
> and
> > > get to the JIRA)
> > > - Many more developers have a github account, to contribute to Hudi
> > though,
> > > they need an additional sign-up on jira.
> > >
> > > So wondering if we should just use one thing - Github Issues, and build
> > > scripts/hubot or something to get the missing project management from
> > > boards.
> > >
> > > B) Our design docs are on cWiki. Even though we link it off the site,
> > from
> > > my experience, many do not discover them.
> > > For large PRs, we need to manually enforce that design and code are in
> > sync
> > > before we land. If we can, I would love to make RFC being in good
> shape a
> > > pre-requisite for landing the PR.
> > > Once again, separate signup is needed to write design docs or comment
> on
> > > them.
> > >
> > > So, wondering if we can move our process docs etc into Github Wiki and
> > RFCs
> > > to the master branch in a rfc folder, and we just use github PRs to
> raise
> > > RFCs and discuss them.
> > >
> > > This all also makes it easy for us to measure community activity and
> keep
> > > streamlining our processes.
> > >
> > > personally, these different channels are overwhelming to me at-least :)
> > >
> > > Love to hear thoughts. Please specify if you are for,against each of A
> > and
> > > B.
> > >
> > >
> > > Thanks
> > > Vinoth
> > >
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Raymond Xu <xu...@gmail.com>.
+1 for both A and B
Also a related suggestion:
we can put the release notes and new feature highlights in the release
notes section in GitHub releases instead of separately writing them in the
asf-site
On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason <pw...@uber.com.invalid>
wrote:
> +1 for complete Github migration. JIRA is too cumbersome and painful to
> use.
>
> Github PRs and wiki also improve visibility of the project and I think may
> increase community feedback and participation as its simpler to use.
>
> Prashant
>
>
> On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org> wrote:
>
> > Hi all,
> >
> > When we incubated Hudi, we made some initial choices around collaboration
> > tools of choice. I am wondering if there are still optimal, given the
> scale
> > of the community at this point.
> >
> > Specifically, two points.
> >
> > A) Our issue tracker is JIRA, while we just use Github Issues for support
> > triage. While JIRA is pretty advanced and gives us the ability to track
> > releases, versions and kanban boards, there are few practical operational
> > problems.
> >
> > - Developers often open bug fixes/PR which all need to be continuously
> > tagged against a release version (fix version)
> > - Referencing JIRAs from Pull Requests is great (we cannot do things like
> > `fixes #1234` to close issues when PR lands, not an easy way to click and
> > get to the JIRA)
> > - Many more developers have a github account, to contribute to Hudi
> though,
> > they need an additional sign-up on jira.
> >
> > So wondering if we should just use one thing - Github Issues, and build
> > scripts/hubot or something to get the missing project management from
> > boards.
> >
> > B) Our design docs are on cWiki. Even though we link it off the site,
> from
> > my experience, many do not discover them.
> > For large PRs, we need to manually enforce that design and code are in
> sync
> > before we land. If we can, I would love to make RFC being in good shape a
> > pre-requisite for landing the PR.
> > Once again, separate signup is needed to write design docs or comment on
> > them.
> >
> > So, wondering if we can move our process docs etc into Github Wiki and
> RFCs
> > to the master branch in a rfc folder, and we just use github PRs to raise
> > RFCs and discuss them.
> >
> > This all also makes it easy for us to measure community activity and keep
> > streamlining our processes.
> >
> > personally, these different channels are overwhelming to me at-least :)
> >
> > Love to hear thoughts. Please specify if you are for,against each of A
> and
> > B.
> >
> >
> > Thanks
> > Vinoth
> >
>
Re: [DISCUSS] Consolidate all dev collaboration to Github
Posted by Prashant Wason <pw...@uber.com.INVALID>.
+1 for complete Github migration. JIRA is too cumbersome and painful to use.
Github PRs and wiki also improve visibility of the project and I think may
increase community feedback and participation as its simpler to use.
Prashant
On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar <vi...@apache.org> wrote:
> Hi all,
>
> When we incubated Hudi, we made some initial choices around collaboration
> tools of choice. I am wondering if there are still optimal, given the scale
> of the community at this point.
>
> Specifically, two points.
>
> A) Our issue tracker is JIRA, while we just use Github Issues for support
> triage. While JIRA is pretty advanced and gives us the ability to track
> releases, versions and kanban boards, there are few practical operational
> problems.
>
> - Developers often open bug fixes/PR which all need to be continuously
> tagged against a release version (fix version)
> - Referencing JIRAs from Pull Requests is great (we cannot do things like
> `fixes #1234` to close issues when PR lands, not an easy way to click and
> get to the JIRA)
> - Many more developers have a github account, to contribute to Hudi though,
> they need an additional sign-up on jira.
>
> So wondering if we should just use one thing - Github Issues, and build
> scripts/hubot or something to get the missing project management from
> boards.
>
> B) Our design docs are on cWiki. Even though we link it off the site, from
> my experience, many do not discover them.
> For large PRs, we need to manually enforce that design and code are in sync
> before we land. If we can, I would love to make RFC being in good shape a
> pre-requisite for landing the PR.
> Once again, separate signup is needed to write design docs or comment on
> them.
>
> So, wondering if we can move our process docs etc into Github Wiki and RFCs
> to the master branch in a rfc folder, and we just use github PRs to raise
> RFCs and discuss them.
>
> This all also makes it easy for us to measure community activity and keep
> streamlining our processes.
>
> personally, these different channels are overwhelming to me at-least :)
>
> Love to hear thoughts. Please specify if you are for,against each of A and
> B.
>
>
> Thanks
> Vinoth
>