Le mer. 12 févr. 2025 à 10:51, Richard Purdie < [email protected]> a écrit :
> On Wed, 2025-02-12 at 09:08 +0100, Yoann Congal wrote: > > Le mer. 12 févr. 2025 à 00:36, Richard Purdie via lists.yoctoproject.org > <[email protected]> a écrit : > > > The repositories were added to try and share bandwidth costs, give > > > people easier mirrors and various other justifications. I warned > > > strongly about the pull request problems at the time, I was told it > > > would get handled and people would help and I was over reacting. Some > > > of the people who made those offers aren't active with the project any > > > more, other things just drifted with time. At one point I ended up > > > having to add those mirrors to my own push scripts and maintain them > > > because nobody else was willing and we had complaints they were not up > > > to date. > > > > > > You used to be able to disable pull requests for six month periods, it > > > looks like you can no longer do that and it was a pain having to try > > > and remember anyway. > > > > > > The bandwidth/mirror/backup benefits are valid and I'd be reluctant to > > > delete them as some people can only discover things through github too. > > > Google indexing doesn't work well with our own server. > > > > > > So I guess I made my own peace with their existence. I know touching > > > them will make it look more like a condoned submission method but I > > > really don't see many good options here. Removing them is a simple easy > > > option but life sometimes isn't easy/simple. > > > > We can try things to push users out of github : > > * Leaving a fake PR at the top of the list with a title along the > > line of "Please don't open a PR but instead go to <contributing guide > > link>" > > * using the PR template (the text pre-filled for the new PR > > description) to convey the same info > > * A bot that automatically answer the PRs with a comment with the > > same idea (the bot could also close the PR but that might be a bit > > harsh) > > If anyone has experience of setting this up I'd welcome help. The > things I did learn briefly looking yesterday are that: > > * the template requires putting .git* files in the repo which is a bit > annoying > > * there is a way to do it in a separate repo but that would apply to > all repos, not just oe-core and bitbake, at least from what I read > > * our type of account may or may not have some of the features needed > for bots and so on > > So I'm not against any of these but it could do with someone with some > experience. I can probably learn what is needed but I have time > challenges like everyone else. > > There will probably be a need to maintain any bot going forward too. > I volunteer to setup a PoC in my repos to see what is possible given those constraints. I'm more experienced in Gitlab than GitHub but I should be able to translate. Obviously, if anyone has direct experience on that, don't hesitate to speak up. What kind of account does the yocto project has on GitHub? Cheers, > > Richard > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64782): https://lists.yoctoproject.org/g/yocto/message/64782 Mute This Topic: https://lists.yoctoproject.org/mt/111128176/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
