linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: damon@lists.linux.dev
Cc: SeongJae Park <sj@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re:Organizing DAMON GitHub repos (damo, damon-tests, and damoos)
Date: Tue, 13 Aug 2024 16:21:58 -0700	[thread overview]
Message-ID: <20240813232158.83903-1-sj@kernel.org> (raw)

Hello DAMON community,


Current Sitaution
-----------------

We are currently maintaining three repos for non-kernel part of DAMON project,
namely 'damo'[1], 'damon-tests'[2], and 'damoos'[3].  Those under 'awslabs'
organization[4] are currently the main repos for contributors who prefer GitHub
workflow.  That is, such contributors are supposed to send GitHub pull requests
and issue reports to those.  We also have a GitHub organization that is
dedicated for DAMON project and neutral to companies, namely 'damonitor'[5].
The 'damonitor' repos are currently working as mirrors of the 'awslabs' repos.

Upcoming Changes
----------------

We decided to use the 'damonitor' repos as the main repos for GitHub workflow
users.  The transition will be made by 2024-09-05.  Until the date, we will
samely support all the repos.  After the date, we may not be able to actively
respond to GitHub pull requests and issue reports that sent to the 'awslabs'
repos.  Also, source code on 'awslabs' repos might not always be up to date,
and could even be diverged.

Requests to You
---------------

So, if you're using the 'awslabs' repos, please move to 'damonitor' repos by
2024-09-05.  Also, after 2024-09-05, please send GitHub pull requests and issue
reports to only the 'damonitor' repos.

If you have any blocker for these, please reach out to the community via issue
trackers of 'damonitor' repos, sj@kernel.org, damon@lists.linux.dev, and/or
linux-mm@kvack.org.

[1] https://github.com/damonitor/damo
[2] https://github.com/damonitor/damon-tests
[3] https://github.com/damonitor/damoos
[4] https://github.com/awslabs
[5] https://github.com/damonitor


Thanks,
SJ


                 reply	other threads:[~2024-08-13 23:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240813232158.83903-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox