JIRA problem
I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
I would assume that you will have to go to this page: https://issues.apache.org/jira/plugins/servlet/project-config/KAFKA/roles I don’t have access there, I’ve just replaced project name SQOOP with KAFKA :-) Jarcec On Jul 18, 2014, at 9:35 AM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
To my best knowledge ICLA is required only for committers - people that do have commit bit on ASF repositories. Contributors can’t commit their patch themselves and hence they have to attach their patch to JIRA where they implicitly agree with all the legal stuff. There is some license agreement about that, but I can’t find it right now. Jarcec On Jul 18, 2014, at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
I do see separate concerns here, so let me describe how we’re addressing them in other projects where I’m involved. It doesn’t mean that Kafka need to follow them, just sharing my experience. 1) Submitting a patch to JIRA No paper work required, all legalities are resolved implicitly by the fact that contributor submitted patch to JIRA. There is small trouble with the fact that new contributor can’t assign the item to himself - this is the way JIRA is configured and you need to talk with Infra about changing that. I’ve tried to change that at some point in the past for my projects and I’ve failed. Feel free to ask again though :-) 2) Editing wiki We’re giving edit privileges to anyone who asks for it. So far it worked very well for us. 3) Promoting contributor to committer Do require ICLA to be signed and faxed to ASF. Jarcec On Jul 18, 2014, at 10:25 AM, Jay Kreps jay.kr...@gmail.com wrote: I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
Jay, I agree with you. This goes back to the spam fiasco that occurred on confluence and the pendulum swinging because of it. Re-reading that email there doesn't seem anything specific requiring us to have them sign the ICLA but it looks like that is a requirement if we wanted INFRA to assign the person in the asf-cla group... so we could just have our own contributor group and manage that in confluence however we wanted? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 1:25 PM, Jay Kreps jay.kr...@gmail.com wrote: I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
Joe--that sounds great, let's do that! So I guess we should put something in the wiki about how to get added to that group? Jarek--thanks for the summary, that is very helpful. I will follow-up with the infra people on letting people assign JIRAs. -jay On Fri, Jul 18, 2014 at 10:36 AM, Joe Stein joe.st...@stealth.ly wrote: Jay, I agree with you. This goes back to the spam fiasco that occurred on confluence and the pendulum swinging because of it. Re-reading that email there doesn't seem anything specific requiring us to have them sign the ICLA but it looks like that is a requirement if we wanted INFRA to assign the person in the asf-cla group... so we could just have our own contributor group and manage that in confluence however we wanted? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 1:25 PM, Jay Kreps jay.kr...@gmail.com wrote: I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
Re: JIRA problem
I once noticed Samza also had a similar problem and Jacob resolved it by talking to the Apache people. We can probably ask him how he gets it done. On Fri, Jul 18, 2014 at 10:36 AM, Joe Stein joe.st...@stealth.ly wrote: Jay, I agree with you. This goes back to the spam fiasco that occurred on confluence and the pendulum swinging because of it. Re-reading that email there doesn't seem anything specific requiring us to have them sign the ICLA but it looks like that is a requirement if we wanted INFRA to assign the person in the asf-cla group... so we could just have our own contributor group and manage that in confluence however we wanted? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 1:25 PM, Jay Kreps jay.kr...@gmail.com wrote: I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay -- -- Guozhang
Re: JIRA problem
I have been assigning people on confluence (they granted us access at that time after some back and forth) we already have permission to-do that no reason to talk to INFRA. Everyone in the PMC should have access. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 1:43 PM, Jay Kreps jay.kr...@gmail.com wrote: Joe--that sounds great, let's do that! So I guess we should put something in the wiki about how to get added to that group? Jarek--thanks for the summary, that is very helpful. I will follow-up with the infra people on letting people assign JIRAs. -jay On Fri, Jul 18, 2014 at 10:36 AM, Joe Stein joe.st...@stealth.ly wrote: Jay, I agree with you. This goes back to the spam fiasco that occurred on confluence and the pendulum swinging because of it. Re-reading that email there doesn't seem anything specific requiring us to have them sign the ICLA but it looks like that is a requirement if we wanted INFRA to assign the person in the asf-cla group... so we could just have our own contributor group and manage that in confluence however we wanted? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 1:25 PM, Jay Kreps jay.kr...@gmail.com wrote: I think having people fax in permission slips to edit the wiki or get bugs assigned to them is a bit hostile to potential contributors. Is this a legal Apache restriction that we have to abide by or just the way our permissions defaulted? Can we change this? Would people be opposed to changing it? -Jay On Fri, Jul 18, 2014 at 9:54 AM, Jun Rao jun...@gmail.com wrote: I am not sure if an ICLA is required for contributing patches. Requiring that may make it harder for people who want to contribute. Currently, only Kafka PMC members can change the contributors list. Thanks, Jun On Fri, Jul 18, 2014 at 9:45 AM, Joe Stein joe.st...@stealth.ly wrote: Shouldn't we make sure that the people in the contributor group have signed and sent in their ICLA http://www.apache.org/licenses/icla.txt much like we do for confluence? This helps to control also that all contributors have signed an ICLA too. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Fri, Jul 18, 2014 at 12:35 PM, Jarek Jarcec Cecho jar...@apache.org wrote: You have to add those people as a contributors in JIRA project administration. Click on “roles” in the KAFKA project administration and find field “contributors”. Jarcec On Jul 18, 2014, at 9:32 AM, Jay Kreps jay.kr...@gmail.com wrote: I can't seem to assign JIRAs to anyone but a few committer people. Does anyone know what causes this or how to fix it? Is this happening to anyone else? -Jay
