On Thu, Feb 27, 2020 at 6:24 PM Maciej Stachowiak wrote:
>
> I think we should have some structure, not just freeform emails. We can
> start with a simple template, but there’s some info that folks almost
> always want, so it’s easier if it’s included in the first place, rather
> than needing
I think we should have some structure, not just freeform emails. We can start
with a simple template, but there’s some info that folks almost always want, so
it’s easier if it’s included in the first place, rather than needing
predictable follow-up questions
I also like having a title
Hi Ryosuke, just replying quickly to two points:
On 27/02/2020 08:08, Ryosuke Niwa wrote:
>
> Or do you mean that we enabling new feature / behavior by default? If
> so, then making such an announcement on webkit-dev requirement for Web
> facing feature / behavior change makes sense to me. But we
Thanks for starting this discussion.
On Wed, Feb 26, 2020 at 10:33 PM Frédéric Wang wrote:
>
> The idea of an "intent to" process has been raised several times in the
> past (e.g. in our 2020 goals [1]) and some people already use it
> informally, but it does not seem that we have any agreement
Hi,
The idea of an "intent to" process has been raised several times in the
past(e.g. in our 2020 goals [1])and some people already use it
informally, but it does not seem that we have any agreement right now.
Such a process would help to coordinate changes internally (between port
maintainers
5 matches
Mail list logo