Cordova dev discussions on GitHub

[Chris Brody <ch...@gmail.com>]

I started thinking it might be cool to have Cordova dev discussions in
issues separate from apache/cordova/issues, which I think is the standard,
default place where users raise general issues they encounter and where we
can communicate major things such as breaking changes and deprecated
functionality. My idea would be to have a "cordova-dev" issue repository,
as a GitHub equivalent to the dev channel on Slack, lower level than
cordova-contribute and higher level than cordova-coho.

I completely understand that this would not be super practical given both
the impending major release and how we work with Apache infra. But just
food for thought we can chew on in the background. Maybe we could use
something else such as cordova-discuss, cordova-coho, or even
cordova-common?

Just an idea.

Re: Cordova dev discussions on GitHub

[Chris Brody <ch...@gmail.com>]

Thanks for the feedback. I would definitely agree not increase the number
of communication channels, just to evaluate possibly optimize what we have
now. I would also hope to find ways to consolidate, rename, and/or remove
some of these communication channels. The mailing list does seem good for
discussions, but seems pretty bad to me for anything that should be tracked
and not forgotten.

My main point was to see if we can find a way to improve the abstraction
between high-level discussions that do affect the user community and
lower-level tasks that would not be of interest to most users.


On Wed, Feb 19, 2020 at 4:05 AM <ra...@gmail.com> wrote:

> I agree with Niklas that we should not increase the number of communication
> channels.
>
> Rather, we should try to better communicate the existence and the intended
> scopes of the ones we already have. Maybe even get rid of some of them.
>
> Niklas Merz <ni...@apache.org> schrieb am Mi., 19. Feb. 2020, 08:10:
>
> > I understand that it might be difficult for users to find the right place
> > to discuss, ask things or get announcements. When I was new I did not
> > follow the mailing list for some time, because mailing lists a concept
> many
> > people are not familiar anymore I guess.
> >
> > I don't think adding another place (especially a second Github repo like
> > cordova-discuss) makes this easier. I have always seen cordova-discuss
> as a
> > place where discussion on specific proposals happen. The mailing list is
> > the place where decissions and all official stuff like VOTES and
> > announcments must take place.
> >
> > That's why I think we are better off by promoting the lists for
> developers
> > interrested. Maybe add note to every README, explain more on website, add
> > to issue template and so on. dev@cordova.apache.org is the official
> > channel how Apache works even I fully agree this is not the most modern,
> > user-friendly way, but after some time I came to like the list, even
> before
> > being an official PMC member.
> >
> > This is just my opinion. @Chris I thinks it's good that you brought up
> > this discussion. I just wanted to point out that we should think
> carefully
> > before introducing another channel. It can become hard to follow-up all
> > discussions on different channels, know where to find and post stuff.
> >
> > February 19, 2020 3:13 AM, "Chris Brody" <ch...@gmail.com> wrote:
> >
> > > I started thinking it might be cool to have Cordova dev discussions in
> > > issues separate from apache/cordova/issues, which I think is the
> > standard,
> > > default place where users raise general issues they encounter and where
> > we
> > > can communicate major things such as breaking changes and deprecated
> > > functionality. My idea would be to have a "cordova-dev" issue
> repository,
> > > as a GitHub equivalent to the dev channel on Slack, lower level than
> > > cordova-contribute and higher level than cordova-coho.
> > >
> > > I completely understand that this would not be super practical given
> both
> > > the impending major release and how we work with Apache infra. But just
> > > food for thought we can chew on in the background. Maybe we could use
> > > something else such as cordova-discuss, cordova-coho, or even
> > > cordova-common?
> > >
> > > Just an idea.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>

Re: Cordova dev discussions on GitHub

[ra...@gmail.com]

I agree with Niklas that we should not increase the number of communication
channels.

Rather, we should try to better communicate the existence and the intended
scopes of the ones we already have. Maybe even get rid of some of them.

Niklas Merz <ni...@apache.org> schrieb am Mi., 19. Feb. 2020, 08:10:

> I understand that it might be difficult for users to find the right place
> to discuss, ask things or get announcements. When I was new I did not
> follow the mailing list for some time, because mailing lists a concept many
> people are not familiar anymore I guess.
>
> I don't think adding another place (especially a second Github repo like
> cordova-discuss) makes this easier. I have always seen cordova-discuss as a
> place where discussion on specific proposals happen. The mailing list is
> the place where decissions and all official stuff like VOTES and
> announcments must take place.
>
> That's why I think we are better off by promoting the lists for developers
> interrested. Maybe add note to every README, explain more on website, add
> to issue template and so on. dev@cordova.apache.org is the official
> channel how Apache works even I fully agree this is not the most modern,
> user-friendly way, but after some time I came to like the list, even before
> being an official PMC member.
>
> This is just my opinion. @Chris I thinks it's good that you brought up
> this discussion. I just wanted to point out that we should think carefully
> before introducing another channel. It can become hard to follow-up all
> discussions on different channels, know where to find and post stuff.
>
> February 19, 2020 3:13 AM, "Chris Brody" <ch...@gmail.com> wrote:
>
> > I started thinking it might be cool to have Cordova dev discussions in
> > issues separate from apache/cordova/issues, which I think is the
> standard,
> > default place where users raise general issues they encounter and where
> we
> > can communicate major things such as breaking changes and deprecated
> > functionality. My idea would be to have a "cordova-dev" issue repository,
> > as a GitHub equivalent to the dev channel on Slack, lower level than
> > cordova-contribute and higher level than cordova-coho.
> >
> > I completely understand that this would not be super practical given both
> > the impending major release and how we work with Apache infra. But just
> > food for thought we can chew on in the background. Maybe we could use
> > something else such as cordova-discuss, cordova-coho, or even
> > cordova-common?
> >
> > Just an idea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

Re: Cordova dev discussions on GitHub

[Niklas Merz <ni...@apache.org>]

I understand that it might be difficult for users to find the right place to discuss, ask things or get announcements. When I was new I did not follow the mailing list for some time, because mailing lists a concept many people are not familiar anymore I guess.

I don't think adding another place (especially a second Github repo like cordova-discuss) makes this easier. I have always seen cordova-discuss as a place where discussion on specific proposals happen. The mailing list is the place where decissions and all official stuff like VOTES and announcments must take place.

That's why I think we are better off by promoting the lists for developers interrested. Maybe add note to every README, explain more on website, add to issue template and so on. dev@cordova.apache.org is the official channel how Apache works even I fully agree this is not the most modern, user-friendly way, but after some time I came to like the list, even before being an official PMC member.

This is just my opinion. @Chris I thinks it's good that you brought up this discussion. I just wanted to point out that we should think carefully before introducing another channel. It can become hard to follow-up all discussions on different channels, know where to find and post stuff.

February 19, 2020 3:13 AM, "Chris Brody" <ch...@gmail.com> wrote:

> I started thinking it might be cool to have Cordova dev discussions in
> issues separate from apache/cordova/issues, which I think is the standard,
> default place where users raise general issues they encounter and where we
> can communicate major things such as breaking changes and deprecated
> functionality. My idea would be to have a "cordova-dev" issue repository,
> as a GitHub equivalent to the dev channel on Slack, lower level than
> cordova-contribute and higher level than cordova-coho.
> 
> I completely understand that this would not be super practical given both
> the impending major release and how we work with Apache infra. But just
> food for thought we can chew on in the background. Maybe we could use
> something else such as cordova-discuss, cordova-coho, or even
> cordova-common?
> 
> Just an idea.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org