Re: MAINTAINER lines and Real Names
they have the much more pleasant and personal style; I have prepared a patch ... As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. Sounds good. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
I see the proposal less about *FreeBSD Ports Teams* and more about *Non-FreeBSD* groups. We can only blame ourselves for having non-responsive teams, or having *mailing lists* be maintainers. I see the benefit here more about allowing us to commit PR from any of the listed addresses, as well as allow end-users to have more *people* to contact. I'd welcome a patch to allow multiple maintainers. It would be an enabling, Doesn't imply requirement to have multiple for all ports. Individual ports maintainers users might feel different numbers of Maintainers were appropriate to different ports, a luxury to choose that FreeBSD hasn't offered till now. Could give faster response when prime=first maintainer is on holiday, or snowed under. As to list names used for Maintainer, That seems to remain a seperate policy not enabling technology issue, (assuming there's no auto detect on eg known list names). Though as some ports have mail list dedicated to one port, some human maintainers may want to add a list name as eg a secondary Maintainer, some ports just with a list might get a human appended. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
MAINTAINER lines and Real Names
Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees cr...@freebsd.org How would people feel about supporting that in our ports tree? I have prepared a patch that keeps the old behaviour for make maintainer, and while I did it I couldn't help but notice that the code for make readmes actually supports such a style. http://www.bayofrum.net/~crees/patches/bsd-port-mk-maintainer-not-just-email.diff As well as being nice to see, it would also mean that addport could use the data in the MAINTAINER line to get real names back into Submitted by: commit logs (currently it only has maintainer email). As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. Chris [1] http://www.openbsd.org/cgi-bin/cvsweb/ports/shells/bash/Makefile?rev=1.73 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On 9/11/2012 3:59 PM, Chris Rees wrote: Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees cr...@freebsd.org I like this! How would people feel about supporting that in our ports tree? I have prepared a patch that keeps the old behaviour for make maintainer, and while I did it I couldn't help but notice that the code for make readmes actually supports such a style. http://www.bayofrum.net/~crees/patches/bsd-port-mk-maintainer-not-just-email.diff As well as being nice to see, it would also mean that addport could use the data in the MAINTAINER line to get real names back into Submitted by: commit logs (currently it only has maintainer email). As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. This would definitely be a huge plus. Chris [1] http://www.openbsd.org/cgi-bin/cvsweb/ports/shells/bash/Makefile?rev=1.73 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On 09/11/2012 03:59 PM, Chris Rees wrote: Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees cr...@freebsd.org I think it is a good idea. (But I thought I suggested the same idea a few days ago!) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On 11 September 2012 22:14, Stephen Montgomery-Smith step...@missouri.edu wrote: On 09/11/2012 03:59 PM, Chris Rees wrote: Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees cr...@freebsd.org I think it is a good idea. (But I thought I suggested the same idea a few days ago!) Haha, so you did, and I remember reading it too. Sorry! Now there's a patch that could make it reality :P Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On Tue, Sep 11, 2012 at 10:59 PM, Chris Rees utis...@gmail.com wrote: As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. Multiple maintainers? It's the best way to make no one responsible for a port: Should I handle the update? Oh, no matter, $someone will do it. ;) -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
Like with Apache, x 11, or perl? Trying to get something there committed it's like pulling tiger teeth with a pair of pliers. return I agree multiple maintainers is a bad idea. If someone is technical enough to want to maintain that, they can always use an alias it goes to a group. Oh, were talking to Apache x 11 or Perl again -- Michael Scheidell Will Hack For Food On Sep 11, 2012 5:46 PM, Alberto Villa avi...@freebsd.org wrote: On Tue, Sep 11, 2012 at 10:59 PM, Chris Rees utis...@gmail.com wrote: As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. Multiple maintainers? It's the best way to make no one responsible for a port: Should I handle the update? Oh, no matter, $someone will do it. ;) -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On Wed, Sep 12, 2012 at 12:50 AM, Michael Scheidell scheid...@freebsd.org wrote: Like with Apache, x 11, or perl? Trying to get something there committed it's like pulling tiger teeth with a pair of pliers. return I agree multiple maintainers is a bad idea. If someone is technical enough to want to maintain that, they can always use an alias it goes to a group. Oh, were talking to Apache x 11 or Perl again Teams are a different matter, they have an organisation so they can work (exceptions to this are caused by some teams being formed by too few people). Multiple individual maintainers will never be as organised as a team can be. -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On 2012-09-12 00:50, Michael Scheidell wrote: Like with Apache, x 11, or perl? Trying to get something there committed it's like pulling tiger teeth with a pair of pliers. return I agree multiple maintainers is a bad idea. If someone is technical enough to want to maintain that, they can always use an alias it goes to a group. Oh, were talking to Apache x 11 or Perl again I see no reason for having multiple MAINTAINERS. Commit with implicit and if you like give a statement http://wiki.freebsd.org/MaintainerNotes about co-maintaining. I already wiped my eyes on this commit http://svnweb.freebsd.org/ports?view=revisionrevision=304107 Or as Alberto already explained the reasons for a team form one. @Michael Trolling or experience? $ query-pr -c ports -r apache -y scheidel -q query-pr: no PRs matched $ query-pr -c ports -r perl -y scheidel -q oh, found two PR's for 4.11 and 5.5 $ query-pr -c ports -r x11 -y scheidel -q query-pr: no PRs matched -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
Two lls. Direct experience with x 11 But you can see this list for many complaints about trying to get port committed owned by teams. Ps I don't troll. -- Michael Scheidell Will Hack For Food ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: MAINTAINER lines and Real Names
On 9/11/2012 6:32 PM, Olli Hauer wrote: On 2012-09-12 00:50, Michael Scheidell wrote: Like with Apache, x 11, or perl? Trying to get something there committed it's like pulling tiger teeth with a pair of pliers. return I agree multiple maintainers is a bad idea. If someone is technical enough to want to maintain that, they can always use an alias it goes to a group. Oh, were talking to Apache x 11 or Perl again I see the proposal less about *FreeBSD Ports Teams* and more about *Non-FreeBSD* groups. We can only blame ourselves for having non-responsive teams, or having *mailing lists* be maintainers. I see the benefit here more about allowing us to commit PR from any of the listed addresses, as well as allow end-users to have more *people* to contact. I see no reason for having multiple MAINTAINERS. Commit with implicit and if you like give a statement http://wiki.freebsd.org/MaintainerNotes about co-maintaining. I already wiped my eyes on this commit http://svnweb.freebsd.org/ports?view=revisionrevision=304107 This is less about implicit approval, and more about having more support contact for end-users. There's nothing stopping anyone from doing this in other pors, why not make it standard for 'make maintainer' to list these people. There's no harm. Or as Alberto already explained the reasons for a team form one. @Michael Trolling or experience? $ query-pr -c ports -r apache -y scheidel -q query-pr: no PRs matched $ query-pr -c ports -r perl -y scheidel -q oh, found two PR's for 4.11 and 5.5 $ query-pr -c ports -r x11 -y scheidel -q query-pr: no PRs matched -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
