Print Story discussion
Diary
By cam (Mon Mar 16, 2009 at 10:56:43 AM EST) (all tags)
 Amusing but true in my anecdotal experience, and one I am guilty of;

One particular pitfall of open source projects is that, if you don't manage the project carefully, you can tend to attract developers who are more interested in discussion than writing code


 Also, we need more meetings to discuss stuff.
< So I guess I should. | An exercise in futility. >
discussion | 7 comments (7 topical, 0 hidden) | Trackback
Not just open sores... by wiredog (4.00 / 1) #1 Mon Mar 16, 2009 at 11:07:52 AM EST
Here at $SecurityContractor we have several meetings/week.

Earth First!
(We can strip mine the rest later.)

I believe that this project has suffered by Herring (4.00 / 3) #2 Mon Mar 16, 2009 at 11:10:12 AM EST
by concentrating too much on stuff at the expense of things. 9:30 - 12:30, meeting room 4.

christ, we're all old now - StackyMcRacky
Code for words by duxup (4.00 / 1) #3 Mon Mar 16, 2009 at 12:36:05 PM EST
I've no idea what I’m talking about but would it be possible to limit discussion by only allowing X amount words for Y amount of code?  Might be a cool idea if only to see how it fails.


____
All developer posts by dark nowhere (4.00 / 1) #7 Mon Mar 16, 2009 at 04:03:35 PM EST
must be accompanied by a commit that resolves an issue in the tracker.

Chill out, snowflake.

[ Parent ]
was going to post a link to bikeshed by clover kicker (4.00 / 1) #4 Mon Mar 16, 2009 at 12:52:07 PM EST
but I see the article is just a bikeshed link.

what is your favorite colored bikeshed? by cam (2.00 / 0) #5 Mon Mar 16, 2009 at 01:30:37 PM EST
You have just the one shed? by ad hoc (4.00 / 1) #6 Mon Mar 16, 2009 at 02:33:26 PM EST

--
[ Parent ]
discussion | 7 comments (7 topical, 0 hidden) | Trackback