Re: status of FreeBSD ports you maintain as of 20090705
On Tue, Aug 04, 2009 at 05:44:57PM -0400, Alex Goncharov wrote: Could do more for the project -- but looks like nobody needs it. Oh, well, I am not insisting. Persistence is the name of the game. The more PRs you submit, the more you are likely to attract the attention of the existing committers, and that's the track to becoming a new committer. How a new port would have broken the existing ones? (5.4 is not an upgrade -- it's a separate port not touching 5.0, 5.1 or 6.0.) - CONFLICTS must be set properly - latest_link must be set properly - the name can't be the exact same as an existing port (kind of equal to latest-link being right) - must be added correctly in category Makefile These are the most common errors people make when adding new ports. Yes, they are all easily learned. the words we need more volunteers, committers etc. sound insincere. We have a tremendous backlog of PRs and not all incoming PRs get noticed. However, historically, folks who persist and send a large number of PRs _do_ get noticed. But it doesn't happen overnight. Anyways, I don't think I'm going to be able to change your mind about this topic, so I'll step back and listen to other people's opinions now. mcl ___ 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: status of FreeBSD ports you maintain as of 20090705
2009/8/1 Mark Linimon lini...@lonesome.com: On Thu, Jul 23, 2009 at 07:37:27PM +0200, Martin Tournoij wrote: I now know more than ever why I switched to OpenBSD. FreeBSD people no longer seem to care about broken ports, or making people who submit broken patches maintainers, or even replying to my messages. [snip] To summarize: my own view is that we don't want bad patches or bad updates to be committed; but our committers are human, too. It's worth repeating that we rely on our committers to be responsible for verifying that the changes that they're committing are correct and useful; but, they're volunteers as well, so we have to rely on a combination of constructive criticism and encouragement to try to improve things. There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports - increase the number of volunteers/committers/testers... - switch to a multi-level solution (e.g. Archlinux). Regards -- Diego Depaoli ___ 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: status of FreeBSD ports you maintain as of 20090705
Diego Depaoli wrote: There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports We trim dead/useless ports all the time. - increase the number of volunteers/committers/testers... This is the only valid answer for FreeBSD. - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Doug -- This .signature sanitized for your protection ___ 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: status of FreeBSD ports you maintain as of 20090705
,--- You/Doug (Tue, 04 Aug 2009 08:26:08 -0700) * | - increase the number of volunteers/committers/testers... | This is the only valid answer for FreeBSD. `---* Take a look at the PR submission and update dates in http://www.freebsd.org/cgi/query-pr.cgi?pr=137046 (the port I maintain). Doesn't it seem excessive to you, for an update as simple as that? Wouldn't it be better for everybody if more people could commit the changes in their ports themselves? (Subject to a commit-privilege revocation on a substantial breakage anyplace). How could I, for example, turn from a volunteer to a committer? Take also a look at the history of an attempt to volunteer elsewhere in http://www.freebsd.org/cgi/query-pr.cgi?pr=136263. Something doesn't feel right about the way ports are handled in FreeBSD these days. Of course, the easiest is to dismiss the voices of discontent. -- Alex -- alex-goncha...@comcast.net -- ___ 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: status of FreeBSD ports you maintain as of 20090705
2009/8/4 Doug Barton do...@freebsd.org: Diego Depaoli wrote: There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports We trim dead/useless ports all the time. - increase the number of volunteers/committers/testers... This is the only valid answer for FreeBSD. How? I think your following comment (even smiled) isn't the right starting point. - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Please look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 Ok, I agree, is an useless port, but 3 months without further notices are enough to demotivate any volunteer. Cheers -- Diego Depaoli ___ 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: status of FreeBSD ports you maintain as of 20090705
On Tue 04 Aug 2009 at 09:21:07 PDT Diego Depaoli wrote: 2009/8/4 Doug Barton do...@freebsd.org: Diego Depaoli wrote: There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports We trim dead/useless ports all the time. - increase the number of volunteers/committers/testers... This is the only valid answer for FreeBSD. How? I think your following comment (even smiled) isn't the right starting point. - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Please look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 Ok, I agree, is an useless port, but 3 months without further notices are enough to demotivate any volunteer. I've been a maintainer since the beginning of this year, and I've yet to have any of my updates go unnoticed for that long. I suspect that your PR is the exception rather than the rule. But it does suggest the need for more guidance on how maintainers can work effectively with the committers. What can we do to help streamline the process? What sort of things create extra, unnecessary work for committers? If a PR doesn't get picked up within a week, it doesn't seem to be showing up on the committers' scans when they're looking for something to do. Perhaps they should fix their scans, but perhaps the maintainer should post a message here, asking for someone to look at the PR? I've seen messages like that in the past, and the response has always been that one of the committers volunteers to take care of it. ___ 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: status of FreeBSD ports you maintain as of 20090705
On Tue, Aug 04, 2009 at 11:52:03AM -0700, Charlie Kester wrote: On Tue 04 Aug 2009 at 09:21:07 PDT Diego Depaoli wrote: 2009/8/4 Doug Barton do...@freebsd.org: Diego Depaoli wrote: There are too many ports and too few people who care them. IMHO the options are: - decrease the number of ports We trim dead/useless ports all the time. - increase the number of ?volunteers/committers/testers... This is the only valid answer for FreeBSD. How? I think your following comment (even smiled) isn't the right starting point. - switch to a multi-level solution (e.g. Archlinux). In DiegoBSD you should feel free to use any solution you think is useful. :) Please look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/134443 Ok, I agree, is an useless port, but 3 months without further notices are enough to demotivate any volunteer. I've gone ahead and grabbed this PR. I will get to it when time permits (I've currently got a lot on my plate so please be patient). I've been a maintainer since the beginning of this year, and I've yet to have any of my updates go unnoticed for that long. I suspect that your PR is the exception rather than the rule. I don't know if it's true or not but I certainly agree with you here. But it does suggest the need for more guidance on how maintainers can work effectively with the committers. What can we do to help streamline the process? What sort of things create extra, unnecessary work for committers? Submitting PRs in the proper format and that need no extra work is the best. Unfortunately knowing when an update is done is not something that one intuitively knows; it comes with practice. Paying attention to what you submitted compared to what got committed is a good way to find out if you made any mistakes. Talking to the committers (we don't bite, I promise) also helps. The IRC channels are documented on the wiki and are a great source of getting help with things. Another great resource on how to submit good PRs is the porter's handbook[1]. It covers a lot of things in detail that can help your PR handled get handled quickly and easily. If a PR doesn't get picked up within a week, it doesn't seem to be showing up on the committers' scans when they're looking for something to do. Perhaps they should fix their scans, but perhaps the maintainer should post a message here, asking for someone to look at the PR? I've seen messages like that in the past, and the response has always been that one of the committers volunteers to take care of it. Yes, if a PR goes unclaimed for some period of time please feel free to ask here for someone to take a look at it. -- WXS [1]: http://www.freebsd.org/doc/en/books/porters-handbook/ ___ 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: status of FreeBSD ports you maintain as of 20090705
On Tue, Aug 04, 2009 at 11:55:19AM -0400, Alex Goncharov wrote: Wouldn't it be better for everybody if more people could commit the changes in their ports themselves? (Subject to a commit-privilege revocation on a substantial breakage anyplace). IMHO: no. Too many people automatically update their ports on a regular basis, and rely on us to not introduce brokenness. Having updates filtered through people that have shown themselves to having had a good track record seems prudent to me. Those folks who submit a number of good-quality PRs over a period of months tend to get noticed and nominated as committers. In the past year, we have added 10 ports committers. On occasion we turn someone down for an insufficient track record but it's rare, and most often they reapply once they have established one. (For the record, we have 157 ports comitters, of whom 131 have been active in the last 3 months.) How could I, for example, turn from a volunteer to a committer? Please see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ for a good starting point. Its last section has cross-references to other sources of information. Take also a look at the history of an attempt to volunteer elsewhere in http://www.freebsd.org/cgi/query-pr.cgi?pr=136263. I understand your frustration, but the mysql ports are key ports that have been handled for a long time by their current maintainer. (He has 234 commits over the past 12 months, with only one maintainer-timeout during that time, which suggests to me that he's doing a good job.) I can see why a committer would be reluctant to commit that upgrade because of that. As for your other question: my own personal opinion is that we do have too many ports, but who decides when a port is useful enough? Other projects have a process to vote or otherwise decide on that. Several of our committers have voiced reluctance to add more process in the past, when the same subject has been brought up. Frankly, I wouldn't want to serve on the committee that decides :-) Of course, the easiest is to dismiss the voices of discontent. Well, you have a right to your opinion ... I'm not saying that our process is perfect, far from it. (As an insider, especially as one of the people who wrangles the package-building machines, I have a front-row seat to many of our problems.) But IMHO it works better than it appears. mcl ___ 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: status of FreeBSD ports you maintain as of 20090705
On Thu, Jul 23, 2009 at 07:37:27PM +0200, Martin Tournoij wrote: I now know more than ever why I switched to OpenBSD. FreeBSD people no longer seem to care about broken ports, or making people who submit broken patches maintainers, or even replying to my messages. First of all, I have to apologize that I did not track this thread (which I myself started) more closely. I had assumed that maintainerships were being handed off well. I was wrong. You have to understand: when I send out the 'status of FreeBSD ports' emails, I am sending them to maintainers who have already had 2 or more maintainer-timeouts (i.e. failure to respond to PRs). (Sorry, I don't usually get around to the maintainers who only have one :-/ ) In almost all of these cases, the maintainers have either a) lost interest in maintaining their ports, or b) now lack the time to respond to PRs about their ports. It usually takes an email or two to establish which of the two that it is -- but in most cases, the result is that the ports wind up being reassigned. In a few cases, the maintainers promise to do better, and retain their ports. But I can't recall a case where the maintainer said I'll maintain them for a little while -- but then give them up. So I can understand where a committer would see a posting, and say, ok, these are up for reassignment. (I think this is a fair reading of the here are the ports I maintain list.) I've been waiting for more than a week to revert the maintainer switch I can't speak to that; I have not talked to the committer in question. However, there is a lot of traffic that goes by on the mailing list every week ... The same guy that broke this port is now the scribus maintainer and a maintainer of a bunch of other ports, hope you don't use scribus since I suspect the quality of the port will not improve. The way that we have things set up is that: we hope that maintainers will submit good updates; but we rely on committers to ensure that the updates they commit are necessary and sufficient. This is why we have a mentorship period for committers -- there are things you just need to know that may not be sufficiently detailed in the Porter's Handbook. Most maintainers start off not understanding the ins-and-outs of the Ports Collection. We try to help by making the Porter's Handbook as complete as we can; however, there is some degree of learning on the job. Remember: we're a volunteer project. (Also: this is supposed to be fun, not a job, right??? :-) ) So if a particular maintainer doesn't understand how things work (yet), it's the job of the committers to educate him/her so that we can turn their enthusiasm into a more concrete contribution. But everyone's got to start somewhere. To summarize: my own view is that we don't want bad patches or bad updates to be committed; but our committers are human, too. It's worth repeating that we rely on our committers to be responsible for verifying that the changes that they're committing are correct and useful; but, they're volunteers as well, so we have to rely on a combination of constructive criticism and encouragement to try to improve things. mcl ___ 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: status of FreeBSD ports you maintain as of 20090705
Martin Tournoij ha scritto: Really, I have better things to do, I would have liked to do this in a nicer way, but I've been waiting for more than a week to revert the maintainer switch Do you mean you never approved the switch, as stated in the commit log? Change maintainer to scjamo...@bsd.com.br Submitted by: scjamo...@bsd.com.br (to ports@) Approved by:carpetsmo...@rwxrwxrwx.net (maintainer) -- Alex Dupre ___ 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: status of FreeBSD ports you maintain as of 20090705
On Fri, 24 Jul 2009 12:00:13 +0200, Alex Dupre a...@freebsd.org wrote: Martin Tournoij ha scritto: Really, I have better things to do, I would have liked to do this in a nicer way, but I've been waiting for more than a week to revert the maintainer switch Do you mean you never approved the switch, as stated in the commit log? Change maintainer to scjamo...@bsd.com.br Submitted by: scjamo...@bsd.com.br (to ports@) Approved by: carpetsmo...@rwxrwxrwx.net (maintainer) Not explicitly, and in my original post I said ``will resign the maintainership of all my ports in the **coming weeks**, (For a few ports I have a few changes/ updates **in the pipeline I would like to finish**).'' Misunderstandings happen, and that's ok. I explained reassigning maintainership immediately was not my intention and asked to revert the changes, no word ever since ... Which is not so ok IMO... ___ 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: status of FreeBSD ports you maintain as of 20090705
On Fri, Jul 24, 2009 at 04:52:00PM +0200, Martin Tournoij wrote: On Fri, 24 Jul 2009 12:00:13 +0200, Alex Dupre a...@freebsd.org wrote: Martin Tournoij ha scritto: Really, I have better things to do, I would have liked to do this in a nicer way, but I've been waiting for more than a week to revert the maintainer switch Do you mean you never approved the switch, as stated in the commit log? Change maintainer to scjamo...@bsd.com.br Submitted by: scjamo...@bsd.com.br (to ports@) Approved by:carpetsmo...@rwxrwxrwx.net (maintainer) Not explicitly, and in my original post I said ``will resign the maintainership of all my ports in the **coming weeks**, (For a few ports I have a few changes/ updates **in the pipeline I would like to finish**).'' Misunderstandings happen, and that's ok. I explained reassigning maintainership immediately was not my intention and asked to revert the changes, no word ever since ... Which is not so ok IMO... And this is why I think we should have a policy of not changing maintainer of things based upon mailing list traffic. I know I'm guilty of doing it in the past but I have come to the conclusion that it can cause these kinds of problems and set a precedent of people expecting mailing list traffic to result in commits. We should have an official record of who requested changes in the PR database and not give the community the idea that mailing list traffic asking for a commit to happen is the right way to do things. -- WXS ___ 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: status of FreeBSD ports you maintain as of 20090705
I now know more than ever why I switched to OpenBSD. FreeBSD people no longer seem to care about broken ports, or making people who submit broken patches maintainers, or even replying to my messages. Really, I have better things to do, I would have liked to do this in a nicer way, but I've been waiting for more than a week to revert the maintainer switch, I'm also waiting for 3 weeks now to undo the scribus update to 1.1.13 since it is broken not just in one but in several ways. The same guy that broke this port is now the scribus maintainer and a maintainer of a bunch of other ports, hope you don't use scribus since I suspect the quality of the port will not improve. Please remove my maintainer status from all ports. Also remove my sites from MASTER_SITES (xs4all.nl/~tournoij, rwxrwxrwx.net, carpetsmoker.net), they no longer work anyway. ___ 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: status of FreeBSD ports you maintain as of 20090705
Hi guys, I would like to be the maintainer of ports audio/csound devel/cdialog print/scribus sysutils/bashburn sysutils/daa2iso sysutils/mybashburn sysutils/uif2iso I am very active and the ports would help even more. Regards, Sylvio Cesar. 2009/7/15 Martin Tournoij carpetsmo...@rwxrwxrwx.net: On Sun, 5 Jul 2009 20:47:19 -0500, lini...@freebsd.org wrote: I have noticed some maintainer-timeouts on ports that you maintain. Please let me know if you are still interested in these ports; otherwise, I would like to reassign them. Thanks. mcl audio/mpdscribble carpetsmo...@rwxrwxrwx.net 1 x11-wm/pekwm carpetsmo...@rwxrwxrwx.net 2 Hi there, I would like to maintain these ports, but unfortunately I haven't had the time in the last few months. And not having a X11-enabled FreeBSD machine installed doesn't help either... I thought about it during the last week, and will resign the maintainership of all my ports in the coming weeks, (For a few ports I have a few changes/ updates in the pipeline I would like to finish). So it's Ok to reassign these ports. Note: Please CC me in replies since I'm not subscribed to ports@ Regards, Martin -- For reference a list of ports I maintain: audio/csound audio/mpdscribble deskutils/zorro devel/cdialog devel/clanlib devel/clig devel/p5-Config-ApacheFormat devel/pear-XML_Tree editors/e93 editors/vigor emulators/catapult games/avanor games/crimson games/super_methane_brothers games/trophy games/wrogue graphics/geeqie graphics/gsculpt graphics/pqiv graphics/qiv irc/tkirc math/add math/mpexpr misc/ewipe misc/freeguide misc/tkregexp print/scribus sysutils/bashburn sysutils/daa2iso sysutils/mybashburn sysutils/uif2iso textproc/cost x11-fm/gprename x11-fm/pcmanfm x11-fm/xfe x11-wm/pekwm x11/grabc x11/xrsi ___ 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: status of FreeBSD ports you maintain as of 20090705
Martin Tournoij wrote: games/avanor games/crimson games/wrogue I would take these. ___ 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: status of FreeBSD ports you maintain as of 20090705
On Thu, 16 Jul 2009 11:45:07 -0400, Steven Kreuzer skreu...@exit2shell.com wrote: Hey Sylvio- On Jul 16, 2009, at 7:36 AM, Sylvio Cesar wrote: Hi guys, I would like to be the maintainer of ports audio/csound devel/cdialog print/scribus sysutils/bashburn sysutils/daa2iso sysutils/mybashburn sysutils/uif2iso You are now that maintainer of those ports. Treat them well ;) Please revert this. As I mentioned before I have changes pending for a few ports, need to make other changes (i.e. MASTER_SITES I maintain) and I also would like to ensure the ports end up with a port maintainer that doesn't break them. Martin ___ 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: status of FreeBSD ports you maintain as of 20090705
On Thu, 16 Jul 2009 11:45:28 -0400, Steven Kreuzer skreu...@exit2shell.com wrote: Hey Frank- On Jul 16, 2009, at 10:37 AM, Frank Steinborn wrote: Martin Tournoij wrote: games/avanor games/crimson games/wrogue I would take these. You are now that maintainer of those ports. Treat them well ;) Please revert this. As I mentioned before I have changes pending for a few ports, need to make other changes (i.e. MASTER_SITES I maintain) and I also would like to ensure the ports end up with a port maintainer that doesn't break them. Martin ___ 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: status of FreeBSD ports you maintain as of 20090705
Hey Sylvio- On Jul 16, 2009, at 7:36 AM, Sylvio Cesar wrote: Hi guys, I would like to be the maintainer of ports audio/csound devel/cdialog print/scribus sysutils/bashburn sysutils/daa2iso sysutils/mybashburn sysutils/uif2iso You are now that maintainer of those ports. Treat them well ;) -- Steven Kreuzer http://www.exit2shell.com/~skreuzer ___ 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: status of FreeBSD ports you maintain as of 20090705
Hey Frank- On Jul 16, 2009, at 10:37 AM, Frank Steinborn wrote: Martin Tournoij wrote: games/avanor games/crimson games/wrogue I would take these. You are now that maintainer of those ports. Treat them well ;) -- Steven Kreuzer http://www.exit2shell.com/~skreuzer ___ 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: status of FreeBSD ports you maintain as of 20090705
* Martin Tournoij (carpetsmo...@rwxrwxrwx.net) wrote: I thought about it during the last week, and will resign the maintainership of all my ports in the coming weeks, (For a few ports I have a few changes/ updates in the pipeline I would like to finish). Is it ok to take graphics/geeqie? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: status of FreeBSD ports you maintain as of 20090705
On Wed 15 Jul 2009 at 14:08:18 PDT Martin Tournoij wrote: On Sun, 5 Jul 2009 20:47:19 -0500, lini...@freebsd.org wrote: I have noticed some maintainer-timeouts on ports that you maintain. Please let me know if you are still interested in these ports; otherwise, I would like to reassign them. Thanks. mcl audio/mpdscribble carpetsmo...@rwxrwxrwx.net 1 x11-wm/pekwmcarpetsmo...@rwxrwxrwx.net 2 Hi there, I would like to maintain these ports, but unfortunately I haven't had the time in the last few months. And not having a X11-enabled FreeBSD machine installed doesn't help either... I thought about it during the last week, and will resign the maintainership of all my ports in the coming weeks, (For a few ports I have a few changes/ updates in the pipeline I would like to finish). So it's Ok to reassign these ports. Judging by your followups, Martin, there seems to be some confusion about which ports you're relinquishing at this time. Was your OK meant to apply only to the mpdscribble and pekwm ports? And your mention of your other ports was only a heads-up that you intend to be resigning maintainership in the near future, after submitting some final changes? Just trying to clarify the situation. It's good to see that there are volunteers ready to take over once you're done, but nobody wants to rush you out the door. ;-) ___ 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: status of FreeBSD ports you maintain as of 20090705
On Thu, 16 Jul 2009 11:17:11 -0700, Charlie Kester corky1...@comcast.net wrote: On Wed 15 Jul 2009 at 14:08:18 PDT Martin Tournoij wrote: On Sun, 5 Jul 2009 20:47:19 -0500, lini...@freebsd.org wrote: I have noticed some maintainer-timeouts on ports that you maintain. Please let me know if you are still interested in these ports; otherwise, I would like to reassign them. Thanks. mcl audio/mpdscribble carpetsmo...@rwxrwxrwx.net 1 x11-wm/pekwmcarpetsmo...@rwxrwxrwx.net 2 Hi there, I would like to maintain these ports, but unfortunately I haven't had the time in the last few months. And not having a X11-enabled FreeBSD machine installed doesn't help either... I thought about it during the last week, and will resign the maintainership of all my ports in the coming weeks, (For a few ports I have a few changes/ updates in the pipeline I would like to finish). So it's Ok to reassign these ports. Judging by your followups, Martin, there seems to be some confusion about which ports you're relinquishing at this time. Was your OK meant to apply only to the mpdscribble and pekwm ports? And your mention of your other ports was only a heads-up that you intend to be resigning maintainership in the near future, after submitting some final changes? Yep, that was it (See below). Just trying to clarify the situation. It's good to see that there are volunteers ready to take over once you're done Indeed, thanks to everyone. I would like to pass on maintainership of all my ports, most ports I maintain are X11 based and I don't really use FreeBSD with X11 anymore nowadays (Due to crappy Xorg ``releases'' if you can call 'em that, OpenBSD works much better for me ATM). However, I don't want to pass maintainership *right now*, for example, I have spent quite some time a few months ago improving the audio/csound port, and this afternoon I spent some time making final adjustments and some (hopefully useful) instructions for the new maintainer. I guess all of this can also be done after maintainership is passed, but my idea was that people would call out that they were willing to maintain a port, that I would make final adjustments (if any), and then submit a PR with the adjustments and maintainer change. Sorry if I wasn't too clear, I just assumed this must be standard procedure ... Regards, Martin ___ 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: status of FreeBSD ports you maintain as of 20090705
On Sun, 5 Jul 2009 20:47:19 -0500, lini...@freebsd.org wrote: I have noticed some maintainer-timeouts on ports that you maintain. Please let me know if you are still interested in these ports; otherwise, I would like to reassign them. Thanks. mcl audio/mpdscribble carpetsmo...@rwxrwxrwx.net 1 x11-wm/pekwmcarpetsmo...@rwxrwxrwx.net 2 Hi there, I would like to maintain these ports, but unfortunately I haven't had the time in the last few months. And not having a X11-enabled FreeBSD machine installed doesn't help either... I thought about it during the last week, and will resign the maintainership of all my ports in the coming weeks, (For a few ports I have a few changes/ updates in the pipeline I would like to finish). So it's Ok to reassign these ports. Note: Please CC me in replies since I'm not subscribed to ports@ Regards, Martin -- For reference a list of ports I maintain: audio/csound audio/mpdscribble deskutils/zorro devel/cdialog devel/clanlib devel/clig devel/p5-Config-ApacheFormat devel/pear-XML_Tree editors/e93 editors/vigor emulators/catapult games/avanor games/crimson games/super_methane_brothers games/trophy games/wrogue graphics/geeqie graphics/gsculpt graphics/pqiv graphics/qiv irc/tkirc math/add math/mpexpr misc/ewipe misc/freeguide misc/tkregexp print/scribus sysutils/bashburn sysutils/daa2iso sysutils/mybashburn sysutils/uif2iso textproc/cost x11-fm/gprename x11-fm/pcmanfm x11-fm/xfe x11-wm/pekwm x11/grabc x11/xrsi ___ 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
