[Bug 286462] devel/svn2git: update 1.0.18 ==> 1.0.20 fix WWW and take MAINTAINER

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286462

--- Comment #8 from Chris Hutchinson <portmaster@bsdforge.com> ---
(In reply to Zsolt Udvari from comment #7)
I see your point. But if someone is interested in a port
bug and wants to contribute. Can't they contribute to the
same pr(1)? That's what I suggested in our case. I find
this situation even more important where newcomers are
concerned. I've been doing this since we were using CVS(1).
Life was simpler back then. The ports framework was not as
powerful and potentially complicated to understand as it
is now. IOW it's a much higher hurdle to overcome to
become a maintainer than it was back then. So somebody new
to the ports system sees a port they want to maintain. They
do all the reading to learn how to maintain it. But what
happened here, happens to them. It was a lot of work for
them. Now they find all that work was wasted and have a
bad opinion of FreeBSD. We may loose a good candidate for
no good reason. :(
Couple of possibilities come to mind:
 - committers may not commit their own ports
 - all maintenance *must* go through bugzilla (save sweeping portmgr
maintenance)
All of this may be somewhat moot. As it's clear that git(1)
workflows will need to be the path forward, see; git pull/
git push/...
I'm currently working on a unified git based CI src/port management
system. Think Git(Hub|Lab) exclusively for BSD. This will centralize
all activity in a way that will greatly circumvent cases like this. :)

Lastly, we're really spamming buczilla log. Which is a no-no. :O
We should probably continue this off bugzilla. Please feel free
to email me directly. This is a great conversation and it would be
nice if we were able to find the ultimate solution. :)

Best wishes.

-- 
You are receiving this mail because:
You are the assignee for the bug.