<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Guys,<div class=""><br class=""></div><div class="">I’d like to ask all Fuel component leads to take a look at the proposed changes and check whether all important sections were added.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg<br class=""><div><blockquote type="cite" class=""><div class="">18 черв. 2015 о 13:14 Roman Prykhodchenko <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I realize, that discussing this topic in the email is hard. I filed a review request with some changes to the template and invite you folks to take a look at that: <a href="https://review.openstack.org/193070" class="">https://review.openstack.org/193070</a><div class=""><br class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">16 черв. 2015 о 17:08 Roman Prykhodchenko <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class="">Hi folks!<br class=""><br class="">I was reviewing one of specs for Fuel 7.0 and realized the information there is messed up and it’s pretty hard to put it all together. The reason for that is basically that Fuel is a multicomponent project but the template does not consider that — there is a Proposed change section which is used to define all the changes in the entire project; then there is the API and Data impact sections that are specific to only specific components but still have to be filled in.<br class=""><br class="">Since most of new features consider changes to several components I propose to stick to the following structure. It eliminates the need to create several specs to describe one feature and allows to organize everything in one document without messing it up:<br class=""><br class="">--> Title<br class="">--> Excerpt (short version of the Problem description, proposed solution and final results)<br class="">--> Problem description<br class="">--> Proposed changes<br class="">------> Web UI<br class="">------> Nailgun<br class="">----------> General<br class="">----------> REST API<br class="">----------> Data model<br class="">------> Astute<br class="">----------> General<br class="">----------> RPC protocol<br class="">------> Fuel Client<br class="">------> Plugins<br class="">--> Impact<br class="">------> End-user<br class="">------> QA<br class="">------> Developer<br class="">------> Infrastructure (operations)<br class="">------> Upgrade<br class="">------> Performance<br class="">--> Implementation<br class="">------> Assignee<br class="">------> Work items<br class="">----------> Web UI<br class="">----------> Nailgun<br class="">----------> Astute<br class="">----------> Fuel Client<br class="">----------> Plugins<br class="">----------> Documentation<br class="">--> References<br class=""><br class=""><br class="">- romcheg<br class=""><br class=""><br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div>__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>