Hi Samo, I don't have the bandwidth to do detail work on git-subrepo at the moment, please open an RFS bug for this upload.
I could just add you to the DM ACL so you can do your own uploads, but I'm not sure you're ready for that. Instead I have invited you to the debian/git-subrepo now so you can push straight there and use it for sponsor collaboration (some prefer source packages on mentors tho so don't presume that use). My hope/intention is that working with another sponsor will also be a good thing for your Debian career. (I think I asked before if becoming a DD eventually is something that interests you but I don't remember if I got an answer so I'm assuming "yes") Remember *not* to create tags in the debian repo. Your sponsor will do it or ask you to. On Sat, Dec 07, 2024 at 11:50:02AM +0100, Samo Pogačnik wrote: > I pushed a snapshot change, where i reordered, redesigned a bit and > extended the initial patch set, which is now linked to a new upstream PR > - https://github.com/ingydotnet/git-subrepo/pull/639 - (i accidentally > closed the original one). Those changes should better integrate with > upstream test environments i believe, however still not perfect. You should be able to re-open PRs no need to repost. This can come across as spammy. While we're on the topic of competence signaling: I'm also concerned that you're not using GH markdown properly (`code blocks`, #issue references, - itemization, etc). This can be offputting to upstreams. Your writing could also use some refinement you may want to try using some tools to clean it up or just spending more time on it. > Then i added two additional patches for an additional upstream PR - > https://github.com/ingydotnet/git-subrepo/pull/640 - regarding ff=only git > settings causing git-subrepo to fail. The first patch introduces the problem > and > the other hopefully solves it. What's the `$(shell uname) patch for? I don't think upstream will want to take that without justification. Otherwise it looks good modulo upstream preference for whether the test environment should be fully defined or not. > p.s. So far, unfortunately no reaction from upstream regarding those two PRs. It's tricky when that happens. This is where the social part of FLOSS work comes to the foreground. One approach is to try finding ingy in some place other than GH. They list a matrix ID on their profile so perhaps that's a way to get in touch. Please keep in mind you're not entitled to their help or attention. Your goal should be to make a personal connection based on your mutual interest in git-subrepo (or anything else really), not to pressure them to work on it. What tends to work much better than pressure is *positive feedback*. We get so little of it in FLOSS, a simple "thanks for this super useful $thing" can go a long way. You may also choose to highlight that that as Debian maintainer you're enabling their work to be (more) widely adopted and be even more useful. --Daniel
signature.asc
Description: PGP signature
