PR Load Solutions
in [Ports]
|
From: Jesse Smith on 10 Jul 2010 09:46 I'm a bit new to FreeBSD Ports, but I agree that there is quite a backlog. Everyone seems to be working hard and yet the work keeps piling up. Though I don't have much experience, I would like to learn (and help). At the moment I'm the upstream maintainer for four projects (two of which are established ports and two are pending PRs). I would be happy to take over maintaining those to ease the load. Veteran maintainers might not like the idea of new blood having commit access, which is understandable, but I'd like to help out. -Jesse _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Mark Linimon on 11 Jul 2010 00:55 On Sat, Jul 10, 2010 at 06:46:36AM -0700, Jesse Smith wrote: >I would be happy to take over maintaining those to ease the load. OK, we always welcome help :-) If you need help submitting PRs, let us know. > Veteran maintainers might not like the idea of new blood having commit > access, which is understandable, but I'd like to help out. The issue isn't about "not liking" -- it's more of a question of trust. We're asking our users to trust that the ports come from known places and have been through at least some kind of QA. To do that, we've set up a minimum threshhold to get commit access (a track record with filed PRs; some demonstrated ability to work with user questions; and so forth). It's actually not that difficult, in general, to wind up with a ports commit bit. mcl _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Jesse Smith on 11 Jul 2010 07:39 ----Original Message----- From: Mark Linimon <linimon(a)lonesome.com> To: Jesse Smith <jessefrgsmith(a)yahoo.ca> Cc: freebsd-ports(a)freebsd.org Subject: Re: PR Load Solutions Date: Sat, 10 Jul 2010 23:55:32 -0500 On Sat, Jul 10, 2010 at 06:46:36AM -0700, Jesse Smith wrote: >I would be happy to take over maintaining those to ease the load. OK, we always welcome help :-) If you need help submitting PRs, let us know. > Veteran maintainers might not like the idea of new blood having commit > access, which is understandable, but I'd like to help out. The issue isn't about "not liking" -- it's more of a question of trust. We're asking our users to trust that the ports come from known places and have been through at least some kind of QA. To do that, we've set up a minimum threshhold to get commit access (a track record with filed PRs; some demonstrated ability to work with user questions; and so forth). It's actually not that difficult, in general, to wind up with a ports commit bit. mcl Perhaps I should have phrased that differently. I realize there needs to be a level of trust. Having come in recently to the world of Ports, it looks to me like there may be a small catch-22 involved. That is, people gain trust by submitting (and getting approved) PRs, but the existing maintainers seem to be too busy to keep up with the PRs coming in. Which means it takes a long time to earn that level of trust. I'm not saying I have a solution. Just that I'd like to help out as much as the veteran maintainers are willing. On a related note, what about trying to actively attract upstream maintainers to help out with the ports of their projects? I didn't even know until recently that two of my projects had been added to the Ports tree. Once I found out, I wanted to help keep those ports maintained and up to date. Maybe other up-stream developers could be recruited to babysit their ports? - Jesse _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Matthias Andree" on 12 Jul 2010 07:41 Jesse Smith wrote on 2010-07-11: > I'm not saying I have a solution. Just that I'd like to help out as much > as the veteran maintainers are willing. There's also the burden of testing PRs, we "veteran committers" (I still have two mentors myself) need to make sure the port builds and installs cleanly on the supported FreeBSD releases. For that purpose, we set up so-called "tinderboxes" which builds ports in a controlled environment. If port maintainers can do that and provide the logs on a web-/fileserver and include the Tinderbox log URL in their PR, that may help a bit. > On a related note, what about trying to actively attract upstream > maintainers to help out with the ports of their projects? I didn't even > know until recently that two of my projects had been added to the Ports > tree. Once I found out, I wanted to help keep those ports maintained and > up to date. Maybe other up-stream developers could be recruited to > babysit their ports? This has some drawbacks, especially for smaller upstream projects, so this should be decided case by case: - if I am doing most of the upstream work, there are fewer eyes to look at the FreeBSD port; - upstream maintainers may in some cases be less familiar with FreeBSD, they may not even use it. One such example is sysutils/e2fsprogs, another security/openvpn; just from my collection. - upstream maintainers may be very good at programming, project management, whatever; FreeBSD port maintainers always cannot be too alien to systems administration. - it usually pays off if the maintainer is actively using FreeBSD and the port he is maintaining. This is often not the case, otherwise the upstream maintainer already is the port maintainer :) If this is done in the wrong way, it will backfire and actually raise support burden because the load of getting the actual "porting" part (FreeBSD adjustments) done propagates to committers... Sure there are cases when the upstream maintainer is the port maintainer (f.i. news/leafnode, mail/bogofilter*), but I'm not sure this could fly as a general concept. Note this is a personal opinion, not necessarily consensus. I'm /not/ posting on behalf of FreeBSD here. Best regards Matthias -- Matthias 'mandree@' Andree _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Jesse Smith on 12 Jul 2010 09:24 -----Original Message----- From: freebsd-ports-request(a)freebsd.org Reply-to: freebsd-ports(a)freebsd.org To: freebsd-ports(a)freebsd.org Subject: freebsd-ports Digest, Vol 373, Issue 1 Date: Mon, 12 Jul 2010 12:00:25 +0000 (UTC) > On a related note, what about trying to actively attract upstream > maintainers to help out with the ports of their projects? I didn't even > know until recently that two of my projects had been added to the Ports > tree. Once I found out, I wanted to help keep those ports maintained and > up to date. Maybe other up-stream developers could be recruited to > babysit their ports? This has some drawbacks, especially for smaller upstream projects, so this should be decided case by case: - if I am doing most of the upstream work, there are fewer eyes to look at the FreeBSD port; - upstream maintainers may in some cases be less familiar with FreeBSD, they may not even use it. One such example is sysutils/e2fsprogs, another security/openvpn; just from my collection. - upstream maintainers may be very good at programming, project management, whatever; FreeBSD port maintainers always cannot be too alien to systems administration. - it usually pays off if the maintainer is actively using FreeBSD and the port he is maintaining. This is often not the case, otherwise the upstream maintainer already is the port maintainer :) If this is done in the wrong way, it will backfire and actually raise support burden because the load of getting the actual "porting" part (FreeBSD adjustments) done propagates to committers... Sure there are cases when the upstream maintainer is the port maintainer (f.i. news/leafnode, mail/bogofilter*), but I'm not sure this could fly as a general concept. Note this is a personal opinion, not necessarily consensus. I'm /not/ posting on behalf of FreeBSD here. Best regards Matthias -- Matthias 'mandree@' Andree I see where you're coming from. Admittedly I came to the party only recently. But I've found that, in trying to get my projects into Ports, I'm finding things in my code that could be more cross-platform friendly. So it's been a positive learning experience for me. I'm hoping other upstream developers can be encouraged to help out with their ports. Especially ports that have already been committed and just need minor adjustments. You mentioned the tinderbox. Is that a clean build environment in a jail/chroot? I use something like that to build PBI modules on PC-BSD, but I haven't tried using such as tool for Ports. - Jesse _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Next
|
Last
Pages: 1 2 Prev: devel/icu4 update -- chase LIB_DEPENDS Next: Simple Hack To Get $2000 To Your PayPal Account |