All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yunseong Kim <yskelg@gmail.com>
To: Ian Rogers <irogers@google.com>, Namhyung Kim <namhyung@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	linux-perf-users@vger.kernel.org,
	Howard Chu <howardchu95@gmail.com>,
	MichelleJin <shjy180909@gmail.com>,
	Austin Kim <austindh.kim@gmail.com>
Subject: Re: Migrating from perf.wiki.kernel.org to RTD
Date: Sun, 20 Oct 2024 13:49:11 +0900	[thread overview]
Message-ID: <a0626ecb-cc64-4c6a-abf3-76868178234f@gmail.com> (raw)
In-Reply-To: <CAP-5=fXsVXYkncR0rwxXvKp_f5dR40L9_x-qoLxwHXWMiyXh3g@mail.gmail.com>

Hi 

I would like to express my sincere gratitude to everyone for their help in the
official renewal of the perf wiki.

Additionally, the reason I chose to use Markdown is that I wanted to actively
utilize its media features. For example, I wanted to embed videos,
presentation slide or display Mermaid diagrams directly on the page.
I thought these features would be welcomed by users who are new to perf tools.

On 10/19/24 8:47 오전, Ian Rogers wrote:
> On Tue, Oct 15, 2024 at 6:51 PM Namhyung Kim <namhyung@kernel.org> wrote:
>>
>> Hello Konstantin,
>>
>> On Tue, Oct 15, 2024 at 02:25:02PM -0400, Konstantin Ryabitsev wrote:
>>> On Fri, Oct 11, 2024 at 06:39:09PM -0400, Konstantin Ryabitsev wrote:
>>>>> Yunseong created:
>>>>> https://perfwiki.github.io/main/
>>>>> Perhaps the solution here is to make perf.wiki.kernel.org a redirect
>>>>> to https://perfwiki.github.io/main/
>>>
>>> To speed things along, and since the old perf wiki was near-unusable anyway,
>>> I went ahead and set the redirects from perf.wiki.kernel.org to
>>> perfwiki.github.io.
>>>
>>> Please feel free to follow up if we need to revisit this, but things look good
>>> to me with this change.
>>
>> Thanks for your work, it looks good to me too.

I have been continuously improving the content of the documentation, so please
feel free to share any good ideas you may have. :)

> Thanks Konstantin and Yunseong, I think it looks good!
> I think the pages need some improving, there are empty pages and
> things that look abandoned, such as the white paper linked from the
> side bar:
> https://perfwiki.github.io/main/white-paper/
> I pushed a few improvements to the glossary and useful links. It
> should be as easy as creating a pull request for others to contribute,
> so I look forward to this.

Thank you so much Ian, I added per-page editing features to make it more convenient
for people to edit the documentation and submit pull requests.
Link: https://github.com/perfwiki/main/commit/4289b6a6e5c2e53d69a7605d01d0773366a33c52

> Thanks,
> Ian

Best regards,
Yunseong Kim

  reply	other threads:[~2024-10-20  4:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 20:24 Migrating from perf.wiki.kernel.org to RTD Konstantin Ryabitsev
2024-10-11 21:37 ` Ian Rogers
2024-10-11 22:39   ` Konstantin Ryabitsev
2024-10-15 18:25     ` Konstantin Ryabitsev
2024-10-16  1:51       ` Namhyung Kim
2024-10-18 23:47         ` Ian Rogers
2024-10-20  4:49           ` Yunseong Kim [this message]
2024-10-23 17:34             ` Adrian Hunter
2024-10-23 18:17               ` Yunseong Kim
2024-10-23 21:54                 ` Namhyung Kim
2024-10-23 22:33                   ` Arnaldo Carvalho de Melo
2024-10-24  2:20                     ` Ian Rogers
2024-10-24  5:58                     ` Adrian Hunter
2024-10-27 17:08                       ` Yunseong Kim
2024-10-28 16:03                         ` Adrian Hunter
2024-10-28 16:22                         ` Konstantin Ryabitsev
2024-10-28 17:49                           ` Yunseong Kim
2024-10-24  6:07                 ` Adrian Hunter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a0626ecb-cc64-4c6a-abf3-76868178234f@gmail.com \
    --to=yskelg@gmail.com \
    --cc=austindh.kim@gmail.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=shjy180909@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.