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?
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.
Alex
On Sun, 23 Jul 2023 at 06:15, Khem Raj <[email protected]> wrote:
On Fri, Jul 21, 2023 at 8:24 AM Alex Stewart <[email protected]> wrote:
I suppose I'll open this thread under -architecture; since this is
really a policy decision.
Hey List,
At the moment, our fork of the opkg project is using a legacy Google
Group as its primary mailing list [1].
Google Groups has been abandoned by Google for years. It is not being
updated and the only projects which exist there have been grandfathered
in. Subscribing to the list is difficult. You either have to link your
Google account - which most posters aren't going to want to do. Or you
must send an email to an undocumented plus-extension for the list. And
the whole process is generally obsolescent and off-putting, even for
experienced devs.
So I'd like to move opkg-development discussion somewhere else. At a
minimum, it seems reasonable to move discussion to one of the OE lists,
since the vast majority of contributors are on that list as well. But I
can also see it being confusing that we are mixing discussions between
the opkg project itself, and the opkg/OE recipes.
How are other Yocto subprojects like this handled?
Alternatively, I think it would make sense to move the project to a
modern SCM implementation - like gitlab - where we can consolidate PRs,
issues, and the codebase. As much as I'm comfortable using the
email+gitolite+bugzilla workflow, it doesn't make the project very
appealing to the newer developer generations.
And I have to admit that my corporate IT department makes it as annoying
as possible to use mailing lists: changing subject lines, changing urls,
writing into the email body, blocking and swallowing ML emails as
spam... While that's a me-problem, it is also an increasingly-prevalent
us-problem for those who are contributing from corps.
Do we have a gitlab solution within the Yocto project? Or has there been
any discussion on this topic among the Yocto steering mindshare?
Currently yocto project uses email workflow for patches and there are no
plans in works to use something else as far as I know. It uses groups.io to
host mailing lists and thats what most subprojects use. There is also a
patchwork instance which monitors these mailing lists and some projects
do use that [1]. Some projects e.g. meta-raspberrypi uses git.yoctoproject.org
and github.com to host the repository and uses github workflow for development
We have tried to do gitlab for OE projects [2] but it did not fly much.
I suppose there is some history there that I'm not aware of. What was
the reason that the gitlab instances didn't gain traction? Was there
anything specific?
[1] https://patchwork.yoctoproject.org/
[2] https://gitlab.com/openembedded
[1] https://groups.google.com/g/opkg-devel
Thanks,
--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)
[email protected]
--
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 (#1719):
https://lists.openembedded.org/g/openembedded-architecture/message/1719
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]]
-=-=-=-=-=-=-=-=-=-=-=-
