I'd rather it stay on GitHub; I think it makes more sense _for this project_. First of all, it already is on GitHub, so moving it is likely more disruptive to the workflow
Secondly, it already has CI setup through GitHub actions, which we would need to spend effort to replicate elsewhere. Thirdly, I've always wanted this to be published as a python module on PyPi to make it easier for users to keep up to date; GitHub and PyPi have streamlined this process to the point that it's surprisingly trivial. Finally, if we are worried about the maintenance, it's pretty easy to delegate the maintenance of the repo to the people who are volunteering to maintain it here, which is likely what would happen if it went somewhere other than the Yocto GitHub account anyway. On Fri, Jan 26, 2024 at 6:33 AM Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Thu, 2024-01-25 at 17:58 -0500, Philip Balister wrote: > > On 1/25/24 11:58, Trevor Woerner wrote: > > > On Wed 2024-01-24 @ 03:16:04 PM, Tim Orling wrote: > > > > On Wed, Jan 24, 2024 at 2:02 PM Joshua Watt <jpewhac...@gmail.com> > > > > wrote: > > > > > > > > > On Wed, Jan 24, 2024 at 10:59 AM Trevor Woerner <twoer...@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. > > > > > > > Michael, if you need any support from the Yocto Project advisory board > > to move bmaptool to the yoctoproject github, I can help with that. > > This falls to the YP TSC, not the board. > > I have no problem with the project hosting that git repo and > maintaining it. I do worry quite a bit about moving it to github. Would > moiving it to git.yoctoproject.org be ok? > > The reason I say this is that I already get a lot of comments/randon > questions against commits in github repos. I feel quite sad that people > are effectively talking into a void. If we start supporting different > workflows for different repos under yoctoproject, we're going to really > confuse people. > > You might argue that we should host issues for bmap-tools. The > challenge is that we have bugzilla, we have a triage team and we have a > load of processes. Telling those people to just cover both would likely > result in a flat refusal. > > Cheers, > > Richard > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62299): https://lists.yoctoproject.org/g/yocto/message/62299 Mute This Topic: https://lists.yoctoproject.org/mt/103930262/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
