On Sun, Jun 12, 2011 at 7:08 PM, Jeff Forcier
<address@hidden> wrote:
On Sun, Jun 12, 2011 at 2:07 PM, address@hidden
<address@hidden> wrote:
> Adjusting the "chunk-size" on tickets would help too. Some of them are more like debate/discussion forums.
Yea, this is a known issue (heh. get it? ugh.) and something I
constantly struggle with. Especially lately I've been better at
noticing that I'm jotting down a bulleted list of some kind, and going
"No! Bad Jeff! Make individual tickets!".
Some things occasionally *do* justify a "big ticket" because there's
no one clear action to take, or stuff is debatable...but even those
could be broken down into "Decide first step approach to X",
"Implement <that first step>", and "Notes for later releases". Again,
emphasis on "less waffling, more releasing".
As a side note, Pull Requests will help here in my opinion. I'd much rather have big discussions around code that in the ether. By putting a priority on code rather than ideas, it also helps focus contribution. It's somewhat easier to write long, very well thought out defenses for a particular implementation. It's another thing entirely to write out the code.
Consider this yet another +1 for GH :-)
> This might be a good time to condense some of the (incredibly) long tickets cum discussion forums down to actionable chunks/actual tickets.
Agreed. Would also be a good time for aforementioned bucket
consolidation (née labels) so I may try to just do both at the same
time...but again it'll take a bit of thought. (mostly comes down to
"lock Redmine and just start making new stuff on GH" vs "try to import
Redmine's data into GH"...and there's a bunch of pros/cons about
either.)
Fresh starts are always a good thing. I'd say lock Redmine, throw up a link redirecting people to @fabric/fabric and pull over what's needed as it's determined that it's needed.
On a semi-related note -- are you planning on moving over to the @fabric Organization instead of your personal account? I'd definitely be plus one for that and make everything a Pull Request into the main repo. PRs have proven very effective for us on Armstrong as they make sure lots of eyes are on the code during the development of a particular feature and it's evolution is tracked in one place.
-T
P.S. Do I get to update my signature to be the Patron Saint of Fabric? Not sure if I qualify as a true patron saint, but it'd still be a cool title. :-D