lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20240813232158.83903-1-sj@kernel.org>
Date: Tue, 13 Aug 2024 16:21:58 -0700
From: SeongJae Park <sj@...nel.org>
To: damon@...ts.linux.dev
Cc: SeongJae Park <sj@...nel.org>,
	linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re:Organizing DAMON GitHub repos (damo, damon-tests, and damoos)

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@...nel.org, damon@...ts.linux.dev, and/or
linux-mm@...ck.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ