[Prototype-core] Re: Getting patches reviewed and applied
Historically the JS libraries haven't seen enough patch volume to justify the process overhead. I feel like we're turning the corner there, though; we should probably start following the Report 12 process for Prototype. What does the rest of Core think? Any message that proposes a new feature is most welcome on this list, so feel free to post here first if you want to gauge how well a patch would be received. I'm qualified to answer only the Prototype half of your question. I'll let Thomas speak to the Scriptaculous half. Cheers, Andrew On Oct 13, 7:39 pm, Ryan McGeary [EMAIL PROTECTED] wrote: I've got one prototype patch and one scriptaculous patch awaiting review from the core team. I went through the process of getting them both reviewed and verified under the new Rails process, but I didn't realize the javascript spinoff teams didn't track Report 12. It took a comment from Koz for me to realize this. What's the best way to receive feedback from the core team? Does it make sense for prototype and scriptaculous to follow the same Report 12 process that Rails is using? Add optional 'distance' and 'duration' options to Effect.Shakehttp://dev.rubyonrails.org/ticket/8637 Add optional context argument to Number#timeshttp://dev.rubyonrails.org/ticket/9252 Thanks, Ryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Getting patches reviewed and applied
I feel like we're turning the corner there, though; we should probably start following the Report 12 process for Prototype. What does the rest of Core think? +1 ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Getting patches reviewed and applied
Love the addtions to Effect.Shake. Applied. Best, Thomas Am 14.10.2007 um 02:39 schrieb Ryan McGeary: I've got one prototype patch and one scriptaculous patch awaiting review from the core team. I went through the process of getting them both reviewed and verified under the new Rails process, but I didn't realize the javascript spinoff teams didn't track Report 12. It took a comment from Koz for me to realize this. What's the best way to receive feedback from the core team? Does it make sense for prototype and scriptaculous to follow the same Report 12 process that Rails is using? Add optional 'distance' and 'duration' options to Effect.Shake http://dev.rubyonrails.org/ticket/8637 Add optional context argument to Number#times http://dev.rubyonrails.org/ticket/9252 Thanks, Ryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
