While the Git guide suggests creating branches named for tickets when generating pull requests, you don't have to. You can just give the branch a descriptive name (i.e. hotfix/remove-zend-log-string-dependency) and submit a pull request from there. Discussions can take place on the pull request itself, and if it can't be accepted as-is, the comments there can guide you (i.e. if it needs to be discussed on the lists, or if a ticket needs to be opened, etc.).
(Of course, I'm not a project manager here, so perhaps you'll get different suggestions from someone in a more official capacity... but in my experience as a contributor, it doesn't hurt to just go ahead and send a PR, especially if it's relatively simple; if nothing else, it's a good way to get a conversation started). - Demian ________________________________________ From: Philip G [guice...@gmail.com] Sent: Friday, October 19, 2012 6:39 PM To: Zend FW General Subject: [fw-general] Contributing improvements to components? What's the process for adding mini-features / improving functionality to components? Currently, I have a few "TODOs" I would like to add: - Add loadModule.post event support to loadModule() within \Zend\ModuleManager\ModuleManager - Improvements to missing features within \Zend\Log\Writer\FirePhp (including adding much needed support for 'extra' parameter). - And possibly: improvements Zend\Log: remove (string) dependency, and make the writers aware (i.e. issue #2638). But I'm not sure what's the process for discussing them, and moving forward. I have ZF2 forked and checked out. But I got stopped at creating a new branch for changes. That would imply creating an issue ticket? Or a feature ticket? I'm a little lost on this part. I have the code changes already locally (albeit in another local copy); I ready to move towards sending pull requests. --- Philip g...@gpcentre.net http://www.gpcentre.net/ -- List: fw-general@lists.zend.com Info: http://framework.zend.com/archives Unsubscribe: fw-general-unsubscr...@lists.zend.com
