From: Trevor Woerner <twoerner@gmail.com>
To: Tim Orling <ticotimo@gmail.com>
Cc: JPEWhacker@gmail.com, yocto@lists.yoctoproject.org, dedekind1@gmail.com
Subject: Re: [yocto] bmap-tools repository closes
Date: Thu, 25 Jan 2024 11:58:53 -0500 [thread overview]
Message-ID: <20240125165853.GA16381@localhost> (raw)
In-Reply-To: <CANx9H-BPNxygNezUyDeHf3GseETi0N9n8D=cwdDrZWWK1W0jBw@mail.gmail.com>
On Wed 2024-01-24 @ 03:16:04 PM, Tim Orling wrote:
> On Wed, Jan 24, 2024 at 2:02 PM Joshua Watt <JPEWhacker@gmail.com> wrote:
>
> > On Wed, Jan 24, 2024 at 10:59 AM Trevor Woerner <twoerner@gmail.com>
> > wrote:
> > >
> > > Hi Artem,
> > >
> > > On Wed 2024-01-24 @ 02:01:08 PM, 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.
> > >
> > > Thank you for your contribution, this tool has been quite useful for me
> > over
> > > the years.
> > >
> > > > 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.
> > >
> > > Thank you for this update and letting us know ahead of time.
> > >
> > > > Would Yocto community have enthusiasts to fork it and maintain the
> > fork?
> > >
> > > Yes, I'll volunteer to maintain it going forward. My non-stackoverflow
> > python
> > > knowledge is minimal, but I recently dug deeply into bmaptools to solve
> > an
> > > issue I had noticed. So I'm confident enough to take it over if nobody
> > else is
> > > interested.
> >
> > Ya, it's an awesome tool and a huge time saver for us, so can also
> > help maintain it
> >
>
> We can probably move it under the https://github.com/yoctoproject umbrella?
> I can also help maintain this tremendous time saver.
https://github.com/yoctoproject and the github workflow is fine with me as
long as I can commit to it from my @gmail identity.
@tim do you want to import the current repository from intel? Then we can
update the recipe in oe-core and go from there.
next prev parent reply other threads:[~2024-01-25 16:59 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 [this message]
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
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=20240125165853.GA16381@localhost \
--to=twoerner@gmail.com \
--cc=JPEWhacker@gmail.com \
--cc=dedekind1@gmail.com \
--cc=ticotimo@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