Hi Bart,

I am in favour of moving to GitHub discussions and moving the more informal 
conversations to a slack channel.
Having questions marked as solved and publicly available will indirectly 
improve the overal documentation available for the project.

Cheers,
Hans
On 8 Oct 2024 at 08:33 +0200, Bart Maertens <bartm...@apache.org>, wrote:
> Hi Brandon,
>
> GitHub Discussions are different from GitHub issues. Discussions can be
> around a ticket or issue, but are generally more about discussing
> functionality, features and problems people may have in the use of the
> available functionality.
>
> Have a look at the "Get Inspired" section on the GitHub Discussions page
> [1] or this example of a lengthy thread on the Next.js GitHub Discussions
> [2].
> The longer-form-questions in GitHub Discussions provide a hybrid between
> direct chat and a more forum-like style of interacting, which imho will
> improve the quality of the questions and answers, as described in (c) in my
> initial post.
>
> I understand and agree with your point that the social aspect may be lower
> on GitHub Discussions.
> Even though that argument is valid, I don't know if it justifies running an
> entire Mattermost server.
> We could consider creating a #hop channel in the ASF Slack workspace [3]
> and move the social and more informal part of the discussions there.
>
> [1] https://github.com/features/discussions
> [2] https://github.com/vercel/next.js/discussions/46722
> [3] https://the-asf.slack.com/
>
> Regards,
> Bart
>
> On Tue, Oct 8, 2024 at 5:27 AM Brandon Jackson <usbran...@gmail.com> wrote:
>
> > I like the idea of Question/Answer discussions going to Github; but I would
> > still like to be able to chat with friends on Mattermost.
> > Where would the social aspect be? I see people using github issues for
> > what I think you are suggesting as discussions.
> >
> >
> > On Mon, Oct 7, 2024 at 8:43 AM Bart Maertens <bartm...@apache.org> wrote:
> >
> > > > Dear Hoppers,
> > > >
> > > > As a community, we're all constantly trying to improve Apache Hop and 
> > > > how
> > > > the community members can work together and interact.
> > > >
> > > > In that regard, we've come to a point where we may need to reconsider 
> > > > the
> > > > Mattermost chat [1].
> > > >
> > > > A couple of observations about the Mattermost chat:
> > > > a) it isn't hosted on an "official" Apache Hop subdomain (nor can it 
> > > > be).
> > > > b) access is open and free, but the chat history is not publicly
> > available
> > > > and not indexable by search engines.
> > > > c) the "quality" of the questions is not always as high as we'd like 
> > > > them
> > > > to be. There are a lot of open-ended or "build my pipeline" type of
> > > > questions that should be answered in the documentation and samples. 
> > > > Check
> > > > out the contribution guides [2] if you'd like to help out with the docs
> > and
> > > > samples.
> > > >
> > > > To improve community interaction on a truly open and publicly available
> > > > platform, we could consider enabling GitHub discussions [3] on our 
> > > > GitHub
> > > > repository [4], and move the Mattermost discussions there.
> > > >
> > > > GitHub Discussions have several advantages over our current Mattermost
> > > > chat:
> > > > a) even though not on an Apache subdomain, the discussions are part of
> > the
> > > > source code repository, and as such, they're as close as possible to the
> > > > project's source code and issues
> > > > b) GitHub Discussions are publicly available and indexable by search
> > > > engines
> > > > c) discussions can be labeled, marked as "Answered" etc.
> > > >
> > > > The switch to GitHub discussions is nothing but a suggestion, we're 
> > > > eager
> > > > to know what your thoughts and suggestions are.
> > > > Let's start the discussion!
> > > >
> > > > [1] https://chat.project-hop.org.
> > > > [2] https://hop.apache.org/community/contributing/
> > > > [3] https://github.com/features/discussions
> > > > [4] https://github.com/apache/hop
> > > >
> > > > Regards,
> > > > Bart
> > > >
> >

Reply via email to