Members present: jan____, dch, garren, Kxepal ---------------- Meeting summary: ----------------
1. Preface 2. jira deathmarch a. JIRA cleanup next week, all welcome. Pick tickets, tidy up for 1.3.x or 1.4.+ releases, or terminate with extreme prejudice where appropriate. (dch, 2) b. dch will do Tuesday (dch, 2) 3. docs 4. git discussion a. reminder to get some further comments on the git workflow thread - even a +1 or "I don't care +0" will help. This will be something we all need to get our heads round. Speak up or forever use cvs. (dch, 4) 5. 1.3.x 6. docs workflow 7. meetings over May -------- Actions: -------- - JIRA cleanup next week, all welcome. Pick tickets, tidy up for 1.3.x or 1.4.+ releases, or terminate with extreme prejudice where appropriate. (dch, 12:14:09) IRC log follows: # 1. Preface # 12:11:56 [dch]: ASFBot: meeting start 12:12:04 [dch]: damn postfix bot syntax 12:12:24 [jan____]: I blame Humbedooh # 2. jira deathmarch # 12:13:26 [dch]: JIRA's getting a bit crusty, we have old stuff and new stuff and a bit untidy. I'll pick a day, mmm Tuesday next week, and have a crack at a tidyup. All welcome to join in, sync or async as you like. 12:14:09 [dch]: #action JIRA cleanup next week, all welcome. Pick tickets, tidy up for 1.3.x or 1.4.+ releases, or terminate with extreme prejudice where appropriate. 12:14:17 [dch]: #info dch will do Tuesday # 3. docs # 12:16:22 [dch]: we have 1 pr from skoegel on replication (yay) https://github.com/apache/couchdb/pull/58 but it needs some love on passing distcheck, I'll see if he wants to do it, or fix it myself if not. 12:17:02 [dch]: Kxepal: news from you? 12:18:16 [dch]: last bit from me, I made good progress on integrating the ASF comments system into read-the-docs site COUCHDB-1783 but can't figure out how to force the comments only into the footer. More futzing reqd. 12:18:17 [Kxepal]: for context: https://issues.apache.org/jira/browse/COUCHDB-1781 - this will be my main target for now. doc articles flow is needed to be a bit logical. I have some plan and view about, but I will be very happy to see what others think about 12:18:37 [Kxepal]: dch: sorry, slow-typing-hands (: 12:19:15 [dch]: Kxepal: SHIP IT. It looks great, you have the power, let me know if I can help. Let's get a branch going. 12:19:30 [Kxepal]: dch: skoegel patch looks good, I thinks that I'll handle it with overall refactoring 12:20:07 [Kxepal]: since replications are also needed in protocol description, conflicts resolution and other useful things from wiki, gists, so and ml 12:20:07 [dch]: Kxepal: great, I'll add a comment to that effect in the ticket and you can pick it up. Do you think we could get this in 1.3.x? 12:20:37 [dch]: "should docs promote 3rd party tools"? is really a q for the mailing list, maybe separate thread? 12:21:00 [Kxepal]: dch: sure, I'll targeting on 1.3.x for now, so they are may be picked to 1.3.x branch 12:21:07 [Kxepal]: since there is nothing special for 1.4.x for now 12:21:26 [Kxepal]: dch: there was question about them on ml, I can bump those mail 12:21:46 [dch]: I'll keep an eye out this time. # 4. git discussion # 12:22:59 [dch]: #info reminder to get some further comments on the git workflow thread - even a +1 or "I don't care +0" will help. This will be something we all need to get our heads round. Speak up or forever use cvs. # 5. 1.3.x # 12:23:49 [dch]: I can't add anything as nslater is not here, anybody else want to chip in? 12:24:34 [Kxepal]: dch: I'm a bit confused with git workflow discussion thread. may be it's better to summarize all ideas, rules and policies with single mail? and after that vote for them or against 12:25:19 [dch]: Kxepal: good idea. It's time for a summary thread. I'm a bit cramped atm, anybody willing to pick that action up? 12:25:41 [garren]: Kxepal: I agree with you there. I'm no git expert so a little more detail and a summary would be great. # 6. docs workflow # 12:28:04 [Kxepal]: dch: np (: there is just a simple question that references to git workflow one: where to commit the docs changes and how sync them between release branches 12:30:04 [dch]: I'd not thought very hard about this. I guess in the new workflow we'll prompt people to document their changes (in changes.rst for example, or with versionadded tags), and these get merged in as required to master/1.3.x or whatever. 12:30:26 [dch]: and for incremental improvements we *could* run an ongoing branch that we pull into master/1.3.x as reqd? 12:30:26 [dch]: ACTION is not sure 12:31:05 [Kxepal]: versionadded tags are nice to highlight things, but not for generate changes article 12:31:34 [dch]: I'd love not to have to do that manually each time. 12:32:27 [Kxepal]: for example, what's news in Python docs are stand alone articles that people writes and sync with peps/bugs tickets, describing things more detailed 12:32:35 [dch]: Kxepal: ideas on a better way to handle this are welcome, the release managers will be delighted 12:34:08 [dch]: k, let's roll next topic. 12:34:16 [dch]: any takers? 12:34:43 [Kxepal]: dch: ok, I suppose we'll return to this question back on next release preparations # 7. meetings over May # 12:36:21 [dch]: I'm away next week, in Germany, then again for 2 weeks at end of May + beginning of June. 12:36:46 [dch]: Any takers for running the meeting? I'm happy to send out the reminder etc, you'd just have to turn up and ping people. 12:38:43 [Kxepal]: dch: what requirements for this? 12:38:58 [dch]: see above :-). that's it. 12:39:35 [dch]: ping people on the #couchdb* channels when we are going to start, ask for topics, run through them,, close up and tell asfbot to send an email 12:41:20 [Kxepal]: I see (: if nobody have objections I can try, but may delegate this honor to someone who can do this better 12:41:35 [dch]: Kxepal: you'll be a flying star. If I can do it, anybody can and likely better. 12:41:43 [dch]: ok thanks! 12:42:56 [dch]: #info: Kxepal to host meetings in next few weeks when dch is away. be gentle!
