> On Mar 9, 2023, at 10:48 AM, Brandon Stewart via webkit-dev
> wrote:
>
> Hello,
>
> Sorry for the delay on the documentation update.
>
> For getting the documentation system online, we were trying to settle on a
> subdomain.
>
> What would people prefer we use as the official
On 09/03/2023 19:48, Brandon Stewart via webkit-dev wrote:
> What would people prefer we use as the official documentation location:
> (1) docs.webkit.org
> (2) developer.webkit.org
> (3) documentation.webkit.org
> (4) Other
+1 for docs.webkit.org (shorter is better)
Hi all,
On Thu, 09 Mar 2023 10:48:27 -0800 Brandon Stewart via webkit-dev
wrote:
> Sorry for the delay on the documentation update.
> For getting the documentation system online, we were trying to settle on a
> subdomain.
Looking forward to have the documentation online ^_^
> What would
: Friday, March 10, 2023 at 6:41 AM
To: Brandon Stewart
Cc: Ling Ho via webkit-dev
Subject: Re: [webkit-dev] WebKit Documentation
On Mar 9, 2023, at 10:48 AM, Brandon Stewart via webkit-dev wrote:
Sorry for the delay on the documentation update.
For getting
Subject: Re: [webkit-dev] WebKit Documentation
On Mar 9, 2023, at 10:48 AM, Brandon Stewart via webkit-dev wrote:
Sorry for the delay on the documentation update.
For getting the documentation system online, we were trying to settle on a subdomain.
What would people
I’d vote for (1) since it’s easy to type!
Thanks,
Ross
From: Ryosuke Niwa via webkit-dev
Reply-To: Ryosuke Niwa
Date: Friday, March 10, 2023 at 6:41 AM
To: Brandon Stewart
Cc: Ling Ho via webkit-dev
Subject: Re: [webkit-dev] WebKit Documentation
On Mar 9, 2023, at 10:48 AM, Brandon
> On Mar 9, 2023, at 10:48 AM, Brandon Stewart via webkit-dev
> wrote:
>
> Sorry for the delay on the documentation update.
>
> For getting the documentation system online, we were trying to settle on a
> subdomain.
>
> What would people prefer we use as the official documentation
Hello,
I got feedback that people would prefer not to add Swift as a requirement for
building the documentation. Since WebKit relies heavily on Python for large
parts of its tooling, I decided to port it over to a popular Python
documentation system MkDocs.
This provides a few benefits over
Hello,
Sorry for the delay on the documentation update.
For getting the documentation system online, we were trying to settle on a
subdomain.
What would people prefer we use as the official documentation location:
(1) docs.webkit.org
(2) developer.webkit.org
(3) documentation.webkit.org
(4)
On 9/20/22 05:28, Brandon Stewart via webkit-dev wrote:
> Hi WebKit Developers,
>
> Documentation is an important part of any open source project, especially for
> a larger project like WebKit. Being able to ramp up during the onboarding
> process, reading up on architectural decisions, and
> On Sep 21, 2022, at 6:50 AM, Michael Catanzaro wrote:
>
> On Tue, Sep 20 2022 at 08:03:12 PM -0700, Ryosuke Niwa via webkit-dev
> wrote:
>> (2) is particularly important because many people who are new to WebKit
>> often don´t know what they don´t know. This is why, for example, memory
On Tue, Sep 20 2022 at 08:03:12 PM -0700, Ryosuke Niwa via webkit-dev
wrote:
(2) is particularly important because many people who are new to
WebKit often don’t know what they don’t know. This is why, for
example, memory management section appears towards the beginning of
the document and the
> On Sep 20, 2022, at 1:52 PM, Brent Fulgham wrote:
>
>> On Sep 20, 2022, at 1:16 AM, Ryosuke Niwa via webkit-dev
>> wrote:
>>
>>> On Sep 19, 2022, at 2:28 PM, Brandon Stewart via webkit-dev
>>> mailto:webkit-dev@lists.webkit.org>> wrote:
>>>
>>> Documentation is an important part of any
> On Sep 20, 2022, at 1:16 AM, Ryosuke Niwa via webkit-dev
> wrote:
>
>
>> On Sep 19, 2022, at 2:28 PM, Brandon Stewart via webkit-dev
>> mailto:webkit-dev@lists.webkit.org>> wrote:
>>
>> Documentation is an important part of any open source project, especially
>> for a larger project
> On Sep 20, 2022, at 6:04 AM, Michael Catanzaro wrote:
>
> On Tue, Sep 20 2022 at 01:16:53 AM -0700, Ryosuke Niwa via webkit-dev
> wrote:
>> I´ve been working on
>> https://github.com/WebKit/WebKit/blob/main/Introduction.md for the past
>> couple of years, and I´d would have preferred to
On Tue, Sep 20 2022 at 01:16:53 AM -0700, Ryosuke Niwa via webkit-dev
wrote:
I’ve been working on
https://github.com/WebKit/WebKit/blob/main/Introduction.md for the
past couple of years, and I’d would have preferred to have a
collaboration rather than a competition here.
This
> Why not double-down on the GitHub wiki? It's very easy to learn to use,
> and there are edit buttons everywhere so there is no "distance" between
> the docs and the ability to edit them. The easier it is to edit docs,
> the better we'll do at keeping them up to date.
>
> I like Markdown, and
> On Sep 19, 2022, at 2:58 PM, Michael Catanzaro via webkit-dev
> wrote:
>
> Why not double-down on the GitHub wiki? It's very easy to learn to use, and
> there are edit buttons everywhere so there is no "distance" between the docs
> and the ability to edit them. The easier it is to edit
> On Sep 19, 2022, at 2:28 PM, Brandon Stewart via webkit-dev
> wrote:
>
> Documentation is an important part of any open source project, especially for
> a larger project like WebKit. Being able to ramp up during the onboarding
> process, reading up on architectural decisions, and learning
> On Sep 19, 2022, at 4:48 PM, Fujii Hironori via webkit-dev
> wrote:
>
> Why not double-down on WebKit Git repository?
> The closer the document is to the source code, the easier to keep them
> up-to-date.
> We can modify both the source code and the document in a single commit
> through
On 9/19/22 4:48 PM, Fujii Hironori via webkit-dev wrote:
Why not double-down on WebKit Git repository?
The closer the document is to the source code, the easier to keep them
up-to-date.
We can modify both the source code and the document in a single commit
through our review process.
Do
Why not double-down on WebKit Git repository?
The closer the document is to the source code, the easier to keep them
up-to-date.
We can modify both the source code and the document in a single commit
through our review process.
Do you plan to shutdown https://trac.webkit.org/wiki ?
Why not double-down on the GitHub wiki? It's very easy to learn to use,
and there are edit buttons everywhere so there is no "distance" between
the docs and the ability to edit them. The easier it is to edit docs,
the better we'll do at keeping them up to date.
I like Markdown, and am OK
Hi WebKit Developers,
Documentation is an important part of any open source project, especially for a
larger project like WebKit. Being able to ramp up during the onboarding
process, reading up on architectural decisions, and learning how to perform
common procedures are all features the
-dev] webkit documentation
I have done this, but it was rejected:
https://bugs.webkit.org/show_bug.cgi?id=20125
On Mon, Jul 21, 2008 at 3:22 PM, David Kilzer [EMAIL PROTECTED]
wrote:
We update the web site through patches. Just file a bug on
bugs.webkit.org and attach a patch
. If
you need help on how to create a patch or checkout the source for the web
site, please ask.
Dave
From: Jack Wootton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: webkit-dev@lists.webkit.org
Sent: Friday, November 21, 2008 8:25:32 AM
Subject: Re: [webkit-dev
From: Jack Wootton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: webkit-dev@lists.webkit.org
Sent: Friday, November 21, 2008 8:25:32 AM
Subject: Re: [webkit-dev] webkit documentation
I have done this, but it was rejected:
https://bugs.webkit.org/show_bug.cgi?id=20125
On Mon, Jul 21
I have done this, but it was rejected:
https://bugs.webkit.org/show_bug.cgi?id=20125
On Mon, Jul 21, 2008 at 3:22 PM, David Kilzer [EMAIL PROTECTED] wrote:
We update the web site through patches. Just file a bug on bugs.webkit.org
and attach a patch with ChangeLog for review!
Dave
On
: Jack Wootton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: webkit-dev@lists.webkit.org
Sent: Friday, November 21, 2008 8:25:32 AM
Subject: Re: [webkit-dev] webkit documentation
I have done this, but it was rejected:
https://bugs.webkit.org/show_bug.cgi?id=20125
On Mon, Jul 21, 2008 at 3:22 PM
Hi all,
I am mainly interested in S60 WebKit, however due to the project
seeming to be in complete disarray to those not working for Nokia,
I've decided to focus my efforts on the WebKit branch from which S60
WebKit started. I understand this to be Tiger 10.4.7 (it was one of
the few pieces of
We update the web site through patches. Just file a bug on bugs.webkit.org and
attach a patch with ChangeLog for review!
Dave
On Mon, 7/21/08, Jack Wootton [EMAIL PROTECTED] wrote:
OK, it seems this is a good place to start
31 matches
Mail list logo