Re: [VOTE] OFBiz Test Snapshot Release: 4.0.0 TS5
If I'm not mistaken, we should be just about ready to graduate OFBiz. It's doing very nicely, and the comunity continues to grow. -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
On 11/2/06, Xavier Hanin [EMAIL PROTECTED] wrote: How can I know that the paperwork is ok? I've already sent my ICLA and the software grant, but I don't know if they were properly received and processed. One of your mentors should be able to watch the files in the private repos where those get recorded. It sometimes takes the ASF secretary a few days to get around to processing them, but if they don't get recorded fairly soon it's often a good idea to resend. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
On 11/2/06, Garrett Rooney [EMAIL PROTECTED] wrote: On 11/2/06, Xavier Hanin [EMAIL PROTECTED] wrote: How can I know that the paperwork is ok? I've already sent my ICLA and the software grant, but I don't know if they were properly received and processed. One of your mentors should be able to watch the files in the private repos where those get recorded. It sometimes takes the ASF secretary a few days to get around to processing them, but if they don't get recorded fairly soon it's often a good idea to resend. Ok, thanks. I sent my ICLA last week and the software grant last tuesday, and Antoine told me he can't see them, so maybe I should resend them. I'll also try to send them by postal mail to be sure there's no problem with the fax. Xavier -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JiniProposal - BraintreeProposal
Based on all the emails in this thread (and also some negative reactions from the Jini Community)... it doesn't look like this name is going to stick. I'll start another (sigh) effort to come up with a workable name. In the meantime, Geir - does it make sense to have a vote, or wait on a new name? -Jim Jim Hurley wrote: Thanks, Noel. I'm not sure if the potential trademark conflicts are problems in this case -- it's always a matter of gauging risk, and it's not clear if they'd be a problem or not. I agree that we'd like to get going, and we can address the name issue again during incubation. thanks -Jim On Oct 25, 2006, at 3:44 PM, Noel J. Bergman wrote: In any event, let's get this thing going. *IF* the name has to change again, it can change again. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
Could it have been sent from 0557530080 on Oct 31 at '10:27' ?? If so, then yes, please resend. We rec'd an unreadable fax (very, very light) and the only thing clear was the header lines added by the sending FAX machine. On Nov 2, 2006, at 9:17 AM, Xavier Hanin wrote: On 11/2/06, Garrett Rooney [EMAIL PROTECTED] wrote: On 11/2/06, Xavier Hanin [EMAIL PROTECTED] wrote: How can I know that the paperwork is ok? I've already sent my ICLA and the software grant, but I don't know if they were properly received and processed. One of your mentors should be able to watch the files in the private repos where those get recorded. It sometimes takes the ASF secretary a few days to get around to processing them, but if they don't get recorded fairly soon it's often a good idea to resend. Ok, thanks. I sent my ICLA last week and the software grant last tuesday, and Antoine told me he can't see them, so maybe I should resend them. I'll also try to send them by postal mail to be sure there's no problem with the fax. Xavier -garrett - 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] Request to release TuscanyC++ M2
+1 from me Paul On 11/1/06, ant elder [EMAIL PROTECTED] wrote: A non-binding +1 from me. Any more IPMCers have time to check out and vote on this so we get the magic 3? ...ant On 10/24/06, Andrew Borley [EMAIL PROTECTED] wrote: We have held a vote on tuscany-dev@ws.apache.org to publish a new milestone release of the Tuscany C++ implementation. The vote email thread is available here: http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg09946.html In summary we have 5 +1 votes: 4 from committers and 1 non-binding, and no 0s or -1s. We would like to request approval from the Incubator PMC to release this version. people.apache.org still appears to be unavailable after the weekend changes, but when it's back the candidate distribution is available here: http://people.apache.org/~ajborley/cpp-1.0-incubator-M2-RC3a/ And RAT results for each distro are available here: http://people.apache.org/~ajborley/cpp-1.0-incubator-M2-RC3a/rat Many thanks Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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]
How to bring code to Apache?
One thing that came out of the board meeting was making sure that the community knew how to bring code into the ASF. What the scenarios are, and what the rules are. Looking around at the Incubator, it's well documented at http://incubator.apache.org/ip-clearance/, and I'd like to send a short email to committers@ pointing out the existence of that page and that even if code is written by Apache committers, if it's not developed at Apache then that page needs to be adhered to. Any thoughts on the below? - To: [EMAIL PROTECTED] Subject: Bringing code to Apache Hello ASF committers, At the recent board meeting the subject of whether the committers were all aware of how to handle bringing code to Apache and doing IP clearances. It was felt that a reminder would not be a bad idea (OK I admit it - I admitted to not being sure how it worked and stepped right into being a 'volunteer'). Here goes We're all aware of the Incubator. If we have a project out there that wants to join the ASF then we direct them to the general@incubator.apache.org mailing list and their community becomes an ASF community through a mentored education process. All good, but it doesn't cover large lumps of code that we want to bring into our projects in the ASF, into an already existing community. For these cases we have IP clearance. It applies regardless of whether the author of the code is an ASF committer or not an ASF committer - the important part is that the code was developed outside of the ASF SVN repository and the ASF public mailing lists. This takes the form of an xdoc xml template that needs to be filled out and checked into the Incubator SVN, please see this page for more details - http://incubator.apache.org/ip-clearance/. Thanks, and sorry for the noise if this was something you already knew. Henri Yandell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: incubator-info.txt?
I've committed a first version to: https://svn.apache.org/repos/private/committers/board/incubator-info.txt Hen On 11/1/06, Henri Yandell [EMAIL PROTECTED] wrote: (Forwarding from private@ where I asked it the first time and was told to ask here - and this time I'll use the correct email address so apologies if a dupe occurs from the previous forward) I'd like to add a bit to David Reid's marvin script so it notifies Incubating subprojects that their reports are due. To do this I'd like to emulate the committers/board/committee-info.txt file with an incubator-info.txt file. At first I thought I'd just do a cut-down version of the file, but I think the whole file is worth cloning. 1) List of projects and chairs. In Incubator's case we'd replace chairs with notification emails. Currently I have the private@ addresses there. 2) Reporting Schedule. I'd replicate this entirely using the wiki page for the data. 3) List of PPMCs. I don't think we have anywhere where the list of PPMC members is defined. I'm not sure whether it should live within the incubator svn tree, or in the same direcory as committee-info.txt (for ease of use). Any thoughts? Hen - 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: How to bring code to Apache?
Henri Yandell wrote: One thing that came out of the board meeting was making sure that the community knew how to bring code into the ASF. What the scenarios are, and what the rules are. Looking around at the Incubator, it's well documented at http://incubator.apache.org/ip-clearance/, and I'd like to send a short email to committers@ pointing out the existence of that page and that even if code is written by Apache committers, if it's not developed at Apache then that page needs to be adhered to. Any thoughts on the below? On the ip-clearance page under the Additional Notes section, it says how to handle a contribution by multiple parties instead of by a single entity. Two options are listed and both involve the multiple parties signing a software grant. For Cayenne, we understood the project should just obtain iCLAs from all past contributors (which Cayenne did, and they reimplemented any pieces by contributors whom could not be found). I seem to recall there was another podling this year that was handled similarly. Can that be listed as a valid third option? -jean - To: [EMAIL PROTECTED] Subject: Bringing code to Apache Hello ASF committers, At the recent board meeting the subject of whether the committers were all aware of how to handle bringing code to Apache and doing IP clearances. It was felt that a reminder would not be a bad idea (OK I admit it - I admitted to not being sure how it worked and stepped right into being a 'volunteer'). Here goes We're all aware of the Incubator. If we have a project out there that wants to join the ASF then we direct them to the general@incubator.apache.org mailing list and their community becomes an ASF community through a mentored education process. All good, but it doesn't cover large lumps of code that we want to bring into our projects in the ASF, into an already existing community. For these cases we have IP clearance. It applies regardless of whether the author of the code is an ASF committer or not an ASF committer - the important part is that the code was developed outside of the ASF SVN repository and the ASF public mailing lists. This takes the form of an xdoc xml template that needs to be filled out and checked into the Incubator SVN, please see this page for more details - http://incubator.apache.org/ip-clearance/. Thanks, and sorry for the noise if this was something you already knew. Henri Yandell - 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]
