Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. -g
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Wed, Jul 29, 2015 at 12:25PM, Greg Stein wrote: On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. While I tend to agree with you, it worth noting that there's a whole bunch of TLPs sticking to RTC. So, this data point doesn't reflect on the podling in question. Cos - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Jul 29, 2015 12:45 PM, Konstantin Boudnik c...@apache.org wrote: On Wed, Jul 29, 2015 at 12:25PM, Greg Stein wrote: On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. While I tend to agree with you, it worth noting that there's a whole bunch of TLPs sticking to RTC. So, this data point doesn't reflect on the podling in question. And POW!! There is one excuse on display already :-P But others do it. -g
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Wed, Jul 29, 2015 at 09:08PM, Branko Čibej wrote: On 29.07.2015 19:51, Greg Stein wrote: On Jul 29, 2015 12:45 PM, Konstantin Boudnik c...@apache.org wrote: On Wed, Jul 29, 2015 at 12:25PM, Greg Stein wrote: On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. While I tend to agree with you, it worth noting that there's a whole bunch of TLPs sticking to RTC. So, this data point doesn't reflect on the podling in question. And POW!! There is one excuse on display already :-P But others do it. How 'bout I propose a board resolution forbidding RTC at the ASF for mainline development? :) [popcorn time...] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 29.07.2015 19:51, Greg Stein wrote: On Jul 29, 2015 12:45 PM, Konstantin Boudnik c...@apache.org wrote: On Wed, Jul 29, 2015 at 12:25PM, Greg Stein wrote: On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. While I tend to agree with you, it worth noting that there's a whole bunch of TLPs sticking to RTC. So, this data point doesn't reflect on the podling in question. And POW!! There is one excuse on display already :-P But others do it. How 'bout I propose a board resolution forbidding RTC at the ASF for mainline development? :) -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 29.07.2015 19:25, Greg Stein wrote: On Jul 29, 2015 11:37 AM, Branko Čibej br...@apache.org wrote: On 29.07.2015 18:14, Joe Brockmeier wrote: On Thu, Jul 23, 2015, at 03:19 AM, Branko Čibej wrote: Personally I'm not too happy with how this community tracks issues, but hey, if it works for them, why fix it? It'll be a fine day when the IPMC starts telling podlings how their development workflow should look like. Does works for them translate into people not currently in the community can follow how the existing community tracks issues, so they can contribute and become part of the community? If so, then maybe it's OK. If it's not transparent to folks not currently part of that community, it's hard to see how the community will sustain itself with new members as other folks inevitably move on to other projects. Given that new contributors keep showing up on a regular basis, I have to assume that it's not so opaque as all that. Anyway, Ignite has been discussing and implementing a revised (and IMO better) set of policies for Jira use and git workflow since this discussion started; other than displaying an incomprehensible preference for RTC, it seems to be going well. I always translate RTC as we don't trust you, so somebody else must approve anything you do. Both Cos and I have been doing our best to explain exactly that to the podling community. Unfortunately they have bad examples in some very high profile TLPs, which makes it an uphill battle. It doesn't help that the Incubator does nothing to promote CTR over RTC. To me, that is a lousy basis for creating a community. Trust and peer respect should be the basis, which implies CTR. I have seen many excuses for RTC, but they all are just window dressing over mistrust. As far as I'm concerned, RTC == FUD, especially the eff part. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Ignite from the Incubator
+1 (binding) On 29 July 2015 at 06:03, Konstantin Boudnik c...@apache.org wrote: Following discussions [1],[2] about its current status, the Ignite community has voted [3] to graduate from the Incubator. The vote passed [4] with 14 (non-binding) +1s: 1. Yakov Zhdanov (PPMC) 2. Gianfranco Murador (PPMC) 3. Ira Vasilinets (PPMC) 4. Nikolai Tichinov (PPMC) 5. Semyon Boikov (PPMC) 6. Sergi Vladykin (PPMC) 7. Alexey Goncharuk (PPMC) 8. Ognen Duzlevski (PPMC) 9. Valentin Kulichenko (PPMC) 10. Nikita Ivanov (PPMC) 11. Dmitriy Setrakyan (PPMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa The Ignite community has: * completed all required paperwork: https://incubator.apache.org/projects/ignite.html * completed multiple releases (1.0, 1.1, 1.2, 1.3) * completed the name check procedure: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-58 * opened and worked on 1,150+ JIRAs: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+IGNITE * voted in multiple new committers/PPMC members Therefore, I'm calling a VOTE to graduate Ignite with the following Board resolution. The VOTE will run 72 hours, ending Friday July 31st 2 PM PST. [ ] +1 Graduate Apache Ignite from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Ignite from the Incubator because ... Regards, Cos [1] http://markmail.org/message/5fvca3vr6tkk5q4h [2] http://markmail.org/message/uotzsecmwbiuhgjy [3] http://markmail.org/message/fzslacsyxlvm3mwm [4] http://markmail.org/message/i2mxhgfchlwi34ko Apache Ignite graduation resolution draft WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Ignite Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Ignite podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Ignite podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail:
Re: [VOTE] Graduate Ignite from the Incubator
+1 (binding) On Thu, Jul 30, 2015 at 11:58 AM, John D. Ament johndam...@apache.org wrote: +1 (binding) On Tue, Jul 28, 2015 at 3:56 PM Konstantin Boudnik c...@apache.org wrote: Following discussions [1],[2] about its current status, the Ignite community has voted [3] to graduate from the Incubator. The vote passed [4] with 14 (non-binding) +1s: 1. Yakov Zhdanov (PPMC) 2. Gianfranco Murador (PPMC) 3. Ira Vasilinets (PPMC) 4. Nikolai Tichinov (PPMC) 5. Semyon Boikov (PPMC) 6. Sergi Vladykin (PPMC) 7. Alexey Goncharuk (PPMC) 8. Ognen Duzlevski (PPMC) 9. Valentin Kulichenko (PPMC) 10. Nikita Ivanov (PPMC) 11. Dmitriy Setrakyan (PPMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa The Ignite community has: * completed all required paperwork: https://incubator.apache.org/projects/ignite.html * completed multiple releases (1.0, 1.1, 1.2, 1.3) * completed the name check procedure: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-58 * opened and worked on 1,150+ JIRAs: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+IGNITE * voted in multiple new committers/PPMC members Therefore, I'm calling a VOTE to graduate Ignite with the following Board resolution. The VOTE will run 72 hours, ending Friday July 31st 2 PM PST. [ ] +1 Graduate Apache Ignite from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Ignite from the Incubator because ... Regards, Cos [1] http://markmail.org/message/5fvca3vr6tkk5q4h [2] http://markmail.org/message/uotzsecmwbiuhgjy [3] http://markmail.org/message/fzslacsyxlvm3mwm [4] http://markmail.org/message/i2mxhgfchlwi34ko Apache Ignite graduation resolution draft WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Ignite Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Ignite podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Ignite podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [VOTE] Graduate Ignite from the Incubator
+1 (binding) On Tue, Jul 28, 2015 at 3:56 PM Konstantin Boudnik c...@apache.org wrote: Following discussions [1],[2] about its current status, the Ignite community has voted [3] to graduate from the Incubator. The vote passed [4] with 14 (non-binding) +1s: 1. Yakov Zhdanov (PPMC) 2. Gianfranco Murador (PPMC) 3. Ira Vasilinets (PPMC) 4. Nikolai Tichinov (PPMC) 5. Semyon Boikov (PPMC) 6. Sergi Vladykin (PPMC) 7. Alexey Goncharuk (PPMC) 8. Ognen Duzlevski (PPMC) 9. Valentin Kulichenko (PPMC) 10. Nikita Ivanov (PPMC) 11. Dmitriy Setrakyan (PPMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa The Ignite community has: * completed all required paperwork: https://incubator.apache.org/projects/ignite.html * completed multiple releases (1.0, 1.1, 1.2, 1.3) * completed the name check procedure: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-58 * opened and worked on 1,150+ JIRAs: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+IGNITE * voted in multiple new committers/PPMC members Therefore, I'm calling a VOTE to graduate Ignite with the following Board resolution. The VOTE will run 72 hours, ending Friday July 31st 2 PM PST. [ ] +1 Graduate Apache Ignite from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Ignite from the Incubator because ... Regards, Cos [1] http://markmail.org/message/5fvca3vr6tkk5q4h [2] http://markmail.org/message/uotzsecmwbiuhgjy [3] http://markmail.org/message/fzslacsyxlvm3mwm [4] http://markmail.org/message/i2mxhgfchlwi34ko Apache Ignite graduation resolution draft WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Ignite Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Ignite podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Ignite podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe,
List of all Current Incubator Projects
On this page; http://incubator.apache.org/ there is a list of current projects. I saw SAMOA listing Apache S4 (which I hadn't heard of) and it doesn't show up on that list. Is it manually maintained, or is it auto-generated somehow? Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
