| 03:17.34 | *** join/#asterisk-doc jsmith (n=jsmith@smithfam.dsl.xmission.com) |
| 03:17.47 | *** mode/#asterisk-doc [+o jsmith] by ChanServ |
| 05:27.26 | *** part/#asterisk-doc jsmith (n=jsmith@smithfam.dsl.xmission.com) |
| 09:39.04 | *** join/#asterisk-doc ToTo (n=ToTo@host187-131.pool872.interbusiness.it) |
| 15:53.00 | *** join/#asterisk-doc jsmith (n=jsmith@smithfam.dsl.xmission.com) |
| 15:53.00 | *** mode/#asterisk-doc [+o jsmith] by ChanServ |
| 15:53.58 | *** topic/#asterisk-doc by jsmith -> http://www.asteriskdocs.org || Asterisk: The Future of Telephony published by O'Reilly Media -- http://www.oreilly.com/catalog/asterisk/ -- over 11,601 copies sold! -- We've got a new SVN repository! |
| 15:55.53 | blitzrage | w00t |
| 15:56.17 | jsmith | Still getting things setup on this box... |
| 16:41.25 | blitzrage | the whole box changed? |
| 16:44.39 | jsmith | Well... let's see... |
| 16:44.53 | jsmith | New mobo, new proc, new hard drive, new OS... yeah, pretty much. |
| 16:54.28 | *** join/#asterisk-doc tekati (n=captain@cpe-66-75-215-63.bak.res.rr.com) |
| 16:55.47 | blitzrage | :) |
| 17:51.40 | *** join/#asterisk-doc HDICK (n=hdick@ip5654adce.adsl-surfen.hetnet.nl) |
| 17:53.50 | HDICK | anyone willing to share some thought about the documentation? |
| 17:54.42 | HDICK | I read the last discussions at the mailing list and heard the discussion at the dev call |
| 17:57.18 | blitzrage | what would you like to know? |
| 17:57.52 | HDICK | what about using subject experts to own part of documentation |
| 17:59.02 | blitzrage | hrmmmm, not a bad idea |
| 17:59.26 | blitzrage | by "own" you mean administer :) |
| 18:00.24 | HDICK | no, i don't mind. I was more in the mood watch out what is going on and try to put it in the right perspective |
| 18:00.45 | HDICK | descriptive as well as the reference work |
| 18:02.28 | HDICK | take SIP as an example. A lot of questions could be avoided when we would have a good description so the people know the impact of changing config files |
| 18:03.30 | jsmith | HDICK: Makes sense... |
| 18:04.13 | jsmith | Unfortunately, the subject experts doing the coding aren't the ones doing the documentation for those areas. |
| 18:04.41 | HDICK | well I can not code but would not mind to put it on paper |
| 18:06.13 | HDICK | I read code that is not an issue. What would be required is to have a chat with developer to understand why they make a change, put it on paper and ask them to review |
| 18:06.28 | HDICK | what has been included |
| 18:07.02 | jsmith | That would be great! |
| 18:07.05 | jsmith | Welcome to the team! |
| 18:07.41 | HDICK | well I would not mind to start with the SIP stuff |
| 18:07.50 | jsmith | Great! |
| 18:07.58 | blitzrage | even better -- SIP is huge :) |
| 18:08.21 | HDICK | I know but I like it and have some sip background |
| 18:08.52 | blitzrage | oh yah -- thats great! |
| 18:09.10 | blitzrage | I guess we need to somehow have a place to put the new framework? |
| 18:09.42 | blitzrage | for now I think we're just supposed to be checking it out of SVN outselves, then when you make changes, submit a patch to the docs list |
| 18:09.50 | jsmith | Yep... |
| 18:09.55 | blitzrage | then those with commit rights can add it in |
| 18:09.58 | jsmith | Soon we'll have a place to host the created docs... |
| 18:10.25 | HDICK | I think we should have a chat about this and see if we can find more people that like to go forward in this direction. |
| 18:10.31 | blitzrage | after we see a commitment to a particular area with good work, then we can give someone commit access for a certain area |
| 18:10.44 | blitzrage | HDICK: we can bring it up in the conference calltomorrow maybe? |
| 18:10.54 | blitzrage | or start a thread on the mailing list |
| 18:10.56 | blitzrage | or both! :) |
| 18:11.16 | HDICK | at what time is the actual call |
| 18:11.41 | blitzrage | ummm... noon I think, but will probably be delayed an hour |
| 18:11.48 | blitzrage | plus it needs to be added to the agenda |
| 18:11.59 | jsmith | blitzrage: Noon EDT, that is. |
| 18:12.01 | blitzrage | I think actually starting a thread on the mailing list is the best first step |
| 18:12.08 | jsmith | blitzrage: HDICK is probably halfway around the world... |
| 18:12.20 | blitzrage | I thought everyone was EDT :) |
| 18:12.22 | HDICK | yes CET |
| 18:13.17 | jsmith | http://www.asterisk.org/developers/conferencecalls, but I agree with blitzrage -- we should bring this up on the -doc list first |
| 18:14.16 | HDICK | I think the most important issue that needs to be sorted is the subject ownership. We have to avoid that people are duplicating work. |
| 18:15.01 | blitzrage | I would agree if there was a LOT of people working on documentation, but I have yet to see people stepping on toes... |
| 18:15.15 | blitzrage | plus talking about who is working on what in the -doc list is a good way of overlapping too |
| 18:15.35 | blitzrage | ...good way of not overlapping* |
| 18:15.45 | *** join/#asterisk-doc ToTo (n=ToTo@host187-131.pool872.interbusiness.it) |
| 18:18.30 | HDICK | Well what would be the best. Bring it up as a proposal or ask who would like to be involved? |
| 18:20.36 | blitzrage | both :) |
| 18:21.42 | jsmith | I vote for both |
| 18:27.20 | HDICK | Shall I draft something and email to you |
| 18:28.50 | blitzrage | just go ahead and put it on the mailing list |
| 18:30.38 | HDICK | OK |
| 19:14.10 | HDICK | the email has been sent out |
| 23:53.50 | *** join/#asterisk-doc alerios (n=alerios@201.244.243.43) |