You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by wenjun <we...@apache.org> on 2021/08/25 17:27:04 UTC
[Discuss] Discuss enabling Github Discussions
Hi community,
This email is aimed to discuss enabling GitHub Discussions[1] on the
DolphinScheduler repository.
Most of the time, we hope to use the GitHub Issue to trace a bug or a
specific new feature. A GitHub Issue needs to list the details of a
specific problem in a standard way, this may prevent new users from
discussing questions. And we also don't want to see too many questions in
the Issue list.
GitHub Discussions is a new way to communicate the project in the
community, and it can help contributors to discuss an idea or ask a
question easily. And it provides many operations for the community to
manage the Discussions.
The main concern is that we need to spend extra time to maintain the
Discussions, but I think it's worth doing.
Welcome to discuss this.
[1] https://docs.github.com/en/discussions
Thanks,
Wenjun Ruan
Re: [Discuss] Discuss enabling Github Discussions
Posted by leon bao <le...@apache.org>.
+1
wenjun <we...@apache.org> 于2021年8月26日周四 下午9:40写道：
> I strongly agree with communications should be archived by mail.
>
> I haven't found a way to sync GitHub Discussions to mail yet.
> GitHub Discussions support creates issue from the discussion, I think if we
> think a discussion is important, then we can create an issue to track, and
> the issue can be recorded.
>
>
> CalvinKirs <ac...@163.com> 于2021年8月26日周四 下午2:21写道：
>
> > ISSUE will eventually be archived by mail. Therefore, all our
> > communications on ISSUE and PR can be viewed by email.
> >
> >
> > OK, let's come back to this question. If you want to open it, I suggest
> > that we still insist on using English to communicate on "GITHUB DISCUSS".
> >
> >
> > Best Wishes！
> > CalvinKirs
> >
> >
> > On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
> > hi，
> > of course, the important and deep question should happen in the mailing
> > list, I think github discussion can help us move to be a global project,
> > maybe some users will move from wechat group to here
> > anyway, I think we can have a try, github discussion is new and our
> hope!
> >
> >
> > Best Regards
> >
> >
> >
> > ---------------
> > Apache DolphinScheduler PMC Chair
> > David Dai
> > lidongdai@apache.org
> > Linkedin: https://www.linkedin.com/in/dailidong
> > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> > ---------------
> >
> >
> > On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
> >
> > Hi, wenjun
> > Very good suggestion, but I want to determine whether his content will be
> > included in the mailing list, if not, then I think there may be no need,
> he
> > will cause us to waste a lot of energy, and can not form effective
> > precipitation.
> >
> >
> > Best Wishes！
> > CalvinKirs, Apache DolphinScheduler PMC
> >
> >
> > On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
> > Hi community,
> >
> > This email is aimed to discuss enabling GitHub Discussions[1] on the
> > DolphinScheduler repository.
> >
> > Most of the time, we hope to use the GitHub Issue to trace a bug or a
> > specific new feature. A GitHub Issue needs to list the details of a
> > specific problem in a standard way, this may prevent new users from
> > discussing questions. And we also don't want to see too many questions in
> > the Issue list.
> >
> > GitHub Discussions is a new way to communicate the project in the
> > community, and it can help contributors to discuss an idea or ask a
> > question easily. And it provides many operations for the community to
> > manage the Discussions.
> >
> > The main concern is that we need to spend extra time to maintain the
> > Discussions, but I think it's worth doing.
> >
> > Welcome to discuss this.
> >
> > [1] https://docs.github.com/en/discussions
> >
> > Thanks,
> > Wenjun Ruan
> >
> >
>
--
DolphinScheduler PMC
BaoLiang 鲍亮
leonbao@apache.org
Re: [Discuss] Discuss enabling Github Discussions
Posted by David Dai <li...@apache.org>.
hi users,
I will request the infra team to open the DolphinScheduler github Discussion.
Best Regards
---------------
Apache DolphinScheduler PMC Chair
David Dai
lidongdai@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy
---------------
On Wed, Sep 15, 2021 at 2:52 PM David Dai <li...@apache.org> wrote:
>
> +1
>
>
>
> Best Regards
>
>
>
> ---------------
> Apache DolphinScheduler PMC Chair
> David Dai
> lidongdai@apache.org
> Linkedin: https://www.linkedin.com/in/dailidong
> Twitter: @WorkflowEasy
> ---------------
>
> On Wed, Sep 15, 2021 at 2:31 PM CalvinKirs <ac...@163.com> wrote:
> >
> > +1
> >
> >
> > Regarding the boundary between discussion and issue, we can establish a unified consensus later.
> >
> >
> > Best Wishes！
> > CalvinKirs, Apache DolphinScheduler PMC
> >
> >
> > On 08/26/2021 21:40，wenjun<we...@apache.org> wrote：
> > I strongly agree with communications should be archived by mail.
> >
> > I haven't found a way to sync GitHub Discussions to mail yet.
> > GitHub Discussions support creates issue from the discussion, I think if we
> > think a discussion is important, then we can create an issue to track, and
> > the issue can be recorded.
> >
> >
> > CalvinKirs <ac...@163.com> 于2021年8月26日周四 下午2:21写道：
> >
> > ISSUE will eventually be archived by mail. Therefore, all our
> > communications on ISSUE and PR can be viewed by email.
> >
> >
> > OK, let's come back to this question. If you want to open it, I suggest
> > that we still insist on using English to communicate on "GITHUB DISCUSS".
> >
> >
> > Best Wishes！
> > CalvinKirs
> >
> >
> > On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
> > hi，
> > of course, the important and deep question should happen in the mailing
> > list, I think github discussion can help us move to be a global project,
> > maybe some users will move from wechat group to here
> > anyway, I think we can have a try, github discussion is new and our hope!
> >
> >
> > Best Regards
> >
> >
> >
> > ---------------
> > Apache DolphinScheduler PMC Chair
> > David Dai
> > lidongdai@apache.org
> > Linkedin: https://www.linkedin.com/in/dailidong
> > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> > ---------------
> >
> >
> > On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
> >
> > Hi, wenjun
> > Very good suggestion, but I want to determine whether his content will be
> > included in the mailing list, if not, then I think there may be no need, he
> > will cause us to waste a lot of energy, and can not form effective
> > precipitation.
> >
> >
> > Best Wishes！
> > CalvinKirs, Apache DolphinScheduler PMC
> >
> >
> > On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
> > Hi community,
> >
> > This email is aimed to discuss enabling GitHub Discussions[1] on the
> > DolphinScheduler repository.
> >
> > Most of the time, we hope to use the GitHub Issue to trace a bug or a
> > specific new feature. A GitHub Issue needs to list the details of a
> > specific problem in a standard way, this may prevent new users from
> > discussing questions. And we also don't want to see too many questions in
> > the Issue list.
> >
> > GitHub Discussions is a new way to communicate the project in the
> > community, and it can help contributors to discuss an idea or ask a
> > question easily. And it provides many operations for the community to
> > manage the Discussions.
> >
> > The main concern is that we need to spend extra time to maintain the
> > Discussions, but I think it's worth doing.
> >
> > Welcome to discuss this.
> >
> > [1] https://docs.github.com/en/discussions
> >
> > Thanks,
> > Wenjun Ruan
> >
> >
Re: [Discuss] Discuss enabling Github Discussions
Posted by David Dai <li...@apache.org>.
+1
Best Regards
---------------
Apache DolphinScheduler PMC Chair
David Dai
lidongdai@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy
---------------
On Wed, Sep 15, 2021 at 2:31 PM CalvinKirs <ac...@163.com> wrote:
>
> +1
>
>
> Regarding the boundary between discussion and issue, we can establish a unified consensus later.
>
>
> Best Wishes！
> CalvinKirs, Apache DolphinScheduler PMC
>
>
> On 08/26/2021 21:40，wenjun<we...@apache.org> wrote：
> I strongly agree with communications should be archived by mail.
>
> I haven't found a way to sync GitHub Discussions to mail yet.
> GitHub Discussions support creates issue from the discussion, I think if we
> think a discussion is important, then we can create an issue to track, and
> the issue can be recorded.
>
>
> CalvinKirs <ac...@163.com> 于2021年8月26日周四 下午2:21写道：
>
> ISSUE will eventually be archived by mail. Therefore, all our
> communications on ISSUE and PR can be viewed by email.
>
>
> OK, let's come back to this question. If you want to open it, I suggest
> that we still insist on using English to communicate on "GITHUB DISCUSS".
>
>
> Best Wishes！
> CalvinKirs
>
>
> On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
> hi，
> of course, the important and deep question should happen in the mailing
> list, I think github discussion can help us move to be a global project,
> maybe some users will move from wechat group to here
> anyway, I think we can have a try, github discussion is new and our hope!
>
>
> Best Regards
>
>
>
> ---------------
> Apache DolphinScheduler PMC Chair
> David Dai
> lidongdai@apache.org
> Linkedin: https://www.linkedin.com/in/dailidong
> Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> ---------------
>
>
> On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
>
> Hi, wenjun
> Very good suggestion, but I want to determine whether his content will be
> included in the mailing list, if not, then I think there may be no need, he
> will cause us to waste a lot of energy, and can not form effective
> precipitation.
>
>
> Best Wishes！
> CalvinKirs, Apache DolphinScheduler PMC
>
>
> On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
> Hi community,
>
> This email is aimed to discuss enabling GitHub Discussions[1] on the
> DolphinScheduler repository.
>
> Most of the time, we hope to use the GitHub Issue to trace a bug or a
> specific new feature. A GitHub Issue needs to list the details of a
> specific problem in a standard way, this may prevent new users from
> discussing questions. And we also don't want to see too many questions in
> the Issue list.
>
> GitHub Discussions is a new way to communicate the project in the
> community, and it can help contributors to discuss an idea or ask a
> question easily. And it provides many operations for the community to
> manage the Discussions.
>
> The main concern is that we need to spend extra time to maintain the
> Discussions, but I think it's worth doing.
>
> Welcome to discuss this.
>
> [1] https://docs.github.com/en/discussions
>
> Thanks,
> Wenjun Ruan
>
>
Re: [Discuss] Discuss enabling Github Discussions
Posted by CalvinKirs <ac...@163.com>.
+1
Regarding the boundary between discussion and issue, we can establish a unified consensus later.
Best Wishes！
CalvinKirs, Apache DolphinScheduler PMC
On 08/26/2021 21:40，wenjun<we...@apache.org> wrote：
I strongly agree with communications should be archived by mail.
I haven't found a way to sync GitHub Discussions to mail yet.
GitHub Discussions support creates issue from the discussion, I think if we
think a discussion is important, then we can create an issue to track, and
the issue can be recorded.
CalvinKirs <ac...@163.com> 于2021年8月26日周四 下午2:21写道：
ISSUE will eventually be archived by mail. Therefore, all our
communications on ISSUE and PR can be viewed by email.
OK, let's come back to this question. If you want to open it, I suggest
that we still insist on using English to communicate on "GITHUB DISCUSS".
Best Wishes！
CalvinKirs
On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
hi，
of course, the important and deep question should happen in the mailing
list, I think github discussion can help us move to be a global project,
maybe some users will move from wechat group to here
anyway, I think we can have a try, github discussion is new and our hope!
Best Regards
---------------
Apache DolphinScheduler PMC Chair
David Dai
lidongdai@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
---------------
On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
Hi, wenjun
Very good suggestion, but I want to determine whether his content will be
included in the mailing list, if not, then I think there may be no need, he
will cause us to waste a lot of energy, and can not form effective
precipitation.
Best Wishes！
CalvinKirs, Apache DolphinScheduler PMC
On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
Hi community,
This email is aimed to discuss enabling GitHub Discussions[1] on the
DolphinScheduler repository.
Most of the time, we hope to use the GitHub Issue to trace a bug or a
specific new feature. A GitHub Issue needs to list the details of a
specific problem in a standard way, this may prevent new users from
discussing questions. And we also don't want to see too many questions in
the Issue list.
GitHub Discussions is a new way to communicate the project in the
community, and it can help contributors to discuss an idea or ask a
question easily. And it provides many operations for the community to
manage the Discussions.
The main concern is that we need to spend extra time to maintain the
Discussions, but I think it's worth doing.
Welcome to discuss this.
[1] https://docs.github.com/en/discussions
Thanks,
Wenjun Ruan
Re: [Discuss] Discuss enabling Github Discussions
Posted by wenjun <we...@apache.org>.
I strongly agree with communications should be archived by mail.
I haven't found a way to sync GitHub Discussions to mail yet.
GitHub Discussions support creates issue from the discussion, I think if we
think a discussion is important, then we can create an issue to track, and
the issue can be recorded.
CalvinKirs <ac...@163.com> 于2021年8月26日周四 下午2:21写道：
> ISSUE will eventually be archived by mail. Therefore, all our
> communications on ISSUE and PR can be viewed by email.
>
>
> OK, let's come back to this question. If you want to open it, I suggest
> that we still insist on using English to communicate on "GITHUB DISCUSS".
>
>
> Best Wishes！
> CalvinKirs
>
>
> On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
> hi，
> of course, the important and deep question should happen in the mailing
> list, I think github discussion can help us move to be a global project,
> maybe some users will move from wechat group to here
> anyway, I think we can have a try, github discussion is new and our hope!
>
>
> Best Regards
>
>
>
> ---------------
> Apache DolphinScheduler PMC Chair
> David Dai
> lidongdai@apache.org
> Linkedin: https://www.linkedin.com/in/dailidong
> Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> ---------------
>
>
> On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
>
> Hi, wenjun
> Very good suggestion, but I want to determine whether his content will be
> included in the mailing list, if not, then I think there may be no need, he
> will cause us to waste a lot of energy, and can not form effective
> precipitation.
>
>
> Best Wishes！
> CalvinKirs, Apache DolphinScheduler PMC
>
>
> On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
> Hi community,
>
> This email is aimed to discuss enabling GitHub Discussions[1] on the
> DolphinScheduler repository.
>
> Most of the time, we hope to use the GitHub Issue to trace a bug or a
> specific new feature. A GitHub Issue needs to list the details of a
> specific problem in a standard way, this may prevent new users from
> discussing questions. And we also don't want to see too many questions in
> the Issue list.
>
> GitHub Discussions is a new way to communicate the project in the
> community, and it can help contributors to discuss an idea or ask a
> question easily. And it provides many operations for the community to
> manage the Discussions.
>
> The main concern is that we need to spend extra time to maintain the
> Discussions, but I think it's worth doing.
>
> Welcome to discuss this.
>
> [1] https://docs.github.com/en/discussions
>
> Thanks,
> Wenjun Ruan
>
>
Re: [Discuss] Discuss enabling Github Discussions
Posted by CalvinKirs <ac...@163.com>.
ISSUE will eventually be archived by mail. Therefore, all our communications on ISSUE and PR can be viewed by email.
OK, let's come back to this question. If you want to open it, I suggest that we still insist on using English to communicate on "GITHUB DISCUSS".
Best Wishes！
CalvinKirs
On 08/26/2021 13:16，David Dai<da...@gmail.com> wrote：
hi，
of course, the important and deep question should happen in the mailing
list, I think github discussion can help us move to be a global project,
maybe some users will move from wechat group to here
anyway, I think we can have a try, github discussion is new and our hope!
Best Regards
---------------
Apache DolphinScheduler PMC Chair
David Dai
lidongdai@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
---------------
On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
Hi, wenjun
Very good suggestion, but I want to determine whether his content will be
included in the mailing list, if not, then I think there may be no need, he
will cause us to waste a lot of energy, and can not form effective
precipitation.
Best Wishes！
CalvinKirs, Apache DolphinScheduler PMC
On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
Hi community,
This email is aimed to discuss enabling GitHub Discussions[1] on the
DolphinScheduler repository.
Most of the time, we hope to use the GitHub Issue to trace a bug or a
specific new feature. A GitHub Issue needs to list the details of a
specific problem in a standard way, this may prevent new users from
discussing questions. And we also don't want to see too many questions in
the Issue list.
GitHub Discussions is a new way to communicate the project in the
community, and it can help contributors to discuss an idea or ask a
question easily. And it provides many operations for the community to
manage the Discussions.
The main concern is that we need to spend extra time to maintain the
Discussions, but I think it's worth doing.
Welcome to discuss this.
[1] https://docs.github.com/en/discussions
Thanks,
Wenjun Ruan
Re: [Discuss] Discuss enabling Github Discussions
Posted by David Dai <da...@gmail.com>.
hi，
of course, the important and deep question should happen in the mailing
list, I think github discussion can help us move to be a global project,
maybe some users will move from wechat group to here
anyway, I think we can have a try, github discussion is new and our hope!
Best Regards
---------------
Apache DolphinScheduler PMC Chair
David Dai
lidongdai@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
---------------
On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <ac...@163.com> wrote:
> Hi, wenjun
> Very good suggestion, but I want to determine whether his content will be
> included in the mailing list, if not, then I think there may be no need, he
> will cause us to waste a lot of energy, and can not form effective
> precipitation.
>
>
> Best Wishes！
> CalvinKirs, Apache DolphinScheduler PMC
>
>
> On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
> Hi community,
>
> This email is aimed to discuss enabling GitHub Discussions[1] on the
> DolphinScheduler repository.
>
> Most of the time, we hope to use the GitHub Issue to trace a bug or a
> specific new feature. A GitHub Issue needs to list the details of a
> specific problem in a standard way, this may prevent new users from
> discussing questions. And we also don't want to see too many questions in
> the Issue list.
>
> GitHub Discussions is a new way to communicate the project in the
> community, and it can help contributors to discuss an idea or ask a
> question easily. And it provides many operations for the community to
> manage the Discussions.
>
> The main concern is that we need to spend extra time to maintain the
> Discussions, but I think it's worth doing.
>
> Welcome to discuss this.
>
> [1] https://docs.github.com/en/discussions
>
> Thanks,
> Wenjun Ruan
>
Re:[Discuss] Discuss enabling Github Discussions
Posted by CalvinKirs <ac...@163.com>.
Hi, wenjun
Very good suggestion, but I want to determine whether his content will be included in the mailing list, if not, then I think there may be no need, he will cause us to waste a lot of energy, and can not form effective precipitation.
Best Wishes！
CalvinKirs, Apache DolphinScheduler PMC
On 08/26/2021 01:27，wenjun<we...@apache.org> wrote：
Hi community,
This email is aimed to discuss enabling GitHub Discussions[1] on the
DolphinScheduler repository.
Most of the time, we hope to use the GitHub Issue to trace a bug or a
specific new feature. A GitHub Issue needs to list the details of a
specific problem in a standard way, this may prevent new users from
discussing questions. And we also don't want to see too many questions in
the Issue list.
GitHub Discussions is a new way to communicate the project in the
community, and it can help contributors to discuss an idea or ask a
question easily. And it provides many operations for the community to
manage the Discussions.
The main concern is that we need to spend extra time to maintain the
Discussions, but I think it's worth doing.
Welcome to discuss this.
[1] https://docs.github.com/en/discussions
Thanks,
Wenjun Ruan