ccess stories with GitHub
> issues/discussions.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: [DISCUSS] Deprecate user@ in favor for github issues/discussions"
> on Thu, 7 Oct 2021 20:06:34 -0700,
> Micah Kornfield wrote:
>
> > Yeah, I think we can keep
ve better ideas. It
seems that they have their success stories with GitHub
issues/discussions.
Thanks,
--
kou
In
"Re: [DISCUSS] Deprecate user@ in favor for github issues/discussions" on
Thu, 7 Oct 2021 20:06:34 -0700,
Micah Kornfield wrote:
> Yeah, I think we can keep the both
Yeah, I think we can keep the both active. Would the experiment be
removing the guidance to use user@? What do you think the success metrics
would be?
On Tue, Oct 5, 2021 at 8:14 AM Aldrin wrote:
> >
> > How about trying GitHub issues and/or discussion in a
> > specified period without depreca
>
> How about trying GitHub issues and/or discussion in a
> specified period without deprecating user@? e.g. between
> 6.0.0 release and 7.0.0 release.
Oooh, I like this idea.
Aldrin Montana
Computer Science PhD Student
UC Santa Cruz
On Mon, Oct 4, 2021 at 7:11 PM Sutou Kouhei wrote:
> Hi,
Hi,
How about trying GitHub issues and/or discussion in a
specified period without deprecating user@? e.g. between
6.0.0 release and 7.0.0 release.
If we can see significant improvements in the period, we can
discuss this again.
In my opinion, I want to disable GitHub issues entirely by
.asf.yam
Mail is archived at [1] and [2], which uses Pony mail [3][4].
Contributed to an issue to make this more search engine friendly[5].
Search is really helpful to find answers as a user before posting a
question.
Arrow is developing rapidly, at present with greater engagement between
developers b
I'm +1 for GH issues due to it lowering the barrier for participation. As
someone who is sometimes a bit nervous about interacting with new open
source projects/communities, adding a GH Issue is fairly familiar and feels
inconsequential, whereas emailing everyone on a mailing list is
intimidating.
Just a comment on discussions: They already have answered/unanswered
filters and they have most of the same properties that "stack overflow"
questions have,
You do not need to "track" discussions. It's great to answer and react
quickly and if you have more discussions all the community might get m
+1 for issues because I believe it would lower the barrier for entry.
I'm +0 on discussions, they can work but would require more active
curation / labeling as they cannot be closed so an "answered /
unanswered" label would probably be needed.
> I think I already get e-mails from issues but
> hav
I'm not for or against this proposal.
I took a few minutes to browse the archives [1]. It seems to me that
the user@ list is working extremely well. People get answers quickly,
problems are converted into JIRA cases, and the discussion often
references existing information sources.
I want to than
On Wed, Sep 29, 2021 at 3:08 PM Antoine Pitrou wrote:
>
> Le 29/09/2021 à 20:51, Micah Kornfield a écrit :
> >>
> >> Cons:
> >> - Github is a not a mailing-list and does not integrate well in a normal
> >> e-mail workflow.
> >
> >
> > Would a mailing list mirror of the issues work for you (I gues
Le 29/09/2021 à 20:51, Micah Kornfield a écrit :
Cons:
- Github is a not a mailing-list and does not integrate well in a normal
e-mail workflow.
Would a mailing list mirror of the issues work for you (I guess it would
require an extra click). I think I already get e-mails from issues but
h
Just to comment on that - we are still using users@ mailing list (though it
has very low traffic/value) at Apache Airflow - but GitHub
Issues/Discussions are indeed rather useful I think and we are rather happy
with those.
I just created
https://cwiki.apache.org/confluence/pages/viewpage.action?pa
I am also +1 for all of the same reasons both Neal and Philip mention.
Lowering that barrier to participation for getting help + having that
information more easily findable will make it easiest for folks to use
and adopt Arrow. I will add personally I didn't realize I already do
this when working
>
> Cons:
> - Github is a not a mailing-list and does not integrate well in a normal
> e-mail workflow.
Would a mailing list mirror of the issues work for you (I guess it would
require an extra click). I think I already get e-mails from issues but
have them filtered out with the rest of other gi
+1 from me too. More and more developers seem to be accustomed to using
GitHub Issues to ask for help, and redirecting them to a mailing list adds
a barrier to participation.
Neal
On Wed, Sep 29, 2021 at 2:32 PM Phillip Cloud wrote:
> I am +1 on steering users towards GitHub issues for support
I am +1 on steering users towards GitHub issues for support questions. I
think there's a lot of value in someone being able to use a search engine
to potentially find an answer to their problem.
On Wed, Sep 29, 2021 at 2:16 PM Micah Kornfield
wrote:
> We discussed briefly on the sync this mornin
Le 29/09/2021 à 20:16, Micah Kornfield a écrit :
We discussed briefly on the sync this morning, but I was wondering what
people thought about removing the user@ mailing list in favor of either
Github issues or discussions. We can try to mirror issues to an
appropriate mailing list if archiving
I personally think this would be a nice switch.
The ease of searching alone is a worthwhile reason for this switch, which
would
also make the overall barrier to adoption a little bit lower.
I didn't think about decentralizing user issues before, so I think it's a
good thing
to mention. To some de
19 matches
Mail list logo
