Hello WebKit Contributors,
This year, Apple would like to push WebKit’s source code management off of
Subversion and onto git. Our rationale for this is the rest of the industry has
settled on git as their source code management solution. We’re also interested
in moving to a hosted Git solutio
This is great!
On Fri, 2020-10-02 at 09:43 -0700, Jonathan Bedard wrote:
> Hello WebKit Contributors,
>
> This year, Apple would like to push WebKit’s source code management
> off of Subversion and onto git. Our rationale for this is the rest of
> the industry has settled on git as their source c
On Fri, Oct 2, 2020 at 6:36 pm, Philippe Normand
wrote:
Would you also consider preventing merge commits in order to keep a
clean mainline branch?
Big +1 to blocking merge commits. Merge commits in a huge project like
WebKit would make commit archaeology very frustrating. (I assume this
is i
Hi Jonathan,
As a contributor, I hear this change positively and I'm looking
forward to transition to a new process.
I have some questions and feelings:
1. Will we continue to use https://trac.webkit.org/wiki after moving
to something to host the Git repository?
This is just my curiosity.
2.
On Fri, Oct 2, 2020 at 11:00 AM Michael Catanzaro wrote:
>
> On Fri, Oct 2, 2020 at 6:36 pm, Philippe Normand
> wrote:
> > Would you also consider preventing merge commits in order to keep a
> > clean mainline branch?
>
> Big +1 to blocking merge commits. Merge commits in a huge project like
> We
On Fri, Oct 2, 2020 at 11:51 am, Ryosuke Niwa wrote:
Since Igalia has a lot
more experience working with other open source projects, do you have
some suggestions in how to approach that?
Sorry for a long-ish mail. I didn't mean for this to turn into an
essay. Too late. :P
I actually moved t
> On Oct 2, 2020, at 11:47 AM, Tetsuharu OHZEKI
> wrote:
>
> Hi Jonathan,
>
> As a contributor, I hear this change positively and I'm looking
> forward to transition to a new process.
>
> I have some questions and feelings:
>
> 1. Will we continue to use https://trac.webkit.org/wiki after m
On Fri, Oct 2, 2020 at 09:43, Jonathan Bedard wrote:
The biggest blocker we are aware of is managing security bugs, since
the security advisory system used by GitHub is essentially the
opposite of how WebKit security bugs work. Moving to GitHub Issues,
if it happens, will be the last part of t
On Fri, Oct 2, 2020 at 13:48, Ken Russell wrote:
Github's code review UI has a couple of feature gaps in my opinion.
It's difficult to look at earlier versions of the pull request, in
particular to verify that issues found during code review have been
fixed. I remember it also being difficult
On Fri, Oct 2, 2020 at 5:06 PM Michael Catanzaro wrote:
>
> On Fri, Oct 2, 2020 at 13:48, Ken Russell wrote:
> > Github's code review UI has a couple of feature gaps in my opinion.
> > It's difficult to look at earlier versions of the pull request, in
> > particular to verify that issues found du
I feel like I should write longer replies but here we go.
On Fri, Oct 2, 2020 at 12:53 PM Michael Catanzaro wrote:
>
> On Fri, Oct 2, 2020 at 11:51 am, Ryosuke Niwa wrote:
> > Since Igalia has a lot
> > more experience working with other open source projects, do you have
> > some suggestions in
11 matches
Mail list logo
