Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
OK I slept on it, and I finally see no reasons to not allow all contributors this possibility! It will help the community by and large. Jacques Le 12/03/2015 17:49, Jacques Le Roux a écrit : I think, it's a bit early to tell, but so far it has proved good Jacques Le 12/03/2015 17:43, Jacopo Cappellato a écrit : What is the status of this experiment? If you are considering it successful then we should extend similar rights to all the contributors. Jacopo On Feb 11, 2015, at 9:50 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Pierre, I have added you as a Jira contributor to test things (should be OK). When I will get a chance I will add other wiki contributors Jacques Le 11/02/2015 08:58, Jacques Le Roux a écrit : Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Hi That's great news, and I think it will also help to facilitate participation in general as well as the Community Day that's coming up next week. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/PROPOSAL-Increase-community-involvement-by-enabling-contributors-to-assign-themselves-to-their-own-i-tp4662454p4664898.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
What is the status of this experiment? If you are considering it successful then we should extend similar rights to all the contributors. Jacopo On Feb 11, 2015, at 9:50 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Pierre, I have added you as a Jira contributor to test things (should be OK). When I will get a chance I will add other wiki contributors Jacques Le 11/02/2015 08:58, Jacques Le Roux a écrit : Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
I think, it's a bit early to tell, but so far it has proved good Jacques Le 12/03/2015 17:43, Jacopo Cappellato a écrit : What is the status of this experiment? If you are considering it successful then we should extend similar rights to all the contributors. Jacopo On Feb 11, 2015, at 9:50 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Pierre, I have added you as a Jira contributor to test things (should be OK). When I will get a chance I will add other wiki contributors Jacques Le 11/02/2015 08:58, Jacques Le Roux a écrit : Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
I find it successful. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, Mar 12, 2015 at 5:43 PM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: What is the status of this experiment? If you are considering it successful then we should extend similar rights to all the contributors. Jacopo On Feb 11, 2015, at 9:50 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Pierre, I have added you as a Jira contributor to test things (should be OK). When I will get a chance I will add other wiki contributors Jacques Le 11/02/2015 08:58, Jacques Le Roux a écrit : Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization , the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Pierre, I have added you as a Jira contributor to test things (should be OK). When I will get a chance I will add other wiki contributors Jacques Le 11/02/2015 08:58, Jacques Le Roux a écrit : Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Gavin did it, it's available Jacques Le 02/02/2015 19:06, Jacques Le Roux a écrit : Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Hi Pierre I think this is a good proposal. It would also work in the case where we have a jira created but don't necessarily need a patch to fix the issue (I'm thinking potentially of any general documentation related tasks etc) Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/PROPOSAL-Increase-community-involvement-by-enabling-contributors-to-assign-themselves-to-their-own-i-tp4662454p4662520.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Done at https://issues.apache.org/jira/browse/INFRA-9103 Jacques Le 02/02/2015 11:06, Jacopo Cappellato a écrit : On Jan 30, 2015, at 6:43 PM, Pierre Smits pierre.sm...@gmail.com wrote: Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? +1 Jacopo
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
+1 Good Idea ! Gil Le 30/01/2015 14:13, Pierre Smits a écrit : Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Jira is really easy to use, at least when you being and don't try to setting it from the inside This could help you https://www.atlassian.com/software/university/overview Did you know that Jira is underneath using the OFBiz Entity Engine ? Jacques Le 31/01/2015 17:30, Blaxton a écrit : What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Did you know that Jira is underneath using the OFBiz Entity Engine? That is interesting, could you elaborate? On 15-01-31 09:58 AM, Jacques Le Roux wrote: Jira is really easy to use, at least when you being and don't try to setting it from the inside This could help you https://www.atlassian.com/software/university/overview Did you know that Jira is underneath using the OFBiz Entity Engine ? Jacques Le 31/01/2015 17:30, Blaxton a écrit : What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
https://developer.atlassian.com/static/javadoc/jira/5.0.5/reference/com/atlassian/jira/ofbiz/package-summary.html https://stackoverflow.com/questions/620215/jira-using-enterprise-architecture-by-ofbiz By and large try https://www.google.com/search?q=jira+ofbizie=UTF-8 OFBiz is a the heart of Jira. Atlassian built its success on Jira, which was built on OFBiz Entity Engine, QED Then ORMs like Hibernate did not exist... Maybe it was a chance for Atlassian... and Jira, this is only my opinion :D Jacques Le 31/01/2015 19:03, Todd Thorner a écrit : Did you know that Jira is underneath using the OFBiz Entity Engine? That is interesting, could you elaborate? On 15-01-31 09:58 AM, Jacques Le Roux wrote: Jira is really easy to use, at least when you being and don't try to setting it from the inside This could help you https://www.atlassian.com/software/university/overview Did you know that Jira is underneath using the OFBiz Entity Engine ? Jacques Le 31/01/2015 17:30, Blaxton a écrit : What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
I believe Ruth is one of the persons qualified for that http://www.aesolves.com/control/main Jacques Le 31/01/2015 23:18, Blaxton a écrit : What about OfBiz itself ?Any recommendation on how to start with it to get to development faster ?Is there any training courses available in North America ? From: Jacques Le Roux jacques.le.r...@les7arts.com To: user@ofbiz.apache.org Sent: Saturday, January 31, 2015 11:58 AM Subject: Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Jira is really easy to use, at least when you being and don't try to setting it from the inside This could help you https://www.atlassian.com/software/university/overview Did you know that Jira is underneath using the OFBiz Entity Engine ? Jacques Le 31/01/2015 17:30, Blaxton a écrit : What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
What about OfBiz itself ?Any recommendation on how to start with it to get to development faster ?Is there any training courses available in North America ? From: Jacques Le Roux jacques.le.r...@les7arts.com To: user@ofbiz.apache.org Sent: Saturday, January 31, 2015 11:58 AM Subject: Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Jira is really easy to use, at least when you being and don't try to setting it from the inside This could help you https://www.atlassian.com/software/university/overview Did you know that Jira is underneath using the OFBiz Entity Engine ? Jacques Le 31/01/2015 17:30, Blaxton a écrit : What is the best way of starting with OfBiz? I was thinking get a host , use the CMS feature of OfBiz and build a website to get familiar with OfBiz and then start contributing to development. I have never worked with JIRA but have a good knowledge of Java, JSP and Servlet. Is there any training courses available in North America ? Any suggestion that help me to contribute to development as soon as possible is appreciated. Thanks From: Pierre Smits pierre.sm...@gmail.com To: user@ofbiz.apache.org Sent: Friday, January 30, 2015 7:13 AM Subject: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues. Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
[PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
+1 Best Regards, Ruth Hoffman rhoff...@aesolves.net On 1/30/15 8:13 AM, Pierre Smits wrote: Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [PROPOSAL] Increase community involvement by enabling contributors to assign themselves to their own issues.
Hi Pierre, Thanks for the research and the detailed proposal. Good idea, I'm all for it. If nobody is against I will ask infra to switch the OFBiz Jira to the *Default plus Contributor Assign Permission Scheme.* Jacques Le 30/01/2015 14:13, Pierre Smits a écrit : Hi All, *Preamble* Currently community involvement in the project is good, but like in any other other open source project it could be better. And better is more favourable than just good or good enough, right? The thing is, that many perceive that contributors don't take ownership of their own issues in JIRA. They create the issue and at best provide comments to further explain and/or add replies to questions? But that is that. And the person assigned to the issue is regarded as the one responsible for having the issue brought to closure. This has led to the situation that we now have approx of 780 open issues, of which 600 are unassigned. Some of which are quite old (pre r10), even those with committers assigned. But this isn't how it should be. The creator of the issue should be regarded as the owner, the persons who brings the issue to closure. And the committer should be regarded as the gatekeeper/enabler regarding having patches committed and process followed. Currently contributors can't be assigned to issues they are willing to work on, so that they can take ownership. That contributors can't be assigned to a JIRA issue, is due to the fact that they don't have the proper role set. In stead of being identified with the role 'Contributor Project Role', they are treated as 'Any Registered User' (in accordance with the standard permissions scheme for JIRA, see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization ). *Improvement (the proposal)* In order to improve this situation and increase community involvement, we should assign the 'Contributor Project Role' to recognised contributors (see the Contributors page in the wiki: https://cwiki.apache.org/confluence/display/OFBADMIN/Apache+OFBiz+Contributors) so that they can be assigned to JIRA issues. Also, we should enable contributors to be able to assign themselves to their own issues and have them take ownership. Enabling contributors to take ownership of JIRA issues will enable the project to identify the more active community members more easily (as opposed to those who fire and forget) and get more issues assigned and closed, but it also helps lessening the burden on committers. Infrastructure has already such a construct in place to enable project contributors to do more (see https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization, the *Default plus Contributor Assign Permission Scheme*). What do you think? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
