Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
I've updated your original document in the MCF wiki to be current. I had forgotten it was there. Karl On Tue, Mar 1, 2011 at 5:29 PM, Grant Ingersoll gsing...@apache.org wrote: On Mar 1, 2011, at 11:30 AM, Karl Wright wrote: Karl, what do you think we can do to make it easier for people to get into the code? Are other people putting up patches? What's been happening is that we do indeed get code from contributors, but the contributors in question seem like they are new to open-source. I usually have to provide quite a bit of process advice, and explain the steps, and even sometimes do a chunk of the code myself. So we definitely are not at the point yet where we have knowledgeable developers contributing regularly. We should document on the wiki the steps for contributing patches, like we do for Lucene, et. al. This generally helps and gives us something to point people to in the future. Also, if we get a few patches from one or two people on a regular basis, we should look to add them as committers (discussion on specific people should be handled on the project PMC list). Also, what do people think about collapsing c-dev@ and c-user@ into just connectors-dev@? -Grant
Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 March 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
On Tue, Mar 1, 2011 at 11:15 AM, Grant Ingersoll gsing...@apache.org wrote: I think we need to brainstorm around this board report a bit more, especially the steps for graduation: We definitely need more active committers. It's basically Karl at this point and Robert, Simon and I jump in from time to time for higher level discussions. I can tell you schedule wise I'm going to have a hard time contributing code for the foreseeable future, which is unfortunate because when I signed up for this I really thought I would be more involved in it. So, how do we get people engaged more? We presumably have a ton of committers already on the project, but none are contributing. One thought is that we should merge user and dev mailing lists together. This is actually considered best practice for incubating projects (I had missed that) since it gets users interacting w/ devs right away and can likely help encourage contributions. In order to graduate, I think we need the following: 1. one or two more releases 2. At least 3 other active committers besides Karl 3. Whatever other criteria is listed on the Incubator site (we can review it) I agree. Karl, what do you think we can do to make it easier for people to get into the code? Are other people putting up patches? What's been happening is that we do indeed get code from contributors, but the contributors in question seem like they are new to open-source. I usually have to provide quite a bit of process advice, and explain the steps, and even sometimes do a chunk of the code myself. So we definitely are not at the point yet where we have knowledgeable developers contributing regularly. On the other hand, ManifoldCF in Action went MEAP just last night, and I have structured the book to make it a very good training exercise for potential contributors. My suggestion is to work that angle as much as possible. I'm looking now for people who want free copies in exchange for reviews for marketing purposes. This probably means you gotta at least read it. ;-) Let me know if you're willing. Karl On Mar 1, 2011, at 9:00 AM, no-re...@apache.org wrote: Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 March 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- Grant Ingersoll http://www.lucidimagination.com
Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
Also, would LucidImagination be willing to put up a blurb for the book on its site? Karl On Tue, Mar 1, 2011 at 11:30 AM, Karl Wright daddy...@gmail.com wrote: On Tue, Mar 1, 2011 at 11:15 AM, Grant Ingersoll gsing...@apache.org wrote: I think we need to brainstorm around this board report a bit more, especially the steps for graduation: We definitely need more active committers. It's basically Karl at this point and Robert, Simon and I jump in from time to time for higher level discussions. I can tell you schedule wise I'm going to have a hard time contributing code for the foreseeable future, which is unfortunate because when I signed up for this I really thought I would be more involved in it. So, how do we get people engaged more? We presumably have a ton of committers already on the project, but none are contributing. One thought is that we should merge user and dev mailing lists together. This is actually considered best practice for incubating projects (I had missed that) since it gets users interacting w/ devs right away and can likely help encourage contributions. In order to graduate, I think we need the following: 1. one or two more releases 2. At least 3 other active committers besides Karl 3. Whatever other criteria is listed on the Incubator site (we can review it) I agree. Karl, what do you think we can do to make it easier for people to get into the code? Are other people putting up patches? What's been happening is that we do indeed get code from contributors, but the contributors in question seem like they are new to open-source. I usually have to provide quite a bit of process advice, and explain the steps, and even sometimes do a chunk of the code myself. So we definitely are not at the point yet where we have knowledgeable developers contributing regularly. On the other hand, ManifoldCF in Action went MEAP just last night, and I have structured the book to make it a very good training exercise for potential contributors. My suggestion is to work that angle as much as possible. I'm looking now for people who want free copies in exchange for reviews for marketing purposes. This probably means you gotta at least read it. ;-) Let me know if you're willing. Karl On Mar 1, 2011, at 9:00 AM, no-re...@apache.org wrote: Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 March 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- Grant Ingersoll http://www.lucidimagination.com
Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
On Mar 1, 2011, at 11:30 AM, Karl Wright wrote: Karl, what do you think we can do to make it easier for people to get into the code? Are other people putting up patches? What's been happening is that we do indeed get code from contributors, but the contributors in question seem like they are new to open-source. I usually have to provide quite a bit of process advice, and explain the steps, and even sometimes do a chunk of the code myself. So we definitely are not at the point yet where we have knowledgeable developers contributing regularly. We should document on the wiki the steps for contributing patches, like we do for Lucene, et. al. This generally helps and gives us something to point people to in the future. Also, if we get a few patches from one or two people on a regular basis, we should look to add them as committers (discussion on specific people should be handled on the project PMC list). Also, what do people think about collapsing c-dev@ and c-user@ into just connectors-dev@? -Grant
Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
+1 for collapsing, provided we can merge the existing subscription lists. If we can't do that, than I'm not in favor. Karl On Tue, Mar 1, 2011 at 5:29 PM, Grant Ingersoll gsing...@apache.org wrote: On Mar 1, 2011, at 11:30 AM, Karl Wright wrote: Karl, what do you think we can do to make it easier for people to get into the code? Are other people putting up patches? What's been happening is that we do indeed get code from contributors, but the contributors in question seem like they are new to open-source. I usually have to provide quite a bit of process advice, and explain the steps, and even sometimes do a chunk of the code myself. So we definitely are not at the point yet where we have knowledgeable developers contributing regularly. We should document on the wiki the steps for contributing patches, like we do for Lucene, et. al. This generally helps and gives us something to point people to in the future. Also, if we get a few patches from one or two people on a regular basis, we should look to add them as committers (discussion on specific people should be handled on the project PMC list). Also, what do people think about collapsing c-dev@ and c-user@ into just connectors-dev@? -Grant
Re: Incubator PMC/Board report for March 2011 (connectors-dev@incubator.apache.org)
We should document on the wiki the steps for contributing patches, like we do for Lucene, et. al. This generally helps and gives us something to point people to in the future. Also, if we get a few patches from one or two people on a regular basis, we should look to add them as committers (discussion on specific people should be handled on the project PMC list). I don't think anybody has hit the regular contribution threshold, but I'll certainly signal when somebody passes it. I found the Lucene patch contribution page, but it's in the wiki. Any preference for the site vs. the wiki for this? Probably process stuff goes in wiki? Karl
