From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: yocto@lists.yoctoproject.org, philip@balister.org,
twoerner@gmail.com, Tim Orling <ticotimo@gmail.com>,
Michael Halstead <michael@yoctoproject.org>,
dedekind1@gmail.com
Subject: Re: [yocto] bmap-tools repository closes
Date: Fri, 26 Jan 2024 15:37:32 +0000 [thread overview]
Message-ID: <138469ee4a323e906c16516c8b2fd438cd37b72b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJdd5GZvPZDZmL5WS53j=hAp_hJAUAK4qT+ykPTMc_eLfj-bHA@mail.gmail.com>
On Fri, 2024-01-26 at 08:26 -0700, Joshua Watt wrote:
> 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.
I hadn't realised there was CI in there, that does change things quite
a bit.
For bmap-tools it therefore makes sense.
From the wider Yocto Project perspective, this will cause problems as
you can't just enable some bits of github on a per repo basis very
easily but disable them for others. Obviously those are issues others
will have to worry about, probably Michael and I.
I do feel it makes sense to join bmap-tools to the wider Yocto Project
umbrella of projects rather than letting it sit in isolation on a
personal account.
Cheers,
Richard
next prev parent reply other threads:[~2024-01-26 15:37 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 [this message]
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=138469ee4a323e906c16516c8b2fd438cd37b72b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dedekind1@gmail.com \
--cc=jpewhacker@gmail.com \
--cc=michael@yoctoproject.org \
--cc=philip@balister.org \
--cc=ticotimo@gmail.com \
--cc=twoerner@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