Re: wiki access for ClimateModelDiagnosticAnalyzerProposal
On Wed, 8 Apr 2015, Whitehall, Kim D (398M) wrote: my user account is kimwhitehall Karma granted, good luck with the proposal! Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
File podling reports next month rather than late
On Sat, Apr 4, 2015 at 9:29 PM, Ted Dunning ted.dunn...@gmail.com wrote: General section looks grand. We have a few projects unreported, DataFu, ODF Toolkit, OpenAz. I know a bit about Datafu which has been very quiet for some time. Who knows more about the others? Andrei, Konstantin, Suresh are the respective shepherds? Any thoughts? We should feel good about the content of the report for this month -- it meets or exceeds our usual standards. However, we've had a few process glitches here at the end. * The report was filed with the Board on Tuesday -- one day early. * The report was sent to board@apache and committed to the Board's agenda in svn, but private@incubator has not received a copy. * The version of the report filed with the Board contains changes which were not added to the wiki version. * I neglected to let Ted know that he should mark the wiki as FINAL before submitting to the Board. * At least one Mentor signoff was added to the wiki after the report was filed. * OpenAZ just submitted a report moments ago. I don't want OpenAZ to feel as though their report is unwanted, so I'm going to take action to ensure that the Board sees it. However... The IPMC should not encourage podlings to file late reports. First, the Board expects the Incubator to review podling reports, not just forward them blindly. When reports are late, Mentors, shepherds, and community members are not fully able to take part in the review process -- including raising objections about what's in the report if necessary. Second, we have a shortage of people who are willing to work on coordinating the Incubator's report. Adding to our workload with a bunch of last minute changes is unhelpful. The alternative is simply to encourage podlings to file a report next month rather than file late. Skipping one month is not a big deal. For TLPs, the Board has exactly the same preference -- file next month rather than at the last minute, because last minute filings do not allow sufficient time for review. To clean up this month's report, I will take the following actions later this evening. 1. Add the changes from the filed version of the report to the wiki. 2. Review the OpenAZ report to ensure that its format is consistent with the rest of the report, add them to the podling summary, double check the narrative, etc. 3. Check for any other Mentor signoffs, etc. added after the report was filed. 4. Mark the wiki as final. 5. Commit the modifications to the Board agenda. Since I'm taking great care to make sure things get done right and no Board member has yet remarked on the Incubator's report, I trust that the Board and the IPMC Chair will tolerate my overstep. 6. Forward the final version of the report to private@incubator. Thanks again to everyone who has contributed towards another strong report from the Incubator this month -- I'm confident that we'll meet the same standards next month but with smoother running. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: File podling reports next month rather than late
On Wed, Apr 8, 2015 at 7:32 PM, John D. Ament johndam...@apache.org wrote: On Wed, Apr 8, 2015 at 10:02 PM Marvin Humphrey mar...@rectangular.com wrote: We should feel good about the content of the report for this month -- it meets or exceeds our usual standards. However, we've had a few process glitches here at the end. * The report was filed with the Board on Tuesday -- one day early. * The report was sent to board@apache and committed to the Board's agenda in svn, but private@incubator has not received a copy. * The version of the report filed with the Board contains changes which were not added to the wiki version. These last two to me are pretty bad. Especially since I'm sitting in on a long drawn out discussion on a TLP where we have board members accusing PMC and committers of said TLP doing things behind peoples backs (no, not the incubator). Considering this is Ted's first month as VP I'm going to assume this was purely him being a n00b at submitting the report. Ted's additions to the narrative are very nice and are one of the reasons that the report is strong this month. Glitches are to be expected when there's a new Chair. Ted should feel confident that he has my support -- I want his term in office to be a success, and it would be great if we didn't burn him out so that maybe he sticks around to help the next Chair. ;) We'll get the process stuff tightened up. Second, we have a shortage of people who are willing to work on coordinating the Incubator's report. Adding to our workload with a bunch of last minute changes is unhelpful. Good news at least, I'm back walking up right and most other issues are clearing off my plate so I should be able to help out again with the upcoming report. Sweet! We should try to recruit some more people to take a turn as Report Manager. It would be great if you could help support them. I've taken care of formatting for OpenAZ. Wiki's being super slow though. Thanks! I think the wiki slowness was related to the Infra emergency maintenance (now completed successfully). Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: File podling reports next month rather than late
On Wed, Apr 8, 2015 at 10:02 PM Marvin Humphrey mar...@rectangular.com wrote: On Sat, Apr 4, 2015 at 9:29 PM, Ted Dunning ted.dunn...@gmail.com wrote: General section looks grand. We have a few projects unreported, DataFu, ODF Toolkit, OpenAz. I know a bit about Datafu which has been very quiet for some time. Who knows more about the others? Andrei, Konstantin, Suresh are the respective shepherds? Any thoughts? We should feel good about the content of the report for this month -- it meets or exceeds our usual standards. However, we've had a few process glitches here at the end. * The report was filed with the Board on Tuesday -- one day early. * The report was sent to board@apache and committed to the Board's agenda in svn, but private@incubator has not received a copy. * The version of the report filed with the Board contains changes which were not added to the wiki version. These last two to me are pretty bad. Especially since I'm sitting in on a long drawn out discussion on a TLP where we have board members accusing PMC and committers of said TLP doing things behind peoples backs (no, not the incubator). Considering this is Ted's first month as VP I'm going to assume this was purely him being a n00b at submitting the report. * I neglected to let Ted know that he should mark the wiki as FINAL before submitting to the Board. * At least one Mentor signoff was added to the wiki after the report was filed. * OpenAZ just submitted a report moments ago. I don't want OpenAZ to feel as though their report is unwanted, so I'm going to take action to ensure that the Board sees it. However... The IPMC should not encourage podlings to file late reports. Agreed, though I feel like we've had this discussion before and I ended up on the losing side of it. First, the Board expects the Incubator to review podling reports, not just forward them blindly. When reports are late, Mentors, shepherds, and community members are not fully able to take part in the review process -- including raising objections about what's in the report if necessary. Second, we have a shortage of people who are willing to work on coordinating the Incubator's report. Adding to our workload with a bunch of last minute changes is unhelpful. Good news at least, I'm back walking up right and most other issues are clearing off my plate so I should be able to help out again with the upcoming report. The alternative is simply to encourage podlings to file a report next month rather than file late. Skipping one month is not a big deal. For TLPs, the Board has exactly the same preference -- file next month rather than at the last minute, because last minute filings do not allow sufficient time for review. To clean up this month's report, I will take the following actions later this evening. 1. Add the changes from the filed version of the report to the wiki. 2. Review the OpenAZ report to ensure that its format is consistent with the rest of the report, add them to the podling summary, double check the narrative, etc. I've taken care of formatting for OpenAZ. Wiki's being super slow though. 3. Check for any other Mentor signoffs, etc. added after the report was filed. 4. Mark the wiki as final. 5. Commit the modifications to the Board agenda. Since I'm taking great care to make sure things get done right and no Board member has yet remarked on the Incubator's report, I trust that the Board and the IPMC Chair will tolerate my overstep. 6. Forward the final version of the report to private@incubator. Thanks again to everyone who has contributed towards another strong report from the Incubator this month -- I'm confident that we'll meet the same standards next month but with smoother running. You would think for a guy with such dedication to getting the board report right, he'd be on the IPMC. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: wiki access for ClimateModelDiagnosticAnalyzerProposal
Thanks Nick! Best regards, Kim ** Kim Whitehall, Ph.D. Scientific Applications Software Engineer Computer Science for Data Intensive Applications Group (398M) NASA Jet Propulsion Laboratory, 4800 Oak Grove Drive, Pasadena, CA 91109, USA Mailstop: 158 - 242 Phone: (+1) (818) 354-5162 Mobile: (+1) (626) 808-7026 Email: kim.d.whiteh...@jpl.nasa.govmailto:kim.d.whiteh...@jpl.nasa.gov Fax: (+1) (818) 393-1190 On WednesdayApr 8, at 3:07 PM, Nick Burch apa...@gagravarr.orgmailto:apa...@gagravarr.org wrote: On Wed, 8 Apr 2015, Whitehall, Kim D (398M) wrote: my user account is kimwhitehall Karma granted, good luck with the proposal! Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgmailto:general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.orgmailto:general-h...@incubator.apache.org
wiki access for ClimateModelDiagnosticAnalyzerProposal
Hi, my user account is kimwhitehall I would like access to edit the ClimateModelDiagnosticAnalyzerProposal wiki Thanks! Best regards, Kim
Re: IP Clearance Questions
On 4/8/15, 11:09 AM, Marvin Humphrey mar...@rectangular.com wrote: JIRA has been used for this purpose before. However, if we're going to the trouble of codifying this process, is there any reason not to `svn mkdir` the `donations` directory and use it henceforth? IMO, it would be better to not use SVN. Most version control systems make it difficult to truly delete something. If something truly bad is in the donation, you may get forced to truly delete it. An SVN remove only hides it. I’ve been using reviews.a.o for donations. -Alex
Re: IP Clearance Questions
On Wednesday, April 8, 2015, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Apr 8, 2015 at 7:05 AM, jan i j...@apache.org javascript:; wrote: But even so In Corinthia we bended the rules and imported directly into out git repo. This still ensures a record == initial commit. I trust that Corinthia's actions were reasonable, but bending the rules is an approach you might take when the rules don't fit; it's not a justification for keeping bad rules. We should fix this document so that it doesn't keep coming up. +1, to me it seems we have a lot of projects where the initial repo == the donation, so I am for keeping it simple and remove the donation area from the doc. we (IPMC) consider mostly new project. ASF as a whole must consider how to handle donations which are addon to an existing codebase. Also, note that this particular form is not for incoming podlings. The important message here is that ASF must acknowledge the grant before it comes into any of our repos. The intent is also to assemble exactly what is being granted and provide a permanent legal record of the donation. which is typically identical to the initial repo. If it's a tarball containing a export of from version control with no history, then it's clear: only that version. If it's a Git repo or a Subversion dump file, does the grant include all past commits on the mainline? All branches, all tags? What if there's some bad history? This is simple if we get it with history, then it is included, however we are well advised to check that the SGA it is limited to current version. If it's a Git SHA, does the grant include all past commits, or other branches -- or is it only the *tree* represented by that SHA? Is anything crucial missing from the donation -- e.g. plugins, documentation, or platform-specific code maintained separately? The IP clearance process should ensure that all such questions are answered and entered into the permanent record. is it not more correct to say that the IP clearance process must ensure that the delivery does not exceed the SGA. rgds jan i Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Sent from My iPad, sorry for any misspellings.
Re: File podling reports next month rather than late
On Wed, Apr 8, 2015 at 9:00 PM, Marvin Humphrey mar...@rectangular.com wrote: Thanks again to everyone who has contributed towards another strong report from the Incubator this month -- I'm confident that we'll meet the same standards next month but with smoother running. Thanks for the help Marvin. The processes are, as usual with Apache, simple, but a bit opaque the first time around. And thanks for Roman for helping with the transition.
Re: IP Clearance Questions
On Wednesday, April 8, 2015, Niclas Hedhman nic...@hedhman.org wrote: I would like to bring this question up again. BLOCKER. The http://incubator.apache.org/ip-clearance/ip-clearance-template.html document states that quote *Note:* the grant form *must* be acknowledged before continuing. If the source is referenced by checksum in the grant, commit the canonical tarball for the donated code into the incubator drop area (/repos/asf/incubator/donations) together with a checksum and a detached signature. This will ensure that apache has a legal record of the grant. /quote which means that no one can complete this, without the drop area, unless there is a new process and this document is out of date. why do you see the donations dir as a problem? But even so In Corinthia we bended the rules and imported directly into out git repo. This still ensures a record == initial commit. The important message here is that ASF must acknowledge the grant before it comes into any of our repos. just my opinion, I am not the legal expert jan i Cheers Niclas On Tue, Mar 17, 2015 at 7:29 AM, P. Taylor Goetz ptgo...@gmail.com javascript:; wrote: Thanks for the clarification, Ross. That's what I figured. In terms of the source drop, it's been attached to the associated JIRA, and the SHA1 is in the yet-to-be-submitted ip clearance XML, and should be in the grant as well. My guess is that MIGHT suffice in terms of it being documented in ASF-controlled systems. I'd like to hear if the incubator drop area has been moved, or deprecated in favor of an alternative process. Either way, we should think about updating the template/docs to reflect the current process. -Taylor On Mar 16, 2015, at 3:36 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com javascript:; wrote: 1. CCLA is never used instead of an SGA, they serve different purposes. The SGA is for a body of work that pre-exists entry into the foundation. The CCLA is an optional document that says future work by named individuals can be contributed. 2. Yes (although secretary tries his best to CC the appropriate people on his replies) 3. Yes 4. Pass - so I'll repeat the question for others - The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: P. Taylor Goetz [mailto:ptgo...@gmail.com javascript:;] Sent: Monday, March 16, 2015 12:20 PM To: Incubator Subject: IP Clearance Questions I'm working on filling out the necessary IP Clearance paperwork for code donation and have a few questions (forgive me if they are stupid, this is my first time through the process): Based on the IP clearance template documentation [1]: 1. When should a CCLA be used as opposed to a grant [2]? 2. How do I verify that a grant or ccla has been acknowledged by the ASF Secretary? Poll the grants.txt/cclas.txt files for changes? 3. I assume I don't commit anything until the grant/ccla has been acknowledged. Is this correct? 4. The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Thanks in advance, -Taylor [1] http://incubator.apache.org/ip-clearance/ip-clearance-template.html [2] https://www.apache.org/licenses/software-grant.txt [3] https://svn.apache.org/repos/asf/incubator/donations - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java -- Sent from My iPad, sorry for any misspellings.
Re: IP Clearance Questions
I would like to bring this question up again. BLOCKER. The http://incubator.apache.org/ip-clearance/ip-clearance-template.html document states that quote *Note:* the grant form *must* be acknowledged before continuing. If the source is referenced by checksum in the grant, commit the canonical tarball for the donated code into the incubator drop area (/repos/asf/incubator/donations) together with a checksum and a detached signature. This will ensure that apache has a legal record of the grant. /quote which means that no one can complete this, without the drop area, unless there is a new process and this document is out of date. Cheers Niclas On Tue, Mar 17, 2015 at 7:29 AM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks for the clarification, Ross. That's what I figured. In terms of the source drop, it's been attached to the associated JIRA, and the SHA1 is in the yet-to-be-submitted ip clearance XML, and should be in the grant as well. My guess is that MIGHT suffice in terms of it being documented in ASF-controlled systems. I'd like to hear if the incubator drop area has been moved, or deprecated in favor of an alternative process. Either way, we should think about updating the template/docs to reflect the current process. -Taylor On Mar 16, 2015, at 3:36 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: 1. CCLA is never used instead of an SGA, they serve different purposes. The SGA is for a body of work that pre-exists entry into the foundation. The CCLA is an optional document that says future work by named individuals can be contributed. 2. Yes (although secretary tries his best to CC the appropriate people on his replies) 3. Yes 4. Pass - so I'll repeat the question for others - The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: P. Taylor Goetz [mailto:ptgo...@gmail.com] Sent: Monday, March 16, 2015 12:20 PM To: Incubator Subject: IP Clearance Questions I'm working on filling out the necessary IP Clearance paperwork for code donation and have a few questions (forgive me if they are stupid, this is my first time through the process): Based on the IP clearance template documentation [1]: 1. When should a CCLA be used as opposed to a grant [2]? 2. How do I verify that a grant or ccla has been acknowledged by the ASF Secretary? Poll the grants.txt/cclas.txt files for changes? 3. I assume I don't commit anything until the grant/ccla has been acknowledged. Is this correct? 4. The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Thanks in advance, -Taylor [1] http://incubator.apache.org/ip-clearance/ip-clearance-template.html [2] https://www.apache.org/licenses/software-grant.txt [3] https://svn.apache.org/repos/asf/incubator/donations - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java
Re: [PROPOSAL] Climate Model Diagnostic Analyzer
Sounds great Chris. Thanks much. I'll get myself added in there in just a second. -- Joyce On Wed, Apr 8, 2015 at 11:11 AM, Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov wrote: Yes, Mike would love for you to help out! Please add yourself as a mentor thank you! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Michael Joyce jo...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, April 8, 2015 at 10:46 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Climate Model Diagnostic Analyzer Great proposal Chris. If you're still looking for mentors I would be happy to help out. -- Joyce On Mon, Apr 6, 2015 at 11:24 AM, jonathon toki.kant...@gmail.com wrote: On 06/04/15 17:05, James Carman wrote: I would love to help out. I don't know much about the problem domain, but I am a sciency kind of guy. Mentors don't need to know the problem domain. The most important quality of a mentor is outstanding communication skills. The second most important quality is knowing when to be diplomatic, and when not to be diplomatic. The third most important qualities are: * How to anticipate potential issues; * How to solve problems; * How to resolve points of difference; * How to guide a group into following _The Apache Way_; * Teaching the project how to solve problems; The legacy of a good mentor, is a project that anticipates potential issues, and solves them, without ever realizing that they have done so. jonathon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance Questions
Ok, I was more reading it as must be placed into the drop box with the checksum so it can be referenced properly. In any event, I think the text is confusing me quite a bit and would like to know what is 'proper' process for a GitHub project to come in? Does it even make sense when Git has no 'canonical' repository? Cheers Niclas On Wed, Apr 8, 2015 at 10:05 PM, jan i j...@apache.org wrote: On Wednesday, April 8, 2015, Niclas Hedhman nic...@hedhman.org wrote: I would like to bring this question up again. BLOCKER. The http://incubator.apache.org/ip-clearance/ip-clearance-template.html document states that quote *Note:* the grant form *must* be acknowledged before continuing. If the source is referenced by checksum in the grant, commit the canonical tarball for the donated code into the incubator drop area (/repos/asf/incubator/donations) together with a checksum and a detached signature. This will ensure that apache has a legal record of the grant. /quote which means that no one can complete this, without the drop area, unless there is a new process and this document is out of date. why do you see the donations dir as a problem? But even so In Corinthia we bended the rules and imported directly into out git repo. This still ensures a record == initial commit. The important message here is that ASF must acknowledge the grant before it comes into any of our repos. just my opinion, I am not the legal expert jan i Cheers Niclas On Tue, Mar 17, 2015 at 7:29 AM, P. Taylor Goetz ptgo...@gmail.com javascript:; wrote: Thanks for the clarification, Ross. That's what I figured. In terms of the source drop, it's been attached to the associated JIRA, and the SHA1 is in the yet-to-be-submitted ip clearance XML, and should be in the grant as well. My guess is that MIGHT suffice in terms of it being documented in ASF-controlled systems. I'd like to hear if the incubator drop area has been moved, or deprecated in favor of an alternative process. Either way, we should think about updating the template/docs to reflect the current process. -Taylor On Mar 16, 2015, at 3:36 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com javascript:; wrote: 1. CCLA is never used instead of an SGA, they serve different purposes. The SGA is for a body of work that pre-exists entry into the foundation. The CCLA is an optional document that says future work by named individuals can be contributed. 2. Yes (although secretary tries his best to CC the appropriate people on his replies) 3. Yes 4. Pass - so I'll repeat the question for others - The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: P. Taylor Goetz [mailto:ptgo...@gmail.com javascript:;] Sent: Monday, March 16, 2015 12:20 PM To: Incubator Subject: IP Clearance Questions I'm working on filling out the necessary IP Clearance paperwork for code donation and have a few questions (forgive me if they are stupid, this is my first time through the process): Based on the IP clearance template documentation [1]: 1. When should a CCLA be used as opposed to a grant [2]? 2. How do I verify that a grant or ccla has been acknowledged by the ASF Secretary? Poll the grants.txt/cclas.txt files for changes? 3. I assume I don't commit anything until the grant/ccla has been acknowledged. Is this correct? 4. The incubator drop area [3] doesn't seem to exist. Where should I commit the tarball once everything else is in order? Thanks in advance, -Taylor [1] http://incubator.apache.org/ip-clearance/ip-clearance-template.html [2] https://www.apache.org/licenses/software-grant.txt [3] https://svn.apache.org/repos/asf/incubator/donations - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java -- Sent from My iPad, sorry for any misspellings. -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java
Re: IP Clearance Questions
On Wed, Apr 8, 2015 at 7:05 AM, jan i j...@apache.org wrote: But even so In Corinthia we bended the rules and imported directly into out git repo. This still ensures a record == initial commit. I trust that Corinthia's actions were reasonable, but bending the rules is an approach you might take when the rules don't fit; it's not a justification for keeping bad rules. We should fix this document so that it doesn't keep coming up. Also, note that this particular form is not for incoming podlings. The important message here is that ASF must acknowledge the grant before it comes into any of our repos. The intent is also to assemble exactly what is being granted and provide a permanent legal record of the donation. If it's a tarball containing a export of from version control with no history, then it's clear: only that version. If it's a Git repo or a Subversion dump file, does the grant include all past commits on the mainline? All branches, all tags? What if there's some bad history? If it's a Git SHA, does the grant include all past commits, or other branches -- or is it only the *tree* represented by that SHA? Is anything crucial missing from the donation -- e.g. plugins, documentation, or platform-specific code maintained separately? The IP clearance process should ensure that all such questions are answered and entered into the permanent record. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Climate Model Diagnostic Analyzer
Yes, Mike would love for you to help out! Please add yourself as a mentor thank you! ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Michael Joyce jo...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, April 8, 2015 at 10:46 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Climate Model Diagnostic Analyzer Great proposal Chris. If you're still looking for mentors I would be happy to help out. -- Joyce On Mon, Apr 6, 2015 at 11:24 AM, jonathon toki.kant...@gmail.com wrote: On 06/04/15 17:05, James Carman wrote: I would love to help out. I don't know much about the problem domain, but I am a sciency kind of guy. Mentors don't need to know the problem domain. The most important quality of a mentor is outstanding communication skills. The second most important quality is knowing when to be diplomatic, and when not to be diplomatic. The third most important qualities are: * How to anticipate potential issues; * How to solve problems; * How to resolve points of difference; * How to guide a group into following _The Apache Way_; * Teaching the project how to solve problems; The legacy of a good mentor, is a project that anticipates potential issues, and solves them, without ever realizing that they have done so. jonathon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance Questions
On Wed, Apr 8, 2015 at 6:31 AM, Niclas Hedhman nic...@hedhman.org wrote: I would like to bring this question up again. BLOCKER. The http://incubator.apache.org/ip-clearance/ip-clearance-template.html document states that quote *Note:* the grant form *must* be acknowledged before continuing. If the source is referenced by checksum in the grant, commit the canonical tarball for the donated code into the incubator drop area (/repos/asf/incubator/donations) together with a checksum and a detached signature. This will ensure that apache has a legal record of the grant. /quote which means that no one can complete this, without the drop area, unless there is a new process and this document is out of date. JIRA has been used for this purpose before. However, if we're going to the trouble of codifying this process, is there any reason not to `svn mkdir` the `donations` directory and use it henceforth? There are also outdated references to ASF SVN in that document which should be changed to ASF version control or similar. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
