Please don't edit website files on the server machine(s)
Hi gang, While running 'svn up' inside people.apache.org:/www/incubator.apache.org I saw this: Gprojects/felix.html which indicates someone edited that file at the live location, or scp-ed it over, or something similar. Please **don't do anything like that**. The website management process for the incubator website is quite clearly documented at http://incubator.apache.org/guides/website.html and by doing things any other way you're making things confusing for everyone else working on the website, reducing oversight simplicity, and introducing a potential for merge conflicts showing up on the live site. thanks! cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-7) STATUS file out of date, confusing
[ http://issues.apache.org/jira/browse/INCUBATOR-7?page=all ] Leo Simons closed INCUBATOR-7: -- Resolution: Fixed Assign To: Leo Simons Keeping track of changes to a track record in an issue tracker seems rather silly to me! Anyhow, previous comments indicated closing this is ok. STATUS file out of date, confusing -- Key: INCUBATOR-7 URL: http://issues.apache.org/jira/browse/INCUBATOR-7 Project: Incubator Type: Bug Components: policy Environment: all Reporter: Martin Sebor Assignee: Leo Simons The STATUS file (http://svn.apache.org/repos/asf/incubator/public/trunk/STATUS) posted to general@incubator.apache.org once a week is out of date and confusing. See this thread for details: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] A tentative patch for the problems pointed out in the post above is here: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] In addition, in his response (below) to this thread, David Crossley identifies two specific issues that should be addressed: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] -- 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] Commented: (INCUBATOR-1) document copyright changes
[ http://issues.apache.org/jira/browse/INCUBATOR-1?page=comments#action_12365207 ] Leo Simons commented on INCUBATOR-1: Our VP legal is working on a detailed policy about this. The incubator can incorporate by reference when its finished. document copyright changes -- Key: INCUBATOR-1 URL: http://issues.apache.org/jira/browse/INCUBATOR-1 Project: Incubator Type: Improvement Components: policy Reporter: Rodent of Unusual Size there is an issue with files contributed to the asf through the incubator. currently it is unclear how the copyright issue should be managed; what gets put into the NOTICE file, what goes into each individual file, et cetera. once this is officially sorted out, it needs to be added to the incubator documentation -- along with a notation about whether the changes should be made RTC with review by the board, the incubator, or whom. -- 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] Closed: (INCUBATOR-2) fixed a few URLs in apollo/hermes/muse STATUS pages
[ http://issues.apache.org/jira/browse/INCUBATOR-2?page=all ] Leo Simons closed INCUBATOR-2: -- Resolution: Won't Fix Assign To: Leo Simons The original patch is two years old. fixed a few URLs in apollo/hermes/muse STATUS pages --- Key: INCUBATOR-2 URL: http://issues.apache.org/jira/browse/INCUBATOR-2 Project: Incubator Type: Task Components: site Reporter: Ian P. Springer Assignee: Leo Simons Priority: Minor Attachments: status-pages.patch Please apply the attached patch to http://svn.apache.org/repos/asf/incubator/public/. -- 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] Commented: (INCUBATOR-4) better docs for new committer procedure
[ http://issues.apache.org/jira/browse/INCUBATOR-4?page=comments#action_12365209 ] Leo Simons commented on INCUBATOR-4: Let's not try and have policy discussions within jira... better docs for new committer procedure --- Key: INCUBATOR-4 URL: http://issues.apache.org/jira/browse/INCUBATOR-4 Project: Incubator Type: Improvement Components: site Reporter: Jukka Zitting Priority: Minor Attachments: newcommiter.r371425.html, newcommitter.patch, newcommitter.r371425.patch There doesn't currently seem to be a good consensus on the correct procedure for adding new committers to incubating projects. See the recent mailing list discussion at http://thread.gmane.org/gmane.comp.apache.incubator.general/5408. -- 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] Closed: (INCUBATOR-9) Patch to create docs using coat skin
[ http://issues.apache.org/jira/browse/INCUBATOR-9?page=all ] Leo Simons closed INCUBATOR-9: -- Resolution: Won't Fix Assign To: Leo Simons Incubator has moved to use anakia for website, so patch is no longer relevant or apply-able. Patch to create docs using coat skin Key: INCUBATOR-9 URL: http://issues.apache.org/jira/browse/INCUBATOR-9 Project: Incubator Type: Improvement Components: site Reporter: Ross Gardler Assignee: Leo Simons Priority: Trivial Attachments: coat-skin.diff, coat.zip The coat skin is a new skin for Apache Forrest designed to mimic the look and feel of http://www.apache.org This patch will change the incubator site to be built with the coar skin. (NOTE the skin is not currently part of the 0.7-branch of SVN that the Incubator uses, the Forrest devs may not want it to go into the branch as we are only supposed to be putting bug fixes in there. I'll therefore attach a zip of the skin to this issue as well) -- 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] Closed: (INCUBATOR-8) Incubate Tuscany SOA project
[ http://issues.apache.org/jira/browse/INCUBATOR-8?page=all ] Leo Simons closed INCUBATOR-8: -- Resolution: Fixed Assign To: Leo Simons Looking at http://svn.apache.org/repos/asf/incubator/tuscany/, it seems this stuff has been imported into SVN, so I'm closing this issue. Incubate Tuscany SOA project Key: INCUBATOR-8 URL: http://issues.apache.org/jira/browse/INCUBATOR-8 Project: Incubator Type: Wish Components: subversion Reporter: Kenneth Tam Assignee: Leo Simons Attachments: Tuscany-apache-proposal.tar.gz, tuscany-cpp.tar.gz, tuscany-java-contrib.jar, tuscany_cpp.tar.gz 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]
[website] Note a bunch of changes
Oi! For those who don't read the incubator cvs list, I just spent a few hours on the incubator website. Mostly it was a large amount of small tweaks, fixes and changes; no (serious) content changes except for a bit of a rewrite of the text on the front page. Please do review and change (back) the bits you don't like :-) David, Geir, et al, thanks again for doing so much of the hard work; the workflow for this stuff is much more enjoyable now! cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: License grant
On Wed, 1 Feb 2006, Manuel Mall wrote: On the grant form is says: Licensor owns or has sufficient rights to contribute the software source code. In this case we don't have a single Licensor but a group of people. How does the form work in such a case as it seems to make the assumption that the Licensor is either a single person or a single organisation? In the past this was solved by: - All the people in the group all sign the same software grant and thus together hand over the code. (And assuming that all authors are still alive and willing to do so). Logistically this is a bit of a pain; so what was done in the past is simply to have each person sign his 'own' (but identical) version of the softwate grant (with the other people listed as well - but with a blank behind their name) - and then filing the umpteen copies together which are all idnetical expect that they have a different dotted line signed. Dw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Let's rewind!!! (Re: [VOTE] accept donation of a business process engine into the ServiceMix project)
Hi Matthieu, good to hear from you. At this point, it might be worth determining what you think the starting point is for building a strong implementation. If it is in the Sybase contribution, we could start with a new project and integrate any additional value from Agila towards that so that you don't lose anything. On 2/4/06, Matthieu Riou [EMAIL PROTECTED] wrote: Bill, I just want to clarify that we (myself and Chris Lim) were not against your contribution in Agila at all, we just wanted to make sure that the code remained open to others' code contributions as well. We wanted to keep the project open and collaborate with you without ditching the existing code that might have some good things in it too and eventually accept other pieces of work. I think we were more in the prospect of building a strong implementation by assembling good pieces than integrating one out of the box. I apologize if this is the source of the current controversy. Best regards, Matthieu. On 2/3/06, Bill Flood [EMAIL PROTECTED] wrote: Dims, I'll take Cory off the hook since he was acting in good faith on behalf of Sybase :-). As we are learning, there are a variety of ways to work within the Apache process as long as the community is supportive. From the Sybase perspective, we are interested in working with a vibrant community in a meaningful way that balances the needs of the community with that of our own. when we first started thinking about the open source path, we looked at Agila and communicated with the developers. While the Agila developers were quite helpful, the project was not open to our contribution and our assessment was that their existing code line would take substantial work to bring it up to where we thought we already were. When we looked at ServiceMix, we found a mature community that not only appeared open to a contribution such as ours but one which would help us establish a good affinity with the ESB. The Sybase folks working on this code line will continue to vigorously support the orchestration component and provide help in adjacent areas related to SCA. At this point, we feel comfortable in our contribution to the ServiceMix project based on the positive uptake. Under the rules of meritocracy, we will work to ensure that the interfaces remain clean and the build granular enough to be reused and hope to work with you in the future. Best Regards, Bill ---Original Message--- From: Davanum Srinivas [EMAIL PROTECTED] Subject: Re: Let's rewind!!! (Re: [VOTE] accept donation of a business process engine into the ServiceMix project) Sent: 02 Feb '06 21:12 Cory, Could you please get James' help and draft a complete proposal? Please see http://www.google.com/search?hl=enlr=safe=offq=incubator+proposal+site%3Awiki.apache.orgbtnG=Search for a list of proposals, their format and their content. Once the proposal is ready, please post it to [EMAIL PROTECTED] Also, please take a peek at the documentation on the http://incubator.apache.org/ site especially w.r.t to the incubation process, what to expect and steps involved. thanks, dims On 2/2/06, cory [EMAIL PROTECTED] wrote: Hi, BPEL 1.1 is supported. The code works with Axis 1.3. Sybase wants this code to be successful within the community and is going to work to support it. Cheers, -cory On 2/2/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Folks, There is no proposal, there is just a zip, unless someone is a clairvoyant, we can't figure out things like. *PLEASE* CC [EMAIL PROTECTED] - Which specific version of the spec is implemented? - Where are the list of known issues? - Where is the TODO list? - Why is Axis version 1.2 RC1 (and not even Axis 1.2 final even if we forget that the current version is Axis 1.3) - Is there any relation to workflow? - Is there no opportunity for interaction with our Existing incubation project Agila? - Are there people from sybase who will be working? - Geronimo is becoming an umbrella rapidly and now ServiceMix wants to be one too? - Why are people talking as though the code is FINAL (Quoting greg - there is no need to develope a community around this code) (Quoting Rob - If you've looked at the proposed donated code, this BPEL engine is complete, I can't see any sense in combining it with something else ? ) - Do *ANY* of the existing servicemix committers know this code inside out? - If people are not going to touch this contrib code with a barge pole then why should it be accepted? thanks, dims On 2/2/06, James Strachan [EMAIL PROTECTED] wrote: We have received the generous
Re: [website] Note a bunch of changes
All thanks go to David. At best, I just kicked a pebble down a hill... geir Leo Simons wrote: Oi! For those who don't read the incubator cvs list, I just spent a few hours on the incubator website. Mostly it was a large amount of small tweaks, fixes and changes; no (serious) content changes except for a bit of a rewrite of the text on the front page. Please do review and change (back) the bits you don't like :-) David, Geir, et al, thanks again for doing so much of the hard work; the workflow for this stuff is much more enjoyable now! cheers, Leo - 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] accept donation of a business process engine into the ServiceMix project
These are the dependencies for building and/or using the whole transaction module. For example, the geronimo-system, geronimo-core and geronimo-kernel and geronimo-j2ee dependencies are mainly needed to build / use the gbeans for the transaction manager. The jencks project (www.jencks.org) uses the geronimo transaction manager and geronimo jca connector to provide jca enabled pojos. If you take a look at the maven pom (http://cvs.codehaus.org/viewrep/jencks/jencks/project.xml?r=1.24), only the geronimo-transaction and geronimo-connector are used (I exclude the specs) and none of the aforementioned dependencies are really required in this context. True dependencies of a jar really depends on what classes you use in the given jar... ;) Cheers, Guillaume Nodet Niclas Hedhman wrote: On Friday 03 February 2006 23:53, James Strachan wrote: The TM is in a single download-able jar all by itself; so you can download only what you need. e.g. here's the latest snapshot of just the transaction manager... IMHO, this is a vast exaggeration that is not entirely fair to make, and would like to counter with the dependencies list of the said project (see below)... Saying that TM is independent and having Geronimo's system, core, j2ee and kernel modules listed, is definately catching my attention and asking What's your agenda, James? for such misrepresentation. You could have high-lighted the true dependencies. dependencies dependency groupIdgeronimo/groupId artifactIdgeronimo-system/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdgeronimo/groupId artifactIdgeronimo-core/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdgeronimo/groupId artifactIdgeronimo-j2ee/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdgeronimo/groupId artifactIdgeronimo-kernel/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-jta_1.0.1B_spec/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-ejb_2.1_spec/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-j2ee-connector_1.5_spec/artifactId version1.1-SNAPSHOT/version /dependency dependency groupIdconcurrent/groupId artifactIdconcurrent/artifactId version1.3.4/version /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version urlhttp://jakarta.apache.org/commons/logging//url /dependency dependency groupIdhowl/groupId artifactIdhowl-logger/artifactId version0.1.11/version urlhttp://forge.objectweb.org/projects/howl/url /dependency dependency groupIdmx4j/groupId artifactIdmx4j/artifactId version3.0.1/version /dependency dependency groupIdcommons-jelly/groupId artifactIdcommons-jelly-tags-velocity/artifactId version1.0/version /dependency dependency groupIdvelocity/groupId artifactIdvelocity/artifactId version1.4/version /dependency /dependencies Cheers Niclas - 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: Board reporting change for the Incubator
Justin, Yes, I discussed this with Greg after the last Board meeting, but we've had enough to deal with lately, and we'll likely start this in March, which was alright with Greg (after all, we just did them all in January), so there's still time. We'll have to divide up the current projects, and the reports will be due for new projects each quarter in the same offset as when they begin. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] accept donation of a business process engine into the ServiceMix project
The way this 'debate' has continued has been very embarrassing - It just makes me wonder why anyone would consider donating code to Apache in the future ... On 5 Feb 2006, at 21:03, Geir Magnusson Jr wrote: James Strachan wrote: We have received the generous donation of a complete and working BPE engine to the ServiceMix project... http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-dev/ 200602.mbox/% [EMAIL PROTECTED] the contributor has offered to donate to Apache complete the necessary software grants IP clearance and to work with us on integrating it into ServiceMix. I assume we'd all get to see the code under an Apache License before deciding to accept. How else could we vote it in? [SNIP] I'll go out on a limb here : [X] -1 I object because: ... ... I think that a BPEL engine is something that spans many of the WS and SOA oriented projects at the ASF, such as ServiceMix, Tuscany, Synapse, Agila, etc... However, that's not my main reason, because honestly, if I was the only one that cared about that, I wouldn't ever attempt to stand in the way of people wanting to do cool things. However, this proposal has sent up far too many red flags, has alienated too many people, and is causing too much of a bad feeling in people, for ServiceMix, for Geronimo and for the ASF in general. I'd suggest you make a big effort to cool things down and get a broad conversation going, over at [EMAIL PROTECTED], drive to consensus, and then regroup and try again. geir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] accept donation of a business process engine into the ServiceMix project
There is a process for incubation, this is what happens when the process(es) are by-passed. A well written through and inclusive proposal would sail thru in a jiffy. thanks, -- dims On 2/5/06, Rob Davies [EMAIL PROTECTED] wrote: The way this 'debate' has continued has been very embarrassing - It just makes me wonder why anyone would consider donating code to Apache in the future ... On 5 Feb 2006, at 21:03, Geir Magnusson Jr wrote: James Strachan wrote: We have received the generous donation of a complete and working BPE engine to the ServiceMix project... http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-dev/ 200602.mbox/% [EMAIL PROTECTED] the contributor has offered to donate to Apache complete the necessary software grants IP clearance and to work with us on integrating it into ServiceMix. I assume we'd all get to see the code under an Apache License before deciding to accept. How else could we vote it in? [SNIP] I'll go out on a limb here : [X] -1 I object because: ... ... I think that a BPEL engine is something that spans many of the WS and SOA oriented projects at the ASF, such as ServiceMix, Tuscany, Synapse, Agila, etc... However, that's not my main reason, because honestly, if I was the only one that cared about that, I wouldn't ever attempt to stand in the way of people wanting to do cool things. However, this proposal has sent up far too many red flags, has alienated too many people, and is causing too much of a bad feeling in people, for ServiceMix, for Geronimo and for the ASF in general. I'd suggest you make a big effort to cool things down and get a broad conversation going, over at [EMAIL PROTECTED], drive to consensus, and then regroup and try again. geir - 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]
Re: [VOTE] accept donation of a business process engine into the ServiceMix project
On Feb 5, 2006, at 1:29 PM, Rob Davies wrote: The way this 'debate' has continued has been very embarrassing - It just makes me wonder why anyone would consider donating code to Apache in the future ... Because we care enough to have the debate. If anyone wants silence, they are free to go to sourceforge. Silence is death. Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
Leo Simons wrote: As long as you make sure that the questions are more obvious from the docs afterwards, don't apologize :-) *) IP clearance checklist - I need to make a copy of that in SVN here, /incubator/site-author/ip-clearance. I'll try and get that done over the weekend. Ok, I added /incubator/site-author/ip-clearance/ofbiz.xml - although I only cut the lines to be cut and changed the title. More later... Its not just the ip clearance that's needed. There's the concept of an incubator status file (see below). I added that too, thanks to Jacopo Cappellato, who did the initial version of it. *) iCLA's - the OFBiz guys are working on it. This needs to happen before they get accounts, and conversely, they get accounts once this happens, right? if the right emails are sent as documented on /dev/, yup. Which /dev/ are you referring to? *) Cleaning up the code - they're in the process of cleaning up the code, getting rid of LGPL dependencies. This needs to happen prior to the code touching our subversion repositories, correct? No. It needs to happen prior to making any kind of release, and no LGPL code or binaries should touch our SVN. But working on removing such a dependency while within the incubator is okay. Ok - I get the impression that they've got a good handle on this, and may be able to do the initial import with no dependancies. *) JIRA - they have a JIRA instance of their own, which should be migrated to the ASF. I don't know anything about admin'ing JIRA, so I believe this step will require collaboration between David Jones and someone on the infrastructure team. Should I/we go ahead and open an issue on our side for JIRA migration? Does this step have dependencies, or can it start to happen when people are ready to do the work? Yes, go ahead. I think this is quite a tricky thing to do. Jeff Turner is the guy from the infra team to talk to. Ok. So, if David Jones is reading this, that would be jefft followed by apache.org, right? *) Mailing lists - an issue needs to be opened for the infrastructure team to create them, and then collaborate on moving over the existing subscriber list. Same question on dependencies as above. No particular dependencies. Provide the subscriber list as a file with email addresses seperated by newlines and add it to the jira issue, and its easy for the apmail people to add all those people in one swoop. Once that is done you can send an email to the new mailing list and all those people will know they're on a new list. Handling external mailing list archives (eg marc, mail-archives, gmane) might be a little work and depends on how those archives are set up to interact with the ASF stuff; I think some of them have 'special' support. I'll let the OFBiz guys take it from here on this issue... Anything else? The first step before doing any of the above is to get an incubation status file filled out and up on http://incubator.apache.org/projects/index.html Eg, start off with https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/incubation-status-template.xml Thanks to Jacopo, we have an initial cut at that, but neither he nor I has the tools to turn it into HTML (and I need to get some sleep tonight). If anyone else on the OFBiz team wants to have a crack at it, it's attached to this email (I'm not sure you can access the incubator repo anonymously?). -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ ?xml version=1.0 encoding=UTF-8? document properties !--meta content=HTML Tidy, see www.w3.org name=generator/-- !--meta content=text/html; charset=UTF-8 http-equiv=Content-Type/-- titleOFBiz Incubation Status/title link href=http://purl.org/DC/elements/1.0/; rel=schema.DC/ /properties body section id=OFBiz+Project+Incubation+Status titleOFBiz Project Incubation Status/title pThis page tracks the project status, incubator-wise. For more general project status, look on the project website./p /section section id=Description titleDescription/title p The Open For Business Project (OFBiz) is an open source enterprise automation software project. By open source enterprise automation we mean: Open Source ERP, Open Source CRM, Open Source E-Business / E-Commerce, Open Source SCM, Open Source MRP, Open Source CMMS/EAM, and so on. It is one of the few apps of this type to be developed by a community, rather than one corporation. /p /section section id=News titleNews/title ul li2006-01-31 Project accepted by the Incubator PMC/li li2006-01-10 Project proposed to the Incubator PMC/li /ul /section section id=Project+info titleProject info/title ul lilink to the main website/li /ul ul lilink to the page(s) that tell how to participate (Website,Mailing lists,Bug tracking,Source
Re: SSH and SVN passwords
Martin Sebor wrote: robert burrell donkin wrote: On 2/1/06, Martin Sebor [EMAIL PROTECTED] wrote: Could someone kindly describe (or point us to a document explaining) how to reset a user password at people.apache.org? i don't that this is documented anywhere (or indeed whether there's concensus about the right way to do this). but infrastructure workflow is handled through JIRA ( https://issues.apache.org/jira/browse/INFRA) so creating an issue is probably the best bet. Thanks. I looked through the Jira categories/components but couldn't find anything quite appropriate. But I'm sure it doesn't hurt to try so we'll give it a whirl -- Allen, please go ahead an open an INFRA request. Allen, if you haven't done so yet, please open the INFRA request in Jira as Robert suggested (I don't see it in Jira). You should also vote on INFRA-443 that I just updated with the same request: http://issues.apache.org/jira/browse/INFRA-443 Martin - 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: David Crossley wrote: Hooray, i fixed it. We were using a 1.5-dev version of Velocity. Now back to the 1.4 release version. Whoa. The problem was velocity 1.5? I just needed to move forward and the 1.4 -based setup worked, so i used it and dumped your -dev version. Note that all i did was to synchronise our Anakia with that of infrastructure/site svn. Actually it might be jdom. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
On Sun, Feb 05, 2006 at 11:32:59PM +0100, David N. Welton wrote: *) iCLA's - the OFBiz guys are working on it. This needs to happen before they get accounts, and conversely, they get accounts once this happens, right? if the right emails are sent as documented on /dev/, yup. Which /dev/ are you referring to? http://www.apache.org/dev/, sorry. *) JIRA - they have a JIRA instance of their own, which should be migrated to the ASF. I don't know anything about admin'ing JIRA, so I believe this step will require collaboration between David Jones and someone on the infrastructure team. Should I/we go ahead and open an issue on our side for JIRA migration? Does this step have dependencies, or can it start to happen when people are ready to do the work? Yes, go ahead. I think this is quite a tricky thing to do. Jeff Turner is the guy from the infra team to talk to. Ok. So, if David Jones is reading this, that would be jefft followed by apache.org, right? Think so. Make sure to use the mailing lists :-) If anyone else on the OFBiz team wants to have a crack at it, it's attached to this email (I'm not sure you can access the incubator repo anonymously?). Yep. As open as possible: http://svn.apache.org/repos/asf/incubator/public/trunk/ http://incubator.apache.org/howtoparticipate.html#Project+Website+Howto http://incubator.apache.org/guides/website.html cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] incubate OpenEJB as sub-projects of Geronimo
On Feb 4, 2006, at 9:42 PM, Niclas Hedhman wrote: On Friday 03 February 2006 03:50, David Blevins wrote: OpenEJB has been proposed as a subproject of Geronimo. See the proposal here: I think this is a good idea. However, I would like to hear why OpenEJB was not part of Geronimo's incubation?? After all, it was one of the cornerstones to get Geronimo off the ground, wasn't it... Nothing mysterious really. At the time the team overlap was only two people (myself and RMH) and it was actually *during* incubation that the teams started coming together. Now, I can't even keep track of all the people who wear both OpenEJB and Geronimo hats. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
