On 4/13/12 10:48 AM, Alexander Hansen wrote: > Hi. > > I'd like to propose a policy for the case of people with commit bits > updating other people's packages. > > 1) Please contact the maintainer. > 2) Give the maintainer a reasonable timeframe to respond. Around a > week is good, but this is negotiable. A quicker turnaround may be > needed e.g. if an update to _your_ package is being blocked by > something _someone else's_ package does. See 3B). > 3A) If the maintainer okays your proposed changes, then go ahead. > 3B) If you don't hear from the maintainer or if you can make a case > that there is a pressing need to change the package before getting a > response, then get approval from a Core Team member first via an > emailed message to fink-core or on IRC. Core Team members should get > approval from another Core Team member. > > Any objections to this? > Re: item 2, Macports apparently has a 72 hour turnaround time. I'm leaning toward that.
-- Alexander Hansen, Ph.D. Fink User Liaison http://finkakh.wordpress.com/2012/02/21/got-job/ ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
