Re: [DISCUSS] New Incubator Project for Enterprise Configuration
I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis 2014-11-02 21:31 GMT+01:00 John D. Ament john.d.am...@gmail.com: Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Jean-Louis
Re: [DISCUSS] New Incubator Project for Enterprise Configuration
2014-11-03 9:13 GMT+01:00 Jean-Louis MONTEIRO jeano...@gmail.com: I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Not sure about this last part, [configuration] is active and it will be important to keep it active. But it doesn't prevent to implement any other JSR as we did for [jcs]. That's what I'd do: enrich an existing project with this api and EE side. wdyt? Jean-Louis 2014-11-02 21:31 GMT+01:00 John D. Ament john.d.am...@gmail.com: Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Jean-Louis - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for Nov 2014 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 November 2014, 10:30 am PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Nov 5th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/November2014 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is the leading 'H' in its name; it should be fit for any java distributed systems. Lets make this more plain in the proposal. Thanks Naresh, St.Ack Thanks Naresh On Mon, Nov 3, 2014 at 1:34 AM, Andrew Purtell apurt...@apache.org wrote: Really great to see an incubation proposal for HTrace. If you need another mentor, please consider me. I don't think you need to list HTrace is not the primary focus of any of the current list of contributors as a risk. One can say that about many (perhaps the majority) of contributors to Apache projects. We would hope the incubation process develops a healthy community that sustains a level of contribution that keeps the project moving forward, as we would hope for all incubation candidates. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On 03.11.2014 16:49, Stack wrote: On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is the leading 'H' in its name; it should be fit for any java distributed systems. Lets make this more plain in the proposal. Would it hurt to remove the H from the project name, then? (I won't propose replacing it with D, that would be really confusing.) -- Brane P.S.: Ooh ... Distributed Tracing - Distress, which happens to be what an admin feels when her distributed app goes wonkers ... -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Hi John I am still figuring out a bit how things work here in Apache (running a JSR for me currently is more easy ;) ), so anything that is wrong, it's perfect to just tell me, so we can fix everything. So summarizing: -I add you as a mentor (great! Thanks.) -Add it (or let add it) to the proposal Wiki: http://incubator.apache.org/guides/proposal.html -I will add David Blevins as champion (I cannot be the champion, I did not get that point here...) -The difference between initial and core developers was that the code contribution is completely done from my personal GitHub repo. But I already know that the other case will help on the project. If that makes no sense, we can change that ;) ... ? -Sponsoring Entity might be tomee PMC (will check that with David). Thanks for your help. -Anatole Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389)
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Hi Jean-Louis unfortunately I was a bit deferred in receiving this mail thread here. So sorry for the delay ;) I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. This JSR was targeting mainly EE 8 and mostly deployment aspects. I think, with enough momentum, we could try to discuss of add some kind of SPIs to EE 8 through the umbrella JSR. On the other side, when we get a restful container management API, we could also use this to plugin with any kind of configuration solution. Of course, my hope is that we will be able to have a configuration solution in place that is mature and flexible enough to effectively support these EE scenarios. Application configuration basically is partially covered by Deltaspike as of now, but I think more features would be useful. As of now there is no good place to do a standardization for app config. I will try to revitalize the configuration stream in CDI, so we could at least end up in some kind of EE8 specification appendix. As of now this seems to be the maximum we can do on a standardization level. On the other side I think, Apache is a great chance to further evolve the concepts, so we will have a good chance, that we can standardize them at a later point. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis Fair enough. I am looking forward for any kind of collaboration here -Anatole Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389)
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Hi Anatole, That's part of what the incubator is here for. :-) First step, create an incubator wiki account http://wiki.apache.org/incubator/ and second step send an email to general@i.a.o asking to be made a contributor to the wiki. You'll need this if your proposal is accepted anyways to update the board reports. Agreed, so long as David's ok with it you can list him as champion (I always assume people are in the incubator). I wouldn't list TomEE as sponsor, unless your intention is to become a sub-project of TomEE. If you look at the history of proposals at [1] you'll see that most proposals request that the incubator be the sponsor. The initial committers and PPMC should likely be the same - this will be the intial set of people who do things like vote on releases and have write access to your git repo. If you know people who will be doing this (e.g. strub, Gerhard, David, etc) then make sure they get listed as your initial committers. Also, since you're new to apache, have you processes an ICLA/CCLA yet? John [1]: http://wiki.apache.org/incubator/ProjectProposals On Mon Nov 03 2014 at 11:54:36 AM Tresch, Anatole anatole.tre...@credit-suisse.com wrote: Hi John I am still figuring out a bit how things work here in Apache (running a JSR for me currently is more easy ;) ), so anything that is wrong, it's perfect to just tell me, so we can fix everything. So summarizing: -I add you as a mentor (great! Thanks.) -Add it (or let add it) to the proposal Wiki: http://incubator.apache.org/guides/proposal.html -I will add David Blevins as champion (I cannot be the champion, I did not get that point here...) -The difference between initial and core developers was that the code contribution is completely done from my personal GitHub repo. But I already know that the other case will help on the project. If that makes no sense, we can change that ;) ... ? -Sponsoring Entity might be tomee PMC (will check that with David). Thanks for your help. -Anatole Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389)
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On Mon, Nov 3, 2014 at 8:01 AM, Branko Čibej br...@apache.org wrote: On 03.11.2014 16:49, Stack wrote: On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is the leading 'H' in its name; it should be fit for any java distributed systems. Lets make this more plain in the proposal. Would it hurt to remove the H from the project name, then? (I won't propose replacing it with D, that would be really confusing.) -- Brane P.S.: Ooh ... Distributed Tracing - Distress, which happens to be what an admin feels when her distributed app goes wonkers ... HTrace is 'fairly' generic and the github project is what comes up when you search. That said, I think your suggestion pretty great, funny. Its probably a bad name for a software project though? (Distrace?) St.Ack
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On 03.11.2014 19:12, Stack wrote: On Mon, Nov 3, 2014 at 8:01 AM, Branko Čibej br...@apache.org wrote: On 03.11.2014 16:49, Stack wrote: On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is the leading 'H' in its name; it should be fit for any java distributed systems. Lets make this more plain in the proposal. Would it hurt to remove the H from the project name, then? (I won't propose replacing it with D, that would be really confusing.) -- Brane P.S.: Ooh ... Distributed Tracing - Distress, which happens to be what an admin feels when her distributed app goes wonkers ... HTrace is 'fairly' generic and the github project is what comes up when you search. That said, I think your suggestion pretty great, funny. Its probably a bad name for a software project though? (Distrace?) If Subversion and Git are OK, then Distress fits right in, wouldn't you say? :) -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Thanks very much for the help. And nope, i did not yet sign anything... Will check that out asap... - Anatole Tresch Glärnischweg 10 8620 Wetzikon Tel +41 (43) 317 05 30 - Send from Mobile Am 03.11.2014 um 18:46 schrieb John D. Ament john.d.am...@gmail.com: Hi Anatole, That's part of what the incubator is here for. :-) First step, create an incubator wiki account http://wiki.apache.org/incubator/ and second step send an email to general@i.a.o asking to be made a contributor to the wiki. You'll need this if your proposal is accepted anyways to update the board reports. Agreed, so long as David's ok with it you can list him as champion (I always assume people are in the incubator). I wouldn't list TomEE as sponsor, unless your intention is to become a sub-project of TomEE. If you look at the history of proposals at [1] you'll see that most proposals request that the incubator be the sponsor. The initial committers and PPMC should likely be the same - this will be the intial set of people who do things like vote on releases and have write access to your git repo. If you know people who will be doing this (e.g. strub, Gerhard, David, etc) then make sure they get listed as your initial committers. Also, since you're new to apache, have you processes an ICLA/CCLA yet? John [1]: http://wiki.apache.org/incubator/ProjectProposals On Mon Nov 03 2014 at 11:54:36 AM Tresch, Anatole anatole.tre...@credit-suisse.com wrote: Hi John I am still figuring out a bit how things work here in Apache (running a JSR for me currently is more easy ;) ), so anything that is wrong, it's perfect to just tell me, so we can fix everything. So summarizing: -I add you as a mentor (great! Thanks.) -Add it (or let add it) to the proposal Wiki: http://incubator.apache.org/guides/proposal.html -I will add David Blevins as champion (I cannot be the champion, I did not get that point here...) -The difference between initial and core developers was that the code contribution is completely done from my personal GitHub repo. But I already know that the other case will help on the project. If that makes no sense, we can change that ;) ... ? -Sponsoring Entity might be tomee PMC (will check that with David). Thanks for your help. -Anatole Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
Hi! Thanks for the positive feedback and volunteering. I think the more mentors the merrier -- all the folks who volunteered please add your names to the wiki. As for the name, personally, I really like Distrace. That said, I'd leave this bikesched to be painted for later ;-) Andrew, great point on the wording: I'll update the proposal. Finally, since I'm currently on vacation, I'll let this thread go for a little longer and will start the official VOTE in a few days. Thanks, Roman. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache committers and PMC
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
BTW, wondering how to get the Apache Sirona community involved or if there is a possible common road where the 2 projects could join. 2014-11-03 20:27 GMT+01:00 Roman Shaposhnik r...@apache.org: Hi! Thanks for the positive feedback and volunteering. I think the more mentors the merrier -- all the folks who volunteered please add your names to the wiki. As for the name, personally, I really like Distrace. That said, I'd leave this bikesched to be painted for later ;-) Andrew, great point on the wording: I'll update the proposal. Finally, since I'm currently on vacation, I'll let this thread go for a little longer and will start the official VOTE in a few days. Thanks, Roman. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
2014-11-03 20:04 GMT+00:00 Jean-Louis MONTEIRO jeano...@gmail.com: BTW, wondering how to get the Apache Sirona community involved or if there is a possible common road where the 2 projects could join. +1. having a single solution would be awesome and sirona is just starting to get there so wommunity will be happy to get help on this part 2014-11-03 20:27 GMT+01:00 Roman Shaposhnik r...@apache.org: Hi! Thanks for the positive feedback and volunteering. I think the more mentors the merrier -- all the folks who volunteered please add your names to the wiki. As for the name, personally, I really like Distrace. That said, I'd leave this bikesched to be painted for later ;-) Andrew, great point on the wording: I'll update the proposal. Finally, since I'm currently on vacation, I'll let this thread go for a little longer and will start the official VOTE in a few days. Thanks, Roman. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
I wouldn't list TomEE as sponsor, unless your intention is to become a sub-project of TomEE. If you look at the history of proposals at [1] you'll see that most proposals request that the incubator be the sponsor. David Blevins is enough. 2014-11-03 18:46 GMT+01:00 John D. Ament john.d.am...@gmail.com: Hi Anatole, That's part of what the incubator is here for. :-) First step, create an incubator wiki account http://wiki.apache.org/incubator/ and second step send an email to general@i.a.o asking to be made a contributor to the wiki. You'll need this if your proposal is accepted anyways to update the board reports. Agreed, so long as David's ok with it you can list him as champion (I always assume people are in the incubator). I wouldn't list TomEE as sponsor, unless your intention is to become a sub-project of TomEE. If you look at the history of proposals at [1] you'll see that most proposals request that the incubator be the sponsor. The initial committers and PPMC should likely be the same - this will be the intial set of people who do things like vote on releases and have write access to your git repo. If you know people who will be doing this (e.g. strub, Gerhard, David, etc) then make sure they get listed as your initial committers. Also, since you're new to apache, have you processes an ICLA/CCLA yet? John [1]: http://wiki.apache.org/incubator/ProjectProposals On Mon Nov 03 2014 at 11:54:36 AM Tresch, Anatole anatole.tre...@credit-suisse.com wrote: Hi John I am still figuring out a bit how things work here in Apache (running a JSR for me currently is more easy ;) ), so anything that is wrong, it's perfect to just tell me, so we can fix everything. So summarizing: -I add you as a mentor (great! Thanks.) -Add it (or let add it) to the proposal Wiki: http://incubator.apache.org/guides/proposal.html -I will add David Blevins as champion (I cannot be the champion, I did not get that point here...) -The difference between initial and core developers was that the code contribution is completely done from my personal GitHub repo. But I already know that the other case will help on the project. If that makes no sense, we can change that ;) ... ? -Sponsoring Entity might be tomee PMC (will check that with David). Thanks for your help. -Anatole Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) -- Jean-Louis
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Thanks Anatole. You were the one pushing the JSR so I wanted to be sure about the purpose of this proposal. Sound very interesting to me. Looking forward to help if needed. Jean-Louis 2014-11-03 18:18 GMT+01:00 Tresch, Anatole anatole.tre...@credit-suisse.com : Hi Jean-Louis unfortunately I was a bit deferred in receiving this mail thread here. So sorry for the delay ;) I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. This JSR was targeting mainly EE 8 and mostly deployment aspects. I think, with enough momentum, we could try to discuss of add some kind of SPIs to EE 8 through the umbrella JSR. On the other side, when we get a restful container management API, we could also use this to plugin with any kind of configuration solution. Of course, my hope is that we will be able to have a configuration solution in place that is mature and flexible enough to effectively support these EE scenarios. Application configuration basically is partially covered by Deltaspike as of now, but I think more features would be useful. As of now there is no good place to do a standardization for app config. I will try to revitalize the configuration stream in CDI, so we could at least end up in some kind of EE8 specification appendix. As of now this seems to be the maximum we can do on a standardization level. On the other side I think, Apache is a great chance to further evolve the concepts, so we will have a good chance, that we can standardize them at a later point. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis Fair enough. I am looking forward for any kind of collaboration here -Anatole Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) -- Jean-Louis
Wiki access request
Can someone please add axemclion (Parashuram Narasimhan on the Ripple podling) to the wiki contributors group ( http://wiki.apache.org/incubator/ContributorsGroup) I'd do it myself except that I seem to have forgotten my login and reset emails are not reaching me. Thanks for your help Ross
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Thanks Jean-Louis. I am sure there is enough work where you can help us ;) 2014-11-03 22:13 GMT+01:00 Jean-Louis MONTEIRO jeano...@gmail.com: Thanks Anatole. You were the one pushing the JSR so I wanted to be sure about the purpose of this proposal. Sound very interesting to me. Looking forward to help if needed. Jean-Louis 2014-11-03 18:18 GMT+01:00 Tresch, Anatole anatole.tre...@credit-suisse.com : Hi Jean-Louis unfortunately I was a bit deferred in receiving this mail thread here. So sorry for the delay ;) I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. This JSR was targeting mainly EE 8 and mostly deployment aspects. I think, with enough momentum, we could try to discuss of add some kind of SPIs to EE 8 through the umbrella JSR. On the other side, when we get a restful container management API, we could also use this to plugin with any kind of configuration solution. Of course, my hope is that we will be able to have a configuration solution in place that is mature and flexible enough to effectively support these EE scenarios. Application configuration basically is partially covered by Deltaspike as of now, but I think more features would be useful. As of now there is no good place to do a standardization for app config. I will try to revitalize the configuration stream in CDI, so we could at least end up in some kind of EE8 specification appendix. As of now this seems to be the maximum we can do on a standardization level. On the other side I think, Apache is a great chance to further evolve the concepts, so we will have a good chance, that we can standardize them at a later point. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis Fair enough. I am looking forward for any kind of collaboration here -Anatole Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) -- Jean-Louis -- *Anatole Tresch* Java Engineer Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ http://javaremarkables.blogspot.ch/* *Google: atsticksMobile +41-76 344 62 79*
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On Mon, Nov 3, 2014 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: BTW, wondering how to get the Apache Sirona community involved or if there is a possible common road where the 2 projects could join. How do you see the projects relating? How would the recording and viewing of traces in Sirona look? Do you foresee a zipkin like viewer in Sirona? Thanks, St.Ack
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
Le 3 nov. 2014 22:06, Stack st...@duboce.net a écrit : On Mon, Nov 3, 2014 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: BTW, wondering how to get the Apache Sirona community involved or if there is a possible common road where the 2 projects could join. How do you see the projects relating? How would the recording and viewing of traces in Sirona look? Do you foresee a zipkin like viewer in Sirona? We just started but we have agents to get data on nodes then we push in a store (cassandra mainly today). Gui is not yet complete for tracing part. Thanks, St.Ack
Re: Wiki access request
On Mon, Nov 3, 2014 at 1:19 PM, Ross Gardler rgard...@opendirective.com wrote: Can someone please add axemclion (Parashuram Narasimhan on the Ripple podling) to the wiki contributors group ( http://wiki.apache.org/incubator/ContributorsGroup) Done. I'd do it myself except that I seem to have forgotten my login and reset emails are not reaching me. The wiki is very slow right now --- it took several minutes for my update to complete. (As you note on another list, Infra is aware of the issue and working to resolve it.) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
Really awesome to see this getting off the ground! Thanks, Roman! Re: the name. I don't feel super-strongly about this, but I prefer the name HTrace. It's short and sweet, and very easy to Google for. Distress is not going to be easy to Google for, and might tend to turn up the wrong kinds of results. I think this is pretty important for a new project trying to get mindshare. I think if anything, having Hadoop associated with the project should help it to grow, since people know that it's being used by a real (and really big) distributed systems project rather than just being an experiment. Of course, we should make it absolutely clear in the documentation, project site, mailing list, etc. that there are no dependencies on Hadoop jars and that any Java project (and maybe later, non-Java projects) can use this. best, Colin On Mon, Nov 3, 2014 at 8:01 AM, Branko Čibej br...@apache.org wrote: On 03.11.2014 16:49, Stack wrote: On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal naresh.agar...@inmobi.com wrote: Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is the leading 'H' in its name; it should be fit for any java distributed systems. Lets make this more plain in the proposal. Would it hurt to remove the H from the project name, then? (I won't propose replacing it with D, that would be really confusing.) -- Brane P.S.: Ooh ... Distributed Tracing - Distress, which happens to be what an admin feels when her distributed app goes wonkers ... -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
On Mon, Nov 3, 2014 at 2:15 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Le 3 nov. 2014 22:06, Stack st...@duboce.net a écrit : On Mon, Nov 3, 2014 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: BTW, wondering how to get the Apache Sirona community involved or if there is a possible common road where the 2 projects could join. How do you see the projects relating? How would the recording and viewing of traces in Sirona look? Do you foresee a zipkin like viewer in Sirona? We just started but we have agents to get data on nodes then we push in a store (cassandra mainly today). Gui is not yet complete for tracing part. Ok. When comes time, would be great hooking up Apache Sirona as a Trace Sink (HTrace has a few Sink implemenations as is: zipkin, files, hbase). Thanks, St.Ack
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
I'm happy to champion and endorse for inclusion in the Incubator as long as the foremost focus is creating a functioning, lasting and healthy ASF community and any JSR/JCP points always second. I do not think these goals are mutually exclusive, in fact I think the opposite; the world could benefit from JSRs based on and/or run by strong Apache communities. Provided it's the community leading the JSR and not the JSR leading the community, I think we're a go for Incubation. -David On Mon, Nov 3, 2014 at 1:53 PM, Anatole Tresch atsti...@gmail.com wrote: Thanks Jean-Louis. I am sure there is enough work where you can help us ;) 2014-11-03 22:13 GMT+01:00 Jean-Louis MONTEIRO jeano...@gmail.com: Thanks Anatole. You were the one pushing the JSR so I wanted to be sure about the purpose of this proposal. Sound very interesting to me. Looking forward to help if needed. Jean-Louis 2014-11-03 18:18 GMT+01:00 Tresch, Anatole anatole.tre...@credit-suisse.com : Hi Jean-Louis unfortunately I was a bit deferred in receiving this mail thread here. So sorry for the delay ;) I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. This JSR was targeting mainly EE 8 and mostly deployment aspects. I think, with enough momentum, we could try to discuss of add some kind of SPIs to EE 8 through the umbrella JSR. On the other side, when we get a restful container management API, we could also use this to plugin with any kind of configuration solution. Of course, my hope is that we will be able to have a configuration solution in place that is mature and flexible enough to effectively support these EE scenarios. Application configuration basically is partially covered by Deltaspike as of now, but I think more features would be useful. As of now there is no good place to do a standardization for app config. I will try to revitalize the configuration stream in CDI, so we could at least end up in some kind of EE8 specification appendix. As of now this seems to be the maximum we can do on a standardization level. On the other side I think, Apache is a great chance to further evolve the concepts, so we will have a good chance, that we can standardize them at a later point. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis Fair enough. I am looking forward for any kind of collaboration here -Anatole Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) -- Jean-Louis -- *Anatole Tresch* Java Engineer Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ http://javaremarkables.blogspot.ch/* *Google: atsticksMobile +41-76 344 62 79*
Re: Re: [DISCUSS] New Incubator Project for Enterprise Configuration
+1 that is exactly what I think as well ;) 2014-11-04 2:57 GMT+01:00 David Blevins david.blev...@gmail.com: I'm happy to champion and endorse for inclusion in the Incubator as long as the foremost focus is creating a functioning, lasting and healthy ASF community and any JSR/JCP points always second. I do not think these goals are mutually exclusive, in fact I think the opposite; the world could benefit from JSRs based on and/or run by strong Apache communities. Provided it's the community leading the JSR and not the JSR leading the community, I think we're a go for Incubation. -David On Mon, Nov 3, 2014 at 1:53 PM, Anatole Tresch atsti...@gmail.com wrote: Thanks Jean-Louis. I am sure there is enough work where you can help us ;) 2014-11-03 22:13 GMT+01:00 Jean-Louis MONTEIRO jeano...@gmail.com: Thanks Anatole. You were the one pushing the JSR so I wanted to be sure about the purpose of this proposal. Sound very interesting to me. Looking forward to help if needed. Jean-Louis 2014-11-03 18:18 GMT+01:00 Tresch, Anatole anatole.tre...@credit-suisse.com : Hi Jean-Louis unfortunately I was a bit deferred in receiving this mail thread here. So sorry for the delay ;) I do think it's an interested and important topic. Was wondering what's Anatole position as the Configuration JSR as been deferred from Java EE 8. This JSR was targeting mainly EE 8 and mostly deployment aspects. I think, with enough momentum, we could try to discuss of add some kind of SPIs to EE 8 through the umbrella JSR. On the other side, when we get a restful container management API, we could also use this to plugin with any kind of configuration solution. Of course, my hope is that we will be able to have a configuration solution in place that is mature and flexible enough to effectively support these EE scenarios. Application configuration basically is partially covered by Deltaspike as of now, but I think more features would be useful. As of now there is no good place to do a standardization for app config. I will try to revitalize the configuration stream in CDI, so we could at least end up in some kind of EE8 specification appendix. As of now this seems to be the maximum we can do on a standardization level. On the other side I think, Apache is a great chance to further evolve the concepts, so we will have a good chance, that we can standardize them at a later point. Even if Mark and Gerhard are also part of DeltaSpike, that'd be great to avoid having many different configuration projects in Apache and then splitting forces. Probably also a good opportunity to move commons-configuration from proper/dormant. Jean-Louis Fair enough. I am looking forward for any kind of collaboration here -Anatole Anatole Tresch Platform Strategy Strategic Projects, KGVX 42 +41 44 334 03 89 (*414 0389) -- Jean-Louis -- *Anatole Tresch* Java Engineer Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ http://javaremarkables.blogspot.ch/* *Google: atsticksMobile +41-76 344 62 79* -- *Anatole Tresch* Java Engineer Architect, JSR Spec Lead Glärnischweg 10 CH - 8620 Wetzikon *Switzerland, Europe Zurich, GMT+1* *Twitter: @atsticks* *Blogs: **http://javaremarkables.blogspot.ch/ http://javaremarkables.blogspot.ch/* *Google: atsticksMobile +41-76 344 62 79*
Re: Incubator Shepherd
On Sun, Nov 2, 2014 at 1:05 PM, Timothy Chen tnac...@gmail.com wrote: I am interested in helping out incubator projects as a shepherd, and saw from the wiki the instructions is to simply drop a line here. Thanks for taking an interest, Timothy! I've added you to our shepherd's roster. http://svn.apache.org/viewvc/incubator/public/trunk/content/shepherds.json I wonder what else I need to do to apply? The Python tools which generate the template for the Incubator's monthly report include a utility for assigning shepherds to podlings mostly at random. Those assignments are published at the top of the report wiki page. The November report has already been assigned. However, if there are a podling you'd particularly like to review this month, perhaps contact the currently assigned shepherd, either here on general@incubator or privately. If you have more questions, please ask away. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
