)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4656,"name":"Sean M. Collins","email":"sean@coreitpro.com","username":"scollins"},"change_message_id":"4a33124d8f22afc1d8f1bfb64e3058e7be83b22d","unresolved":false,"context_lines":[{"line_number":10,"context_line":"capture as many of these as I could in the opening section of the"},{"line_number":11,"context_line":"blueprint.rst file. I\u0027ve also modified the process for submitting specs"},{"line_number":12,"context_line":"to move to a feature request model, a slimmed down spec, and a beefed"},{"line_number":13,"context_line":"up devref requirement. The intent is to allow for faster converfence on"},{"line_number":14,"context_line":"ideas, and better in-tree documentation which will lead to better user"},{"line_number":15,"context_line":"facing documentation."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"7ad32947_39ad0b89","line":13,"updated":"2015-04-27 14:04:56.000000000","message":"typo - convergence","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"30b191daf7fde969bf9d34ea0ead78e98f7030b2","unresolved":false,"context_lines":[{"line_number":10,"context_line":"capture as many of these as I could in the opening section of the"},{"line_number":11,"context_line":"blueprint.rst file. I\u0027ve also modified the process for submitting specs"},{"line_number":12,"context_line":"to move to a feature request model, a slimmed down spec, and a beefed"},{"line_number":13,"context_line":"up devref requirement. The intent is to allow for faster converfence on"},{"line_number":14,"context_line":"ideas, and better in-tree documentation which will lead to better user"},{"line_number":15,"context_line":"facing documentation."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"7ad32947_653750e4","line":13,"in_reply_to":"7ad32947_39ad0b89","updated":"2015-04-27 15:05:16.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":11,"context_line":"blueprint.rst file. I\u0027ve also modified the process for submitting specs"},{"line_number":12,"context_line":"to move to a feature request model, a slimmed down spec, and a beefed"},{"line_number":13,"context_line":"up devref requirement. The intent is to allow for faster converfence on"},{"line_number":14,"context_line":"ideas, and better in-tree documentation which will lead to better user"},{"line_number":15,"context_line":"facing documentation."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Change-Id: Id54550fb4314117db8fcfea90dd0627899e80c74"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"7ad32947_07309955","line":14,"updated":"2015-04-27 18:36:01.000000000","message":"will lead to -\u003e can support the development of","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"}],"doc/source/policies/blueprints.rst":[{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"8a565d9140e6904974bb5cb7f19862e43fce2ae1","unresolved":false,"context_lines":[{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."},{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked in the neutron-specs repository, and allow"},{"line_number":24,"context_line":"for the submission and review of these early ideas before code is"},{"line_number":25,"context_line":"submitted. This allows the team to verify the validity of a feature request"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_b253ed38","line":22,"updated":"2015-04-25 01:12:13.000000000","message":"I\u0027m all for this change, apart from this part. Why are we using git and neutron-specs for feature requests? That alone is a non-trivial barrier (Some users don\u0027t want anything to do with git, cloning the neutron-specs repo and the git workflow).\n\nCould we discuss the pros and cons of using launchpad to submit and track feature requests?","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."},{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked in the neutron-specs repository, and allow"},{"line_number":24,"context_line":"for the submission and review of these early ideas before code is"},{"line_number":25,"context_line":"submitted. This allows the team to verify the validity of a feature request"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_d4f7edf3","line":22,"in_reply_to":"bab921fb_b253ed38","updated":"2015-04-27 13:03:45.000000000","message":"To be honest, Maru and I talked about this, and he was suggesting using bugs. I am not in favor of that, but perhaps moving back to using Launchpad BPs purely for feature requests does make a lot of sense. I\u0027ll rework this one to indicate that and we\u0027ll see how it turns out.","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"c49ca773ef5a42bd5f9264e6db4dfe31b3a7e0e4","unresolved":false,"context_lines":[{"line_number":28,"context_line":"feature by voting +1/-1 on the feature. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_772e6a44","line":31,"updated":"2015-04-24 23:28:02.000000000","message":"would gaming the system include one company supporting a feature and getting as many people they employ that is active in openstack to +1 the feature?","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"e1223844061486d0b40e7de3b97929041b3bed90","unresolved":false,"context_lines":[{"line_number":28,"context_line":"feature by voting +1/-1 on the feature. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ad32947_e79d9a5a","line":31,"in_reply_to":"9abe1de1_74e70141","updated":"2015-04-27 20:49:36.000000000","message":"good!","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":28,"context_line":"feature by voting +1/-1 on the feature. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_74e70141","line":31,"in_reply_to":"bab921fb_772e6a44","updated":"2015-04-27 13:03:45.000000000","message":"Yes.","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"c49ca773ef5a42bd5f9264e6db4dfe31b3a7e0e4","unresolved":false,"context_lines":[{"line_number":45,"context_line":"* Continuous feedback on feature requests means rejected specs are given"},{"line_number":46,"context_line":"  firm answers quickly."},{"line_number":47,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":48,"context_line":"  for deadlines."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Specs and Feature Requests"},{"line_number":51,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_37fc7271","line":48,"updated":"2015-04-24 23:28:02.000000000","message":"does a feature request need to be unanimously approved by the drivers team or will there be a certain number of -1\u0027s or -2\u0027s a request can have before it is rejected?","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"* Continuous feedback on feature requests means rejected specs are given"},{"line_number":46,"context_line":"  firm answers quickly."},{"line_number":47,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":48,"context_line":"  for deadlines."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Specs and Feature Requests"},{"line_number":51,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_f4c9d1ad","line":48,"in_reply_to":"bab921fb_37fc7271","updated":"2015-04-27 13:03:45.000000000","message":"We\u0027ve typically gone lazy consensus, and I think keeping that approach makes a lot of sense.","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"8a565d9140e6904974bb5cb7f19862e43fce2ae1","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Specs and Feature Requests"},{"line_number":51,"context_line":"--------------------------"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"A quick note on the differences. The neutron-specs repository will be updated"},{"line_number":54,"context_line":"to include a directory for feature requests. These will not be targeted at"},{"line_number":55,"context_line":"a specific release, and will be a lightweight way for people to propose a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_a5e2892d","line":52,"updated":"2015-04-25 01:12:13.000000000","message":"While the proposed change makes it much easier for non-developers to submit feature requests, it makes it harder for developers. I\u0027d now have to submit a feature request as well as a spec. Afterwards, I\u0027d have to submit the code as well as its devref. Since in the current proposal the devref doesn\u0027t replace the spec, this adds quite a bit of work!","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Specs and Feature Requests"},{"line_number":51,"context_line":"--------------------------"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"A quick note on the differences. The neutron-specs repository will be updated"},{"line_number":54,"context_line":"to include a directory for feature requests. These will not be targeted at"},{"line_number":55,"context_line":"a specific release, and will be a lightweight way for people to propose a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_d4cecdb3","line":52,"in_reply_to":"bab921fb_a5e2892d","updated":"2015-04-27 13:03:45.000000000","message":"Reworking to not require neutron-specs.","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"c49ca773ef5a42bd5f9264e6db4dfe31b3a7e0e4","unresolved":false,"context_lines":[{"line_number":90,"context_line":"Feature Request Acceptance"},{"line_number":91,"context_line":"---------------------------"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"Once a feature request bug has been deemed as fitting within the framework for"},{"line_number":94,"context_line":"the upcoming release, the neutron-drivers team will approve the feature request"},{"line_number":95,"context_line":"and work with the submitter to file either a bug or a LP BP and spec in the"},{"line_number":96,"context_line":"neutron-specs repository."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_179cce5b","line":93,"updated":"2015-04-24 23:28:02.000000000","message":"is this supposed to be \"feature request or bug\"?","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":90,"context_line":"Feature Request Acceptance"},{"line_number":91,"context_line":"---------------------------"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"Once a feature request bug has been deemed as fitting within the framework for"},{"line_number":94,"context_line":"the upcoming release, the neutron-drivers team will approve the feature request"},{"line_number":95,"context_line":"and work with the submitter to file either a bug or a LP BP and spec in the"},{"line_number":96,"context_line":"neutron-specs repository."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_b4c47992","line":93,"in_reply_to":"bab921fb_179cce5b","updated":"2015-04-27 13:03:45.000000000","message":"Done","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"c49ca773ef5a42bd5f9264e6db4dfe31b3a7e0e4","unresolved":false,"context_lines":[{"line_number":137,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":138,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":139,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":140,"context_line":"accepted into the release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bab921fb_170f2e89","line":140,"updated":"2015-04-24 23:28:02.000000000","message":"will the neutron sub projects (lbaas, vpnaas, fwaas) require the same?","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"987dad4724baceb941385b797fa35faeb9fa3b9d","unresolved":false,"context_lines":[{"line_number":137,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":138,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":139,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":140,"context_line":"accepted into the release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9abe1de1_146325b3","line":140,"in_reply_to":"bab921fb_170f2e89","updated":"2015-04-27 13:03:45.000000000","message":"Yes! And I\u0027ll indicate that here. Thanks!","commit_id":"bb44cd2b4a0dc258e82f366e0ba7f47c70dd7ca1"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Blueprints and Specs"},{"line_number":2,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Starting with the Liberty release cycle, the Neutron team has evolved it\u0027s"},{"line_number":5,"context_line":"spec process. The current process is meant to assist both those submitting"},{"line_number":6,"context_line":"new use cases and ideas into Neutron, as well as assist those reviewing the"},{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_45069421","line":4,"updated":"2015-04-27 15:52:07.000000000","message":"can \"it\u0027s\" be used in place of \"its\". My english teacher taught me \"it\u0027s\" was for \"it is\". But that happened 25 years ago, and the teacher wasn\u0027t even english...","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"19eaf7066ad42e5a0cc9521e2633420c9eb8bb78","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Blueprints and Specs"},{"line_number":2,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Starting with the Liberty release cycle, the Neutron team has evolved it\u0027s"},{"line_number":5,"context_line":"spec process. The current process is meant to assist both those submitting"},{"line_number":6,"context_line":"new use cases and ideas into Neutron, as well as assist those reviewing the"},{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_93f993cb","line":4,"in_reply_to":"7ad32947_45069421","updated":"2015-04-27 19:18:52.000000000","message":"@Salvatore is right.  ;)","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Blueprints and Specs"},{"line_number":2,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Starting with the Liberty release cycle, the Neutron team has evolved it\u0027s"},{"line_number":5,"context_line":"spec process. The current process is meant to assist both those submitting"},{"line_number":6,"context_line":"new use cases and ideas into Neutron, as well as assist those reviewing the"},{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_69414d0b","line":4,"in_reply_to":"7ad32947_93f993cb","updated":"2015-04-28 11:03:26.000000000","message":"My english teacher wasn\u0027t english either,  I have a lot of native (or almost native) english teachers now ;) Thank you! ;D","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"bb3a1516832e015d94a8106ca73e2ee4c708ae96","unresolved":false,"context_lines":[{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"},{"line_number":8,"context_line":"as possible, catch design issues up-front, and work to collapse overlap"},{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_736a771c","line":10,"updated":"2015-04-27 16:59:45.000000000","message":"So, this is basically going from the waterfall model to the agile model, using gerrit as the demo/feedback step. This will be great for velocity of smaller things, but what about something large, like DVR?  launchpad seems a terrible place to design something like that. Where would that take place?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"},{"line_number":8,"context_line":"as possible, catch design issues up-front, and work to collapse overlap"},{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_f8dc1b48","line":10,"in_reply_to":"7ad32947_736a771c","updated":"2015-04-27 22:37:19.000000000","message":"Prototyping is still an important tool in doing any large-scale effort, and it doesn\u0027t have to be code that lands in tree.  This change also makes clear that high-level documentation is a precondition for merging any code.  We are proposing to separate feature requests from design, and that doesn\u0027t preclude making the design review process more rigorous.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":7,"context_line":"ideas and the eventual code. The end goals are to remove friction as much"},{"line_number":8,"context_line":"as possible, catch design issues up-front, and work to collapse overlap"},{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_836808f7","line":10,"in_reply_to":"7ad32947_f8dc1b48","updated":"2015-04-28 11:27:09.000000000","message":"High-level documentation describing basic design, background, use cases are still important. In my understanding the key point is to lower hurdles to describe implementation details in spec reviews. In some case code describes a lot.\n\nThere are several open questions in the process with a large patch series. When can we merge devref docs? when all patches are merged? First merge rough design documents and improve them gradually?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"e19aded8c967ef1022326d159c8ec1344005b0d8","unresolved":false,"context_lines":[{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_2e35a645","line":12,"updated":"2015-04-28 02:55:27.000000000","message":"it\u0027s better to put rationale/history/background/etc into a separate section so that new comers who just want to know how to submit their bp/spec/fr find it out more easily.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"3cf2f6ebd0e766371db575b2c7619f69a65174a1","unresolved":false,"context_lines":[{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_dfddbe71","line":12,"in_reply_to":"7ad32947_2e35a645","updated":"2015-04-28 06:31:03.000000000","message":"I agree with Yamamoto. Now we need the history and background to review the proposal but they aren\u0027t needed in future.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":9,"context_line":"in proposed ideas earlier."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Some of the pain points of the previous specs process included the"},{"line_number":12,"context_line":"following:"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_3b4bbf5b","line":12,"in_reply_to":"7ad32947_dfddbe71","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_20602335","line":16,"updated":"2015-04-27 18:36:01.000000000","message":"May want to expand this point to highlight that the specs repo is effectively a graveyard - once approved, specs are rarely kept in sync with what actually gets implemented.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"2be418aaf074f7ee4ee79fbe54e783be7af21c73","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_070c1693","line":16,"in_reply_to":"7ad32947_02308755","updated":"2015-04-27 20:08:28.000000000","message":"No, it won\u0027t, and one of my big concerns here is that those debates will now happen *after* code is written, which could lead to some serious frustration.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_f881bbfc","line":16,"in_reply_to":"7ad32947_070c1693","updated":"2015-04-27 22:37:19.000000000","message":"I don\u0027t see how this change relegates discussion until after implementation.  The conversation about which features to implement still has to happen, and then the conversation doesn\u0027t have to be conflated with a plan for implementation.  The plan for implementation","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_5352d0de","line":16,"in_reply_to":"7ad32947_070c1693","updated":"2015-04-27 22:37:19.000000000","message":"I don\u0027t see how this change relegates discussion until after implementation.  The discussion about whether to implement a feature still has to happen first.  Once a feature has been designated for implementation, the conversation about the design of that feature has to happen before any code will be considered for merge.  There is nothing stopping us from extending that design process as long as we deem necessary.  What am I missing?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_5bdafb79","line":16,"in_reply_to":"7ad32947_20602335","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"19eaf7066ad42e5a0cc9521e2633420c9eb8bb78","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_02308755","line":16,"in_reply_to":"7ad32947_20602335","updated":"2015-04-27 19:18:52.000000000","message":"Part of problem was that updates to the specs repository was met with resistance [1].  Will all of that resistance go away by moving this to developer documentation?  I hope so.\n\n [1] https://review.openstack.org/#/c/142231/1/specs/kilo/subnet-allocation.rst","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_3bbe1f00","line":16,"in_reply_to":"7ad32947_a318a485","updated":"2015-04-28 16:45:29.000000000","message":"I think we just need a short feature request up front. If we determine it\u0027s good, we can work on the implementation later. That\u0027s the main point of this change.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* Onerous requirements on spec submitters."},{"line_number":15,"context_line":"* Challenges of requiring full up-front design."},{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_a318a485","line":16,"in_reply_to":"7ad32947_f881bbfc","updated":"2015-04-28 11:27:09.000000000","message":"We can start a discussion of a new feature by proposing a review only with devref doc, so we can do similar process even after we move the new process.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"4c8088a8a09924a12d37128048d4025c9a1cbe2c","unresolved":false,"context_lines":[{"line_number":16,"context_line":"* Separation of design documents from source code."},{"line_number":17,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":18,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":19,"context_line":"* Rejected specs getting lost in the shuffle for a new release."},{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_91ff4b34","line":19,"updated":"2015-04-27 18:03:16.000000000","message":"Kind of a non-helpful note: This last point can be solved with a much simpler / gradual change than what is proposed here. This could be mentioned in the alternatives section if you feel up for it (Like changing the process so that specs can be submitted and approved any time in the cycle and not just in the beginning, like is mentioned below).","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_16d0d152","line":23,"updated":"2015-04-27 18:36:01.000000000","message":"I don\u0027t think blueprints are the best way to track feature requests.  As a launchpad capability, blueprints are more focused on tracking implementation of a desired feature, and that imposes the following limitations:\n\n* no way to differentiate \u0027I want this\u0027 (e.g. \u0027this affects me\u0027 on bugs) from \u0027I want to track progress\u0027 (subscribe), since the presumption is that the feature is going to happen if a blueprint is tracking it.\n* blueprints have only one comment area and it can be changed arbitrarily (vs bugs having immutable comments)\n* blueprints don\u0027t appear to support tagging (bugs do)\n* the values for a blueprint\u0027s \u0027direction\u0027 and \u0027definition\u0027 fields are geared towards a work item that should happen, rather than one that might.  There isn\u0027t really a way to reject (e.g. invalid, wontfix) or defer (low, wishlist) a feature request, and that would seem to be an important capability.\n\nI think there is also an advantage to treating \u0027issues\u0027 (e.g. questions, bugs and feature requests) uniformly in the triaging process.  It allows prioritization to consider all demands on resources rather than having those demands silo\u0027d.  Once a feature has been triaged as important enough to devote resources to, then it can be upgraded to tracking as a blueprint.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"df4fb78183e8dd03303dd89080b7487adf09acd9","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_c25baf2d","line":23,"in_reply_to":"7ad32947_16d0d152","updated":"2015-04-27 18:50:59.000000000","message":"I went back and forth on this. At first, I was onboard with bugs. But I thought about it and changed my mind to BPs. I didn\u0027t like the migration from bugs to BPs.\n\nHowever, you make a strong case for this. And ultimately, as long as people ok with migrating certain feature requests to BPs, then I\u0027m fine with starting with bugs.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"2be418aaf074f7ee4ee79fbe54e783be7af21c73","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_67ef4ab1","line":23,"in_reply_to":"7ad32947_4290bfec","updated":"2015-04-27 20:08:28.000000000","message":"I think we might be trying to find a one-size-fits-all solution to a problem with layers.  Trivial?  bug.  Less so?  bp.  Even less so?  spec.  Or something, e.g.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"8fb5cef67bd46db5d273f5449f52c1f23d475c2f","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_4aa1f5a8","line":23,"in_reply_to":"7ad32947_4290bfec","updated":"2015-04-27 20:49:28.000000000","message":"the one minor issue I have with using launchpad bugs as feature requests is the obvioius, they\u0027re not bugs.  It might be confusing to new people who want to make a feature request. Then again, it could be the right amount of confusing and simple to weed out the superfluous requests.  No real objection here, just commentary.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_b320044b","line":23,"in_reply_to":"7ad32947_4aa1f5a8","updated":"2015-04-27 22:37:19.000000000","message":"It might be worth considering that a user reporting an issue may not know if a bug or a feature request should be the result.  The primitive in most \u0027bug\u0027 trackers is actually the \u0027issue\u0027 and not strictly a bug (witness github and bugzilla).","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_a98f6522","line":23,"in_reply_to":"7ad32947_b320044b","updated":"2015-04-28 11:03:26.000000000","message":"I believe bugs are a better place for initial RFE discussion, then they can be moved to BP, this will remove a lot of noise on the BP side, and probably operators and users are more familiar with the bug submission process than BP.\n\nWe could tag rfe bugs with the \"RFE\" tag, not sure if adding [RFE] in front of the subject makes them easier to spot if they\u0027re wrongly tagged (the tagging input is hidden after an \"Extra Options\" click)","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"19eaf7066ad42e5a0cc9521e2633420c9eb8bb78","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":23,"context_line":"Feature requests are tracked as Launchpad blueprints, and allow for the"},{"line_number":24,"context_line":"submission and review of these early ideas before code is submitted. This"},{"line_number":25,"context_line":"allows the team to verify the validity of a feature request before the"},{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_4290bfec","line":23,"in_reply_to":"7ad32947_c25baf2d","updated":"2015-04-27 19:18:52.000000000","message":"I think I lean toward using bugs too.  I\u0027m interested to see what process we put around this.  I do have some concerns with doing this with bugs.\n\n* There is some ambiguity around the term \"wishlist\".  According to its description, it should be used for feature requests.  But, it also implies lower priority.  If we use \"wishlist\" for all new features then we cannot use it to mark the relative importance of new features.\n* I\u0027m concerned about the \"migration\" to a BP.  What happens to the bug when a blueprint is created?  Is there a good way to cross-link the bug and the BP or will that be manual?  This isn\u0027t a huge concern but I am a little worried that it will be difficult to track a feature request through this process.\n\nI wonder if we should just forget blueprints and use a tag in the bugs to differentiate feature requests from bugs.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"19eaf7066ad42e5a0cc9521e2633420c9eb8bb78","unresolved":false,"context_lines":[{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"},{"line_number":27,"context_line":"written. It also allows the community to express interest in a feature by"},{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_d3814bfd","line":29,"updated":"2015-04-27 19:18:52.000000000","message":"Any links to examples of this history?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":26,"context_line":"process of submitting a full specification is undertaken, or code is"},{"line_number":27,"context_line":"written. It also allows the community to express interest in a feature by"},{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_5bf55b81","line":29,"in_reply_to":"7ad32947_d3814bfd","updated":"2015-04-28 16:45:29.000000000","message":"I would point you at the GBP debacle from last summer on the mailing list and IRC meetings, especially this meeting [1] for an example of the kind of egregious behavior I\u0027m talking about.\n\n[1] http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-08-11-21.00.log.txt","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"d90f029f827814f6d284ac02b1cd040ff505bed8","unresolved":false,"context_lines":[{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_55cbec72","line":31,"updated":"2015-04-28 15:47:19.000000000","message":"I can understand not tolerating this activity, with the minimal outcome of dropping whatever feature was proposed by \"gaming the system\".\n\nBut instead of calling someone out on the ML, which may or may not deter others, should you just be very specific on the torture, err, consequences, for such action?  Will that person not be able to submit any more code for the cycle?  Or lose some responsibility (eg core) ?  Or ???","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_301758ef","line":31,"updated":"2015-04-27 15:52:07.000000000","message":"preamble: anything works for me, and this avoids the issue that a feature request might become a shortcut to get a spec approved.\n\nhowever, your solution is opening up \"voting\" not only to the openstack community, but to all launchpad users. I think this is a non-issue. The only issue could be that sometimes one subscribes to a blueprint he/she disagrees with... so you should clarify that registering for a blueprint is pretty much like putting a like on a facebook post.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_fb11c7b0","line":31,"in_reply_to":"5ad0253b_55cbec72","updated":"2015-04-28 16:45:29.000000000","message":"Yes to all of what you\u0027ve indicated. The system is built on trust, once that is lost, it falls apart. It\u0027s as simple as that.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"8fb5cef67bd46db5d273f5449f52c1f23d475c2f","unresolved":false,"context_lines":[{"line_number":28,"context_line":"subscribing to the blueprint in Launchpad. Note the temptation to game the"},{"line_number":29,"context_line":"system exists, but given the history in Neutron for this type of activity,"},{"line_number":30,"context_line":"it will not be tolerated and will be called out as such in public on the"},{"line_number":31,"context_line":"mailing list."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_6a9cb169","line":31,"in_reply_to":"7ad32947_301758ef","updated":"2015-04-27 20:49:28.000000000","message":"can we use facebook for feature requests instead? :)","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":35,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":36,"context_line":"  simple Launchpad blueprint with the feature request is all that is"},{"line_number":37,"context_line":"  required."},{"line_number":38,"context_line":"* Full up-front design no longer required, but will be required as part of"},{"line_number":39,"context_line":"  devref along with code."},{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_76adc530","line":38,"updated":"2015-04-27 18:36:01.000000000","message":"Consider clarifying this statement to indicate that we don\u0027t want to do full up-front design at all.  Something like the following is suggested:\n\n\"A high-level design overview should merge to devref before code implementing that design should be considered for serious review, and that design should be evolved to keep in sync (and accumulate detail) in the implementing changes.\"","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":35,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":36,"context_line":"  simple Launchpad blueprint with the feature request is all that is"},{"line_number":37,"context_line":"  required."},{"line_number":38,"context_line":"* Full up-front design no longer required, but will be required as part of"},{"line_number":39,"context_line":"  devref along with code."},{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_6e6ef3ca","line":38,"in_reply_to":"7ad32947_76adc530","updated":"2015-04-28 11:03:26.000000000","message":"+1 for the clarification.\n\nExtending that, I\u0027d propose:\n\nWhat about having the devref + implementation in the same patch?, one could start by writing the devref , and then extend it with the real code, this way we\u0027re sure everything is in sync.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":35,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":36,"context_line":"  simple Launchpad blueprint with the feature request is all that is"},{"line_number":37,"context_line":"  required."},{"line_number":38,"context_line":"* Full up-front design no longer required, but will be required as part of"},{"line_number":39,"context_line":"  devref along with code."},{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_bb0b4f7d","line":38,"in_reply_to":"7ad32947_76adc530","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  simple Launchpad blueprint with the feature request is all that is"},{"line_number":37,"context_line":"  required."},{"line_number":38,"context_line":"* Full up-front design no longer required, but will be required as part of"},{"line_number":39,"context_line":"  devref along with code."},{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_0e665fed","line":39,"updated":"2015-04-28 11:03:26.000000000","message":"Hmm, probably mestery you were trying to express the same I\u0027ve done right above?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Full up-front design no longer required, but will be required as part of"},{"line_number":39,"context_line":"  devref along with code."},{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_ae82cb50","line":41,"updated":"2015-04-28 11:03:26.000000000","message":"Sounds good.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_6b93a1a4","line":43,"updated":"2015-04-27 15:52:07.000000000","message":"Fail-fast or \"put your soul to rest quickly\"?\n\nSorry about the snarky comment, which is pointing to the fact the on the one hand you are setting up a community-driver prioritization process, but on the other hand you are also stating \"no matter what the community thinks, it\u0027s the driver team that decides\".\n\nI think the truth is that the driver team will take into account as much as possible community support for features, but ultimately approval of a feature requests depend on how much it fits within the release goals, or on potential conflicts with other activities in the same area.\n\nPerhaps you could make the above part of your document if you agree with it.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"8fb5cef67bd46db5d273f5449f52c1f23d475c2f","unresolved":false,"context_lines":[{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_6a73914e","line":43,"in_reply_to":"7ad32947_51a7734f","updated":"2015-04-27 20:49:28.000000000","message":"+1","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_8eeeef20","line":43,"in_reply_to":"7ad32947_6a73914e","updated":"2015-04-28 11:03:26.000000000","message":"+1","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_5bad5b30","line":43,"in_reply_to":"7ad32947_6b93a1a4","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"4c8088a8a09924a12d37128048d4025c9a1cbe2c","unresolved":false,"context_lines":[{"line_number":40,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_51a7734f","line":43,"in_reply_to":"7ad32947_6b93a1a4","updated":"2015-04-27 18:03:16.000000000","message":"I agree with Salvatore, the reality in which we live should be written down so that it\u0027s communicated ahead of time to people who submit feature requests. It might soften the rejection process for some.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_b177e7d3","line":44,"updated":"2015-04-27 18:36:01.000000000","message":"Consider emphasizing the idea that triaging of issues (bugs and features) is an ongoing process in which some priority churn is a recognized cost of constantly shifting circumstances.  Hopefully there will be more acceptance of this if the process is more open and accountable.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"19eaf7066ad42e5a0cc9521e2633420c9eb8bb78","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_22b6e3dc","line":44,"updated":"2015-04-27 19:18:52.000000000","message":"I read this incorrectly the first time.  I think maybe it could be clarified:\n\n\"Features which had been targeted to a release and miss that target will be automatically ...\"\n\nTo be fair, you did write it correctly; I misunderstood it not realizing that this only applied to features that had been accepted and targeted to a release.  My suggestion is only to try to avoid letting others misunderstand it in the same way.\n\nAlso, +1 to Maru\u0027s suggestion.  I think it is important to re-review priorities at regular intervals.  I\u0027m not sure that the history of a feature request\u0027s acceptance or refusal necessarily makes it a priority for the next or any future release.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_9b489389","line":44,"in_reply_to":"7ad32947_22b6e3dc","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  the source code."},{"line_number":42,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":43,"context_line":"  cycle, with quick feedback."},{"line_number":44,"context_line":"* Features which do not land in their targeted release will be automatically"},{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_9b71b3e3","line":44,"in_reply_to":"7ad32947_b177e7d3","updated":"2015-04-28 16:45:29.000000000","message":"Done","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_f0e1e0d1","line":48,"updated":"2015-04-27 15:52:07.000000000","message":"I know for a fact that contributors hardly accept a \"NO\" without fighting it.\nIf we\u0027re moving to launchpad we need to be aware that the bp whiteboard is rubbish for any kind of discussion.\nI would be ok if any discussion pertaining blueprint rejection for a release is moved to the -dev mailing list","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_7b5ed746","line":48,"in_reply_to":"7ad32947_4e469724","updated":"2015-04-28 16:45:29.000000000","message":"Bugs instead of BPs.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  promoted to the subsequent release, unless they no longer fall in the"},{"line_number":46,"context_line":"  project scope."},{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_4e469724","line":48,"in_reply_to":"7ad32947_f0e1e0d1","updated":"2015-04-28 11:03:26.000000000","message":"That\u0027s true, whiteboard is a bit of a mess sometimes, -dev mailing list could be used as a formal method for blueprint rejection, and then use a link on the blueprint to the ML.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Specs and Feature Requests"},{"line_number":53,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_ab8779d6","line":50,"updated":"2015-04-28 11:27:09.000000000","message":"It is nice.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Specs and Feature Requests"},{"line_number":53,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_906d0c35","line":50,"updated":"2015-04-27 15:52:07.000000000","message":"strongly agreed","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"3cf2f6ebd0e766371db575b2c7619f69a65174a1","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Specs and Feature Requests"},{"line_number":53,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_df95be40","line":50,"in_reply_to":"7ad32947_87db861b","updated":"2015-04-28 06:31:03.000000000","message":"+1","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"2be418aaf074f7ee4ee79fbe54e783be7af21c73","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Specs and Feature Requests"},{"line_number":53,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_87db861b","line":50,"in_reply_to":"7ad32947_906d0c35","updated":"2015-04-27 20:08:28.000000000","message":"+1","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":47,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":48,"context_line":"  are given firm answers quickly."},{"line_number":49,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":50,"context_line":"  for deadlines."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Specs and Feature Requests"},{"line_number":53,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_ee6c439e","line":50,"in_reply_to":"7ad32947_df95be40","updated":"2015-04-28 11:03:26.000000000","message":"+1, they are going to be prioritized, so.. as long as we do it right, it should be ok.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":55,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":56,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":57,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":58,"context_line":"blueprints to track feature requests and target them to milestone releases."},{"line_number":59,"context_line":"Richer documentation will now be required in-tree when you submit code for"},{"line_number":60,"context_line":"the feature request."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_0ee53f08","line":58,"updated":"2015-04-28 11:27:09.000000000","message":"I think \"to track status of feature requests\" is clearer description. s In my understanding, \"feature requests\" are only with small descriptions and are mainly used to track their status.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":56,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":57,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":58,"context_line":"blueprints to track feature requests and target them to milestone releases."},{"line_number":59,"context_line":"Richer documentation will now be required in-tree when you submit code for"},{"line_number":60,"context_line":"the feature request."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Feature Request Proposal"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_2cd01c53","line":59,"updated":"2015-04-27 18:36:01.000000000","message":"Consider rephrasing this last sentence to be something like the following:\n\nRich in-tree developer documentation is required for all new features, and documentation updates should be included in each implementing change rather than being added after development is complete.\n\nedit: not sure if this suggestion has merit since lines 95 on seem to say the same thing.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":57,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":58,"context_line":"blueprints to track feature requests and target them to milestone releases."},{"line_number":59,"context_line":"Richer documentation will now be required in-tree when you submit code for"},{"line_number":60,"context_line":"the feature request."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Feature Request Proposal"},{"line_number":63,"context_line":"------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_0b5e6de9","line":60,"updated":"2015-04-27 15:52:07.000000000","message":"I think this is consistent with my opinion that the specification repository has become a bottleneck and failed to fulfil its purpose.\n\nJust a personal question... what am I supposed to now with my liberty specs?\n\nAs a corollary no code for a blueprint will be merge if the corresponding devref stuff is not at least on gerrit for review.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"3cf2f6ebd0e766371db575b2c7619f69a65174a1","unresolved":false,"context_lines":[{"line_number":58,"context_line":"blueprints to track feature requests and target them to milestone releases."},{"line_number":59,"context_line":"Richer documentation will now be required in-tree when you submit code for"},{"line_number":60,"context_line":"the feature request."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Feature Request Proposal"},{"line_number":63,"context_line":"------------------------"},{"line_number":64,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_7f4b4ab1","line":61,"updated":"2015-04-28 06:31:03.000000000","message":"We must consider who need the documentations. I believe that detailed specifications was also needed by ops which don\u0027t agree with  implement first. I don\u0027t think that spec was effective against ops. However, we must consider so that ops can participate in Neutron community.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"3cf2f6ebd0e766371db575b2c7619f69a65174a1","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"The first step in proposing a feature request is to register a blueprint in"},{"line_number":66,"context_line":"`Launchpad \u003chttps://blueprints.launchpad.net/neutron\u003e`_. The request should"},{"line_number":67,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":68,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":69,"context_line":"Direction should be set to \"Needs Approval\" and the definition should be set"},{"line_number":70,"context_line":"to \"Discussion.\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_ffe19aff","line":67,"updated":"2015-04-28 06:31:03.000000000","message":"We need a example required at least. Because we have used launchpad only once but the quality was inconsistent and, consequently, made launchpad useless.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"55129000e1431f79597a43252a7affb838d60619","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"The first step in proposing a feature request is to register a blueprint in"},{"line_number":66,"context_line":"`Launchpad \u003chttps://blueprints.launchpad.net/neutron\u003e`_. The request should"},{"line_number":67,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":68,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":69,"context_line":"Direction should be set to \"Needs Approval\" and the definition should be set"},{"line_number":70,"context_line":"to \"Discussion.\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ad0253b_be6d7dce","line":67,"in_reply_to":"7ad32947_0e93ff5c","updated":"2015-04-28 16:45:29.000000000","message":"Agree with Akihiro.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"The first step in proposing a feature request is to register a blueprint in"},{"line_number":66,"context_line":"`Launchpad \u003chttps://blueprints.launchpad.net/neutron\u003e`_. The request should"},{"line_number":67,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":68,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":69,"context_line":"Direction should be set to \"Needs Approval\" and the definition should be set"},{"line_number":70,"context_line":"to \"Discussion.\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_0e93ff5c","line":67,"in_reply_to":"7ad32947_ffe19aff","updated":"2015-04-28 11:27:09.000000000","message":"Launchpad is a bad place to discuss even for use cases, so I personally would not like to require anything, and requiring just \"clear and concise description\" is enough. I think even \"of use cases\" is not a requirement.\n\nIf the description has too less information, we can request authors to add a bit more.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"The first step in proposing a feature request is to register a blueprint in"},{"line_number":66,"context_line":"`Launchpad \u003chttps://blueprints.launchpad.net/neutron\u003e`_. The request should"},{"line_number":67,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":68,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":69,"context_line":"Direction should be set to \"Needs Approval\" and the definition should be set"},{"line_number":70,"context_line":"to \"Discussion.\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_eef1e3ce","line":67,"in_reply_to":"7ad32947_ffe19aff","updated":"2015-04-28 11:03:26.000000000","message":"May be we can define some sort of template for blueprint RFEs as we had for specs?, something short, of course.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"bb3a1516832e015d94a8106ca73e2ee4c708ae96","unresolved":false,"context_lines":[{"line_number":80,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":81,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":82,"context_line":"submissions, and will be tracked as either bugs or as the existing LP BP."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"Feature Request Acceptance"},{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_1363431c","line":83,"updated":"2015-04-27 16:59:45.000000000","message":"So if I\u0027m a new contributor, dipping in my toe.  I submit an FR, it gets approved, now I\u0027m kind of lost, but go ahead and code up my thing and submit it.  There is about a 100% chance that either: 1) a reviewer tells me to rewrite it all, or 2) I put up something partial, and get a billion hammer darts telling me that I need unit tests and _LE() and....  It feels like an optional place to discuss approach/design is needed.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":80,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":81,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":82,"context_line":"submissions, and will be tracked as either bugs or as the existing LP BP."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"Feature Request Acceptance"},{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_53c53059","line":83,"in_reply_to":"7ad32947_1363431c","updated":"2015-04-27 22:37:19.000000000","message":"The intention is for the next step after acceptance of a feature request to be submit a change that documents (in devref) the high-level details (the good parts of the spec) of the proposed implemention.  Until that change merges, no code submissions for that feature should be considered for merge.\n\nPlease check lines 96-102, and consider suggesting how to make the intention clear to yourself in others.  Maybe it needs to be stated more explicitly and earlier in the document?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":80,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":81,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":82,"context_line":"submissions, and will be tracked as either bugs or as the existing LP BP."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"Feature Request Acceptance"},{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_4e11f7ab","line":83,"in_reply_to":"7ad32947_53c53059","updated":"2015-04-28 11:27:09.000000000","message":"Agree with Maru. L.96-102 describes the expected action which feature proposer is encouraged to take after registering launchpad blueprints.\n\nIf I am new to this new process, moving the paragraph of L.96-102 is really helpful.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6788,"name":"Rossella Sblendido","email":"rsblendido@suse.com","username":"rossella-o"},"change_message_id":"72a5a4937984e8b8b39444910dbad20cb19d91c0","unresolved":false,"context_lines":[{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Once a feature request or bug has been deemed as fitting within the framework for"},{"line_number":88,"context_line":"the upcoming release, the neutron-drivers team will approve the feature request"},{"line_number":89,"context_line":"by updating the Launchpad blueprint to have a Direction of \"Approved\" and a"},{"line_number":90,"context_line":"Definition of \"Approved.\" The team will also map the feature request to a milestone"},{"line_number":91,"context_line":"for the existing release. If the neutron-drivers team feels as if the feature does"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9abe1de1_6f904c96","line":88,"updated":"2015-04-27 13:30:19.000000000","message":"is it a requirement for the feature request acceptance to have volunteers that will implement the feature? I mean the submitter might not be a developer or might not be interested in implementing the feature.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Once a feature request or bug has been deemed as fitting within the framework for"},{"line_number":88,"context_line":"the upcoming release, the neutron-drivers team will approve the feature request"},{"line_number":89,"context_line":"by updating the Launchpad blueprint to have a Direction of \"Approved\" and a"},{"line_number":90,"context_line":"Definition of \"Approved.\" The team will also map the feature request to a milestone"},{"line_number":91,"context_line":"for the existing release. If the neutron-drivers team feels as if the feature does"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_d417d8eb","line":88,"in_reply_to":"7ad32947_85682cbc","updated":"2015-04-28 11:27:09.000000000","message":"Agree in the direction.\n\nIt is important how to coordinate such orphaned feature requests too. one idea is to use launchpad drafter and assignee. Blacking assignee is one possible option.\n\nAnother point is the authorship of proposed reviews.\nIn general, we are suggesting to merge code along with appropriate devref doc. In a case of orphaned/call-for-developer features, it does not work. Discussion of usecase or high-level abstraction/API are also important and we can merge docs at some point and find implementors. Just an idea.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"30b191daf7fde969bf9d34ea0ead78e98f7030b2","unresolved":false,"context_lines":[{"line_number":85,"context_line":"---------------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Once a feature request or bug has been deemed as fitting within the framework for"},{"line_number":88,"context_line":"the upcoming release, the neutron-drivers team will approve the feature request"},{"line_number":89,"context_line":"by updating the Launchpad blueprint to have a Direction of \"Approved\" and a"},{"line_number":90,"context_line":"Definition of \"Approved.\" The team will also map the feature request to a milestone"},{"line_number":91,"context_line":"for the existing release. If the neutron-drivers team feels as if the feature does"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_85682cbc","line":88,"in_reply_to":"9abe1de1_6f904c96","updated":"2015-04-27 15:05:16.000000000","message":"No, in fact, you can submit a feature request without the intent to actually implement it. Over my last two cycles as PTL I\u0027ve had multiple people reach out to indicate they have cycles to work on Neutron, but need something to do. These orphaned feature requests would be perfect for such cases, in addition to bugs which we already have.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":12912,"name":"John Belamaric","email":"jbelamaric@infoblox.com","username":"johnbelamaric"},"change_message_id":"40eedaea2e685140727c07496f25b58eb3dcc27a","unresolved":false,"context_lines":[{"line_number":91,"context_line":"for the existing release. If the neutron-drivers team feels as if the feature does"},{"line_number":92,"context_line":"not fit within the scope of the current release, the Definition will be set to"},{"line_number":93,"context_line":"\"Pending Approval\" to indicate the feature request makes sense in the context of"},{"line_number":94,"context_line":"Neutron, but does not fit in the current release."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"Please note a high-level overview of the proposed feature should land in the"},{"line_number":97,"context_line":"Neutron devref along with the code for the feature. This will naturally evolve into"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_30d611c6","line":94,"updated":"2015-04-28 13:54:58.000000000","message":"Deciding the scope and whether it will fit would seem to be difficult from the minimal \"requirements\" definition that is described in this document. Wouldn\u0027t there need to be at least a high-level design or idea of the approach before a decision could be made on scope?\n\nI am all for streamlining the process here, but I am not getting a clear sense from this where the design discussion happens.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"cfcb6268c8018314bd8c1846f0a4ee20ac429cfe","unresolved":false,"context_lines":[{"line_number":93,"context_line":"\"Pending Approval\" to indicate the feature request makes sense in the context of"},{"line_number":94,"context_line":"Neutron, but does not fit in the current release."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"Please note a high-level overview of the proposed feature should land in the"},{"line_number":97,"context_line":"Neutron devref along with the code for the feature. This will naturally evolve into"},{"line_number":98,"context_line":"the actual developer documentation as the feature is worked on. Please note this"},{"line_number":99,"context_line":"documentation should evolve over the course of feature development. It should evolve"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_2e8a3bc0","line":96,"updated":"2015-04-28 11:27:09.000000000","message":"Once we land this proposal, the next step will be to define what are expected to be covered: background/motivations, proposed approach/design, use cases, high-level behavior and so on. Most are already covered by spec templates. It is important for larger feature requests.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"7843cb549b5ca5df8172ff0529c61bf77c3d0b98","unresolved":false,"context_lines":[{"line_number":99,"context_line":"documentation should evolve over the course of feature development. It should evolve"},{"line_number":100,"context_line":"as other feature requests naturally interact with or enhance this area of the code."},{"line_number":101,"context_line":"Thus, feature requests which modify existing code should submit devref updates for"},{"line_number":102,"context_line":"these areas of the documentation as well."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"Feature Requests Slipping"},{"line_number":105,"context_line":"-------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_0b054dc1","line":102,"updated":"2015-04-27 15:52:07.000000000","message":"perhaps this paragraph might be integrated with the above comment on devref I posted.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":114,"context_line":"  not be targeted at the next release and the Definition will be left as \"Pending"},{"line_number":115,"context_line":"  Approval.\""},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"This allows for fast-tracking blueprints into future releases."},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"Documentation for the Feature Request"},{"line_number":120,"context_line":"-------------------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_47aa1172","line":117,"updated":"2015-04-27 18:36:01.000000000","message":"It may be worth de-emphasizing needing ideas like \u0027fast tracking\u0027 in favor or regular effort being directed towards prioritization (maybe every milestone and at the start of every cycle)?  While we do need to minimize the potential for unnecessary lobbying, I think it\u0027s counterproductive to evaulate priority only once a cycle.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"d700a73c86f9f377d4d669828b9f52f20ea18012","unresolved":false,"context_lines":[{"line_number":119,"context_line":"Documentation for the Feature Request"},{"line_number":120,"context_line":"-------------------------------------"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_67dbcd1c","line":122,"updated":"2015-04-27 18:36:01.000000000","message":"This section and lines 92-102 appear to cover largely the same ground.  Consider using this section to highlight the intended relationship between developer and user documentation, or otherwise reconcile the 2 paragraphs.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"bb3a1516832e015d94a8106ca73e2ee4c708ae96","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_33463fc0","line":126,"updated":"2015-04-27 16:59:45.000000000","message":"We\u0027re removing the design spec requirement and adding a doc requirement. There is a real danger of terrible docs just to meet the check-off requirement.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"0b6e0285e9a08ab693bec9ceaf2605363f351ffd","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_073bf6ec","line":126,"in_reply_to":"7ad32947_27c152e5","updated":"2015-04-27 20:16:16.000000000","message":"Ha, well, this issue is far from a deal-killer to me. If we can address how someone can optionally get design buy-in before coding, I\u0027m happy.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"4c8088a8a09924a12d37128048d4025c9a1cbe2c","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_cc72c8ad","line":126,"in_reply_to":"7ad32947_33463fc0","updated":"2015-04-27 18:03:16.000000000","message":"This is why reviewers will have to force the devref changes in the same patches that change the code. If the devref isn\u0027t up to par, slap a -1 on it. This is *the* most effective way to ensure quality documentation. (Same reason why you\u0027d want in-tree tests, and not have people promise they\u0027ll add tests later in some other repo).","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"2be418aaf074f7ee4ee79fbe54e783be7af21c73","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_c7d17efd","line":126,"in_reply_to":"7ad32947_425f9f0e","updated":"2015-04-27 20:08:28.000000000","message":"I think any process that puts onus on review is fundamentally broken. Reviews are a final check, another set of eyeballs, not a primary means of ensuring quality.  At least, they\u0027re pretty bad at being the primary means of ensuring quailty.  In this case, of docs standards.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"8fb5cef67bd46db5d273f5449f52c1f23d475c2f","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_8a938dfa","line":126,"in_reply_to":"7ad32947_425f9f0e","updated":"2015-04-27 20:49:28.000000000","message":"we\u0027re looking at huge gerrit chains with all of this.  I\u0027ve done a few 5+ gerrit chains and each time a part of me died.  There\u0027s not much of me left.\n\nHowever, the bigger pain points of the chain was because the chain was then made longer because other reviewers started depending on the initial chain.  If it is the same author maintaining it all then it shouldn\u0027t be too big of a problem.  Just the thought of it makes me cry though.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":6951,"name":"Brandon Logan","email":"brandon.logan@rackspace.com","username":"brandon-logan"},"change_message_id":"caab96c2c497420cd2d8be76d329df3cf14fbe49","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_aee7763f","line":126,"in_reply_to":"7ad32947_7306ec21","updated":"2015-04-28 02:33:02.000000000","message":"I almost convinced myself into defending gerrit chains *shivers*, but I think the gerrit chain argument is one that can be had outside of this document.  However, with the increase of deliverables this spec defines (and needing tests in tree as well) there\u0027s going to be many reviews with a ton of lines or many chains with a ton of reviews in most cases.  In any case, the learning curve for new contributors has increased and this will continue that increase.  They need to know everything to include in their patches, not just code and unit tests and not to mention know the correct way submit the code for easy review.\n\nObviously communication is key with a core, but like doug said that is the rare case.  It really is a lot a new contributor now needs to know to get their code in, and it\u0027s going to take a lot of time.  When this is finalized can we get a list of everything a fully implemented new feature should have before it is considered complete?","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"7539a079eab5ab84498b032ba2e43c338e8f93c9","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_b37c8421","line":126,"in_reply_to":"7ad32947_8a938dfa","updated":"2015-04-27 22:37:19.000000000","message":"Stop posting chains.  It\u0027s corrosive to all involved.  Iterate on the smallest thing that could possibly move the effort forward in close coordination with at least one reviewer, and merge it.  Rinse, repeat.  This also requires that reviewers be more accepting of changes whose target is expected to evolve quickly, rather than trying to get it perfect the first time.  Without this kind of iteration, we\u0027re doing waterfall and of course it sucks.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"96441a0189a0fe87d76f1dfc565cb04c0b349e6a","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_89d5c944","line":126,"in_reply_to":"7ad32947_aee7763f","updated":"2015-04-28 11:03:26.000000000","message":"The primary thing against -specs, is that it\u0027s going to be outdated and rotten very very quickly, it\u0027s better if we can turn them in to up-to-date design documents instead, because we can require in the same patch updates to the design document and the code.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"eec5bf2ed47322d35b8dcad3412de6e0ec0ba102","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_7306ec21","line":126,"in_reply_to":"7ad32947_b37c8421","updated":"2015-04-27 22:59:02.000000000","message":"Whoa, whoa, there are a couple of *major* hand waives going on in your replies. \n\nFirstly, chains are a fact of life for those that aren\u0027t working with cores on a day to day basis. The process *must* realize and accomodate that, or it\u0027s off in wishes and fairies land. New contributors will not iterate this quickly, and we can\u0027t leave them behind.\n\nSecond, we\u0027re slimming the spec process, but requiring docs, which are arguably harder to produce than a spec, as the intended audience is much broader) That does the opposite of the stated intention of making things easier, it actually adds friction.  \"We don\u0027t want your code unless you\u0027re a tech writer!\"\n\nAnd third, the process you outlined above, all we\u0027re doing is moving the specs repo under devref, and insisting it be docs instead. At which point, why? If it needs enough spec to be a doc in devref merged before coding, why not in -specs?  That\u0027s not streamlining anything.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"a2fbd4dc5839ef1e951776d6558fea1af6e0771e","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_27c152e5","line":126,"in_reply_to":"7ad32947_c7d17efd","updated":"2015-04-27 20:12:28.000000000","message":"Our current docs situation likely is awful, and the current specs process hasn\u0027t helped that in any way. I\u0027m making an effort to improve that here. You\u0027re right, it may not be ideal. But much like our testing (which was awful before Kilo), it will get better if we focus on it.\n\nFamous last words hopefully don\u0027t apply here. :)","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"df4fb78183e8dd03303dd89080b7487adf09acd9","unresolved":false,"context_lines":[{"line_number":123,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":124,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":125,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":126,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ad32947_425f9f0e","line":126,"in_reply_to":"7ad32947_cc72c8ad","updated":"2015-04-27 18:50:59.000000000","message":"Agree with Assaf.","commit_id":"c5c1a6bd46729741bfb80ce81ee2e1fda477ff05"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"deb1a0a70ae7c3de2700ed5be85c710b42f3331f","unresolved":false,"context_lines":[{"line_number":20,"context_line":"---------------"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The previous specs repository documented above is no longer used for Liberty"},{"line_number":23,"context_line":"development. It is a relic of the past who\u0027s purpose is to serve as a"},{"line_number":24,"context_line":"reminder to future generations of experiments we\u0027ve tried in managing the"},{"line_number":25,"context_line":"inbound workload."},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ad0253b_be3a1de6","line":23,"updated":"2015-04-28 17:10:16.000000000","message":"nit: /who\u0027s/whose/","commit_id":"0057fb6363f5e41925402f641a07e08bd762e636"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"389b970ce762da66216646e0c886172308fd9b0f","unresolved":false,"context_lines":[{"line_number":20,"context_line":"---------------"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The previous specs repository documented above is no longer used for Liberty"},{"line_number":23,"context_line":"development. It is a relic of the past who\u0027s purpose is to serve as a"},{"line_number":24,"context_line":"reminder to future generations of experiments we\u0027ve tried in managing the"},{"line_number":25,"context_line":"inbound workload."},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ad0253b_e42a447e","line":23,"in_reply_to":"5ad0253b_be3a1de6","updated":"2015-04-28 17:34:02.000000000","message":"Done","commit_id":"0057fb6363f5e41925402f641a07e08bd762e636"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"deb1a0a70ae7c3de2700ed5be85c710b42f3331f","unresolved":false,"context_lines":[{"line_number":70,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":71,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":72,"context_line":"  past."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Specs and Feature Requests"},{"line_number":75,"context_line":"--------------------------"},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ad0253b_893a89cc","line":73,"updated":"2015-04-28 17:10:16.000000000","message":"Alright, so in effect, the changes are:\n\n- Start the process in launchpad, wait for drivers.\n- Write a spec, get it reviewed\n- Write code (plus docs!)\n\nAnd do this at any time, not just during the spec window (this point is good.)\n\nSo the actual changes are:\n\n- No more spec window\n- A higher class of dev docs is now required.\n\nIt\u0027s effectively heavier-weight than before, and the repo elimination is entirely cosmetic. I don\u0027t see any reason it won\u0027t work, but some of it seems change for change\u0027s sake.","commit_id":"0057fb6363f5e41925402f641a07e08bd762e636"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"389b970ce762da66216646e0c886172308fd9b0f","unresolved":false,"context_lines":[{"line_number":70,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":71,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":72,"context_line":"  past."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Specs and Feature Requests"},{"line_number":75,"context_line":"--------------------------"},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5ad0253b_245f1c10","line":73,"in_reply_to":"5ad0253b_893a89cc","updated":"2015-04-28 17:34:02.000000000","message":"No, in fact, I\u0027m not sure how you read into that. In fact, the process is:\n\n* Propose bug as feature request.\n* neutron-drivers targets bug to milestone.\n* develop code, tests, documentation together.\n* submit together and get reviewed.\n* profit.","commit_id":"0057fb6363f5e41925402f641a07e08bd762e636"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"ef19288e93f0f9655a4dad87fda4d0ff7f962858","unresolved":false,"context_lines":[{"line_number":89,"context_line":"`Launchpad \u003chttps://bugs.launchpad.net/neutron\u003e`_. The request should"},{"line_number":90,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":91,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":92,"context_line":"bug should be tagged with the \u0027RFE\u0027 tag."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"Feature Request Review"},{"line_number":95,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ad0253b_4481f88e","line":92,"updated":"2015-04-28 17:54:00.000000000","message":"Could we provide a template for RFEs so people can know what details are the most important?","commit_id":"b561bb3a46052780874144f493adf2b75121a59b"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"c461bb2a39f0b1c7ac264156f230cf9d2f983a15","unresolved":false,"context_lines":[{"line_number":89,"context_line":"`Launchpad \u003chttps://bugs.launchpad.net/neutron\u003e`_. The request should"},{"line_number":90,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":91,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":92,"context_line":"bug should be tagged with the \u0027RFE\u0027 tag."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"Feature Request Review"},{"line_number":95,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5ad0253b_b710fba9","line":92,"in_reply_to":"5ad0253b_4481f88e","updated":"2015-04-28 19:59:03.000000000","message":"This makes some sense. I can reference this, but not have it in this document. I\u0027ll add that logic.","commit_id":"b561bb3a46052780874144f493adf2b75121a59b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":39,"context_line":"Feature requests are tracked as Launchpad bugs, tagged with the new \u0027RFE\u0027 tag,"},{"line_number":40,"context_line":"and allow for the submission and review of these early ideas before code is"},{"line_number":41,"context_line":"submitted. This allows the team to verify the validity of a feature request"},{"line_number":42,"context_line":"before the process of submitting a devref documentation is undertaken, or code"},{"line_number":43,"context_line":"is written. It also allows the community to express interest in a feature by"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_aa41b03b","line":40,"updated":"2015-04-29 19:34:28.000000000","message":"We have a bug section in the IRC meeting; I am assuming that these \u0027bugs\u0027 are not to be taken into account, but are going to be discussed during neutron-drivers meetings, as indicated below. If so, are we going to have the latter meeting on a regular basis?","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":39,"context_line":"Feature requests are tracked as Launchpad bugs, tagged with the new \u0027RFE\u0027 tag,"},{"line_number":40,"context_line":"and allow for the submission and review of these early ideas before code is"},{"line_number":41,"context_line":"submitted. This allows the team to verify the validity of a feature request"},{"line_number":42,"context_line":"before the process of submitting a devref documentation is undertaken, or code"},{"line_number":43,"context_line":"is written. It also allows the community to express interest in a feature by"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_266398b3","line":40,"in_reply_to":"3acd31a7_aa41b03b","updated":"2015-04-29 19:55:07.000000000","message":"I think we\u0027ll have to yes, because we\u0027re not going to have any deadlines for RFEs to be limited by.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":46,"context_line":"activity, it will not be tolerated and will be called out as such in public on"},{"line_number":47,"context_line":"the mailing list."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":52,"context_line":"  simple Launchpad bug with the feature request is all that is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_0a0ae4d2","line":49,"updated":"2015-04-29 19:34:28.000000000","message":"This paragraphs below are part of the \u0027current progress\u0027 section. I wonder if we should split this for clarity.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":46,"context_line":"activity, it will not be tolerated and will be called out as such in public on"},{"line_number":47,"context_line":"the mailing list."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":52,"context_line":"  simple Launchpad bug with the feature request is all that is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_260a78d3","line":49,"in_reply_to":"3acd31a7_0a0ae4d2","updated":"2015-04-29 19:55:07.000000000","message":"You mean from here and below start a new section? Can do!","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"d9b11ad233b90a4483d1762963775a28d1a49634","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":52,"context_line":"  simple Launchpad bug with the feature request is all that is"},{"line_number":53,"context_line":"  required."},{"line_number":54,"context_line":"* A high-level design is encouraged as part of the patch containing the code."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_d28705d6","line":51,"updated":"2015-04-28 20:19:00.000000000","message":"super nit: /not/no/","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"7154c3e5b8435e6f4a04645356c0e1ce7dec5409","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"How will this new system work to make the entire specs process better?"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Submitters will not longer have to submit a spec in neutron-specs. A"},{"line_number":52,"context_line":"  simple Launchpad bug with the feature request is all that is"},{"line_number":53,"context_line":"  required."},{"line_number":54,"context_line":"* A high-level design is encouraged as part of the patch containing the code."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_8d860cb8","line":51,"in_reply_to":"5ad0253b_d28705d6","updated":"2015-04-28 20:41:10.000000000","message":"Done","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":56,"context_line":"  detail, as the code is proposed and morphed throughout the review process."},{"line_number":57,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":58,"context_line":"  the source code."},{"line_number":59,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":60,"context_line":"  cycle, with quick feedback. The drivers team will take into account"},{"line_number":61,"context_line":"  many things but ultimately will make the tough decisions of what is"},{"line_number":62,"context_line":"  targeted at each milestone."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_aac41092","line":59,"updated":"2015-04-29 19:34:28.000000000","message":"are we giving the neutron-drivers team a time window by which every RFE must be evaluated?","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"afea4af4f53daa2fa9b63330cfd919899c4f5045","unresolved":false,"context_lines":[{"line_number":56,"context_line":"  detail, as the code is proposed and morphed throughout the review process."},{"line_number":57,"context_line":"* Spec becomes a feature request, design document lives in devref with"},{"line_number":58,"context_line":"  the source code."},{"line_number":59,"context_line":"* Fail-fast for submitters. Regular reviews by driver team through the"},{"line_number":60,"context_line":"  cycle, with quick feedback. The drivers team will take into account"},{"line_number":61,"context_line":"  many things but ultimately will make the tough decisions of what is"},{"line_number":62,"context_line":"  targeted at each milestone."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_266838f5","line":59,"in_reply_to":"3acd31a7_aac41092","updated":"2015-04-29 20:05:35.000000000","message":"No, it\u0027s reasonable to assume we\u0027ll triage as fast as we can.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":66,"context_line":"  issues, both bugs and feature requests, is an ongoing event."},{"line_number":67,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":68,"context_line":"  are given firm answers quickly."},{"line_number":69,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":70,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":71,"context_line":"  past."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_2a8fe024","line":69,"updated":"2015-04-29 19:34:28.000000000","message":"I suppose this means that feature requests  can be submitted and evaluated throughout the release cycles with no deadlines to comply with.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":66,"context_line":"  issues, both bugs and feature requests, is an ongoing event."},{"line_number":67,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":68,"context_line":"  are given firm answers quickly."},{"line_number":69,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":70,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":71,"context_line":"  past."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_46ba14e3","line":69,"in_reply_to":"3acd31a7_2a8fe024","updated":"2015-04-29 19:55:07.000000000","message":"That\u0027s exactly the intent. We\u0027re not saying they will all get in. But, for example, if some enterprising person proposes a useful feature request during milestone-2, and has a history of delivering code, lets give them a shot.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"a3673428f30588bc7d7f61f72bfbf37937cb2e5a","unresolved":false,"context_lines":[{"line_number":67,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":68,"context_line":"  are given firm answers quickly."},{"line_number":69,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":70,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":71,"context_line":"  past."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Specs and Feature Requests"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_cfaf5e93","line":70,"updated":"2015-04-29 18:10:57.000000000","message":"+1 for accepting feature requests anytime.  Hopefully this doesn\u0027t lead anyone to think their request is guaranteed to interrupt established priorities mid-cycle, though.  We may want to clarify that _acceptance_ of feature requests depends on available resources to carry out the work (including coding, reviewing, documentation, and testing) as well as fit with project goals.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":67,"context_line":"* Continuous feedback on feature requests means rejected feature requests"},{"line_number":68,"context_line":"  are given firm answers quickly."},{"line_number":69,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":70,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":71,"context_line":"  past."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Specs and Feature Requests"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_06b41cf0","line":70,"in_reply_to":"3acd31a7_cfaf5e93","updated":"2015-04-29 19:55:07.000000000","message":"Good call.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"8a552fc0ba83d1fe1f7a9bae6e8e9d999ad0e51f","unresolved":false,"context_lines":[{"line_number":76,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_cc6881bd","line":79,"updated":"2015-04-28 23:10:17.000000000","message":"It just occurred to me that we\u0027ll need to reference feature requests like this unless we take some action with infra:\n\n  Closes-Bug: #\u003cRFE #\u003e\n\nI wonder if we can enable a different way to reference them.  At least something like this:  \n\n  Implements-Feature: #\u003cRFE #\u003e\n  Partially-Implements-Feature: #\u003cRFE #\u003e","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"a3673428f30588bc7d7f61f72bfbf37937cb2e5a","unresolved":false,"context_lines":[{"line_number":76,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_6f03aab9","line":79,"in_reply_to":"5ad0253b_aeb647da","updated":"2015-04-29 18:10:57.000000000","message":"I\u0027m not sure this matters.  Closes-Bug vs Implements-Blueprint is a matter of the scope at present, and this proposal doesn\u0027t change that.  We\u0027re tied to launchpad\u0027s nomenclature whether we like it or not.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"9b6e664e051061b17b82d6dcd1e827e58a38d4f0","unresolved":false,"context_lines":[{"line_number":76,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_af9f725e","line":79,"in_reply_to":"5ad0253b_cc6881bd","updated":"2015-04-29 05:45:18.000000000","message":"Carl, that makes a lot of sense,","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"80d4dee6c4e654cf5f750f38117152ad28366f6b","unresolved":false,"context_lines":[{"line_number":76,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_cdaaad70","line":79,"in_reply_to":"5ad0253b_cc6881bd","updated":"2015-04-29 11:29:43.000000000","message":"I just realized the spec-backing-blueprints are not mentioned in this document, I just assumed we\u0027d keep those around. We could just continue to use Implements-Blueprint (And feature request bugs would reference blueprints).","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"79c6676607e8b7cddd6090669bdf2d9a52044dbd","unresolved":false,"context_lines":[{"line_number":76,"context_line":"While the team previously used the neutron-specs repository for specs, the"},{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_aeb647da","line":79,"in_reply_to":"5ad0253b_cdaaad70","updated":"2015-04-29 12:41:35.000000000","message":"Hmm, line 106.\n\nThat makes sense, may be we can just \"close the bug\" and use the Implements-Blueprint at the same time?.\n\nOr make some sort of automation to close linked bugs from blueprints?","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":7715,"name":"Hirofumi Ichihara","email":"ichihara.hirofumi@gmail.com","username":"Hirofumi-Ichihara"},"change_message_id":"cacbf0a054eb55b6d0ab6f41d7dcf7caeda19c3f","unresolved":false,"context_lines":[{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"5ad0253b_25b6e38a","line":80,"updated":"2015-04-29 07:23:48.000000000","message":"We should decide to not use launchpad BPs[1] or use both Bugs and it. Currentry, there are 497 blueprints in it. It seems most of proposals isn\u0027t managed properly. If we don\u0027t use it, we had better arrange(or delete) it so that new developer will not misunderstand.\n\nOn the other hand, I think other plan may be good, which we use both Bugs and BPs. If so, that involves costs for dual custody. But I like this plan because Work Items and Dependency tree will be useful for us.\n\n[1] https://blueprints.launchpad.net/neutron","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_cad50cba","line":80,"in_reply_to":"3acd31a7_9102ab3d","updated":"2015-04-29 19:34:28.000000000","message":"Are Launchpad Bugs fundamentally different from Launchpad Blueprints that the latter can\u0027t be tracked like the former? A launchpad blueprint can be associated to a bug report. I wonder if the process can\u0027t be changed slightly so that for every RFE we have a BP page and a Bug page. We could ask submitters to create d BP page and the neutron-drivers job is to create a bug report page to initiate and engage with  the discussion?\n\nThen for the code submission itself, we could still use Implements-blueprints tag.\n\nBottom line I am a bit unclear as to what blueprints are for in this new model.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_66c5105a","line":80,"in_reply_to":"3acd31a7_cad50cba","updated":"2015-04-29 19:55:07.000000000","message":"I think requiring both a BP and bug is problematic. I\u0027ll take a stab at re-wording this to make it clearer.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"65dbe9a05114a32e742be0bef7102ff1b1c2fee2","unresolved":false,"context_lines":[{"line_number":77,"context_line":"problems highlighted in the section above mean we\u0027re moving away from this"},{"line_number":78,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":79,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":80,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":81,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":82,"context_line":"feature request."},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_9102ab3d","line":80,"in_reply_to":"5ad0253b_25b6e38a","updated":"2015-04-29 17:21:50.000000000","message":"Agreed, I plan to spend some time cleaning out the Launchpad BP section for Neutron.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":85,"context_line":"------------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"The first step in proposing a feature request is to register a bug in"},{"line_number":88,"context_line":"`Launchpad \u003chttps://bugs.launchpad.net/neutron\u003e`_. The request should"},{"line_number":89,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":90,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":91,"context_line":"bug should be tagged with the \u0027RFE\u0027 tag. To make things easier for feature"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_0ac1c4e4","line":88,"updated":"2015-04-29 19:34:28.000000000","message":"I wonder if it makes more sense to submit a blueprint, which is effectively the combined action \u0027bug+RFE tag\u0027. \n\nThen, we could make the acknowledgement of the feature request, the creation of a linked bug report where we track the discussion?\n\nEither way, I am unclear what happens to blueprints in this new model.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":85,"context_line":"------------------------"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"The first step in proposing a feature request is to register a bug in"},{"line_number":88,"context_line":"`Launchpad \u003chttps://bugs.launchpad.net/neutron\u003e`_. The request should"},{"line_number":89,"context_line":"include a clear and concise description of the use case the feature request"},{"line_number":90,"context_line":"is tracking. It should not include implementation details at this stage. The"},{"line_number":91,"context_line":"bug should be tagged with the \u0027RFE\u0027 tag. To make things easier for feature"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_468fb423","line":88,"in_reply_to":"3acd31a7_0ac1c4e4","updated":"2015-04-29 19:55:07.000000000","message":"I think BPs are optional. Maybe we don\u0027t even need them. We\u0027ll experiment and see.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":101,"context_line":"`weekly IRC meeting \u003chttps://wiki.openstack.org/wiki/Meetings/NeutronDrivers\u003e`_."},{"line_number":102,"context_line":"Ideas which are proposed earlier in the cycle will be mapped into the"},{"line_number":103,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":104,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":105,"context_line":"submissions, and will be tracked as either the existing bug or as a new"},{"line_number":106,"context_line":"Launchpad blueprint."},{"line_number":107,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_a0e78f11","line":104,"updated":"2015-04-29 19:34:28.000000000","message":"Should the work spawn more than a bug submission, I think it would be beneficial considering blueprints as a mean of submitting features that\u0027s because a blueprint can be associated to more than one bug report and we\u0027d have a nice way of collecting related bugs together (unless we introduced a per-feature tag).\n\nHaving said that, we\u0027re really devising the aspects of the process to work around the limitation of the tool...which kinda defeats the purpose :)","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"836c9f5825094a1333ed8b3a2d96b37bcb7fb22b","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":104,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":105,"context_line":"submissions, and will be tracked as either the existing bug or as a new"},{"line_number":106,"context_line":"Launchpad blueprint."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"Feature Request Acceptance"},{"line_number":109,"context_line":"---------------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_69860dbb","line":106,"updated":"2015-04-29 16:09:07.000000000","message":"I\u0027m a little concerned with it being difficult to follow the progress of a feature request if it is broken out in to \"work items\" which could be almost anything according to this description.  What would be the advantage of creating a new blueprint to track the progress?","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"a3673428f30588bc7d7f61f72bfbf37937cb2e5a","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":104,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":105,"context_line":"submissions, and will be tracked as either the existing bug or as a new"},{"line_number":106,"context_line":"Launchpad blueprint."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"Feature Request Acceptance"},{"line_number":109,"context_line":"---------------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_6fc4ca3f","line":106,"in_reply_to":"3acd31a7_31e2b7a0","updated":"2015-04-29 18:10:57.000000000","message":"The launchpad docs have some useful detail: https://help.launchpad.net/Blueprint","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"65dbe9a05114a32e742be0bef7102ff1b1c2fee2","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development schedule for the upcoming release. The ideas will themselves"},{"line_number":104,"context_line":"potentially spawn some work items. The work items could include bugs or code"},{"line_number":105,"context_line":"submissions, and will be tracked as either the existing bug or as a new"},{"line_number":106,"context_line":"Launchpad blueprint."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"Feature Request Acceptance"},{"line_number":109,"context_line":"---------------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_31e2b7a0","line":106,"in_reply_to":"3acd31a7_69860dbb","updated":"2015-04-29 17:21:50.000000000","message":"For some larger feature requests, having a Blueprint to track the work would make sense. If the feature request boils down to a simple code change, then a bug is appropriate.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":134,"context_line":"  release, assuming the feature remains in scope for the future release."},{"line_number":135,"context_line":"* If the feature request is no longer valid, it will be marked as \"Won\u0027t Fix\"."},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"This allows for fast-tracking blueprints into future releases."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_a07c2f21","line":137,"updated":"2015-04-29 19:34:28.000000000","message":"I think it would be beneficial if we had some graphical workflows that show how the process works, but I appreciate that\u0027s a bonus","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":134,"context_line":"  release, assuming the feature remains in scope for the future release."},{"line_number":135,"context_line":"* If the feature request is no longer valid, it will be marked as \"Won\u0027t Fix\"."},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"This allows for fast-tracking blueprints into future releases."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_e69da05a","line":137,"in_reply_to":"3acd31a7_a07c2f21","updated":"2015-04-29 19:55:07.000000000","message":"I\u0027ll see if I can draw some pretty pictures.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"2eaea451b09d4fa63c393e18bfbcc741c90f4d02","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_fb3540f7","line":142,"updated":"2015-04-29 16:37:12.000000000","message":"This paragraph is key but it is little more than a footnote in this document with a few mentions of it sprinkled around.   Does this need a little more attention?  Maybe a short policy document of its own?  It should make it clear that major design decisions still need to be worked out early enough to allow sufficient discussion.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":7448,"name":"Carl Baldwin","email":"carl@ecbaldwin.net","username":"carl-baldwin"},"change_message_id":"c71992a07891338eb08cb76bb023b6904d9b5839","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_ef821ac8","line":142,"in_reply_to":"3acd31a7_0f09d695","updated":"2015-04-29 18:15:40.000000000","message":"A second proposal is fine.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"a9130acee4c0ad7cadf54fc68aa57e617860d014","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_946859bc","line":142,"in_reply_to":"3acd31a7_11957be3","updated":"2015-04-29 17:27:11.000000000","message":"I don\u0027t see this as needing more prominence here, so much as the increase in docs is *an entire second proposal* wedged into this one. I\u0027d vote for merging as is, and making the docs process a standalone follow-up.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"a3673428f30588bc7d7f61f72bfbf37937cb2e5a","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_0f09d695","line":142,"in_reply_to":"3acd31a7_946859bc","updated":"2015-04-29 18:10:57.000000000","message":"I agree with Doug that our plans regarding documentation can be proposed separately.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"65dbe9a05114a32e742be0bef7102ff1b1c2fee2","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Documentation for the Feature Request"},{"line_number":140,"context_line":"-------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_11957be3","line":142,"in_reply_to":"3acd31a7_fb3540f7","updated":"2015-04-29 17:21:50.000000000","message":"If I re-spin this, I could move this section up a bit. Thoughts?","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"79f694b262169673b834db98256bdbd7f35038dd","unresolved":false,"context_lines":[{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":146,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_80ced358","line":145,"updated":"2015-04-29 19:34:28.000000000","message":"Are we following up with patches that describe how to help people transition  from the old model to the model? Do we abandon the specs repo altogether? What happens to specs.openstack.org\nhttp://specs.openstack.org/openstack/neutron-specs/? Is it going to be cured by the drivers team? How do we communicate the change in process so that people who are used to the old process adapt quickly? \n\nI feel this patch leaves a few questions unanswered.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"944f33cd77badd26618adc287a325a522ea6148d","unresolved":false,"context_lines":[{"line_number":142,"context_line":"In the interest of increasing documentation, approved features are required to"},{"line_number":143,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":144,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":145,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":146,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":7,"id":"3acd31a7_e6b480d2","line":145,"in_reply_to":"3acd31a7_80ced358","updated":"2015-04-29 19:55:07.000000000","message":"We\u0027ll have to hold a lot of hands, no doubt, and it\u0027s going to be confusing. But if we think this approach will lead us to a better place, the short term pain is worth it.","commit_id":"a75dd96f33f01ed0dcef607a78e97d89e76a11db"},{"author":{"_account_id":12525,"name":"vishwanath jayaraman","email":"vishwanathj@hotmail.com","username":"vish"},"change_message_id":"865ae1fb4a96173358cc0a1f475e7cf164b9d97c","unresolved":false,"context_lines":[{"line_number":33,"context_line":"* Lack of \"fail fast\" for spec submissions."},{"line_number":34,"context_line":"* Specs which don\u0027t merge get lost in the shuffle."},{"line_number":35,"context_line":"* Rejected specs getting lost in the shuffle for a new release."},{"line_number":36,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":39,"context_line":"Feature requests are tracked as Launchpad bugs, tagged with the new \u0027RFE\u0027 tag,"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_7c3114ec","line":36,"updated":"2015-04-30 05:54:20.000000000","message":"I did feel this pain as a first time contributor in Kilo","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":12525,"name":"vishwanath jayaraman","email":"vishwanathj@hotmail.com","username":"vish"},"change_message_id":"865ae1fb4a96173358cc0a1f475e7cf164b9d97c","unresolved":false,"context_lines":[{"line_number":83,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":84,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":85,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":86,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":87,"context_line":"feature request."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When will an RFE filed as a bug evolve into a Launchpad BP? This is a fair"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_bc932ca3","line":86,"updated":"2015-04-30 05:54:20.000000000","message":"Clarification: Will there be a doc template provided (to guide the new contributors) that will specify the minimum required sections in the doc that need to be authored to meet the richer documentation criteria?","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"e6fb43f5c5847b8a045c43fd0b49105a8be1ec4b","unresolved":false,"context_lines":[{"line_number":83,"context_line":"for the Liberty and beyond cycles. We will be purely using Launchpad"},{"line_number":84,"context_line":"bugs to track feature requests and target them to milestone releases. These"},{"line_number":85,"context_line":"may evolve into Launchpad BPs, or they may remain as bugs. Richer"},{"line_number":86,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":87,"context_line":"feature request."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When will an RFE filed as a bug evolve into a Launchpad BP? This is a fair"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_33497b8c","line":86,"in_reply_to":"3acd31a7_bc932ca3","updated":"2015-04-30 13:22:20.000000000","message":"That is the plan, yes! I\u0027ll post it as a separate patch, but it will be very crisp and concise.","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":2035,"name":"Maru Newby","email":"marun@redhat.com","username":"maru"},"change_message_id":"b683f7c280e7344f7192859a402850b6fa7bb557","unresolved":false,"context_lines":[{"line_number":86,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":87,"context_line":"feature request."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When will an RFE filed as a bug evolve into a Launchpad BP? This is a fair"},{"line_number":90,"context_line":"question. You can envision this happening when the feature request is large"},{"line_number":91,"context_line":"enough it would encompass multiple patches and projects, and may even span"},{"line_number":92,"context_line":"across neutron into other projects. The fact we\u0027ll initially use LP bugs to"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_9a487b2f","line":89,"updated":"2015-04-29 21:39:59.000000000","message":"It might be worth mentioning that an RFE proposed as a bug can optionally evolve into a blueprint at the discretion of those involved (both implementers and those providing oversight).  The question that needs to be asked is - is the scope large enough to benefit from the overhead of a blueprint?","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"e6fb43f5c5847b8a045c43fd0b49105a8be1ec4b","unresolved":false,"context_lines":[{"line_number":86,"context_line":"documentation will now be required in-tree when you submit code for the"},{"line_number":87,"context_line":"feature request."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"When will an RFE filed as a bug evolve into a Launchpad BP? This is a fair"},{"line_number":90,"context_line":"question. You can envision this happening when the feature request is large"},{"line_number":91,"context_line":"enough it would encompass multiple patches and projects, and may even span"},{"line_number":92,"context_line":"across neutron into other projects. The fact we\u0027ll initially use LP bugs to"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_f309c332","line":89,"in_reply_to":"3acd31a7_9a487b2f","updated":"2015-04-30 13:22:20.000000000","message":"Done","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":12444,"name":"John Schwarz","email":"jschwarz@redhat.com","username":"jschwarz"},"change_message_id":"8ce57e2df565ada19a5ed8106eb1fdb029331524","unresolved":false,"context_lines":[{"line_number":125,"context_line":"upcoming release, the neutron-drivers team will approve the feature request by"},{"line_number":126,"context_line":"targeting the bug at a milestone release. If the neutron-drivers team feels as"},{"line_number":127,"context_line":"if the feature does not fit within the scope of the current release, the bug"},{"line_number":128,"context_line":"will be left un-targeted until a future release milestone shows up in Launchpad."},{"line_number":129,"context_line":"This indicates the feature request does not fit into the current release."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Please note a high-level overview of the proposed feature should land in the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_12268768","line":128,"updated":"2015-04-30 07:13:12.000000000","message":"I think in cases where the RFE is deemed not fit, some explicit comment should be made to said launchpad bug. Some developers can\u0027t attend all Neutron meetings and might miss the discussions made on their RFEs, thus implicitly leaving them un-targeted puts the writer into some kind of a limbo state. Also, this implicitly seems very uncomfortable to the RFE writer. How will he know why his RFE was deemed unfit?\n\nIn short, I think it should be necessitated that, when a RFE deems unfit, an explicit, detailed, message specifying the reason why it was deemed so should be written in the launchpad. This will also allow the writer to open a dialog with the drivers team regarding why his RFE was declined/postponed. This will prevent cases where where an RFE is postponed to the next cycle (up to a year from now) without the writer knowing the true reason why.","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"e6fb43f5c5847b8a045c43fd0b49105a8be1ec4b","unresolved":false,"context_lines":[{"line_number":125,"context_line":"upcoming release, the neutron-drivers team will approve the feature request by"},{"line_number":126,"context_line":"targeting the bug at a milestone release. If the neutron-drivers team feels as"},{"line_number":127,"context_line":"if the feature does not fit within the scope of the current release, the bug"},{"line_number":128,"context_line":"will be left un-targeted until a future release milestone shows up in Launchpad."},{"line_number":129,"context_line":"This indicates the feature request does not fit into the current release."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Please note a high-level overview of the proposed feature should land in the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_2e2594aa","line":128,"in_reply_to":"3acd31a7_12268768","updated":"2015-04-30 13:22:20.000000000","message":"Done","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":12525,"name":"vishwanath jayaraman","email":"vishwanathj@hotmail.com","username":"vish"},"change_message_id":"865ae1fb4a96173358cc0a1f475e7cf164b9d97c","unresolved":false,"context_lines":[{"line_number":156,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":157,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":158,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":159,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_dc20284c","line":159,"updated":"2015-04-30 05:54:20.000000000","message":"Suggestion: An explicit statement on how feature request review and acceptance would be treated for vendor code in the advanced services could be helpful even if it is the same as that of neutron features.","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"4c63a1d606a3d59ebcf924c2a1e31ac6b586c1a5","unresolved":false,"context_lines":[{"line_number":156,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":157,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":158,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":159,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_c1a04393","line":159,"updated":"2015-04-30 04:36:30.000000000","message":"What about other repos?  Do we add a devref to each one?  Or put it all in neutron (cross repo changes, yuck)?  Or leave it up to that repo?","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"f2e9a0462051df48922b1da9caf78acd4477d534","unresolved":false,"context_lines":[{"line_number":156,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":157,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":158,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":159,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_3c8ddc31","line":159,"in_reply_to":"3acd31a7_c1a04393","updated":"2015-04-30 05:53:21.000000000","message":"Not sure where/how I understood all repos under the neutron \"tent\" would need to include a devref dir. But that makes sense.","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"e6fb43f5c5847b8a045c43fd0b49105a8be1ec4b","unresolved":false,"context_lines":[{"line_number":156,"context_line":"provide developer documentation in-tree in the Neutron repository. This will also"},{"line_number":157,"context_line":"assist those writing release documentation for feature requests which have been"},{"line_number":158,"context_line":"accepted into the release. Please note this is required for all Neutron repositories,"},{"line_number":159,"context_line":"including the advanced service repositories."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3acd31a7_6e526c15","line":159,"in_reply_to":"3acd31a7_dc20284c","updated":"2015-04-30 13:22:20.000000000","message":"Done","commit_id":"1f2cae180b4ac1fe7a0b90ba6f2d34285de74040"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"9c8e4c620dcdb4d13084013b0da2f57af9bb0ee2","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Ultimately, the optional transition of an RFE submitted as a bug into a"},{"line_number":98,"context_line":"blueprint is at the discretion of both the submitter of the RFE as well as"},{"line_number":99,"context_line":"those providing oversight. Given the overhead of the transition, the main"},{"line_number":100,"context_line":"deciding factor will be the scope of the RFE."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Feature Request Proposal"},{"line_number":103,"context_line":"------------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3acd31a7_002175fb","line":100,"updated":"2015-04-30 20:18:07.000000000","message":"Suggestion to address Maru\u0027s feedback, add this sentence (or similar) to this paragraph:\n\nFeatures with blueprrints are strongly encouraged to submit an initial design document in devref, because the cost of reworking code at review time, due to lack of consensus on design, greatly increases as features size increases.","commit_id":"034615e8c383b914d972570461ded9450c98e2f3"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"4b54c4f9ab2ed1c2e5668eb5ae8c087cff85c050","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Ultimately, the optional transition of an RFE submitted as a bug into a"},{"line_number":98,"context_line":"blueprint is at the discretion of both the submitter of the RFE as well as"},{"line_number":99,"context_line":"those providing oversight. Given the overhead of the transition, the main"},{"line_number":100,"context_line":"deciding factor will be the scope of the RFE."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Feature Request Proposal"},{"line_number":103,"context_line":"------------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3acd31a7_3c7daee7","line":100,"in_reply_to":"3acd31a7_002175fb","updated":"2015-05-01 13:12:58.000000000","message":"Done","commit_id":"034615e8c383b914d972570461ded9450c98e2f3"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"8cd48152dbf15cf3ba4deebdd98c2ad057b97090","unresolved":false,"context_lines":[{"line_number":36,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":39,"context_line":"Feature requests are tracked as Launchpad bugs, tagged with the new \u0027RFE\u0027 tag,"},{"line_number":40,"context_line":"and allow for the submission and review of these early ideas before code is"},{"line_number":41,"context_line":"submitted. This allows the team to verify the validity of a feature request"},{"line_number":42,"context_line":"before the process of submitting a devref documentation is undertaken, or code"}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_473e208d","line":39,"updated":"2015-05-04 20:22:40.000000000","message":"I think one side-effect of this proposal is that we lose the ability to provide a per-line feedback, aka the inline review process we\u0027re so fond of.","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":8873,"name":"Assaf Muller","email":"amuller@redhat.com","username":"amuller"},"change_message_id":"ed13dfee144abe2109e45a0b037a67bdd7ebc70c","unresolved":false,"context_lines":[{"line_number":36,"context_line":"* Small window to propose and get a spec accepted."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With this in mind, we are introducing the concept of feature requests."},{"line_number":39,"context_line":"Feature requests are tracked as Launchpad bugs, tagged with the new \u0027RFE\u0027 tag,"},{"line_number":40,"context_line":"and allow for the submission and review of these early ideas before code is"},{"line_number":41,"context_line":"submitted. This allows the team to verify the validity of a feature request"},{"line_number":42,"context_line":"before the process of submitting a devref documentation is undertaken, or code"}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_a7ef34e8","line":39,"in_reply_to":"3acd31a7_473e208d","updated":"2015-05-04 20:26:25.000000000","message":"Only on the RFEs, which is a fair point. The specs are replaced with devrefs which we\u0027ll be able to beat on until we\u0027ve all reached nirvana.","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"2e5dee116abee0a1abae9752744f76a3994a3a22","unresolved":false,"context_lines":[{"line_number":74,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":75,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":76,"context_line":"  past."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Specs and Feature Requests"},{"line_number":79,"context_line":"--------------------------"},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_5554b11f","line":77,"updated":"2015-05-01 21:48:20.000000000","message":"An alternative for a smaller step towards something similar:\n\n- Keep -specs (stop heating the tar, put away the feathers)\n- Do away with the spec submission deadline\n- Have a smaller template for use with smaller items, or introductory items.\n\nOr, another one:\n\n- Keep -specs\n- Submit to a backlog instead of liberty\n- Drivers move merged items to the appropriate release as needed\n- Still have a smaller template for smaller things/FR\u0027s.","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"42583f469ed9a066699c66f90f9f71eb7fd86ae7","unresolved":false,"context_lines":[{"line_number":74,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":75,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":76,"context_line":"  past."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Specs and Feature Requests"},{"line_number":79,"context_line":"--------------------------"},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_2e832658","line":77,"in_reply_to":"3acd31a7_2b00b800","updated":"2015-05-01 23:38:29.000000000","message":"Completely agree with the no deadlines, that\u0027s what I want out of this.","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":8788,"name":"Miguel Angel Ajo","email":"mangelajo@redhat.com","username":"mangelajo"},"change_message_id":"5223961c16fb510bb8ffd043a5b6d5b16d97c1aa","unresolved":false,"context_lines":[{"line_number":74,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":75,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":76,"context_line":"  past."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Specs and Feature Requests"},{"line_number":79,"context_line":"--------------------------"},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_710d6b36","line":77,"in_reply_to":"3acd31a7_2e832658","updated":"2015-05-04 10:04:57.000000000","message":"I would keep the \"specs\" in the dev tree (devref), otherwise we\u0027re missing other of the important points here. Specs are submitted, and then they get rotten as code evolves.\n\nI believe it\u0027s a good chance to have a healthier and better maintained devref.\n\nI guess what\u0027s missing from having specs in devref is only drivers being able to +2 ?","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"977dcf028804b6d596ddce75371ecb0113484be7","unresolved":false,"context_lines":[{"line_number":74,"context_line":"* Feature requests can be proposed anytime during the cycle, no windows"},{"line_number":75,"context_line":"  for deadlines. Seriously, we mean this. Deadlines are a thing of the"},{"line_number":76,"context_line":"  past."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Specs and Feature Requests"},{"line_number":79,"context_line":"--------------------------"},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"3acd31a7_2b00b800","line":77,"in_reply_to":"3acd31a7_5554b11f","updated":"2015-05-01 22:40:44.000000000","message":"I would mandate a minimal template, where only proposed change and problem description are mandatory.\n\nOther sections might be added is asked by the drivers team. For instance for a spec with ApiImpact flag we might require a spec of the REST change to submit them to the feedback of the API WG.\n\nBut it\u0027s all a big meh from me. You can keep the template as it is. I would just put a lot of \"N/A\" in it.\nBut please no more deadlines. That\u0027s the main reason for which I decided to not be anymore in the drivers team.","commit_id":"b14b64db1889fb82770dd3b93c4d78011229e514"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"b33884b795c34f983456c2af75f6b6463d10a657","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The process for moving work from RFEs into the code involves someone assigning"},{"line_number":57,"context_line":"themselves the RFE bug and filing a matching spec in the neutron-specs"},{"line_number":58,"context_line":"repository. The spec will then be reivewed by the community and approved by"},{"line_number":59,"context_line":"the drivers team before landing in a release. This is the same process as"},{"line_number":60,"context_line":"before REFs existed in Neutron."}],"source_content_type":"text/x-rst","patch_set":14,"id":"1aca2d91_6aa6d6c2","line":58,"updated":"2015-05-06 21:47:33.000000000","message":"reviewed is misspelled here too.","commit_id":"8b0386ad221b53b0ee679e6d6ba294d8a6907730"},{"author":{"_account_id":12525,"name":"vishwanath jayaraman","email":"vishwanathj@hotmail.com","username":"vish"},"change_message_id":"07edcd343668cdec525388f0e12c3afc017a77d7","unresolved":false,"context_lines":[{"line_number":57,"context_line":"themselves the RFE bug and filing a matching spec in the neutron-specs"},{"line_number":58,"context_line":"repository. The spec will then be reivewed by the community and approved by"},{"line_number":59,"context_line":"the drivers team before landing in a release. This is the same process as"},{"line_number":60,"context_line":"before REFs existed in Neutron."}],"source_content_type":"text/x-rst","patch_set":14,"id":"1aca2d91_590adad3","line":60,"updated":"2015-05-06 20:22:53.000000000","message":"nit: REFs should be RFEs","commit_id":"8b0386ad221b53b0ee679e6d6ba294d8a6907730"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"b33884b795c34f983456c2af75f6b6463d10a657","unresolved":false,"context_lines":[{"line_number":57,"context_line":"themselves the RFE bug and filing a matching spec in the neutron-specs"},{"line_number":58,"context_line":"repository. The spec will then be reivewed by the community and approved by"},{"line_number":59,"context_line":"the drivers team before landing in a release. This is the same process as"},{"line_number":60,"context_line":"before REFs existed in Neutron."}],"source_content_type":"text/x-rst","patch_set":14,"id":"1aca2d91_aac50e5c","line":60,"in_reply_to":"1aca2d91_590adad3","updated":"2015-05-06 21:47:33.000000000","message":"Done","commit_id":"8b0386ad221b53b0ee679e6d6ba294d8a6907730"},{"author":{"_account_id":6659,"name":"Paul Michali","email":"pc@michali.net","username":"pcm"},"change_message_id":"2188cdeda26300f9c4758b1cdd72f81ab781043a","unresolved":false,"context_lines":[{"line_number":57,"context_line":"themselves the RFE bug and filing a matching spec in the neutron-specs"},{"line_number":58,"context_line":"repository. The spec will then be reviewed by the community and approved by"},{"line_number":59,"context_line":"the drivers team before landing in a release. This is the same process as"},{"line_number":60,"context_line":"before RFFs existed in Neutron."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1aca2d91_840474c0","line":60,"updated":"2015-05-07 11:04:56.000000000","message":"nit: RFEs","commit_id":"3e085ec97c4a8d77398e70c0db78ae0849dda841"}]}