forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gav...." <brightoncomput...@brightontown.com.au>
Subject RE: [jira] Created: (FOR-921) decide and document the future of ForrestFriday IRC get togethers
Date Fri, 18 Aug 2006 12:09:45 GMT
Thanks for creating this David, sorry it had to be you again, I was getting
around to it. I will answer here as maybe the jira issue shouldn't be filled
with continuing thoughts but maybe just proposals/solutions.

Going back through that initial forrest dev thread I'll pull out a few
things and say what I think now with consideration for the incubator thread
also.

First of all though, I wonder if some sort of calendar might be useful,
where devs can put in dates and times when they are most likely to be
available - or at least have these posted on the jira issue maybe. Then we
could work out the best day of the week to hold the event and the best times
during the day that it will run. This could also determine the actual length
of time in which it could occur. (I'm still happy with 24 hrs gives all a
timeslot to join in but ...)

Forrest Friday was changed from Tuesday originally due to most people 'at
that time' saying that Friday rolling into Saturday would be best. Maybe
this is still the case, maybe not, we need an update of dev availability to
determine this. Or, it might be easier for some to state when they can not
attend.

If all devs could plot their positions on the world map (sorry forget url at
the moment) then this too could help determine best time of day to account
for time zones - and give others a useful graphical insight.

It has been mentioned how useful or not logs are for those that can not
attend sessions. Having the logs in SVN is a good backup and for those that
are ok with trawling through them, having a good summary where only the
relevant stuff is put is also a necessity - some argue a requirement to keep
people in the loop with what went on. (I think 'what went on' is additional
material rather than exclusionary practice but that's me)

The summary needs an agreeable format, destination and style, having a good
combination of those three will make it more useful as a reference or even a
doc. To get the ball roiling again and get IRC back in forrest I am happy to
do the next summary and see what happens after that.

The incubator IRC discussions recently express a wide range of differing
opinions on whether IRC is beneficial or not for particular projects, for
those projects community health, and for the code base. I think we are more
or less agreed here that IRC is still beneficial to forrest, does not harm
or exclude the community, and enables faster production.

To add yet another of my perspectives - I have aired my views many times
regarding IRC and don't want to repeat it all - so here is a new one not
mentioned thus far. 

Consider that perhaps without IRC, those who would have participated may
possibly work out whatever they were working on eventually anyway, then
commit it and it's done. This is a good thing, but with it happening on IRC,
we are missing the 'thoughts' , the 'working out' and all that goes with it
(we still see the code though I know that). 
Sometimes, seeing how the answer was derived is just as important as the
answer itself - just ask any students sitting exams who won't get full marks
for the correct answer - the method of how they got there is what is needed
too.

I'm waffling, I'll try and get around to finishing.

Ross mentioned whether it would be an idea to have 'another' IRC session
where devs could basically run a Q & A for newcomers to forrest. I like this
idea, whether it would work as a second IRC session is debatable, recent
events show that it is difficult enough to get devs together for one
session. In which case then, maybe an hour or so of Q & A could be tagged on
to the end of a normal Forrest Friday (or what day it ends up), any good?

With all the talk of a new and improved forrest, I think it a good idea to
get IRC up and running again very soon. And as others have said previously,
it really does also help the community spirit, being able to virtually meet
up and have a bit of socialising during the event also.


Gav...(first beer on me!)


> -----Original Message-----
> From: David Crossley (JIRA) [mailto:jira@apache.org]
> Sent: Thursday, 17 August 2006 11:15 AM
> To: dev@forrest.apache.org
> Subject: [jira] Created: (FOR-921) decide and document the future of
> ForrestFriday IRC get togethers
> 
> decide and document the future of ForrestFriday IRC get togethers
> -----------------------------------------------------------------
> 
>                  Key: FOR-921
>                  URL: http://issues.apache.org/jira/browse/FOR-921
>              Project: Forrest
>           Issue Type: Task
>           Components: Core operations
>             Reporter: David Crossley
> 
> 
> Discussion is at:
> Re: future of Forrest Friday get togethers
> http://marc.theaimsgroup.com/?t=115130178800001
> 
> The document http://forrest.apache.org/forrest-friday.html has a notice
> about being "on hold".
> 
> http://marc.theaimsgroup.com/?l=forrest-dev&m=115284600021379
> has links to some discussion at Incubator.a.o about the use of IRC and
> there is also recent discussion at:
> http://marc.theaimsgroup.com/?t=115517193600001
> 
> 
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.0/420 - Release Date: 8/16/2006




Mime
View raw message