http://people.apache.org/
Hi folks, Last night, I navigated my way through the process and added myself to http://people.apache.org/ My question is now, how do I create my folder so that http://people.apache.org/~aroush/ will show up? I want to set this up as a staging place for releases to be voted on which I see other folks are doing. Regards, -- George Aroush - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: http://people.apache.org/
On Feb 26, 2007, at 3:49 PM, George Aroush wrote: My question is now, how do I create my folder so that http://people.apache.org/~aroush/ will show up? Your personal web root corresponds to the /home/aroush/public_html/ folder. So you'd ssh to the box and put the files you want to be visible on the web in this folder. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: http://people.apache.org/
George Aroush wrote: Hi folks, Last night, I navigated my way through the process and added myself to http://people.apache.org/ My question is now, how do I create my folder so that http://people.apache.org/~aroush/ will show up? Create yourself a public_html directory in your home directory. Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BouncyCastle IDEA patent
David Jencks wrote: On Feb 21, 2007, at 12:38 PM, Jeremy Boynes wrote: On Feb 21, 2007, at 12:05 PM, Matt Hogstrom wrote: Regarding Bouncy Castle, IIRC they used to include the IDEA algorithm in their distribution and provided a one-off for Geronimo to use to bypass the patent issue. Not sure if that is an issue or not for Tuscany but just a heads up. IIUC && RC the resolution to this is that we copied the non-patent-related bouncycastle code into the geronimo-util module because bouncycastle declined to produce an unencumbered release. I'd suggest that if you don't need the patented code you use the geronimo-util jar instead. Yep, that's my recollection as well. thanks david jencks Bill Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA "patch available" column
Following up on Kelvin's remarks... I think this type of "patch available" column would be useful to many Apache projects. How would one go about requesting this type of update to the Apache JIRA system so that any Apache project could take advantage of it. Is this possible? Thanks, Kevin On 2/25/07, Henri Yandell <[EMAIL PROTECTED]> wrote: It should be pretty easy for us to add that to Tuscany. You don't have to recreate the Geronimo setup, we can just map the Patch Info custom field over to Tuscany too. It doesn't seem the end of the world - so I've gone ahead and done that. Let me know if it causes problems. Hen On 2/23/07, kelvin goodson <[EMAIL PROTECTED]> wrote: > Marshall, > thanks for that pointer. I've now got a little bit further, but not > quite far enough. So given that there are examples of people out there that > have got this right, I'd like to be able to mimic their solutions exactly. > It seems to me that the solution will require the addition of a custom > field. Considering where i have got so far, there is distinct possibility > of creating a half baked solution that we would want to alter in the future. > > So far I have set up a dummy server to play with, within my company's > firewall and added a custom field, but the data type of my custom "Patch > Available" field is "Multi Checkboxes", and I have only defined a single > checkbox element "Patch Available". I would have preferred a simple boolean > type, but that doesn't seem to be available in the set of types ( > http://www.atlassian.com/software/jira/docs/latest/customfields/overview.html > ). > > Also, it seems so far that I can only have this field altered by someone > with jira-developer access or greater after the jira has been created (a > jira-user seems to have authority to set the field value at origination). I > would like for jira-users to be able to set this flag on supplying a > patch, but perhaps that just doesn't fit the ACL model, so we may just > have to live with committers updating the jira on seeing an incoming patch. > > I don't want to alter our live JIRA system with a second rate solution, > since any improvements at a later stage would be likely to cause confusion > because there would have to be 2 differently named fields and users would > have to apply two separate filters in order to search for such jiras. > > If you have any ideas that would be really helpful, thanks. > > -- > Kelvin > > On 23/02/07, Marshall Schor <[EMAIL PROTECTED]> wrote: > > > > > > http://www.atlassian.com/software/jira/docs/v3.7.2/navigatorviews.html?clicked=jirahelp > > > > scroll down to "Customizing your Issue Navigator columns" > > > > -Marshall Schor > > > > kelvin goodson wrote: > > > I'd really like to update the Tuscany JIRA environment to have a "patch > > > available" column (similar to Geronimo's here -- > > > > > http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10220&status=1 > > ) > > > > > > but have no idea how to do it. > > > Can anyone point to me some infor please? > > > > > > Regards, Kelvin. > > > > > > > > > - > > 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: JIRA "patch available" column
Adding it to an individual project is easy enough - unless it's not in the central JIRA (in which case it would need to be copied over into that other JIRA by hand). Applying it globally to all of the projects is likely to elicit grumbles of "we don't want that" or "here's how it should be done" etc; but we could try and see if people feel strongly about wanting it globally. Hen On 2/26/07, Kevin Sutter <[EMAIL PROTECTED]> wrote: Following up on Kelvin's remarks... I think this type of "patch available" column would be useful to many Apache projects. How would one go about requesting this type of update to the Apache JIRA system so that any Apache project could take advantage of it. Is this possible? Thanks, Kevin On 2/25/07, Henri Yandell <[EMAIL PROTECTED]> wrote: > > It should be pretty easy for us to add that to Tuscany. You don't have > to recreate the Geronimo setup, we can just map the Patch Info custom > field over to Tuscany too. It doesn't seem the end of the world - so > I've gone ahead and done that. > > Let me know if it causes problems. > > Hen > > On 2/23/07, kelvin goodson <[EMAIL PROTECTED]> wrote: > > Marshall, > > thanks for that pointer. I've now got a little bit further, but not > > quite far enough. So given that there are examples of people out there > that > > have got this right, I'd like to be able to mimic their solutions > exactly. > > It seems to me that the solution will require the addition of a custom > > field. Considering where i have got so far, there is distinct > possibility > > of creating a half baked solution that we would want to alter in the > future. > > > > So far I have set up a dummy server to play with, within my company's > > firewall and added a custom field, but the data type of my custom > "Patch > > Available" field is "Multi Checkboxes", and I have only defined a > single > > checkbox element "Patch Available". I would have preferred a simple > boolean > > type, but that doesn't seem to be available in the set of types ( > > > http://www.atlassian.com/software/jira/docs/latest/customfields/overview.html > > ). > > > > Also, it seems so far that I can only have this field altered by someone > > with jira-developer access or greater after the jira has been created (a > > jira-user seems to have authority to set the field value at > origination). I > > would like for jira-users to be able to set this flag on supplying a > > patch, but perhaps that just doesn't fit the ACL model, so we may just > > have to live with committers updating the jira on seeing an incoming > patch. > > > > I don't want to alter our live JIRA system with a second rate solution, > > since any improvements at a later stage would be likely to cause > confusion > > because there would have to be 2 differently named fields and users > would > > have to apply two separate filters in order to search for such jiras. > > > > If you have any ideas that would be really helpful, thanks. > > > > -- > > Kelvin > > > > On 23/02/07, Marshall Schor <[EMAIL PROTECTED]> wrote: > > > > > > > > > > http://www.atlassian.com/software/jira/docs/v3.7.2/navigatorviews.html?clicked=jirahelp > > > > > > scroll down to "Customizing your Issue Navigator columns" > > > > > > -Marshall Schor > > > > > > kelvin goodson wrote: > > > > I'd really like to update the Tuscany JIRA environment to have a > "patch > > > > available" column (similar to Geronimo's here -- > > > > > > > > http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10220&status=1 > > > ) > > > > > > > > but have no idea how to do it. > > > > Can anyone point to me some infor please? > > > > > > > > Regards, Kelvin. > > > > > > > > > > > > > - > > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BouncyCastle IDEA patent
Good to know. - James Bill Stoddard wrote: > David Jencks wrote: >> >> On Feb 21, 2007, at 12:38 PM, Jeremy Boynes wrote: >> >>> On Feb 21, 2007, at 12:05 PM, Matt Hogstrom wrote: >>> Regarding Bouncy Castle, IIRC they used to include the IDEA algorithm in their distribution and provided a one-off for Geronimo to use to bypass the patent issue. Not sure if that is an issue or not for Tuscany but just a heads up. >> >> IIUC && RC the resolution to this is that we copied the >> non-patent-related bouncycastle code into the geronimo-util module >> because bouncycastle declined to produce an unencumbered release. I'd >> suggest that if you don't need the patented code you use the >> geronimo-util jar instead. >> > Yep, that's my recollection as well. > >> thanks >> david jencks > > Bill > > Bill > > > - > 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]
[IP CLEARANCE] PostScript DSC parser for XML Graphics Commons
I've added a new IP clearance document: https://svn.apache.org/viewvc/incubator/public/trunk/site-publish/ip-clearance/xmlgraphics-commons-postscript-dsc-parser.html?view=co (SVN URL for the lack of karma to update the incubator website.) Incubator PMC, please review and get back to me if something's wrong. Thanks, Jeremias Maerki for the XML Graphics PMC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] PostScript DSC parser for XML Graphics Commons
Jeremias Maerki wrote: > I've added a new IP clearance document: > https://svn.apache.org/viewvc/incubator/public/trunk/site-publish/ip-clearance/xmlgraphics-commons-postscript-dsc-parser.html?view=co > (SVN URL for the lack of karma to update the incubator website.) I did an 'svn up' on people.a.o -- changes should be visible after the next web site sync. -jean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ratify Tuscany vote to release build dependencies
On 25/02/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote: On Sunday 25 February 2007 22:34, Jeremy Boynes wrote: > The vote below was held in the Tuscany podling to release two > artifacts that are used by other modules during the build process; > they are a podling-wide parent pom and configuration data for code > checking. > > There are four +1's from the PPMC but no binding votes and we would > like to ask the IPMC to approve the release. Can someone explain to me why http://ws.apache.org/ lists Tuscany as a su-project of WS, as well as the mailling lists are @ws.apache.org, yet the project is not graduated??? When I responded to the "veto" on the codedump, I got the impression (this is serious) that Tuscany had graduated, hence not really an Incubator issue anymore... Is it only me that feels that something is not "standard" around here?? And it goes for a couple of others as well; Woden, TSIK & Synapse. IMHO, the WS site should list Tuscany & Woden as sponsored podlings and not subprojects. Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ratify Tuscany vote to release build dependencies
On 26/02/07, Jeremy Hughes <[EMAIL PROTECTED]> wrote: > And it goes for a couple of others as well; Woden, TSIK & Synapse. IMHO, the WS site should list Tuscany & Woden as sponsored podlings and not subprojects. I was too slow, incubation notice now on the WS site. Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Ratify Tuscany vote to release build dependencies
Resending as a [VOTE] thread as this one seems to be rambling ... -- Forwarded message -- From: Jeremy Boynes <[EMAIL PROTECTED]> Date: Feb 25, 2007 6:34 AM Subject: Ratify Tuscany vote to release build dependencies To: general@incubator.apache.org The vote below was held in the Tuscany podling to release two artifacts that are used by other modules during the build process; they are a podling-wide parent pom and configuration data for code checking. There are four +1's from the PPMC but no binding votes and we would like to ask the IPMC to approve the release. -- Jeremy Begin forwarded message: From: Jeremy Boynes <[EMAIL PROTECTED]> Date: February 25, 2007 6:14:15 AM PST To: tuscany-dev@ws.apache.org Subject: [RESULT] Release updated parent pom and buildtools Reply-To: tuscany-dev@ws.apache.org Passed with +1's from jboynes, jmarino, isilval, rineholt and no -1's I'll ask the IPMC to ratify this. -- Jeremy On Feb 21, 2007, at 6:34 PM, Jeremy Boynes wrote: The parent pom and buildtools were recently updated and as these are used by all other modules I think we should formally release them. These are distributed through the maven repo rather than as a end-user distribution. Please vote to approve the release content: parent-pom [tag]https://svn.apache.org/repos/asf/incubator/tuscany/tags/ java/pom/parent/2 [binary] http://people.apache.org/repo/m2-incubating-repository/ org/apache/tuscany/parent/2-incubating/ [rat]http://people.apache.org/~jboynes/rat/parent-2.rat buildtools [tag]https://svn.apache.org/repos/asf/incubator/tuscany/tags/ java/buildtools/2 [binary] http://people.apache.org/repo/m2-incubating-repository/ org/apache/tuscany/buildtools/2-incubating/ [rat]http://people.apache.org/~jboynes/rat/buildtools-2.rat Here's my +1 Given the recent discussion on [EMAIL PROTECTED] about crypto issues around Bouncy Castle, I would point out that these artifacts are not impacted by the export issue. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP CLEARANCE] IBM contribution of Network Server system tests to Apache Derby
IBM has contributed system tests to Apache Derby: - The ASF secretary recorded the software grant in cclas.txt. - The code was uploaded to Jira issue DERBY-2248. [1] - The ip clearance form was added to the Incubator site. [2] - The Derby vote to accept the contribution passed. [3] If there are any problems/concerns, please let me know. regards, -jean [1] https://issues.apache.org/jira/browse/DERBY-2248 [2] http://incubator.apache.org/ip-clearance/derby-2248-contribution-tests-ibm.html [3] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200702.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
