On 7/24/23 09:37, Richard Purdie wrote:
On Mon, 2023-07-24 at 09:23 -0400, Alex Stewart wrote:
Thanks for the feedback. Does anyone on the list know who the authority
would be to approve (or deny) this move would be? I can make a
recommendation as the repo maintainer, but I'm not sure I have the
*ownership* to change the canon. Do I need to take this to the Yocto
steering committee?
I suspect the Yocto Project TSC is the decision making "authority" for
this although it obviously needs to be done in conjunction with the
maintainer.

Sounds like I should plan to stop by the next TSC meeting then.

I don't see any details about when/where the next meeting is on either the latest project status email, or the wiki (unless I'm just blind). Is there an invite for that meeting series that I can subscribe to?


On 7/23/23 07:55, Alexander Kanavin wrote:
May I suggest trying out sourcehut as the hosting provider for opkg?

https://sourcehut.org

It has all the web niceties, but it's also been built from the ground
up to integrate with the email workflow, unlike any of the 'big' SCM
providers, so if that works out well for opkg, we could consider using
it elsewhere (yes, the core yocto repos :)
That's an idea. I don't think I have enough knowledge about how the
existing mailing-list based workflows are designed to do an immediate
eval of sourcehut. But I can test it out as an option, if I can get some
traction on the migration.
Moving the list to groups.io where the rest of the Yocto Project/OE
lists are is straight forward and easy to do, if you request that we
can just make that happen.

As has been mentioned, "we" have mixed feelings on github/gitlab. There
are some layers that use those workflows and our policy is that it
needs to be documented in the project's README, whatever the submission
process is. That decision really comes down to the layer maintainer.

sourcehut does sound interesting. Looks like you can run your own
instance or their servers, the latter eventually encouraging you to
support them (which is fair enough). Yocto Project probably can't use
their servers without some kind of support in place. I really don't
know enough about it to know how much it makes sense. It is described
as "alpha" which probably isn't ready for us to depend on too. I am
curious though...

Cheers,

Richard



--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

[email protected]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1721): 
https://lists.openembedded.org/g/openembedded-architecture/message/1721
Mute This Topic: https://lists.openembedded.org/mt/100278606/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to