https://www.chiliproject.org/2011-11-10T14:45:26+01:00ChiliProjectChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=103932011-11-10T14:45:26+01:00Romano Lickerr.licker@finn.de
<ul><li><strong>Start date</strong> set to <i>2011-11-10</i></li><li><strong>Estimated time</strong> deleted ()</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Normal</i></li><li><strong>Project</strong> set to <i>ChiliProject</i></li><li><strong>Target version</strong> set to <i>3.0.0</i></li><li><strong>Assignee</strong> set to <i>Eric Davis</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>0</i></li><li><strong>Subject</strong> set to <i>new design with 263-new-layout-ready</i></li><li><strong>Category</strong> set to <i>User interface</i></li><li><strong>Tracker</strong> set to <i>Feature</i></li><li><strong>Due date</strong> deleted ()</li><li><strong>Subproject of</strong> deleted ()</li><li><strong>Description</strong> set to <i>The last 3 days I was working on a rebase which combines our current design c...</i> <a href="/journals/10393/diff/description" class="lightbox-ajax">More</a></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28772011-11-10T16:44:03+01:00Romano Lickerr.licker@finn.de
<ul></ul><p>Working on it right now. We will post the pull request tomorrow.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28782011-11-10T17:47:01+01:00Eric Davis
<ul></ul><p>Romano Licker wrote:</p>
<blockquote>
<p>The last 3 days I was working on a rebase which combines our current design changes, the changes from <a href="https://www.chiliproject.org/issues/263" class="issue status-5 priority-2 closed" title="New layout (Closed)">#263</a> (<code>edavis10/263-new-layout-ready</code>) and the current core chili 2.4.0.</p>
</blockquote>
<p>Make sure you are targeting 3.0.0 (unstable) and not 2.x (master).</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28862011-11-11T12:58:10+01:00Romano Lickerr.licker@finn.de
<ul></ul><p>This is it - finally :)</p>
<p>Since we ran into more problems rebasing against current unstable, we decided to merge. <br />Comparatively it is quite manageable than anything else.</p>
<p><a class="external" href="https://github.com/chiliproject/chiliproject/pull/121">https://github.com/chiliproject/chiliproject/pull/121</a></p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28872011-11-11T13:09:00+01:00Holger Justchiliproject@meine-er.de
<ul></ul><p>Yay, finally! This is a huge step forward into the us having the next awesome design.</p>
<p>We have spend way more time than initially planned to bring the patches to the current unstable branch. I think we have to reduce that time for future patches, let's talk at the next team meeting what went wrong and how we can improve our process and communication. The merges and rebase attempts were a serious PITA and I wouldn't want to do something like this again (and don't wish that anyone else too).</p>
<p>So here's my plan for review. I think we are now beyond the point that many of the changes in the pull can be changed inplace. So I propose we review it and do any required changes on top of the unchanged pull. So any found changes should be handled in additional issues and be implemented separately. That way we can move to a simpler and more structured approach again.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28882011-11-11T19:35:30+01:00Eric Davis
<ul></ul><p>Romano Licker wrote:</p>
<blockquote>
<p>Since we ran into more problems rebasing against current unstable, we decided to merge.</p>
</blockquote>
<p>Thanks for updating this. Merging it like this is going to make it hard to review. (below)</p>
<p>Holger Just wrote:</p>
<blockquote>
<p>We have spend way more time than initially planned to bring the patches to the current unstable branch.</p>
</blockquote>
<blockquote>
<p>I think we have to reduce that time for future patches, let's talk at the next team meeting what went wrong and how we can improve our process and communication. The merges and rebase attempts were a serious PITA and I wouldn't want to do something like this again (and don't wish that anyone else too).</p>
</blockquote>
<p>This is off-topic for this issue and given that this issue is going to have a complex discussion, I've moved this to the <a href="https://www.chiliproject.org/boards/2/topics/961" class="external">forum</a>.</p>
<blockquote>
<p>So here's my plan for review. I think we are now beyond the point that many of the changes in the pull can be changed inplace. So I propose we review it and do any required changes on top of the unchanged pull. So any found changes should be handled in additional issues and be implemented separately. That way we can move to a simpler and more structured approach again.</p>
</blockquote>
<p>-1 Looking at the commits I'm going to say no. I see several commits that duplicate existing commits (91214e195f0929f5), some commits in German (I think), and a few reverting previous code. The history of this branch is extremely confusing at this point, will be difficult to review, and will hurt the code history.</p>
<p>If someone isn't willing to do a rebase of this on top of unstable, could someone do an internal rebase at least? Where only the commits in the branch are rebased in order to:</p>
<ul>
<li>remove the code and the reverting commits (e.g. commits: A, B, C, revert B would become: A, C)</li>
<li>translate and update the commit logs to be descriptive of <strong>why</strong> a commit is needed and not <strong>how</strong> or <strong>what</strong> a commit is</li>
<li>squash related commits into one commit</li>
</ul> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28892011-11-12T18:38:46+01:00Eric Davis
<ul><li><strong>Assignee</strong> changed from <i>Romano Licker</i> to <i>Eric Davis</i></li></ul><p>I'm starting to rebase and squash this branch with Holger's and Felix's help. I'll post here when the code is ready for review.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28902011-11-12T21:44:46+01:00Eric Davis
<ul></ul><p>I've been working on this in the pull request and adding comments to it as I go. Basically I'm taking Romano's pull request, rebasing it onto unstable to remove the merge commits, and doing a squash rebase to consolidate the 83 commits into logical chunks that can be committed.</p>
<p><a class="external" href="https://github.com/chiliproject/chiliproject/pull/121">https://github.com/chiliproject/chiliproject/pull/121</a></p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=28912011-11-13T00:36:17+01:00Eric Davis
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Ready for review</i></li></ul><p>I've just sent in a <a href="https://github.com/chiliproject/chiliproject/pull/122" class="external">pull request</a> with the results of my rebasing:</p>
<ul>
<li>fix unclear commit logs and add the issue prefixes</li>
<li>remove merge commits from other branches</li>
<li>reorder commits into logically sequence (see this <a href="https://gist.github.com/1361097" class="external">gist</a> for one version)</li>
<li>squashing related commits into a single larger commit</li>
<li>removing unnecessary reverts</li>
</ul>
<p>I've also done a manual diff of the layout, application.css, and application.js to pull request 121 to make sure nothing major was missed.</p>
<p>Since there is so much here, lets try to keep the code review in this issue. We should review this like so:</p>
<ol>
<li>should each commit be included or not?</li>
<li>for code changes as a whole, is each line acceptable (security, code standards, etc)</li>
<li>does the changes make sense? Like is this a good change or should it be different.</li>
</ol>
<p>Eric Davis</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29032011-11-14T02:03:13+01:00Eric Davis
<ul></ul><p>I started a wiki page (<a href="https://www.chiliproject.org/projects/chiliproject/wiki/692_Layout" class="wiki-page">692_Layout</a>) to track all of my feedback. The design review is complete and I'll work on the code and feature review next.</p>
<p>Feel free to add sections for your own reviews and then we can go over everything at once and decide how to proceed.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29072011-11-14T06:22:54+01:00Felix Schäferfelix+chili@oh14.de
<ul></ul><p>Eric Davis wrote:</p>
<blockquote>
<p>I started a wiki page (<a href="https://www.chiliproject.org/projects/chiliproject/wiki/692_Layout" class="wiki-page">692_Layout</a>) to track all of my feedback. The design review is complete and I'll work on the code and feature review next.</p>
<p>Feel free to add sections for your own reviews and then we can go over everything at once and decide how to proceed.</p>
</blockquote>
<p>Wasn't sure how to add my comments to your feedback, I've added them as lower-level list points.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29092011-11-14T16:07:14+01:00Romano Lickerr.licker@finn.de
<ul></ul><p>I fixed two minor bugs. One broke themes of ours.</p>
<p><a class="external" href="https://github.com/edavis10/chiliproject/pull/1">https://github.com/edavis10/chiliproject/pull/1</a></p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29102011-11-14T16:35:45+01:00Eric Davis
<ul></ul><p>Felix Schäfer wrote:</p>
<blockquote>
<p>Wasn't sure how to add my comments to your feedback, I've added them as lower-level list points.</p>
</blockquote>
<p>I guess that is fine. I was hoping everyone would review the design themselves adding their own comments (i.e. append only) and then as a group we would go through them and decide what to do.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29182011-11-15T18:30:45+01:00Eric Davis
<ul></ul><p>I'm changing my mind; using the wiki page for discussion is becoming a mess. Lets keep all discussion of the features and bugs in this issue (or other issues if relevant) and only use the wiki page for listing what everyone has found.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29192011-11-15T19:43:54+01:00Niels Lindenthal
<ul></ul><p>Eric Davis wrote:</p>
<blockquote>
<p>I'm changing my mind; using the wiki page for discussion is becoming a mess. Lets keep all discussion of the features and bugs in this issue (or other issues if relevant) and only use the wiki page for listing what everyone has found.</p>
</blockquote>
<p>What do you mean by that? Do you want to use the wiki to track issues?</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29202011-11-15T20:33:26+01:00Eric Davis
<ul></ul><p>Niels Lindenthal wrote:</p>
<blockquote>
<p>Do you want to use the wiki to track issues?</p>
</blockquote>
<p>That's close to what I meant. I intended the wiki page to be used as a record to collect each persons' feedback as they test the new code. Things like bugs, usability problems, or things that need to be changed. Then, as a group, we would review them all and decide what to do with each one in the issue (e.g. fix now, create issue and fix later, ignore, etc).</p>
<p>Recent edits to that page have been more about discussing the things already listed there (which is better done in this issue once everyone has done their review). This is making the page a mess and difficult to understand.</p>
<p>Roughly the steps are:</p>
<ol>
<li>People review the changes individually</li>
<li>As a group, each thing is discussed and duplicates consolidated if multiple people found the same thing</li>
<li>As a group, decisions made on what to do for each item</li>
<li>Actions taken based on the decisions</li>
</ol>
<p>(This is the same as how all proposed changes are done, though smaller changes move faster since there is less impact than a full redesign)</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=29902011-11-27T18:15:13+01:00Felix Schäferfelix+chili@oh14.de
<ul></ul><p>I've added my comments to the pull request and to the wiki page, not much more to add to Eric's points though.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=30332011-12-01T23:14:32+01:00Eric Davis
<ul></ul><p>Thanks Felix, I've reviewed your comments in the wiki and the pull request. At this point I think it's safe to close this issue for review since there have been almost 3 weeks.</p>
<p>I'm going to try to summarize the issues found and propose some decisions next.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=30342011-12-01T23:47:39+01:00Eric Davis
<ul></ul><p>Okay, I've gone through the notes on the wiki and the pull request and summarized everything.</p>
<p>On the top of the wiki (<a href="https://www.chiliproject.org/projects/chiliproject/wiki/692_Layout" class="wiki-page">692_Layout</a>) is the summary with my opinion of what each feature/part would fall under: blocks the release, would be nice to have but not required, or wait until later.</p>
<p>Does anyone have any feedback on:</p>
<ol>
<li>The "status" of each item? (e.g. blocker, later)</li>
<li>The decision of each item?</li>
</ol>
<p>You can add your feedback under the item with your name or discuss it here.</p>
<p>The sooner we can reach an agreement, the sooner I can update the pull request, and the soon we can finish this issue up (and get 3.0 released). Thinking 3-4 days to get final feedback should be enough time.</p>
<p>It's been a long feature but we're getting close to the end now.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=30762011-12-09T21:07:44+01:00Eric Davis
<ul></ul><p>I'm going to assume that silence on this issue means an agreement. Since this feature is blocking 3.0 and we are already dangerously close to missing our release dates I'm going to take some drastic actions:</p>
<ul>
<li>I've scheduled some time this weekend to work on this</li>
<li>I'll be fixing the most critical problems with this code</li>
<li>I'll be merging that code into unstable</li>
<li>For things I am not able to fix, I'll be ripping out functionality with the explicit goal of getting this code into a working state (expect hacks, workarounds, and lots of cursing... ;) )</li>
</ul>
<p>Once that is done then it will be time to finish or push back on the last 3.0 features and release a beta. Any and all bugs can then be handles post 3.0-beta or in minor releases (3.1.0, 3.2.0, etc).</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=30862011-12-10T00:36:24+01:00Eric Davis
<ul><li><strong>Status</strong> changed from <i>Ready for review</i> to <i>Open</i></li></ul><p>Did a lot of work on the blocker items, specifically around the projects menu. Will continue tomorrow, rebase, and commit.</p> ChiliProject - Feature #692: new design with 263-new-layout-readyhttps://www.chiliproject.org/issues/692?journal_id=30972011-12-10T19:02:56+01:00Eric Davis
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>I've fixed all of the Blocker issues listed on the <a href="https://www.chiliproject.org/projects/chiliproject/wiki/692_Layout" class="wiki-page">wiki page</a> except for one that needs to be discussed first. I'm going to create an issue for that one and then either fix or create issues for the rest of the items.</p>
<p>Thanks to everyone who contributed code, designs, ideas, and helped with this new design. It will be a great step forward for ChiliProject and will make future usability improvements easier.</p>