[VOTE] Synapse release milestone1 from the Incubator
Hi! The Synapse incubator would like to make a Milestone 1 release. We proposed this in December, with a successful vote from the WS PMC. We have read the guidelines http://incubator.apache.org/incubation/Incubation_Policy.html#Releases and understand these. The codebase has enough functionality to support the initial milestone criteria (plus more) and so we would like to release it as a synapse-incubator-M1. We are tracking our status towards the release here: http://wiki.apache.org/ws/Synapse/M1Criteria I have been voted as the release manager. The release candidate zip file is available here: http://people.apache.org/~pzf/synapse/Synapse-Incubating-M1-SNAPSHOT-bin.zip I am just in the process of updating our status page on the incubator. We are also tracking on wiki here: http://wiki.apache.org/ws/Synapse/IncubationStatus Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com
Re: ajax proposal?
Erik Abele wrote: Oh, of course - but for now there's no community yet so he is complaining into the blue sky :) I'd certainly like to see a response to the concerns raised by Martin but OTOH I don't think that it should evolve into a discussion about basic architectural principles or even impact the final consideration of incubation. It's just the initial code, nothing more :) I don't agree with this statement. The code itself is indeed only the initial codebase but along with this codebase come an established group of committers with an interest in keeping their current architecture or at least backward compatibility An established codebase is *much* more difficult to restructure than starting from scratch. Even if someone would be willing to contribute to this projet to help address major technical issues, it would require a huge amount of effort to effect a significant architectural change because of community inertia and backward compatibility requirements. From what I've seen at Apache, major rearchitecture work always happen as a revolution with an entirely new implementation being built and these revolutions are dangerous to a project communiy health. Given the frictions created by revolutions, it's important that these do not happen before the community is mature else they may simply split it. I think my point is simply that in a code grant incubation scenario, initial codebase and initial community *do* matter because they'll act as natural forces towards stability and are likely to shape the community and codebase for a long time. Just my 2 eurocents, -- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ajax proposal?
Raphaël Luta wrote: Erik Abele wrote: Oh, of course - but for now there's no community yet so he is complaining into the blue sky :) I'd certainly like to see a response to the concerns raised by Martin but OTOH I don't think that it should evolve into a discussion about basic architectural principles or even impact the final consideration of incubation. It's just the initial code, nothing more :) I don't agree with this statement. The code itself is indeed only the initial codebase but along with this codebase come an established group of committers with an interest in keeping their current architecture or at least backward compatibility An established codebase is *much* more difficult to restructure than starting from scratch. Even if someone would be willing to contribute to this projet to help address major technical issues, it would require a huge amount of effort to effect a significant architectural change because of community inertia and backward compatibility requirements. From what I've seen at Apache, major rearchitecture work always happen as a revolution with an entirely new implementation being built and these revolutions are dangerous to a project communiy health. Given the frictions created by revolutions, it's important that these do not happen before the community is mature else they may simply split it. I think my point is simply that in a code grant incubation scenario, initial codebase and initial community *do* matter because they'll act as natural forces towards stability and are likely to shape the community and codebase for a long time. Hopefully, at some point, these somewhat abstract discussion of concerns that are relevant to all proposals will solidify into concrete concerns regarding this specific proposal. Is code irrelevant? That would be absurd. That's why the code has been made available for all to download, inspect and comment on. I think a more neutral restatement of what Eric and Noel are trying to say is that while good communities always overcome bad code, no amount of good code can make up for a bad community. On the other had, Raphaël, I see you making implicit assumptions that the committers will have entrenched interests that will be difficult to overcome, and that the existing community is mature. What evidence do you have of that? I'm sure that you can give examples of other communities where that was a problem, and I can give examples of other communities where that was NOT a problem. What do either examples prove? Nothing. What specific concerns do you have with this community and this codebase? - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator site status wrt a move to Anakia?
David Crossley wrote: I am investigating creating a Forrest output plugin to do the complete conversion. If Geir or others come up with another solution then fine, this will still be a useful tool for Forrest. Update: We now have a Forrest output plugin working to generate Anakia xdocs from the current Incubator site. Needs more work on the plugin to transform the output and adjust some xml attributes. We should be able to do a repeatable process. So the rest of you keep on editing content. Later we will do a batch conversion. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ajax proposal?
On Tuesday 17 January 2006 14:27, Martin Cooper wrote: And the impact of giving a project the ASF brand. And the way the incubator operates as an open door to whoever knocks, with virtually no entry criteria. This seems to be a recurring (growing?) concern among people 'inside' ASF. Perhaps the membership+Board should discuss this matter and re-issue a clearer directive to the Incubator. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-13) Add new content to faq
Add new content to faq -- Key: INCUBATOR-13 URL: http://issues.apache.org/jira/browse/INCUBATOR-13 Project: Incubator Type: Improvement Reporter: Gavin Priority: Minor Mentioned on list, extra bullet points added to clarify initial code status and ownership. -- 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]
[jira] Updated: (INCUBATOR-13) Add new content to faq
[ http://issues.apache.org/jira/browse/INCUBATOR-13?page=all ] Gavin updated INCUBATOR-13: --- Attachment: faq.xml.diff Added points raised on list. Hope this is correct and in a suitable place, please check before comitting. Add new content to faq -- Key: INCUBATOR-13 URL: http://issues.apache.org/jira/browse/INCUBATOR-13 Project: Incubator Type: Improvement Reporter: Gavin Priority: Minor Attachments: faq.xml.diff Mentioned on list, extra bullet points added to clarify initial code status and ownership. -- 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: [jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement
- Original Message - From: David N. Welton (JIRA) general@incubator.apache.org To: general@incubator.apache.org Sent: Monday, January 16, 2006 5:12 PM Subject: [jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement |[ http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362832 ] | | David N. Welton commented on INCUBATOR-12: | -- | | I wouldn't get carried away reworking the whole thing. Just provide a link to where the mailing lists are... | | Cheers, | Dave The link to the mailing lists has been provided by DC, pointing to the /howtoparticipate.html document, unless they have a document of their own, I can't see a sensible way of adding a 'mailing lists' link on the navigation, which is how I interpreted your question. The other changes I proposed are mainly spelling corrections (while the document is being updated elsewhere, may as well fix those too). Point 1 needs confirming whether this should be done, a minor point, but we shouldnt make a link look like a mailto: if it is not. Point 2 needs checking by someone, where are the 'ASF Proposal Pages' now? Regarding changing the order of the Menu Items on the left Nav (re issue subject title), this will also change the order for the rest of the site to match. Despite my verbosity, it seems most pages on this particular site need 'approval' before any changes are made. If someone can just answer the queries I raised, it will not take long for me to make the changes and provide a patch. (if that is what people want) Gav... | | Process_Description.html navigation improvement | --- | | Key: INCUBATOR-12 | URL: http://issues.apache.org/jira/browse/INCUBATOR-12 | Project: Incubator | Type: Improvement | Reporter: David N. Welton | Priority: Minor | Attachments: Process_Description.html.diff | | http://incubator.apache.org/incubation/Process_Description.html | mentions a mailing lists section of this site, yet provides no link, and it is not at all obvious from the left-hand navigation where that might reside. A link should be provided. | Thanks, | Dave | | -- | 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] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] accept Solr into incubator
+1 On Jan 10, 2006, at 12:21 PM, Doug Cutting wrote: I propose that we accept the CNET's Solr project into the incubator. Discussion on this list evidenced broad interest in this project, which bodes well for its ability to build a developer community. The Lucene PMC would be happy to accept Solr as a Lucene sub- project once it graduates from the incubator. The proposal is at: http://wiki.apache.org/incubator/SolrProposal +1 Doug - 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] AJAX Toolkit Proposal - Updated
+1 on the proposal. I am assuming that the project will not have a generic technology name (Roy's point) but I'm not withholding my vote for that. On Jan 16, 2006, at 9:12 PM, Sam Ruby wrote: Erik Abele wrote: On 16.01.2006, at 02:42, Sam Ruby wrote: The discussion has died down, and the time has come to call for a VOTE to see if the incubator wants to sponsor and accept this proposal for incubation. As Roy and Leo (and others?) already noted, the proposal as sent is lacking some vital information - so for the time being I'd like to express another -1 here (peanut-gallery, yada yada...). The questions to date (which proposal are we talking about? Does it identify the committers and mentors by name? Is it on the wiki) are all answered here: http://wiki.apache.org/incubator/AjaxProposal Note: this does *not* address Roy's concern that the name represents a general category instead of a simple product name. And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Andy, any preference? - Sam Ruby - 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]
Incubator 2006Q1 Status Report to the ASF Board
Status report for the Apache Incubator Project The Incubator continues to see good progress in a number of projects and their communities. Several items of note from this past quarter: We have had some discussion regarding the rate of growth, how to manage it, how to ensure proper oversight. We have not finalized any policy changes, but should do so shortly. There is a sometimes not-so-subtle- tension between oversight and nimbleness, and we're trying to give as much of the latter as possible without sacrificing the former. We have also had a discussion regarding importing external codebases, with the conclusion that where possible, we DO want to import the entire history. This will require some help from Infrastructure to help us swizzle the imported authors into some canonical format that won't collide with our ASF author namespace. People are unhappy with the state of building the web site. There are two possible paths: switching our content to anakia format, or improvement in the usability of Forrest. Which path we take will depend upon the energy invested by those who want to help effect the change. Jean T. Anderson has helped to revise the Incubator Guidelines, although we will have to continue the process. - 0 - The list of projects in the Incubator is at http://incubator.apache.org/projects/. Here are the STATUS reports from the PPMCs. The drafts were collected at http://wiki.apache.org/incubator/IncubatorBoardReport2006Q1. Axion never began Incubation, despite having been approved by the DB PMC, and will likely be removed from the list in this quarter. AltRMI, FTPServer, Tobago and WSRP4J failed to provide quarterly reports. Several projects below have graduated, and are noted as such, but until they participate by updating their Incubator documents to indicate that fact, I will continue to ping them. PMCs must help to maintain the content for which they are responsible, or we will never be able to scale. AltRMI has gained no traction, and is likely to leave the Incubator to go elsewhere. FTPServer has added two new Committers, and we see continued activity to revitalize a once dormant project. I addressed the e-mail delivery problem I mentioned in the last quarterly report by adding myself to the allow list for every PMC mailing list. Projects ActiveMQ The full status of incubation is at http://wiki.apache.org/geronimo/ActiveMQ_Incubation. In summary we're most of the way through incubation now, things have been progressing very well; the code is clean and using only Apache-compliant libraries, it has the correct copyright notices and is in the org.apache.activemq namespace and is generally working well now. We've got the software grants sorted and most developers have their CLAs on file and accounts created (we've a few more to do once we know the CLAs are on file). We've voted on a milestone release which should go out soon once we've figured out the practicalities of doing an incuabtor milestone release. Our main outstanding issue now is creating the full website at Apache - which should be done in the next week or two - for now there is a simple home page. Apollo Has already graduated. Agila Project is moving along with an interested core continuing to work on the software. Progress is still slow in terms of community building. Recent additions to the incubator in areas of SOA such as Tuscany, ServiceMix, Celtix etc offer an opportunity for Agila's workflow and BPEL implementations. Axion *HAS YET TO START, AND WILL LIKELY BE REMOVED* AltRMI * NO REPORT PROVIDED * Felix Mostly a quarter of contributions and new committers that came with them: Domoware Contribution HttpService Contribution WireAdmin Contribution M2 plugin and archetype for OSGi projects completed Organized repository structure R4 released and ASL compatible ... Might want to list the new committers here: Rob Walker ... FtpServer * NO REPORT PROVIDED * Graffito Graffito has nicely grown recently with activity encouraged by the final release of Jetspeed 2.0 and good progress made on the JCR support though Jackrabbit. We've just added a new committer : Alexandru Popescu and some existing Portals committers also actively contributing to the integration of Graffito with Portals. Harmony Harmony project has moved out of it's initial phase in which it formalized contribution and other governance issues and has now accepted two major class library code contributions, one from IBM and one from Intel. Work continues on those two codebases, with topics ranging from bug fixing, enhancements, as well as other topics such as how to organize test framework and documentation. Two releases of snapshots are imminent, one of a basic VM implementation (JCHEVM) and one of the current classlibrary. We are doing this to make it easier for users to work with the software.
Re: [VOTE] AJAX Toolkit Proposal - Updated
Sam Ruby wrote: And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Andy, any preference? I don't have any particular preference in regards to the name. If people have a problem with AjaxTk being too broad, then any other name will do. I have a natural preference towards Japanese names, though, so I'll suggest Kabuki. :) -- Andy Clark * Zimbra * [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated
Justin Erenkrantz wrote: I see .java files - that has nothing to do with AJAX, so I'm sort of confused. I'd be expecting to see, well, only JavaScript. [...] If it has .java files, it isn't a 'client library'. So, I want to make sure we clarify where the boundaries are, so stupid people like me can make calls as to whether there's scope creep or not. Without communication to the host server, AJAX is just JavaScript in a web page. So there is a natural tendency to have server-side infrastructure to complete the AJAX programming model. At a basic level, there's a need to provide localized content for the application running in the browser. For example, in the Zimbra client, we put all of the resources in a standard Java .properties file and have a simple servlet detect the preferred language, load the resources (merging them), and return the data as a JS class. And at a higher level, there's a need for authorization, notification, etc. While this submission starts with the primary widget toolkit needed to start building AJAX applications, there is a need for server-side code to complete the model. And Java is a natural solution for this part and it ties in nicely with Tomcat and other solutions already at Apache. I hope this helps explain why there is some Java code in the client library. And, as for scope, I don't think the AJAX toolkit will stop simply at client-side widgets because that's only half of the picture. But I think we can start there and have it grow/evolve over time. -- Andy Clark * Zimbra * [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Incubator 2006Q1 Status Report to the ASF Board
This second posting has a revised Roller report, and the WSRP4J report. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated
Hi folks, First off, I would like to thank everyone for taking interest in the ajax toolkit incubator proposal and for the time folks are taking in providing feedback. From reading the various postings, there seems to be three areas of concern: 1) Project name. The issue here seems to be that the project name not be too general. I think that fixing this should not be a big issue. 2) Scope. Concern here stems around the breadth of the project. I think that some folks may be having some trouble drawing a box around what exactly is included in the scope of this project. Bottom line this project provides an SDK for developing ajax apps. The SDK includes the usual things one would expect such as network programming packages, utilities, UI components etc. There is a whitepaper on the Zimbra website that provides an overview of what is included in the toolkit. The URL for it is: http://www.zimbra.com/pdf/Zimbra AJAX TK Whitepaper.pdf 3) Technical issues. This is the area where I personally would love to see some more concrete discussion. From the various posts, it seems that a some folks have issues with the architecture and/or implementation of the code that Zimbra is contributing. I am having trouble diserning what exactly these concerns/issues are. I think it would be great if those with such concerns could perhaps post some details so that we can get some discussion going around them. Cheers Ross
Incubator 2006Q1 Status Report to the ASF Board
Status report for the Apache Incubator Project == The Incubator continues to see good progress in a number of projects and their communities. Several items of note from this past quarter: We have had some discussion regarding the rate of growth, how to manage it, how to ensure proper oversight. We have not finalized any policy changes, but should do so shortly. There is a sometimes not-so-subtle- tension between oversight and nimbleness, and we're trying to give as much of the latter as possible without sacrificing the former. We have also had a discussion regarding importing external codebases, with the conclusion that where possible, we DO want to import the entire history. This will require some help from Infrastructure to help us swizzle the imported authors into some canonical format that won't collide with our ASF author namespace. People are unhappy with the state of building the web site. There are two possible paths: switching our content to anakia format, or improvement in the usability of Forrest. Which path we take will depend upon the energy invested by those who want to help effect the change. Jean T. Anderson has helped to revise the Incubator Guidelines, although we will have to continue the process. - 0 - The list of projects in the Incubator is at http://incubator.apache.org/projects/. Here are the STATUS reports from the PPMCs. The drafts were collected at http://wiki.apache.org/incubator/IncubatorBoardReport2006Q1. Axion never began Incubation, despite having been approved by the DB PMC, and will likely be removed from the list in this quarter. AltRMI, FTPServer, and Tobago failed to provide quarterly reports. Several projects below have graduated, and are noted as such, but until they participate by updating their Incubator documents to indicate that fact, I will continue to ping them. PMCs must help to maintain the content for which they are responsible, or we will never be able to scale. AltRMI has gained no traction, and is likely to leave the Incubator to go elsewhere. FTPServer has added two new Committers, and we see continued activity to revitalize a once dormant project. I addressed the e-mail delivery problem I mentioned in the last quarterly report by adding myself to the allow list for every PMC mailing list. Projects ActiveMQ The full status of incubation is at http://wiki.apache.org/geronimo/ActiveMQ_Incubation. In summary we're most of the way through incubation now, things have been progressing very well; the code is clean and using only Apache-compliant libraries, it has the correct copyright notices and is in the org.apache.activemq namespace and is generally working well now. We've got the software grants sorted and most developers have their CLAs on file and accounts created (we've a few more to do once we know the CLAs are on file). We've voted on a milestone release which should go out soon once we've figured out the practicalities of doing an incuabtor milestone release. Our main outstanding issue now is creating the full website at Apache - which should be done in the next week or two - for now there is a simple home page. Apollo Has already graduated. Agila Project is moving along with an interested core continuing to work on the software. Progress is still slow in terms of community building. Recent additions to the incubator in areas of SOA such as Tuscany, ServiceMix, Celtix etc offer an opportunity for Agila's workflow and BPEL implementations. Axion *HAS YET TO START, AND WILL LIKELY BE REMOVED* AltRMI * NO REPORT PROVIDED * Felix Mostly a quarter of contributions and new committers that came with them: Domoware Contribution HttpService Contribution WireAdmin Contribution M2 plugin and archetype for OSGi projects completed Organized repository structure R4 released and ASL compatible ... Might want to list the new committers here: Rob Walker ... FtpServer * NO REPORT PROVIDED * Graffito Graffito has nicely grown recently with activity encouraged by the final release of Jetspeed 2.0 and good progress made on the JCR support though Jackrabbit. We've just added a new committer : Alexandru Popescu and some existing Portals committers also actively contributing to the integration of Graffito with Portals. Harmony Harmony project has moved out of it's initial phase in which it formalized contribution and other governance issues and has now accepted two major class library code contributions, one from IBM and one from Intel. Work continues on those two codebases, with topics ranging from bug fixing, enhancements, as well as other topics such as how to organize test framework and documentation. Two releases of snapshots are imminent, one of a basic VM implementation (JCHEVM) and one of the current classlibrary. We are doing this to make it easier for users to work with the software. Our focus
RE: ajax proposal?
Martin Cooper wrote: the incubator operates as an open door to whoever knocks, with virtually no entry criteria. The criteria is that another PMC votes or the Incubator PMC votes. In the latter case, we should be looking to see interest from the Membership. In numerous cases, I can think of proposals that came and went with no fanfare, largely because no one was interested. When we DO see interest from ASF Members, I have no problem with a discussion to educate them if one feels that there are reasons to reconsider, but past that, isn't it just down to a vote? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] [RESULT] accept Solr into incubator
With five +1 votes, one +0, and no negative votes, the Solr project has been accepted into the Incubator. As a Mentor, I will now work with the committers to get things going. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ajax proposal?
Raphaël Luta wrote: along with [a] codebase come an established group of committers with an interest in keeping their current architecture or at least backward compatibility That carries a fairly large assumption, and really should be posed as a question, not an answer. An established codebase is *much* more difficult to restructure than starting from scratch. Apache SOAP - Apache Axis Tomcat 3 - Tomcat 4 - Tomcat 5 - Tomcat 5.5 ... Jetspeed 1 - Jetspeed 2 ;-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Incubator 2006Q1 Status Report to the ASF Board
Status report for the Apache Incubator Project == The Incubator continues to see good progress in a number of projects and their communities. Several items of note from this past quarter: We have had some discussion regarding the rate of growth, how to manage it, how to ensure proper oversight. We have not finalized any policy changes, but should do so shortly. There is a sometimes not-so-subtle- tension between oversight and nimbleness, and we're trying to give as much of the latter as possible without sacrificing the former. We have also had a discussion regarding importing external codebases, with the conclusion that where possible, we DO want to import the entire history. This will require some help from Infrastructure to help us swizzle the imported authors into some canonical format that won't collide with our ASF author namespace. People are unhappy with the state of building the web site. There are two possible paths: switching our content to anakia format, or improvement in the usability of Forrest. Which path we take will depend upon the energy invested by those who want to help effect the change. Jean T. Anderson has helped to revise the Incubator Guidelines, although we will have to continue the process. - 0 - The list of projects in the Incubator is at http://incubator.apache.org/projects/. Here are the STATUS reports from the PPMCs. The drafts were collected at http://wiki.apache.org/incubator/IncubatorBoardReport2006Q1. Axion never began Incubation, despite having been approved by the DB PMC, and will likely be removed from the list in this quarter. AltRMI and FTPServer failed to provide quarterly reports. AltRMI has gained no traction, and is likely to leave the Incubator to go elsewhere. FTPServer has added two new Committers, and we see continued activity to revitalize a once dormant project. Several projects below have graduated, and are noted as such, but until they participate by updating their Incubator documents to indicate that fact, I will continue to ping them. PMCs must help to maintain the content for the podlings that they have sponsored, or we will never be able to scale. I addressed the e-mail delivery problem I mentioned in the last quarterly report by adding myself to the allow list for every PMC mailing list. Projects ActiveMQ The full status of incubation is at http://wiki.apache.org/geronimo/ActiveMQ_Incubation. In summary we're most of the way through incubation now, things have been progressing very well; the code is clean and using only Apache-compliant libraries, it has the correct copyright notices and is in the org.apache.activemq namespace and is generally working well now. We've got the software grants sorted and most developers have their CLAs on file and accounts created (we've a few more to do once we know the CLAs are on file). We've voted on a milestone release which should go out soon once we've figured out the practicalities of doing an incuabtor milestone release. Our main outstanding issue now is creating the full website at Apache - which should be done in the next week or two - for now there is a simple home page. Apollo Has already graduated. Agila Project is moving along with an interested core continuing to work on the software. Progress is still slow in terms of community building. Recent additions to the incubator in areas of SOA such as Tuscany, ServiceMix, Celtix etc offer an opportunity for Agila's workflow and BPEL implementations. Axion *HAS YET TO START, AND WILL LIKELY BE REMOVED* AltRMI * NO REPORT PROVIDED * Felix Mostly a quarter of contributions and new committers that came with them: Domoware Contribution HttpService Contribution WireAdmin Contribution M2 plugin and archetype for OSGi projects completed Organized repository structure R4 released and ASL compatible ... Might want to list the new committers here: Rob Walker ... FtpServer * NO REPORT PROVIDED * Graffito Graffito has nicely grown recently with activity encouraged by the final release of Jetspeed 2.0 and good progress made on the JCR support though Jackrabbit. We've just added a new committer : Alexandru Popescu and some existing Portals committers also actively contributing to the integration of Graffito with Portals. Harmony Harmony project has moved out of it's initial phase in which it formalized contribution and other governance issues and has now accepted two major class library code contributions, one from IBM and one from Intel. Work continues on those two codebases, with topics ranging from bug fixing, enhancements, as well as other topics such as how to organize test framework and documentation. Two releases of snapshots are imminent, one of a basic VM implementation (JCHEVM) and one of the current classlibrary. We are doing this to make it easier for users to work with the software. Our focus
RE: Incubator 2006Q1 Status Report to the ASF Board
Tobago came through with its report. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated
--On January 17, 2006 11:36:23 AM -0800 Andrew Clark [EMAIL PROTECTED] wrote: While this submission starts with the primary widget toolkit needed to start building AJAX applications, there is a need for server-side code to complete the model. And Java is a natural solution for this part and it ties in nicely with Tomcat and other solutions already at Apache. I hope this helps explain why there is some Java code in the client library. And, as for scope, I don't think the AJAX toolkit will stop simply at client-side widgets because that's only half of the picture. But I think we can start there and have it grow/evolve over time. Thanks. Before I would vote +1, I'd like to see this mentioned in the proposal (that is, it intends to create server-side code as well) so that this is clear from the project's outset. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated
On Tue, 17 Jan 2006, Andrew Clark wrote: Justin Erenkrantz wrote: I see .java files - that has nothing to do with AJAX, so I'm sort of confused. I'd be expecting to see, well, only JavaScript. [...] If it has .java files, it isn't a 'client library'. So, I want to make sure we clarify where the boundaries are, so stupid people like me can make calls as to whether there's scope creep or not. Without communication to the host server, AJAX is just JavaScript in a web page. So there is a natural tendency to have server-side infrastructure to complete the AJAX programming model. While some AJAX toolkits do include server side code (e.g. Zimbra, DWR), others do not (e.g. Prototype, Dojo). There are pros and cons on both sides. You've detailed some of the advantages of providing it; the main down side would seem to be that it could slow adoption by those who are building their web apps with other server side languages, or even dissuade them from using it. Of course, you could always add support for other languages as well, assuming there are no ties to Java. My 2 cents. -- Martin Cooper At a basic level, there's a need to provide localized content for the application running in the browser. For example, in the Zimbra client, we put all of the resources in a standard Java .properties file and have a simple servlet detect the preferred language, load the resources (merging them), and return the data as a JS class. And at a higher level, there's a need for authorization, notification, etc. While this submission starts with the primary widget toolkit needed to start building AJAX applications, there is a need for server-side code to complete the model. And Java is a natural solution for this part and it ties in nicely with Tomcat and other solutions already at Apache. I hope this helps explain why there is some Java code in the client library. And, as for scope, I don't think the AJAX toolkit will stop simply at client-side widgets because that's only half of the picture. But I think we can start there and have it grow/evolve over time. -- Andy Clark * Zimbra * [EMAIL PROTECTED] - 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] AJAX Toolkit Proposal - Updated
Andrew Clark wrote: Sam Ruby wrote: And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Andy, any preference? I don't have any particular preference in regards to the name. If people have a problem with AjaxTk being too broad, then any other name will do. I have a natural preference towards Japanese names, though, so I'll suggest Kabuki. :) That does seem like a very fitting name. Can I ask you to create the following page, and fold in your answer to Justin's concern? http://wiki.apache.org/incubator/KabukiProposal - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated
how about AJAX? :) Yoav Shapira wrote: Hola, I'll chime in with some name ideas just for consideration ;) And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Mmm, yeah, maybe that's just you ;) natural preference towards Japanese names, though, so I'll suggest Kabuki. :) Kabuki is not bad, though somewhat old-fashioned, no? Here are a couple of Japanese ones: - abarenbo (a hooligan ;)) - aite (the person/entity with which you share something: nice for AJAX since it does depend on some server-side stuff, whatever language you choose) - gumbai (ancient, hand-crafted fan used by sumo referees, and yes, most of my knowledge of japanese comes from being a sumo fan) - haru (spring, as in rebirth) - ketsudan (determination) - yukata (summer kimono, connotation of lightweight, airy...) -- Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com - 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: Incubator site status wrt a move to Anakia?
I thought all of it was pretty much done except for the project pages in cwiki, but you said those are HTML, so just waiting for a shipment of Round Tuits Sounds cool, though. geir David Crossley wrote: David Crossley wrote: I am investigating creating a Forrest output plugin to do the complete conversion. If Geir or others come up with another solution then fine, this will still be a useful tool for Forrest. Update: We now have a Forrest output plugin working to generate Anakia xdocs from the current Incubator site. Needs more work on the plugin to transform the output and adjust some xml attributes. We should be able to do a repeatable process. So the rest of you keep on editing content. Later we will do a batch conversion. -David - 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] AJAX Toolkit Proposal - Updated
Yoav Shapira wrote: natural preference towards Japanese names, though, so I'll suggest Kabuki. :) Kabuki is not bad, though somewhat old-fashioned, no? I guess I'm an old-fashioned kind of guy. :) Actually, my favorite traditional Japanese art is bunraku even though I (sadly) have not seen it in real-life. - abarenbo (a hooligan ;)) - aite (the person/entity with which you share something: nice for AJAX since it does depend on some server-side stuff, whatever language you choose) - gumbai (ancient, hand-crafted fan used by sumo referees, and yes, most of my knowledge of japanese comes from being a sumo fan) - haru (spring, as in rebirth) - ketsudan (determination) - yukata (summer kimono, connotation of lightweight, airy...) I remember going to a sumo basho in Tokyo about 4 years ago. What a blast! And even though I was in the nose-bleed seats (and thus couldn't throw my mat when I disagreed with a match), I could still hear the thunderous slap of the sumos' immense bodies hitting. nazukashii... I went ahead and changed the proposal name to Kabuki on the Incubator Wiki[1]. While I really like your sumo- inspired suggestions, I figured kabuki was one of the few words that even Westerners could identify (besides the obvious hibachi, sushi, sake, and karaoke). And it offers some interesting possibilities for logos. Anyway, we can always change the name later if we want to -- I just want to resolve some of the current issues with the proposal and move forward. [1] http://wiki.apache.org/incubator/KabukiProposal -- Andy Clark * Zimbra * [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated (Again)
I have made a few modifications to the Ajax proposal Wiki page[1] in an attempt to resolve a few of the issues people have raised. The changes include: * Changed name to Kabuki * Added text to clarify the scope of the project Please let me know if there are any other issues that should be addressed by changes to the proposal text. Please note that the name change requires you to update any bookmarks you may already have for the old link. [1] http://wiki.apache.org/incubator/KabukiProposal - Original Message - From: Sam Ruby [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Tuesday, January 17, 2006 1:03:59 PM Subject: Re: [VOTE] AJAX Toolkit Proposal - Updated Andrew Clark wrote: Sam Ruby wrote: And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Andy, any preference? I don't have any particular preference in regards to the name. If people have a problem with AjaxTk being too broad, then any other name will do. I have a natural preference towards Japanese names, though, so I'll suggest Kabuki. :) That does seem like a very fitting name. Can I ask you to create the following page, and fold in your answer to Justin's concern? http://wiki.apache.org/incubator/KabukiProposal - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andy Clark * Zimbra * [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
Is this becoming the current de-facto process, posting to a wiki? (or @)#!)#@ wiki, as I tend to think of them...) Can we please have things go to the mail list, as that should be the 'primary institutional memory' of the incubator community. Feel free to also have on a wiki for collaboration to get it done, but after that, the final proposal should, IMO, go to the mail list. Does anyone else feel this way? Mail archives will live for years in distributed places. Wiki's seem to be single-sourced and a lot more ephemeral geir David N. Welton wrote: David N. Welton wrote: I guess it should be placed on the wiki? I'll do that later today if no one else beats me to it. Here we go: http://wiki.apache.org/incubator/OFBizProposal I changed the proposed sponsor to the Incubator PMC, as that's apparently the done thing. Ciao, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator site status wrt a move to Anakia?
Geir Magnusson Jr wrote: I thought all of it was pretty much done except for the project pages in cwiki, but you said those are HTML, so just waiting for a shipment of Round Tuits Yes but Anakia doesn't deal with HTML, does it? I am not sure what you were waiting for. I think that we were all expecting for you to continue. Like i said in another thread, don't wait for me to provide a solution. Anyway i have fast-tracked my work because the delays cannot be sustained. Sounds cool, though. Yes i am really pleased with the new Forrest ability. -David geir David Crossley wrote: David Crossley wrote: I am investigating creating a Forrest output plugin to do the complete conversion. If Geir or others come up with another solution then fine, this will still be a useful tool for Forrest. Update: We now have a Forrest output plugin working to generate Anakia xdocs from the current Incubator site. Needs more work on the plugin to transform the output and adjust some xml attributes. We should be able to do a repeatable process. So the rest of you keep on editing content. Later we will do a batch conversion. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator site status wrt a move to Anakia?
David Crossley wrote: Geir Magnusson Jr wrote: I thought all of it was pretty much done except for the project pages in cwiki, but you said those are HTML, so just waiting for a shipment of Round Tuits Yes but Anakia doesn't deal with HTML, does it? Right - so I have to convert them all... I am not sure what you were waiting for. I think that we were all expecting for you to continue. My shipment of Round Tuits was delayed. Others can pitch in though :) Like i said in another thread, don't wait for me to provide a solution. Anyway i have fast-tracked my work because the delays cannot be sustained. Sounds cool, though. Yes i am really pleased with the new Forrest ability. -David geir David Crossley wrote: David Crossley wrote: I am investigating creating a Forrest output plugin to do the complete conversion. If Geir or others come up with another solution then fine, this will still be a useful tool for Forrest. Update: We now have a Forrest output plugin working to generate Anakia xdocs from the current Incubator site. Needs more work on the plugin to transform the output and adjust some xml attributes. We should be able to do a repeatable process. So the rest of you keep on editing content. Later we will do a batch conversion. -David - 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 for OFBiz to Join the ASF
On Wednesday 18 January 2006 07:16, Geir Magnusson Jr wrote: Does anyone else feel this way? Mail archives will live for years in distributed places. Wiki's seem to be single-sourced and a lot more ephemeral Yes. As the primary tool of communication for myself and many others, mails are read. Links less so. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
Geir Magnusson Jr wrote: Is this becoming the current de-facto process, posting to a wiki? (or @)#!)#@ wiki, as I tend to think of them...) Can we please have things go to the mail list, as that should be the 'primary institutional memory' of the incubator community. Feel free to also have on a wiki for collaboration to get it done, but after that, the final proposal should, IMO, go to the mail list. Does anyone else feel this way? Mail archives will live for years in distributed places. Wiki's seem to be single-sourced and a lot more ephemeral I agree. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wiki votes, was Re: Proposal for OFBiz to Join the ASF
[changed subject line though I don't intend to have a big discussion about this topic] On 18.01.2006, at 00:16, Geir Magnusson Jr wrote: Is this becoming the current de-facto process, posting to a wiki? (or @)#!)#@ wiki, as I tend to think of them...) Can we please have things go to the mail list, as that should be the 'primary institutional memory' of the incubator community. Feel free to also have on a wiki for collaboration to get it done, but after that, the final proposal should, IMO, go to the mail list. Does anyone else feel this way? Mail archives will live for years in distributed places. Wiki's seem to be single-sourced and a lot more ephemeral Thanks, Geir - there was a half written msg with exactly this topic in my outbox... I fully agree with you that at least anything which is subject to a vote should directly include all the relevant information - no links for substantial content, just for extras like fancy PDFs describing the architecture or tarballs of the initial codebase etc. This may sound a bit picky but everything else unfortunately comes with too many disadvantages (no real archives, dead links, no offline access, etc.). Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
Re: [jira] Created: (INFRA-677) create accounts for new committers for new project Solr
I had read that guide, but it seems geared toward existing projects wasn't clear what to do in the case of a new project in the incubator. Shall I send the email to root? Or do I need a PMC to do so? What is the relevant PMC... Lucene or the Incubator? (Solr is going to be a sub-project of Lucene on incubation). -Yonik On 1/17/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: Please follow guidelines here : http://www.apache.org/dev/pmc.html#newcommitter thanks Begin forwarded message: From: Yonik Seeley (JIRA) [EMAIL PROTECTED] Date: January 17, 2006 5:40:44 PM EST To: [EMAIL PROTECTED] Subject: [jira] Created: (INFRA-677) create accounts for new committers for new project Solr Reply-To: [EMAIL PROTECTED] create accounts for new committers for new project Solr --- Key: INFRA-677 URL: http://issues.apache.org/jira/browse/INFRA-677 Project: Infrastructure Type: Task Reporter: Yonik Seeley Priority: Blocker Project Solr has been accepted for incubation. We need two new apache accounts created for this project: Preferred userid: billa Full name:William Au Forwarding email address: [EMAIL PROTECTED] Preferred userid: hossman Full name:Chris M. Hostetter Forwarding email address: [EMAIL PROTECTED] Solr Incubation VOTE: http://www.mail-archive.com/ general@incubator.apache.org/msg06689.html -- 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 -- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (INFRA-677) create accounts for new committers for new project Solr
On 18.01.2006, at 02:32, Yonik Seeley wrote: I had read that guide, but it seems geared toward existing projects wasn't clear what to do in the case of a new project in the incubator. You are right, this manual is a bit thin on details for incubator- related projects. Shall I send the email to root? Or do I need a PMC to do so? What is the relevant PMC... Lucene or the Incubator? (Solr is going to be a sub-project of Lucene on incubation). The Lucene PMC - the Incubator PMC could also do it but let's save their energy for projects directly sponsored by them ;-) Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
RE: Proposal for OFBiz to Join the ASF
Geir Magnusson Jr wrote: Can we please have things go to the mail list, as that should be the 'primary institutional memory' of the incubator community. +1 But let's try to say such things to be educational, not chastising. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Synapse release milestone1 from the Incubator
+1 for going ahead with the milestone release. Sanjiva. On Tue, 2006-01-17 at 09:09 +, Paul Fremantle wrote: Hi! The Synapse incubator would like to make a Milestone 1 release. We proposed this in December, with a successful vote from the WS PMC. We have read the guidelines http://incubator.apache.org/incubation/Incubation_Policy.html#Releases and understand these. The codebase has enough functionality to support the initial milestone criteria (plus more) and so we would like to release it as a synapse-incubator-M1. We are tracking our status towards the release here: http://wiki.apache.org/ws/Synapse/M1Criteria I have been voted as the release manager. The release candidate zip file is available here: http://people.apache.org/~pzf/synapse/Synapse-Incubating-M1-SNAPSHOT-bin.zip I am just in the process of updating our status page on the incubator. We are also tracking on wiki here: http://wiki.apache.org/ws/Synapse/IncubationStatus Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (INFRA-677) create accounts for new committers for new project Solr
On 18.01.2006, at 02:37, Erik Abele wrote: On 18.01.2006, at 02:32, Yonik Seeley wrote: I had read that guide, but it seems geared toward existing projects wasn't clear what to do in the case of a new project in the incubator. You are right, this manual is a bit thin on details for incubator- related projects. I've just added a short note to the section in question... Cheers, Erik smime.p7s Description: S/MIME cryptographic signature
[doc] Getting Started in the Incubator topic
Here's another starter installment for the Incubator Guidelines Documentation project Noel posted at http://mail-archives.apache.org/mod_mbox/incubator-general/200512.mbox/[EMAIL PROTECTED] Several times during derby's incubation I felt disoriented because while there's a lot of info on the incubator site, I didn't seem to always find what I needed as a completely new podling committer. Below is a first shot at providing a succinct Getting Started that points complete newbies to resources already on the incubator site and fills in a few holes. For those of you currently in incubation, does this help? Or would it have helped when you first started. :-) What more would help? == Getting Started: Podling Committer == Welcome! Your general committer role is described at http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Committers , but here's more information to help you get started. (1) Mailing lists - Subscribe to the user, dev, and commit lists for your project. - Become aware of what else is going on in the Incubator by subscribing to the general@incubator.apache.org list described at http://incubator.apache.org/howtoparticipate.html#Mailing+lists - Become aware of what else is going on at the ASF by subscribing to the Apache-wide lists described at http://incubator.apache.org/learn/mailing-lists.html (Note: we should add [EMAIL PROTECTED] to this list.) (2) Project web site + How to get your project web site going is documented at http://incubator.apache.org/howtoparticipate.html#Project+Website+Howto + Post any questions to [EMAIL PROTECTED] (3) Committer Resources + Browse the pages at http://www.apache.org/dev/ often. + Subscribe to [EMAIL PROTECTED], then raise awareness on your project on what goes on behind the scenes. Be proactive about responding to infrastructure issues on your project mailing lists. Does the web server seem to be down? Is Jira or Subversion down? Check the status at http://monitoring.apache.org/status/ and report back to your list. (4) Podling PMC (PPMC) If you are a member of your PPMC, become familiar with the Incubation Policy at http://incubator.apache.org/incubation/Incubation_Policy.html . You'll likely participate in the following: + Update the podling status on the Incubator site: http://incubator.apache.org/guides/website.html#Edit+your+project+status+report + Add new committers to your project: http://incubator.apache.org/learn/newcommitters.html + Make sure that a quarterly report is submitted when the Incubator PMC Chair requests it. end draft OK, this is pretty thin so far, but should give the idea of what I'm shooting for. I think this information should go in one of these places: http://incubator.apache.org/learn/ http://incubator.apache.org/guides/ It shouldn't be buried deep in a subpage, nor should it be on a page that is already busy. http://incubator.apache.org/howtoparticipate.html is borderline too busy and covers more than this one role. comments? feedback? thanks, -jean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
Hi Geir (and all), my name is Jacopo Cappellato, I'm one of the developers of the OFBiz project and, as you can imagine, I'm very interested in your feedback about our request to join the ASF Incubator. About the proposal posted to the Wiki instead of to this list... well if you go to the first post in this thread you'll find a mail from David Jones with the proposal attached (in PDF format). The document has essentially the same content of the Wiki page, only the proposed sponsor is different (based on feedback from this list, we are now asking that the Incubator PMC be our sponsor). Of course, we have no problems to repost to the list an updated PDF version as well, if PDF is good for you (and we'll probably do this if there are no more comments from this list that we should take into account). Thanks for your time and suggestions, Jacopo Geir Magnusson Jr wrote: Is this becoming the current de-facto process, posting to a wiki? (or @)#!)#@ wiki, as I tend to think of them...) Can we please have things go to the mail list, as that should be the 'primary institutional memory' of the incubator community. Feel free to also have on a wiki for collaboration to get it done, but after that, the final proposal should, IMO, go to the mail list. Does anyone else feel this way? Mail archives will live for years in distributed places. Wiki's seem to be single-sourced and a lot more ephemeral geir David N. Welton wrote: David N. Welton wrote: I guess it should be placed on the wiki? I'll do that later today if no one else beats me to it. Here we go: http://wiki.apache.org/incubator/OFBizProposal I changed the proposed sponsor to the Incubator PMC, as that's apparently the done thing. Ciao, - 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]
Filling out an Incubation Status
Dumb question. Are the completion dates on http://incubator.apache.org/projects/roller.html when the event happened, or when it was marked as complete. ie) to start ticking these things off, do I need to go do mailing list audits etc to figure out when things happen, or can I just put today's date? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On Mon, Jan 16, 2006 at 10:45:49PM +0100, David N. Welton wrote: David N. Welton wrote: I guess it should be placed on the wiki? I'll do that later today if no one else beats me to it. Here we go: http://wiki.apache.org/incubator/OFBizProposal I changed the proposed sponsor to the Incubator PMC, as that's apparently the done thing. I believe J. Aaron said he'd be willing to mentor too[1]. -- justin 1. http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On 1/18/06, Justin Erenkrantz [EMAIL PROTECTED] wrote: On Mon, Jan 16, 2006 at 10:45:49PM +0100, David N. Welton wrote: David N. Welton wrote: I guess it should be placed on the wiki? I'll do that later today if no one else beats me to it. Here we go: http://wiki.apache.org/incubator/OFBizProposal I changed the proposed sponsor to the Incubator PMC, as that's apparently the done thing. I believe J. Aaron said he'd be willing to mentor too[1]. -- justin Certainly willing if they'll have me! :-) -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator site status wrt a move to Anakia?
Here is the result of my experiment ... [1] http://people.apache.org/~crossley/incubator-anakia/ The existing Incubator site was converted to Anakia xdoc format. I used a local copy of Geir's previous experiment [2] but with the forrest-generated anakia xdocs. We can tweak the Forrest plugin to match any changes in Geir's xdoc format and stylesheets. Anakia didn't report any errors with the final run. However, please look out for any strangeness. All the filenames and directories are the same as the existing Incubator site. So existing URLs are maintained. As with Geir's, i dropped the learn directory. The projects/*.cwiki files are all converted. If any documents were not linked in to the existing site then they will be missing. Also other resources will be missing. For example, i needed to manually retrieve a local image at Process_Description.html and if there were any directly linked PDF docs then they will be missing. This can be manually fixed later. There is still a strange situation with extra documents in sub-directories of site-author/projects/ e.g. agila, activemq, servicemix ... these seem to be project websites which are supposed to be elsewhere in the Incubator SVN. There is also some additional stuff in geronimo. None of these documents are in the new site. I did a quick 'diff -rq' on people.apache.org and there are differences. Someone should investigate further. The conversion process can be run at anytime. It might take us a while to decide, etc. Now don't let any of this stop you from editing the current sources in site-author, especially in site-author/projects status reports. We can convert again at any time. This site transformation was done with trunk of Forrest (after i check some stuff in). I could check in new commented config to Incubator and describe how to do it. Lets wait a bit. Thanks to the Forrest project for the new abilities. Good result. [1] http://people.apache.org/~crossley/incubator-anakia/ [2] http://marc.theaimsgroup.com/?l=incubator-generalm=113612265423731 Experiment : Incubator site done in xdocs... -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator site status wrt a move to Anakia?
Responding to some issues that people have with the layout of the current forrest-based website. [1] http://people.apache.org/~crossley/incubator-forrest/ If you want me to implement any of these immediately then say so. Get rid of PDF -- There was a PDF generated for every page. The idea was that with complex process documentation people need to print it to be able to read, comprehend, tick it, show/file a paper copy, etc. A upcoming version of Forrest (probably not next) will enable per-page PDFs rather than all-or-none. The PDF button at top-right is now removed. The Print button remains. Get rid of Tabs --- There were four Tabs: Home - this still remains. Projects - All current projects were listed down the left. This was superfluous and also meant that generated html pages changed when a new project was added. Gone now. Learn - The beginnings of some general documentation. Gone now. I reckon that we should intead point to www.a.o/dev/ documents. Whiteboard - just pointed to Wiki. Gone now. Just have a link in the main navigation. Hidden items in left-hand navigation Incubation policy documents were hidden in collapsed left-hand menus. This is a distinct lack with Forrest. By default these groups of items are shown collapsed, and only open when you select it or visit of the group's pages. Will to Forrest issue tracker. Needs a collapse attribute. The workaround is to bung them all in the About group. Get rid of W3C html/css compliance logos Done. Change the logo and banner -- Can be done, but not done yet. Get rid of the swathes of blue bars --- Could do some minor tweaks, remove breadcrumb trail, reduce footer, change colours. Not done yet. Also Ross has the beginnings of another theme to enable a bland look, if needed. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
