Re: Mentors - the more, the merrier? [WAS Re: [VOTE] Accept Heraldry into the Incubator]
http://incubator.apache.org/incubation/Roles_and_Responsibilities.html "A Mentor is a role undertaken by a permanent member of the Apache Software Foundation and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above)." On 7/13/06, Ted Leung <[EMAIL PROTECTED]> wrote: On Jul 13, 2006, at 1:40 PM, Sam Ruby wrote: > I just want to note that we don't have a requirement that chairs be > members. I thought I recalled a rule that mentors had to be > members, but I can't quickly find confirmation of that. Yep, I was the XML PMC chair for several years and not a member. I do think that we said that mentors have to be members, but I"m in the same boat as you on finding it. Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJAX Toolkit Framework Proposal
I have a more specific question: have you guys considered separating this into a plug-ins/tooling donation to Eclipse, and a runtime donation to Apache? It seems like the IP is already in a form that makes this easy (ie, the AJAX Toolkit Framework Eclipse plugins from IBM, and the AjaxTK Javascript library from Zimbra), and there are several examples that suggest this kind of parallel community building works well. On 12/20/05, Cliff Schmidt <[EMAIL PROTECTED]> wrote: > Adam, > > Can you tell me if you considered proposing this to the Eclipse Foundation? > > Since this project appears to have far stronger dependencies on > Eclipse Foundation projects rather than anything from Apache, can you > tell me why you think bringing this project here is likely to help you > build a stronger community than you would find at Eclipse? Is there > some other overriding reason you prefer to bring this project to > Apache? > > Cliff > > > On 12/20/05, Adam Peller <[EMAIL PROTECTED]> wrote: > > AJAX Toolkit Framework Proposal > > > > 0. Rationale > > > > While the term AJAX (Asynchronous Javascript and XML) has only recently > > been coined, the underlying web standards and technologies (JavaScript > > a.k.a. ECMAScript, DOM, XML, SOAP, and so on) have been around for years. > > Although the term is used in a variety of ways, AJAX typically describes > > techniques towards developing interactive applications on the web client > > including asynchronous messaging, use of XML grammar in client-side > > applications, incremental page updates, and improved user interface > > controls. AJAX applications combine the rich UI experience of programmed > > clients with the low-cost lifecycle management of web-based applications. > > > > AJAX has raised awareness of the high potential of web applications, it has > > encouraged companies to adopt rich web-based interfaces over traditional > > "fat" clients, and it has spawned development activity to create toolkits > > and abstractions to make AJAX-style development easier and more powerful. > > This is an important trend for open source. The client itself can be > > composed entirely of open-source parts, such as Mozilla's Firefox or KDE's > > Konqueror, and does not require any particular operating system, helping to > > make a more level playing field for all development. More importantly, > > AJAX is back-end agnostic as transactions are done over HTTP. Keeping the > > client open forces vendors to keep the communication channel open as well, > > and this can only continue as long as the client technology keeps pace with > > proprietary alternatives. The open, standards based communications channel > > is what drives many technologies inside Apache, so success of the open > > client is vital to Apache. The mission of this project is to encourage > > innovation around enterprise-strength client runtimes and tools and build a > > community which can select and nurture a select set which will be most > > beneficial to the web. > > > > 0.1 Criteria > > > > Meritocracy: > > > > Apache was chosen for an incubator primarily because of the guidance the > > community can provide. The two subprojects put forth are among the first > > attempts to formalize this style of development. Additional ideas, tools > > or entire runtimes may come forward and indeed would be welcomed to the > > project, either wholesale as new subprojects or incorporated into the > > existing code. > > > > Community: > > > > The contributed work was inspired by open source development but needs a > > strong and diverse community to validate its mission and carry it forward. > > A primary objective of the project is to build a vibrant community of users > > and active contributors. > > > > Core Developers: > > > > All of the initial committers are members of Zimbra and IBM development > > teams. All developers have worked on open source projects before and have > > experience and understanding of open source principles. > > > > Alignment: > > > > Initial implementation consists of two sub projects. > > > > The AJAX Toolkit Framework will provide a strategic framework for > > Interactive Development Environments (IDEs) for the many different AJAX > > toolkit offerings in the market. It provides a rich set of tools for the > > AJAX / DHTML developer including: a JavaScript editor with edit-time syntax > > checking; Mozilla web browser; integrated DOM browser; integrated > > JavaScript debugger; and wizards and development aides tuned to specific > > libraries and toolkits. The Framework is extensible to support other AJAX > > toolkits and has a wizard-based tool to facilitate the integration of new > > toolkits in the framework. > > > > The AJAX Toolkit Framework has dependencies on Mozilla XULRunner and > > JavaConnect, and Eclipse WTP. AJAX Toolkit Framework is written as a set of > > Plugin extensions to Eclipse. It embeds 4 other open source components: > > Rhino, JSLint, Rico and Zimbra. No code modif
Re: [tuscany] Mailing lists
Thanks Dims. Did you mean: tuscany-dev-subscribe AT ws.apache.org tuscany-commits-subscribe AT ws.apache.org On 12/11/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Team, > > I've created 2 tuscany mailing lists. > > * tuscany-dev > * tuscany-commits > > Please subscribe by sending an email to > > tuscany-dev AT ws.apache.org > tuscany-commits AT ws.apache.org > > Thanks, > dims > > -- > Davanum Srinivas : http://wso2.com/blogs/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (Re: [PROPOSAL] Incubate Tuscany SOA Project)
> > How about a BoF around Tuscany so all the folks who have expressed > > interest and are present can get together for a f2f? I'll be there > > Monday-Wednesday (no weekend tutorials for me this time) -- I've > > proposed a timeslot/location on the wiki: > > > > http://wiki.apache.org/apachecon/BirdsOfaFeather > > > sounds like it might have quite an overlap with SOA - ServiceMix so perhaps > i'd make more sense to shuffle the rooms around so that they follow on one > from another... A fine idea -- I've emailed Lisa Dusseault who appears to be the organizer of the current BoF in that room following the ServiceMix one, and will update the wiki if she's ok with it. thanks, k - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (Re: [PROPOSAL] Incubate Tuscany SOA Project)
Glad to see a strong show of interest from the WS PMC, look forward to working more w/ you guys. How about a BoF around Tuscany so all the folks who have expressed interest and are present can get together for a f2f? I'll be there Monday-Wednesday (no weekend tutorials for me this time) -- I've proposed a timeslot/location on the wiki: http://wiki.apache.org/apachecon/BirdsOfaFeather On 12/7/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Just hang in there for a few days. Let's wait for any feedback from > incubator PMC, sync up at ApacheCon and move forward from there. > > thanks, > -- dims > > On 12/7/05, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > > Davanum Srinivas wrote: > > > Folks, > > > > > > The WS-PMC has voted to accept the re-written Tuscany proposal with 11 > > > +1 votes (and zero -1/+0/-0 votes) > > > > > > Thanks, > > > dims > > > > > > > Dims > > > > Great, thank you! > > > > I have updated the proposal on the wiki to reflect this result and to > > change sponsor from the Incubator to the WS PMC. My understanding is > > that once we get an ack from the Incubator we should be good to go. If > > that's right, is there anything we can do to help with the next steps? > > > > -- > > Jeremy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Incubate Tuscany SOA Project
On 12/5/05, robert burrell donkin <[EMAIL PROTECTED]> wrote: > On 12/5/05, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > > > > Roy T.Fielding wrote: > > > > > > No, the proposal is all about SOA. What you are saying is that the > > > *actual plan* is about SCA. What I am saying is that the proposal > > > needs to match the actual plan, preferably a plan that is actionable, > > > rather than a statement of how happy the SOA community may someday be. > > > > > > I think everyone understands that now, yet nobody has updated the wiki. > > > There's no rush, I guess, but I do want to be clear that an e-mail > > > exchange is not the same as recording a mission statement that people > > > outside the proposal authors will understand. > > > > I held off making changes as I thought discussing a moving target would > > be confusing. I have now updated the proposal on the wiki expanding the > > Rationale section to indicate that we will be implementing the SCA > > specifications starting from an initial contribution. > > [ ... ] > personally speaking, I'd prefer something more declarative with a new and > better first paragraph. it's hard to build a community around a project > which takes three paragraphs to get to the point. IMHO the first two > paragraphs reads (to me) more like justifying a business case and less like > a call to arms for developers ;) I've rewritten the rationale to be substantially more direct: http://wiki.apache.org/incubator/TuscanyProposal Robert's point is well taken, as we've been socializing this idea in various circles and justifying a business case was definitely a part of some of those discussions. I understand that is not the primary concern here and should probably have dealt with that earlier, mea culpa. Roy, does this address your concerns over excessive vagueness and lack of a crisp statement of a common development goal? k - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Incubate Tuscany SOA Project
> > Specifically, I think the goal of providing a language/platform > > neutral service assembly layer that's backed by an extensible set of > > app developer models (with a shared conceptual framework) for specific > > languages/technologies, is something distinct here. Stuff like > > figuring out how to work with e.g. ServiceMix being built around JBI, > > a Java-centric standard, is definitely in the plan and seems like the > > kind of work that would be appropriate to do while incubating. > > Agreed. Though we can work on that after incubation too :) Yep, I think a lot of value in this kind of integration comes from it being an ongoing process rather than a point-in-time thing. The way the initial seed code has evolved, we're at a point where the overhead of opening up is definitely outweighed by the potential gains from community involvement in this kind of exploration. > > [ integration ideas elided ].. > Glad to see so many ideas -- we know there's prior art -- many of us are very cognizant of the proliferation of work in this very broad space, and the value in keeping a healthy tension between adding value / "offering people a choice" vs. reinventing the wheel just because we think we have a better XML configuration file format :P. > Incidentally I've also wanted a nice Apache licensed SDO > implementation too for some time (thats not bound to EMF :) Heh, I thought the same thing when I got involved.. k - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Incubate Tuscany SOA Project
Hi Noel, (I worked with Jeremy on the proposal, and this seems like a good place to chime in) If by "merge", you mean consolidate the projects organizationally, we debated approaching e.g. the WS PMC with this first but decided that it ultimately make more sense to just come to the incubator and have the discussion here. My take is that the existing codebases involved and the shorter/medium term problems they're trying to solve are distinct enough that it makes sense to let them evolve somewhat independently while encouraging opportunistic integration.. having had some brief exchanges w/ Dims & Sanjiva re: the relationship between this proposal, Synapse, ServiceMix etc, we certainly plan to take advantage of as many existing projects as possible. If given the opportunity and some time, it turns out to make sense to most of the folks involved that the Tuscany work ought to live under an existing PMC or be rolled into an existing project, that's great. Specifically, I think the goal of providing a language/platform neutral service assembly layer that's backed by an extensible set of app developer models (with a shared conceptual framework) for specific languages/technologies, is something distinct here. Stuff like figuring out how to work with e.g. ServiceMix being built around JBI, a Java-centric standard, is definitely in the plan and seems like the kind of work that would be appropriate to do while incubating. On 11/30/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Jeremy, > > How does this proposal fit with other ESB/SOA projects currently underway at > the ASF? At first glance, there appears to be overlap, so I am wondering if > there a plan / opportunity to merge them. > > --- Noel > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-8) Incubate Tuscany SOA project
Incubate Tuscany SOA project Key: INCUBATOR-8 URL: http://issues.apache.org/jira/browse/INCUBATOR-8 Project: Incubator Type: Wish Reporter: Kenneth Tam Placeholder for materials related to Tuscany SOA incubator proposal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [STATUS] (incubator) Wed Nov 2 23:55:42 2005
Hi Ken, one of the msg links in the incubator status look irrelevant (leading me to suspect it's meant to be pointing somewhere else). See inline. On 11/2/05, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: > Resolved Issues > === > ... > > o All projects under incubation must use a STATUS file (or a > status.xml file if the project prefers XML) that contains > information the PMC needs about the project. This file must > live at the root of the project cvs module > (http://mail-archives.apache.org/eyebrowse/[EMAIL > PROTECTED]&by=thread&from=504543) This link only seems to be about incubator disclaimers instead of STATUS. > > o Projects under incubation should display appropriate "disclaimers" > so that it is clear that they are, indeed, under incubation > (http://mail-archives.apache.org/eyebrowse/[EMAIL > PROTECTED]&by=thread&from=504543) > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Beehive quarterly status report
Incubator quarterly status report for Beehive: Beehive did a 1.0m1 incubating milestone release on June 6/2005. With the recent finalization of JSR-181 (Annotated Java Web Services) and its associated TCK, the wheels are turning to get Beehive certified as 181 compliant. The big news, we're in the middle of a vote to graduate from the Incubator to TLP status. We are well poised to do a 1.0 final release should that vote pass. There has been increased traffic on the dev list, and we're seeing ongoing interest from other projects (Geronimo, Struts, etc) in a variety of forums -- a session at JavaOne a few weeks ago was well attended. We are also in the midst of a vote for a new committer. thanks, k - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Beehive into a TLP
I'll follow up separately with Cliff to see whether a CLA ever actually made it to Apache, but in any case he has been inactive since day 1 and should be removed. On 7/15/05, Roy T. Fielding <[EMAIL PROTECTED]> wrote: > On Jul 12, 2005, at 2:38 PM, Davanum Srinivas wrote: > > > Dear Incubator PMC, > > > > I believe Beehive is ready to function as a standalone PMC. Please see > > the latest status at: > > http://incubator.apache.org/projects/beehive.html > > What's the deal with the one committer without a CLA? Either > his CLA and account were activated and he is a committer, > or they weren't and he should be removed from the list. > > Roy > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Beehive into a TLP
Beehive doesn't currently have any implementations of the WS-* standards, including WS-Security -- the intent was to at some point look to other Apache projects that were implementing those standards (I don't subscribe to legal-discuss, but I presume the discussion in question is wrt WSS4J?). On 7/14/05, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > On 7/12/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > Dear Incubator PMC, > > > > > > I believe Beehive is ready to function as a standalone PMC. Please > > see > > > the latest status at: > > > http://incubator.apache.org/projects/beehive.html > > Could someone please provide information on any patents known to apply > to this project? > > There has been discussion on legal-discuss@apache.org regarding the > situation for WS-Security where IBM has granted patent license for the > Apache project but not to anyone who modifies the code (modifiers of the > code must apply for a patent license separately). > > > The "legal issues" section of the beehive status page does not address > patent issues. It would be good to confirm that this situation does not > apply to Beehive. > > Sorry if this has already been discussed... > > Thanks, > > Simon > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
