I think we'll be trying to take as much of that as possible into account as we figure out what people want/need to work on, and what their schedules are. I expect there will be an occasional problem with something along these lines, but hopefully participants will have a good handle on how much time they
realistically have available.
On the other paw, I don't want to see this be a 12 month project. I think we've picked a project that's not so expansive that people will lose interest, nor so short term that it'll be done in a week (hope not, anyway).
Remember, we're going to try to go through all the steps that real programmers hate: planning, writing a specification, scheduling, code reviews, etc. We may hate that part in real life, but it's something that's all part of delivering a real-world project.
Along these lines, I wonder if we need a "motto" that reinforces that project is not an end to the means, but the means to an end.
--Chris
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.