From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@lists.yoctoproject.org, dedekind1@gmail.com
Subject: Re: [yocto] bmap-tools repository closes
Date: Fri, 09 Feb 2024 18:08:17 +0000 [thread overview]
Message-ID: <e6cefe4b20af2ef03793fd096f01482f9f69cf67.camel@linuxfoundation.org> (raw)
In-Reply-To: <5e58c6719d797be31ece8149535531036ae18a47.camel@gmail.com>
On Wed, 2024-01-24 at 14:01 +0200, Artem Bityutskiy wrote:
> Hello Yocto community,
>
> some parts of Yocto software (MIC?) use the 'bmap-tools' project to speed up
> image flashing.
>
> https://github.com/intel/bmap-tools
>
> I am the original author of the software, and I created it many years ago to
> speed up Tizen image flashing, and it helped a lot back at the time. It was also
> my first python project, so it was a lot of fun learning python while also
> creating something useful.
>
> But after that, I stopped working on it and it was mostly Yocto folks who
> contributed changes here and there. I never had time and enough motivation to
> maintain the project further, but other folks helped.
>
> Simon McVitte was active maintainer, but he said he does not have time for it
> now as well.
>
> The project is in "github.com/intel" space, and Intel is going to archive the
> git repository soon. This basically means the repository becomes read-only soon.
>
> Would Yocto community have enthusiasts to fork it and maintain the fork?
Thanks for reaching out to us, it is good to do this proactively rather
than seeing it sit unmaintained. There is interest within the Yocto
Project community to take this on so we'd like to take up that offer
thanks!
There are a few details we're working through but I did want to say
this publicly and also to say thanks for reaching out.
Cheers,
Richard
next prev parent reply other threads:[~2024-02-09 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 12:01 bmap-tools repository closes Artem Bityutskiy
2024-01-24 17:59 ` [yocto] " Trevor Woerner
2024-01-24 22:01 ` Joshua Watt
2024-01-24 23:16 ` Tim Orling
2024-01-25 16:58 ` Trevor Woerner
2024-01-25 22:58 ` Philip Balister
2024-01-26 13:33 ` Richard Purdie
2024-01-26 15:26 ` Joshua Watt
2024-01-26 15:37 ` Richard Purdie
2024-01-26 15:28 ` Trevor Woerner
2024-02-09 18:08 ` Richard Purdie [this message]
2024-02-12 6:45 ` Artem Bityutskiy
2024-02-12 22:53 ` Joshua Watt
2024-02-13 22:16 ` Michael Halstead
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=e6cefe4b20af2ef03793fd096f01482f9f69cf67.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dedekind1@gmail.com \
--cc=yocto@lists.yoctoproject.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