Re: [QUESTION] Oracle JDBC Driver as a test dependency
Hi! I'd say the situation has changed a bit, as those jars are available at central since version 19.3, IIRC ([#1]). They are published under Oracle Free Use Term and Conditions (FUCT) license ([#2]), so I'd check again with legal to see if this license is allowed or not. HTH, juan pablo [#1] https://search.maven.org/search?q=g:com.oracle.database.jdbc [#2] https://www.oracle.com/downloads/licenses/oracle-free-license.html El mié, 10 ene 2024, 16:23, Alex Porcelli escribió: > In KIE podling we have reference for the Oracle JDBC driver being used > only for tests [1], however based on this ticket [2], it's not clear > if we can continue to use it or this dependency has to be removed. > > Guidance on this topic would be highly appreciated! > > Regards, > Alex > > [1] > https://github.com/apache/incubator-kie-kogito-runtimes/blob/3aa26113d7e88f0fd7d0331ec20fe392f343afb6/kogito-test-utils/pom.xml#L89-L99 > [2] https://issues.apache.org/jira/browse/LEGAL-526 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: eliminating MD5 and SHA1 signatures
Hi, somewhat related to the question, and just in case anyone is interested, maven can be configured to generate the .asc and .sha512 files for all the build artifacts. At JSPWiki, we overwrite the checksum maven plugin configuration from the ASF parent pom to do this [#1]. When copying the release artifacts to dist.a.o we also copy these files over too, f.ex any subdirectory under [#2]. This makes [#3] a piece of cake :-) best regards, juan pablo [#1]: https://github.com/apache/jspwiki/blob/master/pom.xml#L610-L626 [#2]: https://dist.apache.org/repos/dist/release/jspwiki [#3]: https://www.apache.org/dev/release-distribution#sigs-and-sums On Thu, Jan 23, 2020 at 9:19 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Fri, Jan 17, 2020 at 9:51 PM leerho wrote: > > ...either the Maven deploy plugin or the repository always adds > > MD5 and SHA1 signatures as well... > > FWIW, we'd like to stop using MD5 but I don't think we're there yet, > the following URLs have more info: > > http://www.apache.org/dev/release-distribution > https://issues.apache.org/jira/browse/INFRA-14923 > https://issues.sonatype.org/browse/NEXUS-21802 > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Cava] Suitable name search - choosing a name
another suggestion from the back of the peanut gallery: Apache InBlock, so phonetically there's block and chain (and Apache :o)) best regards, juan pablo El jue., 21 mar. 2019 8:04, Antoine Toulme escribió: > I’m not sure about avac, doesn’t roll off the tongue. > > On the theme of “no one”, I found Tuweni (from > https://www.lakotadictionary.org/phpBB3/nldo.php < > https://www.lakotadictionary.org/phpBB3/nldo.php>). > > Would that work? > > > On Mar 20, 2019, at 12:02 PM, larry mccay wrote: > > > > Apache Avac ??? > > > > > > On Wed, Mar 20, 2019 at 7:57 PM Antoine Toulme > wrote: > > > >> There exists an outis open source project. > >> > >> Maybe we can riff on this name though. > >> > >>> On Mar 20, 2019, at 11:39, Kenneth Knowles wrote: > >>> > >>> Indeed, http://nemo.apache.org/ > >>> > >>> So I looked for similar ideas and came to Outis [2] via [1]. > >>> > >>> Kenn > >>> > >>> [1] https://en.wikipedia.org/wiki/Captain_Nemo#Etymology > >>> [2] https://en.wikipedia.org/wiki/Outis > >>> > >>> On Wed, Mar 20, 2019 at 11:27 AM Anu Engineer < > aengin...@hortonworks.com > >>> > >>> wrote: > >>> > At this point you should call it “Apache Nemo” or literally Apache No > >> One > (, to indicate we have no affiliations or does not violate any > >> trademarks > or claims. > --Anu > > Just kidding, eventually I am sure you will find a good name, -- that > no > one else has thought off. > > > On 3/20/19, 10:51 AM, "Antoine Toulme" wrote: > > Deep sigh. > > OK. > > > On Mar 20, 2019, at 9:15 AM, Michael Wall wrote: > > > > I did find this, https://github.com/RainBlock. Looks like code > around > > ethereum. Maybe too close? > > > > On Wed, Mar 20, 2019 at 11:59 AM Antoine Toulme > > wrote: > > > >> Yes, you’ve been very flexible, thank you. > >> > >> Anybody with strong opinions, please chime in. > >> > >> I’ll start looking for marks around rainblock. > >> > >>> On Mar 20, 2019, at 5:15 AM, Jim Jagielski > wrote: > >>> > >>> Personally, I'm fine w/ anything... > >>> > On Mar 19, 2019, at 6:53 PM, Antoine Toulme > >> wrote: > > I think we will need a made up name, and we likely need a name > that is > >> rather unambiguous across languages. > > Based on our previous proposals, would you be ok with “RainBlock”? > > > > On Mar 19, 2019, at 11:40 AM, Jim Jagielski > wrote: > > > > Apache PawPaw > > > >> On Mar 19, 2019, at 9:58 AM, Michael Wall > wrote: > >> > >> Since Cava is the Guava for blockchains, what about sticking > with the > >> fruit/veggie theme? > >> > >> Jackfruit > >> Jambolan > >> Jocote > >> Kumquat > >> KangKong > >> Kabosu > >> > >> I also saw the word postcava which is the "the inferior vena > cava of > >> vertebrates higher than fishes" according to > >> https://www.merriam-webster.com/dictionary/postcava. But is > seemed > >> like a > >> name you could use after Cava. > >> > >> Just brainstorming. > >> > >> Mike > >> > >> > >> > >> On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski > >> wrote: > >> > >>> What is somewhat funny is that the "SkyWalking" podling is on > the > >> cusp of > >>> graduation. :) > >>> > On Mar 19, 2019, at 1:42 AM, Antoine Toulme < > anto...@toulme.name> > >> wrote: > > All, the results are in, from VP Legal: > > I am happy to approve the name in isolation. Specifically, > the > >>> community must refrain from linking the project to any Star > Wars > >>> references. The view of the community is that the community is > >> likely to > >>> find that difficult. It was therefore agreed to look for a > different > >> name. > > We need to pick another name. > > > On Mar 4, 2019, at 2:32 PM, Dave Fisher < > dave2w...@comcast.net> > >> wrote: > > > > Hi - > > > >> On Mar 4, 2019, at 2:10 PM, Antoine Toulme < > anto...@toulme.name> > >>> wrote: > >> > >> > >> > >>> On Mar 4, 2019, at 2:00 PM, Dave Fisher < > dave2w...@comcast.net> > >>> wrote: > >>> > >>> Hi - > >>> > >>> I went to look at the Trademark name search and something > is > >> either > >>> messed up or autocorrected. > >>> > >>> PODLINGNAMESEARCH-165 < > >>>
[RESULT] [VOTE] recommend Apache JSPWiki for graduating out of the incubator
Hi, it's been 72 hours and the vote tally is: * Alan D. Cabrera * Ant Elder * Bertrand Delacretaz * Christian Grobmeier * Dave Fisher * Olivier Lamy all of them binding, so the vote passes :-) I'll make the submission of the resolutionto the Board tomorrow thanks all + br, juan pablo On Mon, Jul 8, 2013 at 1:44 PM, Bertrand Delacretaz bdelacre...@apache.orgwrote: On Sun, Jul 7, 2013 at 12:33 AM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: ...I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board Enthusiastic +1, congrats to the JSPWiki team for hanging in there! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] recommend Apache JSPWiki for graduating out of the incubator
shame on me, that adds: * Craig L Russell * Sam Ruby * Siegfried Goeschl to the tally, being 9 +1 binding votes. (as http://incubator.apache.org/guides/graduation.html treats community and IPMC votes as different things I treated both threads independently) thanks for pointing that out br, juan pablo On Wed, Jul 10, 2013 at 1:09 AM, Craig L Russell craig.russ...@oracle.comwrote: .. plus the binding votes from your mentors on the project mailing list... ;-) Craig On Jul 9, 2013, at 3:32 PM, Juan Pablo Santos Rodríguez wrote: Hi, it's been 72 hours and the vote tally is: * Alan D. Cabrera * Ant Elder * Bertrand Delacretaz * Christian Grobmeier * Dave Fisher * Olivier Lamy all of them binding, so the vote passes :-) I'll make the submission of the resolutionto the Board tomorrow thanks all + br, juan pablo On Mon, Jul 8, 2013 at 1:44 PM, Bertrand Delacretaz bdelacre...@apache.orgwrote: On Sun, Jul 7, 2013 at 12:33 AM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: ...I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board Enthusiastic +1, congrats to the JSPWiki team for hanging in there! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
oh, thought it was enough to link the thread vote, thanks for looking into it br, juan pablo On Sun, Jul 7, 2013 at 1:06 AM, Joe Brockmeier j...@zonker.net wrote: On Sat, Jul 6, 2013, at 05:50 PM, Joe Brockmeier wrote: Hi Juan Pablo, I think you meant to link here: Argh, hit send too soon: http://s.apache.org/uM That's the VOTE RESULT. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
community graduation vote at jspwiki-dev
Hi all, a quick email to inform that we've just started the community graduation vote at jspwiki-dev :-) br, juan pablo
Re: [ANNOUNCE] Apache JSPWiki 2.9.1-incubating released
Hi, as Ant notes below, we're discussing graduation at jspwiki-private. Anyone willing to express his opinion about it is invited to do so on that list. br, juan pablo On Fri, May 17, 2013 at 8:18 AM, ant elder ant.el...@gmail.com wrote: On Fri, May 17, 2013 at 5:46 AM, Martin Cooper mart...@apache.org wrote: I'll be the first to admit that I haven't been following along with the progress of this project at all, but I happened to notice that, according to the incubator projects page, this project has been in incubation for almost 6 years. That's an awfully long time in the incubator. What are the prospects of JSPWiki ever making it out of incubation? The prospects are good, its happening right now. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache JSPWiki 2.9.1-incubating released
The Apache JSPWiki team is pleased to announce the release of JSPWiki 2.9.1-incubating from the Apache Incubator. This is the second release of Apache JSPWiki, a feature-rich and extensible WikiWiki engine built around the standard J2EE components. The release is available here: http://www.apache.org/dyn/closer.cgi/incubator/jspwiki/ The full change log is available here: https://issues.apache.org/jira/browse/jspwiki/fixforversion/12321249 We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://incubator.apache.org/jspwiki/ The Apache JSPWiki Team
[VOTE][RESULT] Release JSPWiki version 2.9.1-incubating (2nd RC)
Hi all, I'd now like to summarize the vote, which happened entirely on the jspwiki-dev@i.a.o mailinglist: +1 binding from Ant Elder (IPMC) +1 binding from Siegried Goeschl (mentor) +1 binding from Craig L Russell (mentor) +1 non-binding Harry Metske (PPMC) +1 non-binding Glen Mazza (PPMC) +1 non-binding Dirk Frederickx (PPMC) +1 non-binding Andrew Jaquith (PPMC) +1 non-binding Juan Pablo Santos (PPMC) Since the votes are all positive, we will now proceed with releasing 2.9.1-rc2 as 2.9.1-incubating thanks for all the votes + br, juan pablo
Re: [VOTE] Release JSPWiki version 2.9.1-incubating (2nd RC)
Hi all, the current tally, right now, is: +1 binding from Ant Elder (IPMC) +1 binding from Siegfried Goeschl (Mentor) +5 non binding from PPMC (all votes casted on jspwiki-dev@i.a.o) We still need one more +1 binding vote to be able to release, so we'd be most grateful if someone could take a look at it. thx in advance! br, juan pablo On Thu, May 9, 2013 at 8:29 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi Ant, thanks for the vote :-) Regarding the NOTICE file, specifically which comments? Right now has 4 entries, being the reasons behind each one: - fckconfig.js entry: published under MPL 2.0, so it requires to be in NOTICE - Portions of this code donated by BaseN Corporation. entry: legal's advice [#1] was to keep this entry in NOTICE - SilkIconSet entry: published under Creative Commons Attribution 2.5 License, which in section 4.b states If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or any Derivative Works or Collective Works, You must keep intact all copyright notices [...] - Slimbox: published under MIT license so shouldn't be there, as pointed in [#2]. However, as it's been modified, I thought of it as a derivative work and, it fell under section 4.d of the AL You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. Please note that I'm not saying they *should* be there, only why they are there. If there's anything wrong on that file we'll correct it ASAP (btw, a handy way to check if other projects are including specifics entries in NOTICE files for 3rd party libraries is to search for an specific dependency at [#4] and then checking the svn's NOTICE file of the projects using it) Regarding the missing DISCLAIMER, our distribution target didn't catch it. It's already fixed on trunk, although our plan is release 2.9.1 in order to start graduation discuss soon thereafter. @general: aside from Ant's vote, we've got another couple of votes at jspwiki-dev, so the tally right now is 5PPMC +1 votes, 1 +1 IPMC vote br, juan pablo [#1]: http://s.apache.org/7Hs [#2]: http://www.apache.org/dev/licensing-howto.html#permissive-deps [#3]: http://www.apache.org/licenses/LICENSE-2.0.html#redistribution [#4]: https://analysis.apache.org/dependencies/index On Thu, May 9, 2013 at 10:15 AM, ant elder ant.el...@gmail.com wrote: Hi JSPWiki, I'm from the Incubator PMC and looking at your release. I give it a +1. There are a couple of nits. One is that it looks like the Incubation DISCLAIMER text is missing from the binary zip. It is there in the source artifact and tag though and we've let releases go with these missing before so i don't think this is a blocker, fix it next time, or better, graduate from the Incubator now so its not needed next time. The NOTICE file still has some comments that probably aren't needed there and they could be moved somewhere else like the README. Again many Incubator releases have similar issues so i don't think that should be a blocker and i can help you get that updated for the next release. ...ant On Tue, May 7, 2013 at 10:16 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi all, We've held a vote on jspwiki-dev for a 2nd RC of Apache JSPWiki 2.9.1-incubating [#1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have 3 non-binding votes (from jspwiki developers). I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [#2]. Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo [#1] http://s.apache.org/UDD [#2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc2 Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-4-rc2/ Checksums: JSPWiki-2.9.1-incubating-4-bin.zip MD5:58b7e2fd9290612762825683e81ca22d SHA1: 5eb4cfa7c7b00e2a002573c72f1e83c15f708e2b SHA512: 0e1487d09044e0ce900194b42ff3e465ee96ebde1a75c0603715ec42bbf425b950c901bff87bbadf43173d3c91ced170ab0eebe4525706344642e68db069ba18 JSPWiki-2.9.1-incubating-4-src.zip MD5:707b52ce9ca32fe012bcc3b1a79d8f96 SHA1: 41619359a04d49a2f5b58b8ba1a5d0c186fbbb1c SHA512
Re: [VOTE] Release JSPWiki version 2.9.1-incubating (2nd RC)
Hi Ant, thanks for the vote :-) Regarding the NOTICE file, specifically which comments? Right now has 4 entries, being the reasons behind each one: - fckconfig.js entry: published under MPL 2.0, so it requires to be in NOTICE - Portions of this code donated by BaseN Corporation. entry: legal's advice [#1] was to keep this entry in NOTICE - SilkIconSet entry: published under Creative Commons Attribution 2.5 License, which in section 4.b states If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or any Derivative Works or Collective Works, You must keep intact all copyright notices [...] - Slimbox: published under MIT license so shouldn't be there, as pointed in [#2]. However, as it's been modified, I thought of it as a derivative work and, it fell under section 4.d of the AL You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. Please note that I'm not saying they *should* be there, only why they are there. If there's anything wrong on that file we'll correct it ASAP (btw, a handy way to check if other projects are including specifics entries in NOTICE files for 3rd party libraries is to search for an specific dependency at [#4] and then checking the svn's NOTICE file of the projects using it) Regarding the missing DISCLAIMER, our distribution target didn't catch it. It's already fixed on trunk, although our plan is release 2.9.1 in order to start graduation discuss soon thereafter. @general: aside from Ant's vote, we've got another couple of votes at jspwiki-dev, so the tally right now is 5PPMC +1 votes, 1 +1 IPMC vote br, juan pablo [#1]: http://s.apache.org/7Hs [#2]: http://www.apache.org/dev/licensing-howto.html#permissive-deps [#3]: http://www.apache.org/licenses/LICENSE-2.0.html#redistribution [#4]: https://analysis.apache.org/dependencies/index On Thu, May 9, 2013 at 10:15 AM, ant elder ant.el...@gmail.com wrote: Hi JSPWiki, I'm from the Incubator PMC and looking at your release. I give it a +1. There are a couple of nits. One is that it looks like the Incubation DISCLAIMER text is missing from the binary zip. It is there in the source artifact and tag though and we've let releases go with these missing before so i don't think this is a blocker, fix it next time, or better, graduate from the Incubator now so its not needed next time. The NOTICE file still has some comments that probably aren't needed there and they could be moved somewhere else like the README. Again many Incubator releases have similar issues so i don't think that should be a blocker and i can help you get that updated for the next release. ...ant On Tue, May 7, 2013 at 10:16 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi all, We've held a vote on jspwiki-dev for a 2nd RC of Apache JSPWiki 2.9.1-incubating [#1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have 3 non-binding votes (from jspwiki developers). I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [#2]. Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo [#1] http://s.apache.org/UDD [#2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc2 Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-4-rc2/ Checksums: JSPWiki-2.9.1-incubating-4-bin.zip MD5:58b7e2fd9290612762825683e81ca22d SHA1: 5eb4cfa7c7b00e2a002573c72f1e83c15f708e2b SHA512: 0e1487d09044e0ce900194b42ff3e465ee96ebde1a75c0603715ec42bbf425b950c901bff87bbadf43173d3c91ced170ab0eebe4525706344642e68db069ba18 JSPWiki-2.9.1-incubating-4-src.zip MD5:707b52ce9ca32fe012bcc3b1a79d8f96 SHA1: 41619359a04d49a2f5b58b8ba1a5d0c186fbbb1c SHA512: 2c4f6e0b9e163d2b3ae60a091993598ed6e315a7f7b4c08a9232cbd0c1eccba4259818e0e9ab8a86350a0109924be21cc0627e8a549bbd52b14ca7b40dcccee0 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS [ ] +1 Release this package as Apache JSPWiki 2.9.1-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because...
[VOTE] Release JSPWiki version 2.9.1-incubating (2nd RC)
Hi all, We've held a vote on jspwiki-dev for a 2nd RC of Apache JSPWiki 2.9.1-incubating [#1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have 3 non-binding votes (from jspwiki developers). I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [#2]. Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo [#1] http://s.apache.org/UDD [#2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc2 Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-4-rc2/ Checksums: JSPWiki-2.9.1-incubating-4-bin.zip MD5:58b7e2fd9290612762825683e81ca22d SHA1: 5eb4cfa7c7b00e2a002573c72f1e83c15f708e2b SHA512: 0e1487d09044e0ce900194b42ff3e465ee96ebde1a75c0603715ec42bbf425b950c901bff87bbadf43173d3c91ced170ab0eebe4525706344642e68db069ba18 JSPWiki-2.9.1-incubating-4-src.zip MD5:707b52ce9ca32fe012bcc3b1a79d8f96 SHA1: 41619359a04d49a2f5b58b8ba1a5d0c186fbbb1c SHA512: 2c4f6e0b9e163d2b3ae60a091993598ed6e315a7f7b4c08a9232cbd0c1eccba4259818e0e9ab8a86350a0109924be21cc0627e8a549bbd52b14ca7b40dcccee0 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS [ ] +1 Release this package as Apache JSPWiki 2.9.1-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because...
[VOTE][CANCEL] Release JSPWiki version 2.9.1-incubating
thanks for reminding Brane br, juan pablo On Wed, Apr 17, 2013 at 6:44 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi Marvin, Sebb, thanks for the insights :-) br, juan pablo On Wed, Apr 17, 2013 at 5:13 PM, Marvin Humphrey mar...@rectangular.comwrote: On Tue, Apr 16, 2013 at 2:24 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: - I'm especially worried about the NOTICE file, how short is short enough? Could you provide a good example from any other project so we can take a look at it? To take a grasp of how we should do it. We'd like to have it as good as the LICENSE file (also, the incorrect year in NOTICE was also pointed by Siegfried, but not as a blocker, so it's fixed in trunk). The ASF now has documentation which describes a formulaic approach to creating LICENSE and NOTICE. If you follow the recipe, you should be OK. http://www.apache.org/dev/licensing-howto.html Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release JSPWiki version 2.9.1-incubating
Hi Marvin, Sebb, thanks for the insights :-) br, juan pablo On Wed, Apr 17, 2013 at 5:13 PM, Marvin Humphrey mar...@rectangular.comwrote: On Tue, Apr 16, 2013 at 2:24 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: - I'm especially worried about the NOTICE file, how short is short enough? Could you provide a good example from any other project so we can take a look at it? To take a grasp of how we should do it. We'd like to have it as good as the LICENSE file (also, the incorrect year in NOTICE was also pointed by Siegfried, but not as a blocker, so it's fixed in trunk). The ASF now has documentation which describes a formulaic approach to creating LICENSE and NOTICE. If you follow the recipe, you should be OK. http://www.apache.org/dev/licensing-howto.html Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release JSPWiki version 2.9.1-incubating
Hi Sebb, first of all, thanks for your time reviewing the RC and your comments seems we'll have to cancel the vote. Hopefully, we'll have a new RC in a few days with all these issues fixed. Some notes, though: - I'm especially worried about the NOTICE file, how short is short enough? Could you provide a good example from any other project so we can take a look at it? To take a grasp of how we should do it. We'd like to have it as good as the LICENSE file (also, the incorrect year in NOTICE was also pointed by Siegfried, but not as a blocker, so it's fixed in trunk). - The signature files is big mistake on my side. Don't know how or what did I did when doing the scp of the binaries. It's.. awkward. - IDE specific files: right now our build tool is Ant so, in order to ease the initial hop in, we provide Eclipse specific files with the project configuration. We're working on moving to Maven, which will allow us to delete those files from svn. thanks best regards, juan pablo On Tue, Apr 16, 2013 at 9:54 PM, sebb seb...@gmail.com wrote: On 15 April 2013 22:56, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi all, We've held a vote on jspwiki-dev to release 2.9.1-incubating [1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have the following voting results: - 1 binding vote (from Siegfried Goeschl -mentor-) - 4 non-binding votes (from jspwiki developers) I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://s.apache.org/iy [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. However binaries should still have the correct NL files, and the DISCLAIMER (for Incubator podlings) The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc1 There's no DISCLAIMER file The NOTICE file has lots of extra content which is not relevant; the NOTICE file must be a short as possible, but no smaller. Like a good poem, it's finished when no more can be taken out. Note in particular that the NOTICE file must only contain required notices for bits that are actually included in the enclosing archive. The year in the NOTICE file looks wrong. IMO those must be fixed before a release can be signed off. The LICENSE file is very clear; it's great to have the full jar names with versions. Probably not a good idea to include the Eclipse .classpath and .project files in SVN as these files are host-specific. [Not a blocker] If you want to provide sample versions as a starting point, this can be done by providing copies with a different name and perhaps path. For example, Tomcat puts their versions here: http://svn.apache.org/repos/asf/tomcat/trunk/res/ide-support/eclipse/ Likewise, the .externalToolBuilders and .settings trees don't belong in SVN as they are IDE and host-specific. Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-0-rc1/ There are no signatures (.asc files). There's not much point in including SHA512 hashes as well as SHA1. Hashes are really only useful for checking whether the download succeeded; as such MD5 and SHA1 are sufficient Checksums: JSPWiki-2.9.1-incubating-bin.zip MD5:76bf79828fd709fc3dbf2c230dd546ff SHA1: bec05e47b21cdacaa171323d2fe7e28fa2a99574 SHA512: 13b8f33137287a32a04737b7d2dbe3d32651d527983d88f3c89ebe3db1e6428ece93a1d541d9a2224dbd2a12f8a0bf866952d0b65bd0fb90ccd25f668653a954 JSPWiki-2.9.1-incubating-src.zip MD5:daa25020abeed3762aa901fa6fd35f34 SHA1: 44075855d753335688e1ea89c8dbf6054d4d506d SHA512: ecf8e90a9088ca27d0e302fe81b80b996bcf89d24ec816f475055250b7cc6b0e0e8b1ed5a6499a90285b7f8c8485c3cacd1b7985df9fef44b22e01f0035e95b8 Thanks - it's useful to have at least one hash in the vote email as that helps tie the vote to the archives. JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS Except that there are no signature files... [ ] +1 Release this package as Apache Marmotta 3.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... IMO, there are several blockers that need to be fixed before release.
[VOTE] Release JSPWiki version 2.9.1-incubating
Hi all, We've held a vote on jspwiki-dev to release 2.9.1-incubating [1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have the following voting results: - 1 binding vote (from Siegfried Goeschl -mentor-) - 4 non-binding votes (from jspwiki developers) I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://s.apache.org/iy [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc1 Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-0-rc1/ Checksums: JSPWiki-2.9.1-incubating-bin.zip MD5:76bf79828fd709fc3dbf2c230dd546ff SHA1: bec05e47b21cdacaa171323d2fe7e28fa2a99574 SHA512: 13b8f33137287a32a04737b7d2dbe3d32651d527983d88f3c89ebe3db1e6428ece93a1d541d9a2224dbd2a12f8a0bf866952d0b65bd0fb90ccd25f668653a954 JSPWiki-2.9.1-incubating-src.zip MD5:daa25020abeed3762aa901fa6fd35f34 SHA1: 44075855d753335688e1ea89c8dbf6054d4d506d SHA512: ecf8e90a9088ca27d0e302fe81b80b996bcf89d24ec816f475055250b7cc6b0e0e8b1ed5a6499a90285b7f8c8485c3cacd1b7985df9fef44b22e01f0035e95b8 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS [ ] +1 Release this package as Apache Marmotta 3.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because...
Re: [VOTE] Release JSPWiki version 2.9.1-incubating
/s/Marmota 3.0.0/JSPWiki incubating/g/ O:-) (oops) On Mon, Apr 15, 2013 at 11:56 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi all, We've held a vote on jspwiki-dev to release 2.9.1-incubating [1]. The vote on release candidate has been open for more than 72 hours on the developer mailing list. After the voting timeframe, we have the following voting results: - 1 binding vote (from Siegfried Goeschl -mentor-) - 4 non-binding votes (from jspwiki developers) I'd therefore like to ask now the general incubator to check our release candidate. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://s.apache.org/iy [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12321249 Please find attached below the concrete details on the release and on the vote. thanks in advance, juan pablo === Note that we are voting upon the source (subversion tag and signed artifacts). Binaries are provided for convenience only. The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_1_incubating_rc1 Source and binary files, with RAT report: http://people.apache.org/~juanpablo/releases/2.9.1-incubating-0-rc1/ Checksums: JSPWiki-2.9.1-incubating-bin.zip MD5:76bf79828fd709fc3dbf2c230dd546ff SHA1: bec05e47b21cdacaa171323d2fe7e28fa2a99574 SHA512: 13b8f33137287a32a04737b7d2dbe3d32651d527983d88f3c89ebe3db1e6428ece93a1d541d9a2224dbd2a12f8a0bf866952d0b65bd0fb90ccd25f668653a954 JSPWiki-2.9.1-incubating-src.zip MD5:daa25020abeed3762aa901fa6fd35f34 SHA1: 44075855d753335688e1ea89c8dbf6054d4d506d SHA512: ecf8e90a9088ca27d0e302fe81b80b996bcf89d24ec816f475055250b7cc6b0e0e8b1ed5a6499a90285b7f8c8485c3cacd1b7985df9fef44b22e01f0035e95b8 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS [ ] +1 Release this package as Apache Marmotta 3.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because...
How to handle 3rd party extensions
Hi all, I'd like to ask a quick question to know how 3rd party extensions are handled in other Apache projects. (Historically,) In JSPWiki, all the custom plugins, filters, templates, etc, made by non committers has been uploaded to a wiki page at www.jspwiki.org. Each author uploaded his/her extension to his/her page, taking care of the content of that page, linking it to relevant pages, etc. Due to some legal reasons [#1], www.jspwiki.org is/has been in read-only mode for a while and the need of hosting somewhere new extensions is beginning to arise. We're considering opneing jira tickets under a extensions component, to be able to track all these extensions, but most probably it makes much more sense to give people commit access, per request, to a specific svn repo folder (something similar to the commit policy followed by Jenkins). We were wondering if this approach could be feasible under Apache's svn or if it makes more sense to host these extensions outside Apache infra (a google code or github account). What have other projects done on this situation? thanks br, juan pablo [#1]: https://issues.apache.org/jira/browse/JSPWIKI-739
Re: How to handle 3rd party extensions
Hi! thanks for both inputs :-) Seems that Apache Extras is what I was looking for br, juan pablo On Tue, Mar 12, 2013 at 11:36 PM, Luciano Resende luckbr1...@gmail.comwrote: On Tue, Mar 12, 2013 at 12:41 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi all, I'd like to ask a quick question to know how 3rd party extensions are handled in other Apache projects. (Historically,) In JSPWiki, all the custom plugins, filters, templates, etc, made by non committers has been uploaded to a wiki page at www.jspwiki.org. Each author uploaded his/her extension to his/her page, taking care of the content of that page, linking it to relevant pages, etc. Due to some legal reasons [#1], www.jspwiki.org is/has been in read-only mode for a while and the need of hosting somewhere new extensions is beginning to arise. We're considering opneing jira tickets under a extensions component, to be able to track all these extensions, but most probably it makes much more sense to give people commit access, per request, to a specific svn repo folder (something similar to the commit policy followed by Jenkins). We were wondering if this approach could be feasible under Apache's svn or if it makes more sense to host these extensions outside Apache infra (a google code or github account). What have other projects done on this situation? thanks br, juan pablo [#1]: https://issues.apache.org/jira/browse/JSPWIKI-739 Assuming the new templates are Apache Licensed, you might have few options : - Contributors can submit/update artifacts via JIRA and a committer would update to the proper location - After submitting a CLA, a contributor is granted write access to 3rd party artifact area and can submit/update his Apache Licensed artifacts - Based on the type of contribution, evaluate the contributor and possible make him a committer, then problem solved... For non Apache Licensed artifacts, you might consider Apache Extras, but you probably wil only have a link saying something like For other non Apache Licensed artifacts, see... and point to apache extras. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Markdown issue
Hi, @Ioan: that was exactly what I was trying to avoid, it feels a bit cumbersome to type the whole link instead something like [text][1](.whatevercssclass) or similar @Shane: yep, had checked also that link, unfortunately, Special attribute blocks can be used only with headers fenced code blocks. and I was looking to arbitrarily style a given link (btw, the preview pane doesn't like fenced blocks, or is it just me?) seems I'll stick with inline html, I was puzzled to see that it doesn't seem to be an easy way to put custom styles via markdown :-? anyway, thanks for the insights br, juan pablo On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org wrote: See if this helps: http://michelf.ca/projects/**php-markdown/extra/#spe-attrhttp://michelf.ca/projects/php-markdown/extra/#spe-attr Which is linked from: http://www.apache.org/dev/**cmsref.html#markdownhttp://www.apache.org/dev/cmsref.html#markdown - Shane On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote: Hi all, probably is a dumb issue and I'm missing something obvious, but so far, I haven't been able to solve it: Is there an easy way to tell a markdown link to use a specific css class? I'd like to render links pointing outside the incubator site with an external css class. I know I can write the html equivalent, but that feels unnatural, so I'd better avoid that option. I've been poking at a few site's sources, but haven't had any luck yet.. thx in advance! br, juan pablo --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org
Re: Markdown issue
Hi!
@Manos: that's great! didn't thought of that, but it absolutely solves the
problem
@Joseph: that looks interesting too, could you provide a link to that
extension?
thx a lot for the tips pointers
cheers,
juan pablo
On Tue, Mar 5, 2013 at 7:56 PM, Joseph Schaefer joe_schae...@yahoo.comwrote:
In the custom extension we use there is code that lets you select a CSS
classname by adding {.classname} to the end of the text area.
Sent from my iPhone
On Mar 5, 2013, at 1:48 PM, Emmanouil Batsis (Manos) ma...@abiss.gr
wrote:
IF I understand you correctly you might be able to simply tackle the
issue using the right CSS selector to apply styles for external links.
If links pointing inside the site use URLs not starting with http you
might want to do something like the following to match external links:
a[href^=http://;] { color: red; }
hth,
Manos
On 03/05/2013 10:18 AM, Juan Pablo Santos Rodríguez wrote:
Hi,
@Ioan: that was exactly what I was trying to avoid, it feels a bit
cumbersome to type the whole link instead something like
[text][1](.whatevercssclass) or similar
@Shane: yep, had checked also that link, unfortunately, Special
attribute
blocks can be used only with headers fenced code blocks. and I was
looking
to arbitrarily style a given link (btw, the preview pane doesn't like
fenced blocks, or is it just me?)
seems I'll stick with inline html, I was puzzled to see that it doesn't
seem to be an easy way to put custom styles via markdown :-?
anyway, thanks for the insights
br,
juan pablo
On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org
wrote:
See if this helps:
http://michelf.ca/projects/**php-markdown/extra/#spe-attr
http://michelf.ca/projects/php-markdown/extra/#spe-attr
Which is linked from:
http://www.apache.org/dev/**cmsref.html#markdown
http://www.apache.org/dev/cmsref.html#markdown
- Shane
On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote:
Hi all,
probably is a dumb issue and I'm missing something obvious, but so
far, I
haven't been able to solve it:
Is there an easy way to tell a markdown link to use a specific css
class?
I'd like to render links pointing outside the incubator site with an
external css class. I know I can write the html equivalent, but that
feels unnatural, so I'd better avoid that option. I've been poking at
a
few
site's sources, but haven't had any luck yet..
thx in advance!
br,
juan pablo
--**--**-
To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org
general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.**org
general-h...@incubator.apache.org
--
Manos Batsis, Chief Technologist
___
_/ /_ (_)_ __
/ __ `/ __ \/ / ___/ ___// __ `/ ___/
/ /_/ / /_/ / (__ |__ )/ /_/ / /
\__,_/_.___/_//(_)__, /_/
//
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Markdown issue
Hi all, probably is a dumb issue and I'm missing something obvious, but so far, I haven't been able to solve it: Is there an easy way to tell a markdown link to use a specific css class? I'd like to render links pointing outside the incubator site with an external css class. I know I can write the html equivalent, but that feels unnatural, so I'd better avoid that option. I've been poking at a few site's sources, but haven't had any luck yet.. thx in advance! br, juan pablo
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Hi Alexei, activation-1.1.jar et al are downloaded as part of the build. They're not included in the source because that's contrary to the Apache principles. That was noted in our July report (and tracked at [#1]). Regarding the LICENSE / doc/LICENSE.* files: initially, we kept each license in a separate file (doc/LICENSE.*), while ./LICENSE contained only the AL. This raised some concerns, noted on our 3rd RC vote [#2], which led to ./LICENSE file also having verbatim copies of all used licenses. As for the Mozilla license, it's in the ./LICENSE file (line 1090 onwards), we use custom-rhino in some of the tests, which uses that license. cheers, juan pablo p.d.: your vote being..? O:-D [#1]: https://issues.apache.org/jira/browse/JSPWIKI-738https://issues.apache.org/jira/browse/JSPWIKI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419501#comment-13419501 [#2]: http://mail-archives.apache.org/mod_mbox/incubator-general/201210.mbox/%3c80852492-ac42-4f8d-82ca-760eefccd...@oracle.com%3E On Wed, Nov 14, 2012 at 4:36 PM, Alexei Fedotov alexei.fedo...@gmail.comwrote: Great work! I've got the following questions concerning the ./LICENSE file for the source release: There is a list of jar files in the ./LICENSE file of the following form: activation-1.1.jar doc/LICENSE.cddl What is the point of including licenses for files which are absent in the source release? Why license texts appear twice (both in the ./LICENSE file and ./doc/ folder)? That provides more place for possible errors. I believe the list is good to exist in the ./LICENSE file for the binary release. Why it does not mention all licenses from the source release ./LICENSE file, e.g. Mozilla license? How to understand Copyright (c) year copyright holders in MIT license. The template style cannot appear in final version of the LICENSE. Also, IMHO, copyright attribution does not belong to the license (unless you use a copyrighted license). -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek flori...@apache.org wrote: Hi all, I'd like to start a vote on an incubator release for Apache JSPWiki, version 2.9.0-incubating. Apache JSPWiki (incubating) is a leading open source WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A vote was held on the developer mailing list [1] and passed with 9 +1s [2], two of them from our mentors. This release candidate fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating Source and binary files: http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ Checksums: JSPWiki-2.9.0-incubating-src.zip MD5:287e75857b03b41dca769211591c6144 SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 SHA512: 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a JSPWiki-2.9.0-incubating-bin.zip MD5:7e774dc46c112ca895aad60fb607dc60 SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 SHA512: 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS For convenience, this directory includes a binary distribution and a RAT report on the cited tag. You can manually generate the RAT report from a clean source by running the rat-report Ant target. Please vote: [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) The vote will be open for at least 72 hours. Best regards Florian Holeczek [1] http://markmail.org/message/gksvnjnru2nhhenf [2] http://markmail.org/message/mht24dwvpmm7xgft - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rat report
Hi Craig,
just committed some changes to address those concerns:
- issues #1 and #2: added into NOTICE/LICENSE
- #3: that comment is most probably there because it is a minified version,
anyway, I've added the appropiate text in NOTICE
- #4: more or less, the same issue as #3. We contacted the author and asked
him to explicitly state the license, which was done soon after. The file is
still used although we may switch to other alternatives in the future. The
whole history can be tracked at
https://issues.apache.org/jira/browse/JSPWIKI-382
- #5: removed the All rights reserved text and explicitly stated all
types of licenses in the NOTICE file.
- #6: included all the licenses verbatim in the main LICENSE file. Really
long file there. Also, I've noticed some jars' versions where incorrect and
in some cases the license had also changed (for instance jetty is licensed
under AL2.0 now) so, I updated that too.
Hope that all is fine now, thanks for looking into this!
br,
juan pablo
On Wed, Oct 10, 2012 at 9:53 PM, Craig L Russell
craig.russ...@oracle.comwrote:
Hi Juan Pablo,
The license update is looking very good. Thanks for pitching in and doing
all this heavy lifting!
I have some concerns with the files listed below.
1. The SilkIconSet images are licensed under CC-attribution 2.5 license.
The NOTICE needs to accommodate the comment from the source file:
All I ask is that you include a link back to this page in your credits.
Something like:
SilkIconSet (C) Mark James.
http://www.famfamfam.com/lab/**icons/silk/http://www.famfamfam.com/lab/icons/silk/
2. fckconfig.js can be licensed under any of several licenses, but you
have to choose one of them and include which one in the NOTICE and then
copy the entire license into the LICENSE. The MPL 1.1 or later is
explicitly mentioned, and since there have been issues with MPL 1.1, I'd
suggest choosing MPL 2.0 in which these issues have been resolved.
For example:
fckconfig.js Copyright (C) 2003-2008 Frederico Caldeira Knabben licensed
under the terms of Mozilla Public License Version 2.0 http://
http://www.mozilla.org/**MPL/2.0 http://www.mozilla.org/MPL/2.0
3. mootools.js
The source contains a problematic comment: MIT Style License. But the
web site says MooTools is released under the Open SourceMIT license, which
gives you the possibility to use it and modify it in every circumstance.
So, I'd go with:
mootools.js Copyright (c) 2006 Valerio Proietti, http://mad4milk.net,
licensed under the terms of the MIT license http://opensource.org/**
licenses/mit-license.php http://opensource.org/licenses/mit-license.php
4. posteditor.js
Looking at http://mail-archives.apache.**org/mod_mbox/incubator-**
jspwiki-dev/201204.mbox/%**3C701083845.7526.**
1335706069329.JavaMail.tomcat@**hel.zones.apache.org%3Ehttp://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201204.mbox/%3c701083845.7526.1335706069329.javamail.tom...@hel.zones.apache.org%3Eit's
not clear whether posteditor.js is even part of the release any more?
5. Some other contents of NOTICE are not enlightening. For example,
OSCache Copyright (c) 2001 The OpenSymphony Group. All rights reserved.
The All rights reserved doesn't actually grant us any rights. The
license under which we are using the files needs to be explicit.
Similarly for all the other projects with All rights reserved.
6. The LICENSE file needs to copy verbatim all of the licenses for all of
the projects that we are including. I notice that in the docs/LICENSE.* you
have reproduced many of the licenses in use, but these should be put either
into the top level LICENSE file or in a LICENSE file where the code is
actually located in the source tree. The former is my advice.
Craig
On Oct 9, 2012, at 2:31 PM, juanpa...@apache.org wrote:
Modified: incubator/jspwiki/trunk/build.**xml
URL: http://svn.apache.org/viewvc/**incubator/jspwiki/trunk/build.**
xml?rev=1396339r1=1396338r2=**1396339view=diffhttp://svn.apache.org/viewvc/incubator/jspwiki/trunk/build.xml?rev=1396339r1=1396338r2=1396339view=diff
==**==**
==
--- incubator/jspwiki/trunk/build.**xml (original)
+++ incubator/jspwiki/trunk/build.**xml Tue Oct 9 21:31:17 2012
@@ -1703,8 +1703,8 @@ To automate the JAR signing processs, yo
report reportFile=${doc.rat}/rat.**txt addLicenseHeaders=true
fileset dir=src/org/
- fileset dir=src/webdocs excludes=**/*.js
- /fileset
+ fileset dir=src/webdocs
+ excludes=**/SilkIconSet-**readme.txt,**/fckconfig.js,**/
**mootools.js,**/posteditor.js /
fileset dir=tests/org/
/report
/target
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.**com craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
--**--**-
To unsubscribe, e-mail:
Re: RAT issues [was: Re: [VOTE] JSPWiki version 2.9.0-incubating]
Hi, comments inline On Tue, Oct 9, 2012 at 6:50 AM, Craig L Russell craig.russ...@oracle.comwrote: On Oct 8, 2012, at 3:59 PM, Juan Pablo Santos Rodríguez wrote: Hello, We've added support to generate RAT files (RAT report for RC3 available at [#1]) and began to play with it, via rat-ant-tasks [#2]. As noted in previous e-mails, all the JSP files lack of a proper header. So, a couple of questions: - we pass the addLicenseHeaders argument to the report task. A lot of .new files get generated with the appropiate header, but none of them correspond to JSPs files. On the other hand the RAT report detects the missing header in the JSP files. Is there any way to enforce the process for JSP files? I'm not clear what you are saying here. If the rat addLicenseHeaders does not create .jsp files with the appropriate header, you may need to manually edit the .jsp files. yep, I was wondering if there was some flag to create this files, as other types of files are created automatically. It was like 1:00am and it seems my brain refused to continue looking at this. A little bit of sed usage should do the trick anyways, so this should be easily done. - we also have some .js files which come with their license header (i.e.: mootools.js). RAT detects them as their header doesn't conform with AL Header. In this case I assume we should ignore this files, is that ok? If you review all of the files that have their own license header, you can then notate them. What rat does is report non-conforming files of all types. Any files that are licensed under a non-Apache license need to be called out in the NOTICE and/or LICENSE files. There are many examples of such files in other projects. If you give specific file names, I can help you with what needs to be done to include them. These js libraries are noted in [LICENSE | NOTICE] so I'll exclude them from RAT analysis. Craig We've also made java files conform strictly with AL header, so the headers issue should be solved once we get rid of the two points noted above. thx in advance, juan pablo [#1]: http://people.apache.org/~juanpablo/rat_2.9.0_rc3.txt [#2]: http://creadur.apache.org/rat/apache-rat-tasks/report.html thx for the tips :-) br, juan pablo
RAT issues [was: Re: [VOTE] JSPWiki version 2.9.0-incubating]
Hello, We've added support to generate RAT files (RAT report for RC3 available at [#1]) and began to play with it, via rat-ant-tasks [#2]. As noted in previous e-mails, all the JSP files lack of a proper header. So, a couple of questions: - we pass the addLicenseHeaders argument to the report task. A lot of .new files get generated with the appropiate header, but none of them correspond to JSPs files. On the other hand the RAT report detects the missing header in the JSP files. Is there any way to enforce the process for JSP files? - we also have some .js files which come with their license header (i.e.: mootools.js). RAT detects them as their header doesn't conform with AL Header. In this case I assume we should ignore this files, is that ok? We've also made java files conform strictly with AL header, so the headers issue should be solved once we get rid of the two points noted above. thx in advance, juan pablo [#1]: http://people.apache.org/~juanpablo/rat_2.9.0_rc3.txt [#2]: http://creadur.apache.org/rat/apache-rat-tasks/report.html On Sun, Oct 7, 2012 at 11:53 PM, Craig L Russell craig.russ...@oracle.comwrote: Hi Christian, Thanks for the review of the release. On Oct 7, 2012, at 12:30 PM, Christian Grobmeier wrote: Hello, i'm sorry to -1 your release :-( Please see: http://www.apache.org/legal/**src-headers.html#headershttp://www.apache.org/legal/src-headers.html#headers This is a very important document to read and understand. The jspwiki headers are non-standard and should be rewritten to conform. In particular, there should be no extraneous verbiage before the Licensed to... text. No copyright, no other information. I have found a lot of code like in the the src package /src/webdocs/Captcha.jsp which are missing header licenses. I saw it is in the .java files, but they should be basically in every file we release (including jsp) I agree, .jsp files need the Apache license header just as .java files do. Also export.sh misses headers. In the headers of the .java files is: JSPWiki - a JSP-based WikiWiki clone. Not sure if this is a blocker, but you should use the full name Apache JSPWiki instead of only JSPWiki. Personally I would get rid of this line actually, but i think it is up to you. Getting rid of the line is probably the easiest way to conform. Example: https://svn.apache.org/repos/**asf/incubator/jspwiki/tags/** jspwiki_2_9_0_incubating_rc3/**src/org/apache/catalina/util/** HexUtils.javahttps://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating_rc3/src/org/apache/catalina/util/HexUtils.java I have not tested signatures yet. In other projects sometimes the website is being voted on together with the releases. Is it not the case with JSPWiki? I don't know that I've ever voted on a web site release. Other projects just update the web site as needed, with no vote. On another note, I agree with Ross. Your mentors should have told you that and they should have voted already. This first release has been a long time coming, and I was distracted the last couple of weeks. I agree that the mentors should review the release and advise of remedial action. I'd like to see a rat report on the release. I believe that analysis of the rat report will reinforce the comments that Christian and I made. Regards, Craig Not sure if how the overall situation on your daily project life is. If you feel that you would need more mentor support, please write a separate e-mail to this list. I have only looked at this e-mail as it was open for a couple of days without much responses. Best regards, Christian On Thu, Sep 27, 2012 at 8:11 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi, This is a call for a vote on releasing the following candidate as Apache JSPWiki version 2.9.0-incubating. This will be our first release. A vote was held on the developer mailing list (http://s.apache.org/dzM) and passed with 10 +1s (* denoting PPMC): Janne Jalkannen* Florian Holeczek* Harry Metske* Andrew Jaquith* Dirk Frederickx* Juan Pablo Santos Rodríguez* Fabian Haupt Michael Gerzabek Christophe Dupriez Roberto Venturi We need at least 3 IPMC votes. This release fixes the following issues: https://issues.apache.org/**jira/secure/ReleaseNote.jspa?** projectId=12310732version=**12319521https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 Source and binary files: http://people.apache.org/~**jalkanen/JSPWiki/2.9.0/http://people.apache.org/~jalkanen/JSPWiki/2.9.0/ The tag to be voted upon: https://svn.apache.org/repos/**asf/incubator/jspwiki/tags/** jspwiki_2_9_0_incubating_rc3https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating_rc3 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/**incubator/jspwiki/KEYShttp://www.apache.org/dist/incubator/jspwiki/KEYS Please
Re: [VOTE] JSPWiki version 2.9.0-incubating
Hi again, we have to submit our IPMC Board report this month, and it would be real nice if we could say that we have enough (or at least some, ongoing) IPMC votes. can somebody take a look at this? thanks! br, juan pablo On Sun, Sep 30, 2012 at 8:35 PM, Florian Holeczek flor...@holeczek.dewrote: Hi folks, just want to remind you of the ongoing vote... Best regards Florian Holeczek Am 27.09.2012 20:11, schrieb Juan Pablo Santos Rodríguez: Hi, This is a call for a vote on releasing the following candidate as Apache JSPWiki version 2.9.0-incubating. This will be our first release. A vote was held on the developer mailing list (http://s.apache.org/dzM) and passed with 10 +1s (* denoting PPMC): Janne Jalkannen* Florian Holeczek* Harry Metske* Andrew Jaquith* Dirk Frederickx* Juan Pablo Santos Rodríguez* Fabian Haupt Michael Gerzabek Christophe Dupriez Roberto Venturi We need at least 3 IPMC votes. This release fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 Source and binary files: http://people.apache.org/~jalkanen/JSPWiki/2.9.0/ The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating_rc3 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS Please download, test, and vote by 72 hours from now. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] JSPWiki version 2.9.0-incubating
cool, thanks :-) On Wed, Oct 3, 2012 at 12:41 PM, Benson Margulies bimargul...@gmail.comwrote: I will do an exam this evening when I get where I'm going. On Wed, Oct 3, 2012 at 2:14 AM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi again, we have to submit our IPMC Board report this month, and it would be real nice if we could say that we have enough (or at least some, ongoing) IPMC votes. can somebody take a look at this? thanks! br, juan pablo On Sun, Sep 30, 2012 at 8:35 PM, Florian Holeczek flor...@holeczek.de wrote: Hi folks, just want to remind you of the ongoing vote... Best regards Florian Holeczek Am 27.09.2012 20:11, schrieb Juan Pablo Santos Rodríguez: Hi, This is a call for a vote on releasing the following candidate as Apache JSPWiki version 2.9.0-incubating. This will be our first release. A vote was held on the developer mailing list (http://s.apache.org/dzM) and passed with 10 +1s (* denoting PPMC): Janne Jalkannen* Florian Holeczek* Harry Metske* Andrew Jaquith* Dirk Frederickx* Juan Pablo Santos Rodríguez* Fabian Haupt Michael Gerzabek Christophe Dupriez Roberto Venturi We need at least 3 IPMC votes. This release fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 Source and binary files: http://people.apache.org/~jalkanen/JSPWiki/2.9.0/ The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating_rc3 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS Please download, test, and vote by 72 hours from now. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] JSPWiki version 2.9.0-incubating
Hi, This is a call for a vote on releasing the following candidate as Apache JSPWiki version 2.9.0-incubating. This will be our first release. A vote was held on the developer mailing list (http://s.apache.org/dzM) and passed with 10 +1s (* denoting PPMC): Janne Jalkannen* Florian Holeczek* Harry Metske* Andrew Jaquith* Dirk Frederickx* Juan Pablo Santos Rodríguez* Fabian Haupt Michael Gerzabek Christophe Dupriez Roberto Venturi We need at least 3 IPMC votes. This release fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 Source and binary files: http://people.apache.org/~jalkanen/JSPWiki/2.9.0/ The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating_rc3 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS Please download, test, and vote by 72 hours from now. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, juan pablo
Re: JSPWiki status (Was: [Incubator Wiki] Update of July2012 by JuanPabloSantos)
Hello Jukka, almost there, the only remaining issue blocking the release is JSPWIKI-744, which is almost complete, should be finished this week (most probably tomorrow or Tuesday). So, the vote should be casted real soon. br, juan pablo On Sun, Sep 16, 2012 at 11:51 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi JSPWiki, On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Again, like in April, I'd note that the most pressing blocker is getting an Apache release out. Any progress on this front? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
downloading external dependencies outside of svn.apache.org
Hello, As a part of JSPWiki's July 2012 incubator report [#1], it was noted that JSPWiki (incubating) should not ship external jars alongside with code. This has been achieved in current trunk. However, as part of AOO community graduation vote thread [#2] it was noted that: If you try to build from source the build system will download packages from svn.apache.org instead of from elsewhere or the mirrors. That violates infra policy. Which is exactly what is happening to us: we download jars from Central as much as possible but, as there are a few of them ([#3], [#4]) which are not published in Central, we download them from svn.apache.org. These jar are all AL compatible so, the questions are: - where can we place them in order to not violate infra policy? - could this be a -1 towards voting a release? how to proceed? thx regards, juan pablo [#1] http://s.apache.org/zsq [#2] http://s.apache.org/8Gk [#3] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/lib/ [#4] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/tests/lib/
Re: downloading external dependencies outside of svn.apache.org
Hi Joe, thanks for the insight :-) can you give one project which has done this?, just to have a look at it and have this done the right way from the beggining. Are there any special requirements for these jars in order to be able to distribute them from mirrors (i.e.: being signed with a key corresponding to the Apache web of trust or something like that?) br, juan pablo On Mon, Aug 27, 2012 at 8:45 PM, Joe Schaefer joe_schae...@yahoo.comwrote: Many projects in a similar situation ship a deps package that contains dependencies and distribute those from the mirrors. HTH From: Juan Pablo Santos Rodríguez juanpa...@apache.org To: general@incubator.apache.org Sent: Monday, August 27, 2012 2:42 PM Subject: downloading external dependencies outside of svn.apache.org Hello, As a part of JSPWiki's July 2012 incubator report [#1], it was noted that JSPWiki (incubating) should not ship external jars alongside with code. This has been achieved in current trunk. However, as part of AOO community graduation vote thread [#2] it was noted that: If you try to build from source the build system will download packages from svn.apache.org instead of from elsewhere or the mirrors. That violates infra policy. Which is exactly what is happening to us: we download jars from Central as much as possible but, as there are a few of them ([#3], [#4]) which are not published in Central, we download them from svn.apache.org. These jar are all AL compatible so, the questions are: - where can we place them in order to not violate infra policy? - could this be a -1 towards voting a release? how to proceed? thx regards, juan pablo [#1] http://s.apache.org/zsq [#2] http://s.apache.org/8Gk [#3] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/lib/ [#4] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/tests/lib/
Re: downloading external dependencies outside of svn.apache.org
I'll have a look at it, thanks! br, juan pablo On Mon, Aug 27, 2012 at 8:50 PM, Benson Margulies bimargul...@gmail.comwrote: You can also use OSSRH to push more jars to central. On Mon, Aug 27, 2012 at 2:45 PM, Joe Schaefer joe_schae...@yahoo.com wrote: Many projects in a similar situation ship a deps package that contains dependencies and distribute those from the mirrors. HTH From: Juan Pablo Santos Rodríguez juanpa...@apache.org To: general@incubator.apache.org Sent: Monday, August 27, 2012 2:42 PM Subject: downloading external dependencies outside of svn.apache.org Hello, As a part of JSPWiki's July 2012 incubator report [#1], it was noted that JSPWiki (incubating) should not ship external jars alongside with code. This has been achieved in current trunk. However, as part of AOO community graduation vote thread [#2] it was noted that: If you try to build from source the build system will download packages from svn.apache.org instead of from elsewhere or the mirrors. That violates infra policy. Which is exactly what is happening to us: we download jars from Central as much as possible but, as there are a few of them ([#3], [#4]) which are not published in Central, we download them from svn.apache.org. These jar are all AL compatible so, the questions are: - where can we place them in order to not violate infra policy? - could this be a -1 towards voting a release? how to proceed? thx regards, juan pablo [#1] http://s.apache.org/zsq [#2] http://s.apache.org/8Gk [#3] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/lib/ [#4] http://svn.apache.org/repos/asf/incubator/jspwiki/libs/tests/lib/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: downloading external dependencies outside of svn.apache.org
great, thanks! :-) On Mon, Aug 27, 2012 at 9:21 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Aug 27, 2012 at 8:45 PM, Joe Schaefer joe_schae...@yahoo.com wrote: Many projects in a similar situation ship a deps package that contains dependencies and distribute those from the mirrors. On Mon, Aug 27, 2012 at 3:11 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: ...can you give one project which has done this?... See http://apache.org/dist/incubator/stanbol/apache-stanbol-0.9.0-incubating-deps/ for example. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of July2012 by JuanPabloSantos)
Hi Dave,
thanks for the tip :-) Actually we're downloading a few LGPL jars via
maven-ant-tasks,
but this approach seems simpler for our libs, as we won't have to deal with
transitive
dependencies.
br,
juan pablo
On Thu, Jul 12, 2012 at 9:51 PM, Dave Fisher dave2w...@comcast.net wrote:
On Jul 12, 2012, at 10:38 AM, sebb wrote:
On 11 July 2012 22:26, Juan Pablo Santos Rodríguez
juanpablo.san...@gmail.com wrote:
Oh, my misunderstanding then. If that's the case, then there is one
technicality of the apache release process blocking the release
(distributing dependencies alongside source), although not a tough one.
I'll file a Jira and reflect it at the project incubation status page.
regards,
juan pablo
On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting jukka.zitt...@gmail.com
wrote:
Hi,
On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez
juanpablo.san...@gmail.com wrote:
Regarding the binary dependencies. Wasn't the discussion on
general@more
focused on (or raised because of) transitive dependencies which were
brought into the build and not being AL-compatible?
No, all the dependencies discussed were compliant with Apache
policies. The problem was about having binaries included in the source
archive.
Also, the build is Ant based, so we need them to be there in order to
be
able to build.
Not so; Apache JMeter and Tomcat both use Ant and have external
dependencies which are not held in SVN.
The proposed solution for this case was to put the dependencies in a
separate -deps archive, that can be combined with the source release
to make it buildable. The build script can also automatically download
such separate binary dependencies.
That's what JMeter and Tomcat do: there's a separate Ant task to do
the downloads.
But you could also use Ant+Ivy.
Apache POI uses ant as well. Here are selected parts of the build.xml:
!-- the repository to download jars from --
property name=repository.m2 value=http://repo1.maven.org/
property name=main.lib location=lib/
!-- jars in the /lib directory, see the fetch-jars target--
property name=main.commons-logging.jar
location=${main.lib}/commons-logging-1.1.jar/
property name=main.commons-logging.url
value=${repository.m2}/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.jar/
property name=main.commons-codec.jar
location=${main.lib}/commons-codec-1.5.jar/
property name=main.commons-codec.url
value=${repository.m2}/maven2/commons-codec/commons-codec/1.5/commons-codec-1.5.jar/
property name=main.log4j.jar
location=${main.lib}/log4j-1.2.13.jar/
property name=main.log4j.url
value=${repository.m2}/maven2/log4j/log4j/1.2.13/log4j-1.2.13.jar/
property name=main.junit.jar
location=${main.lib}/junit-3.8.1.jar/
property name=main.junit.url
value=${repository.m2}/maven2/junit/junit/3.8.1/junit-3.8.1.jar/
property name=main.ant.jar location=${main.lib}/ant-1.8.2.jar/
property name=main.ant.url
value=${repository.m2}/maven2/org/apache/ant/ant/1.8.2/ant-1.8.2.jar/
target name=check-jars
condition property=jars.present
or
and
available file=${main.commons-logging.jar}/
available file=${main.commons-codec.jar}/
available file=${main.log4j.jar}/
available file=${main.junit.jar}/
available file=${main.ant.jar}/
/and
isset property=disconnected/
/or
/condition
/target
target name=fetch-jars depends=check-jars unless=jars.present
description=Fetches needed JAR files from the Internet
mkdir dir=${main.lib}/
antcall target=downloadfile
param name=sourcefile value=${main.commons-logging.url}/
param name=destfile value=${main.commons-logging.jar}/
/antcall
antcall target=downloadfile
param name=sourcefile value=${main.commons-codec.url}/
param name=destfile value=${main.commons-codec.jar}/
/antcall
antcall target=downloadfile
param name=sourcefile value=${main.log4j.url}/
param name=destfile value=${main.log4j.jar}/
/antcall
antcall target=downloadfile
param name=sourcefile value=${main.junit.url}/
param name=destfile value=${main.junit.jar}/
/antcall
antcall target=downloadfile
param name=sourcefile value=${main.ant.url}/
param name=destfile value=${main.ant.jar}/
/antcall
/target
HTH,
Dave
BR,
Jukka Zitting
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of July2012 by JuanPabloSantos)
Oh, my misunderstanding then. If that's the case, then there is one technicality of the apache release process blocking the release (distributing dependencies alongside source), although not a tough one. I'll file a Jira and reflect it at the project incubation status page. regards, juan pablo On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Regarding the binary dependencies. Wasn't the discussion on general@more focused on (or raised because of) transitive dependencies which were brought into the build and not being AL-compatible? No, all the dependencies discussed were compliant with Apache policies. The problem was about having binaries included in the source archive. Also, the build is Ant based, so we need them to be there in order to be able to build. The proposed solution for this case was to put the dependencies in a separate -deps archive, that can be combined with the source release to make it buildable. The build script can also automatically download such separate binary dependencies. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: JSPWiki status (Was: [Incubator Wiki] Update of July2012 by JuanPabloSantos)
Hi Jukka, answers inline: On Tue, Jul 10, 2012 at 9:33 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Jul 5, 2012 at 11:39 PM, Apache Wiki wikidi...@apache.org wrote: + Still following the objetive of making the first Apache release: + + 4 JIRA issues were fixed since last period, the project website has been revamped, + and few other niceties fixes have got into trunk (for example lucene library was + upgraded to 3.6.0). + + 2 Release candidates have been made, but they didn't succeed because of + technical issues. Hopefully the third RC will become the first ASF release. If I understand correctly, these issues were about functionality in the JSPWiki software itself, not about the technicalities of the Apache release process. exactly. Do you have any active mentors available to help out in preparing the release? If not, please post a recent RC also to general@ for review by the rest of the IPMC. A quick look at one of the RCs brought up a few issues, most notably the presence of binary dependencies in the source release archive - a practice that's considered contrary to Apache principles based on recent discussion on general@. If I recall correctly, I think that we have two active mentors, Craig L Russell and sam Ruby. We had 2 more mentors, but they stepped down due to lack of time. Regarding the binary dependencies. Wasn't the discussion on general@ more focused on (or raised because of) transitive dependencies which were brought into the build and not being AL-compatible? In our case they're all AL compatible [#1], so that should be fine. We try to look very carefully to this issue. For instance, recently we added cobertura+sonar support, which weren't AL compatible so we had some discussion [#2] about the suitability of including them, given the fact that they were not going to be used to build the main war. We decided to not include them b/c they weren't AL compatible. Also, the build is Ant based, so we need them to be there in order to be able to build. [#1] https://issues.apache.org/jira/browse/JSPWIKI-545 [#2] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201206.mbox/%3CCAMufup6kANwDJT5aVXo4m4D4Uwnj3Srabm=4nvrms_fwbwf...@mail.gmail.com%3E + The main issues blocking graduation keep being the same as in the last report: + resolution acceptance, community and IPMC graduation vote. Again, like in April, I'd note that the most pressing blocker is getting an Apache release out. Beyond that it looks like community activity in JSPWiki is at a bit higher level than it used to be for the most part of the past two years, which is good. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org regards, juan pablo
Write access to Incubator wiki
Hi, could anyone grant me (JuanPabloSantos) write access to the Incubator Wiki? This way I can fill up the JSPWiki report (btw, apologies on the delay on that). thanks br, juan pablo
Re: Write access to Incubator wiki
thanks, have just filed the JSPWiki report. br, juan pablo On Thu, Jul 5, 2012 at 11:29 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Jul 5, 2012 at 11:18 PM, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: could anyone grant me (JuanPabloSantos) write access to the Incubator Wiki? Done. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: DOAP file for Apache JSPWiki (incubating)
The files.xml file lists 3 or 4 incubator projects and the doap site ( http://projects.apache.org/index.html) doesn't specify anything about incubating status :-? br, juan pablo On Tue, Jun 12, 2012 at 1:44 AM, Karl Wright daddy...@gmail.com wrote: I don't think you get your own DOAP file until you are a graduated TLP. Karl On Mon, Jun 11, 2012 at 6:45 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi, can someone with enough commit rights add the DOAP file for JSPWiki (incubating) to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml ? The file is located at http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdfSo far, we haven't been lucky at jspwiki-dev.. thanks, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com Date: Wed, May 9, 2012 at 10:16 PM Subject: Fwd: DOAP file for Apache JSPWiki (incubating) To: jspwiki-...@incubator.apache.org Can anyone with access to that repo commit the required change? it's just adding (at line 96?) location http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf /location to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpa...@apache.org Date: Wed, May 9, 2012 at 8:52 AM Subject: Re: DOAP file for Apache JSPWiki (incubating) To: sebb seb...@gmail.com Cc: site-...@apache.org Thanks for the info. We'll correct the asfext:pmc entry, commit the file and then update the DOAP references file. regards, juan pablo On Wed, May 9, 2012 at 2:07 AM, sebb seb...@gmail.com wrote: On 8 May 2012 22:17, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi! we've placed a DOAP file for Apache JSPWiki (incubating) at: http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf The DOAP file is not quite correct. The asfext:pmc entry should be for the incubator, not jspwiki. asfext:pmc rdf:resource=http://incubator.apache.org/jspwiki// should be asfext:pmc rdf:resource=http://incubator.apache.org// We have one question though, if this DOAP file gets updated (i.e.: Apache JSPWiki graduates from incubation, so most project URLs do change), should we ping this list regarding the changes or is there some sort of background process which does automate the process? The file of DOAP references [1] is manually maintained. ASF members and PMC chairs are the main groups that can update the file. [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: DOAP file for Apache JSPWiki (incubating)
Hi, @sebb: yes, the asfext:pmc entry is corrected @karl: didn't know about any files.txt, I came accross with one DOAP file while looking for Apache CMS site examples, and began to dig backwards, ending up at both https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xmland http://projects.apache.orghttp://projects.apache.org/indexes/pmc.html#Apache%20Incubator thanks br, juan pablo On Tue, Jun 12, 2012 at 8:09 PM, sebb seb...@gmail.com wrote: On 12 June 2012 11:11, Karl Wright daddy...@gmail.com wrote: As I understand it, the doap files are for PMC's. The incubator is the PMC here. That's why you don't get privs to modify files.txt, because you are not the incubator PMC chair. Which incubating projects have files.txt references to doap documents that you know of? See: http://projects.apache.org/indexes/pmc.html#Apache%20Incubator Karl On Tue, Jun 12, 2012 at 2:56 AM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: The files.xml file lists 3 or 4 incubator projects and the doap site ( http://projects.apache.org/index.html) doesn't specify anything about incubating status :-? br, juan pablo On Tue, Jun 12, 2012 at 1:44 AM, Karl Wright daddy...@gmail.com wrote: I don't think you get your own DOAP file until you are a graduated TLP. Karl On Mon, Jun 11, 2012 at 6:45 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi, can someone with enough commit rights add the DOAP file for JSPWiki (incubating) to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml ? The file is located at http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdfSo far, we haven't been lucky at jspwiki-dev.. thanks, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com Date: Wed, May 9, 2012 at 10:16 PM Subject: Fwd: DOAP file for Apache JSPWiki (incubating) To: jspwiki-...@incubator.apache.org Can anyone with access to that repo commit the required change? it's just adding (at line 96?) location http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf /location to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpa...@apache.org Date: Wed, May 9, 2012 at 8:52 AM Subject: Re: DOAP file for Apache JSPWiki (incubating) To: sebb seb...@gmail.com Cc: site-...@apache.org Thanks for the info. We'll correct the asfext:pmc entry, commit the file and then update the DOAP references file. Have you fixed the bugs? regards, juan pablo On Wed, May 9, 2012 at 2:07 AM, sebb seb...@gmail.com wrote: On 8 May 2012 22:17, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi! we've placed a DOAP file for Apache JSPWiki (incubating) at: http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf The DOAP file is not quite correct. The asfext:pmc entry should be for the incubator, not jspwiki. asfext:pmc rdf:resource=http://incubator.apache.org/jspwiki// should be asfext:pmc rdf:resource=http://incubator.apache.org// We have one question though, if this DOAP file gets updated (i.e.: Apache JSPWiki graduates from incubation, so most project URLs do change), should we ping this list regarding the changes or is there some sort of background process which does automate the process? The file of DOAP references [1] is manually maintained. ASF members and PMC chairs are the main groups that can update the file. [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: DOAP file for Apache JSPWiki (incubating)
done, thanks! On Tue, Jun 12, 2012 at 8:26 PM, sebb seb...@gmail.com wrote: On 12 June 2012 19:16, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi, @sebb: yes, the asfext:pmc entry is corrected Could you change the name entry as follows please: nameApache JSPWiki (incubating)/name I know SIS and Stanbol don't do this currently, but those ought to be fixed too. @karl: didn't know about any files.txt, I came accross with one DOAP file while looking for Apache CMS site examples, and began to dig backwards, ending up at both https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xmland http://projects.apache.org http://projects.apache.org/indexes/pmc.html#Apache%20Incubator thanks br, juan pablo On Tue, Jun 12, 2012 at 8:09 PM, sebb seb...@gmail.com wrote: On 12 June 2012 11:11, Karl Wright daddy...@gmail.com wrote: As I understand it, the doap files are for PMC's. The incubator is the PMC here. That's why you don't get privs to modify files.txt, because you are not the incubator PMC chair. Which incubating projects have files.txt references to doap documents that you know of? See: http://projects.apache.org/indexes/pmc.html#Apache%20Incubator Karl On Tue, Jun 12, 2012 at 2:56 AM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: The files.xml file lists 3 or 4 incubator projects and the doap site ( http://projects.apache.org/index.html) doesn't specify anything about incubating status :-? br, juan pablo On Tue, Jun 12, 2012 at 1:44 AM, Karl Wright daddy...@gmail.com wrote: I don't think you get your own DOAP file until you are a graduated TLP. Karl On Mon, Jun 11, 2012 at 6:45 PM, Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com wrote: Hi, can someone with enough commit rights add the DOAP file for JSPWiki (incubating) to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml ? The file is located at http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdfSo far, we haven't been lucky at jspwiki-dev.. thanks, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com Date: Wed, May 9, 2012 at 10:16 PM Subject: Fwd: DOAP file for Apache JSPWiki (incubating) To: jspwiki-...@incubator.apache.org Can anyone with access to that repo commit the required change? it's just adding (at line 96?) location http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf /location to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpa...@apache.org Date: Wed, May 9, 2012 at 8:52 AM Subject: Re: DOAP file for Apache JSPWiki (incubating) To: sebb seb...@gmail.com Cc: site-...@apache.org Thanks for the info. We'll correct the asfext:pmc entry, commit the file and then update the DOAP references file. Have you fixed the bugs? regards, juan pablo On Wed, May 9, 2012 at 2:07 AM, sebb seb...@gmail.com wrote: On 8 May 2012 22:17, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi! we've placed a DOAP file for Apache JSPWiki (incubating) at: http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf The DOAP file is not quite correct. The asfext:pmc entry should be for the incubator, not jspwiki. asfext:pmc rdf:resource=http://incubator.apache.org/jspwiki/ / should be asfext:pmc rdf:resource=http://incubator.apache.org// We have one question though, if this DOAP file gets updated (i.e.: Apache JSPWiki graduates from incubation, so most project URLs do change), should we ping this list regarding the changes or is there some sort of background process which does automate the process? The file of DOAP references [1] is manually maintained. ASF members and PMC chairs are the main groups that can update the file. [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h
DOAP file for Apache JSPWiki (incubating)
Hi, can someone with enough commit rights add the DOAP file for JSPWiki (incubating) to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml? The file is located at http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdfSo far, we haven't been lucky at jspwiki-dev.. thanks, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com Date: Wed, May 9, 2012 at 10:16 PM Subject: Fwd: DOAP file for Apache JSPWiki (incubating) To: jspwiki-...@incubator.apache.org Can anyone with access to that repo commit the required change? it's just adding (at line 96?) location http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf/location to https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo -- Forwarded message -- From: Juan Pablo Santos Rodríguez juanpa...@apache.org Date: Wed, May 9, 2012 at 8:52 AM Subject: Re: DOAP file for Apache JSPWiki (incubating) To: sebb seb...@gmail.com Cc: site-...@apache.org Thanks for the info. We'll correct the asfext:pmc entry, commit the file and then update the DOAP references file. regards, juan pablo On Wed, May 9, 2012 at 2:07 AM, sebb seb...@gmail.com wrote: On 8 May 2012 22:17, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hi! we've placed a DOAP file for Apache JSPWiki (incubating) at: http://svn.apache.org/repos/asf/incubator/jspwiki/site/doap/doap-jspwiki.rdf The DOAP file is not quite correct. The asfext:pmc entry should be for the incubator, not jspwiki. asfext:pmc rdf:resource=http://incubator.apache.org/jspwiki// should be asfext:pmc rdf:resource=http://incubator.apache.org// We have one question though, if this DOAP file gets updated (i.e.: Apache JSPWiki graduates from incubation, so most project URLs do change), should we ping this list regarding the changes or is there some sort of background process which does automate the process? The file of DOAP references [1] is manually maintained. ASF members and PMC chairs are the main groups that can update the file. [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml thanks regards, juan pablo
[RESULT] [VOTE] Graduate JSPWiki from Incubator
Hi, after discussing it on the jspwiki-dev list [1], we have decided to follow the advices given at general@incubator and withdraw the vote, in order to stick better to ASF principles and guidelines. Our current course of action goes through making (at least) one ASF release, tidy up the project's incubator site and then recast the community vote again. regards, juan pablo [1] http://markmail.org/message/f6zan2vcfvr5xujx On Wed, Apr 18, 2012 at 11:38 PM, William A. Rowe Jr. wr...@rowe-clan.netwrote: On 4/15/2012 5:46 PM, Juan Pablo Santos Rodríguez wrote: we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. As noted by others, this seems counter-factual. Although candidates may have been prepared, no candidate was voted for release and therefore no candidate was a release. Made no releases would be an accurate statement, as would Made two candidates. Candidates are not sufficient for graduation as I understand incubator policy. Due to placing an unapproved candidate into distribution, I trust that the second comment, finishing 'learning... accepted Apache practices' is also a statement due to be revisited. I'm sure JSPwiki mentors will be circling the wagons, and working out what went wrong, and ensuring everyone involved understands how the mistakes occurred, and any missing documentation will be added to incubator guidance documents. Please cast your votes: [ ] +1 Graduate JSPWiki from Incubator [ ] +0 Indifferent to graduation status of JSPWiki [ ] +1 Reject graduation of JSPWiki from Incubator This vote will remain open for at least 72 hours from now. At this time, it would be prudent to withdraw this vote from consideration address all identified concerns, and wait for another day to put forward this vote again, once i's are dotted, and t's are crossed. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate JSPWiki from Incubator
On Wed, Apr 18, 2012 at 10:25 PM, Ross Gardler rgard...@opendirective.comwrote: On 18 April 2012 05:43, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 4/17/2012 3:57 AM, Ross Gardler wrote: -1 Unless I am mistaken JSPWiki has not yet made a release under the Apache license: Release 2.9 as first Apache release https://issues.apache.org/jira/browse/JSPWIKI-717 http://www.apache.org/dist/incubator/jspwiki/ Apparently this was released. Interesting. My -1 was posted to this list at 4/17/2012 3:57 AM the last update timestamp 2012-04-17 19:26 A little investigation on the JSP dev list is revealing, in short no vote (I don't believe there is ill intent either, just a misunderstanding of how we work) http://markmail.org/message/lkz77tzyk4onks3f Indeed. Also, regarding the we have made two releases following the ASF policies and guidelines should have been written as two releases were made following ASF *voting* policies . My mistake. They were community-voted but, for example, weren't signed or correctly mirrored. Of course, (at least) one release following ASF guidelines will be made before IPMC voting and going into TLP. regards, juan pablo My -1 stands, this is not a release and is not sanctioned by the ASF (I'll forward this to infra to ensure they know it is there). Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate JSPWiki from Incubator
+1 regards, juan pablo On Mon, Apr 16, 2012 at 8:43 AM, Michael Gerzabek michael.gerza...@gmx.netwrote: +1 Am 16.04.2012 00:04, schrieb Juan Pablo Santos Rodríguez: Hello all, The Apache JSPWiki project entered Incubator in October of 2007. Since then we have added two new committers from diverse organizations. The codebase of our product has been growing slowly but surely, and we think is mature enough to go through graduation; also, we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Given these milestones, I feel that JSPWiki is ready to graduate from Incubator. The first step towards graduation is to vote as a community that JSPWiki is ready to graduate. If the vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. The complete graduation process is described [1]. Please cast your votes: [ ] +1 Graduate JSPWiki from Incubator [ ] +0 Indifferent to graduation status of JSPWiki [ ] +1 Reject graduation of JSPWiki from Incubator This vote will remain open for at least 72 hours from now. [1] http://incubator.apache.org/guides/graduation.html Thanks, juan pablo
[VOTE] Graduate JSPWiki from Incubator
Hello all, The Apache JSPWiki project entered Incubator in October of 2007. Since then we have added two new committers from diverse organizations. The codebase of our product has been growing slowly but surely, and we think is mature enough to go through graduation; also, we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Given these milestones, I feel that JSPWiki is ready to graduate from Incubator. The first step towards graduation is to vote as a community that JSPWiki is ready to graduate. If the vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. The complete graduation process is described [1]. Please cast your votes: [ ] +1 Graduate JSPWiki from Incubator [ ] +0 Indifferent to graduation status of JSPWiki [ ] +1 Reject graduation of JSPWiki from Incubator This vote will remain open for at least 72 hours from now. [1] http://incubator.apache.org/guides/graduation.html Thanks, juan pablo
Re: [VOTE] Graduate JSPWiki from Incubator
Hi Ross, no worries, community voting is also meant to bring up this kind of conversations too. I will try to -briefly- express my opinion. You are quoting the discussion started at [1], followed up at [2]. I would like to highlight Florian's comments on first thread at [3], which summarize pretty well the state of the project. We took Roller as an example of a succesful Apache project, which is close to what happens to JSPWiki: mature project + small numbers of committers, with little time. So, as a community, we decided to proceed with graduation (thread at [2]). In that sense, is not that I have championed anything, just proceeded with what we decided previously. JSPWiki, unlike most Apache projects, is backed by several individuals who work on it only on their free time, so the absence of committers is felt deeper than in other projects. The first thing we should do after we graduate is to somehow ease the initial jump-in into the project. We have postponed this step after graduation because we needed to set a line somewhere in our long journey through incubation, and we felt that current trunk is mature enough to be considered as an Apache TLP ([2] again, heavily summarized). kind regards, juan pablo [1] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3C24918B2E-766A-4F7D-9C8D-F16EA030F392%40ecyrd.com%3E [2] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3CCABp47Es8BGj5jcx6ysP7RxFxBw7_zkrHb8Rbz-Fn7noueutA%3DQ%40mail.gmail.com%3E [3] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3Cbdd708d4-057d-4d20-acc2-24cc55cb3782%40vm103%3E On Mon, Apr 16, 2012 at 2:42 PM, Ross Gardler rgard...@opendirective.comwrote: Looking at the community activity this project looks like it lacks the diversity required. For example, on the vote thread on the projects own dev list there were only three +1 votes, one of which came from someone who has only ever posted to the dev list on two other occasions. Furthermore I'm worried that in Janne said: The point of Apache Incubation is to incubate a community of people who can create good software. So far our community seems to be dwindling more than increasing (and I accept the blame for that - I just haven't had the time nor the interest to put into this project). So I don't think it's wrong to say that our incubation has essentially failed, and that we should consider some other avenue, and go away from messing up the Apache Incubator. and Harry said: We simply can't get people interested in doing the necessary things, both the tech work and the non-tech work, and I personally do not have that much time for the project either anymore. So moving over to github is fine for me. (what will be the starting point in github BTW, the current trunk, or 2.8.4 ?) Now we have this proposal to graduate. Juan Pablo didn't like the idea of saying incubation had failed and has championed graduation. Can I ask for someone more aware of JSPWiki activities please provide a summary of why the proposals to declare failure in Jan were rejected and what activities have been undertaken to turn this failure to graduation. Please don't feel you need to defend the proposal, I'm just looking for information to support my vote and also to help me think about the discussions a couple of months ago about different styles of incubation activity. Ross On 15 April 2012 23:46, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hello all, The Apache JSPWiki project entered Incubator in October of 2007. Since then we have added two new committers from diverse organizations. The codebase of our product has been growing slowly but surely, and we think is mature enough to go through graduation; also, we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Given these milestones, I feel that JSPWiki is ready to graduate from Incubator. The first step towards graduation is to vote as a community that JSPWiki is ready to graduate. If the vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. The complete graduation process is described [1]. Please cast your votes: [ ] +1 Graduate JSPWiki from Incubator [ ] +0 Indifferent to graduation status of JSPWiki [ ] +1 Reject graduation of JSPWiki from Incubator This vote will remain open for at least 72 hours from now. [1] http://incubator.apache.org/guides/graduation.html Thanks, juan pablo -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Re: [VOTE] Graduate JSPWiki from Incubator
100% agree; I was intending to solely stress the fact that we had the same concerns pointed by Ross, but we felt JSPWiki could still stand as an Apache TLP (hence the decision to graduate), and, most important, all of this was community-driven, not as the result of some individuals likings. kind regards, juan pablo On Mon, Apr 16, 2012 at 7:33 PM, Benson Margulies bimargul...@gmail.comwrote: Graduation is very much *not* about maturity of the code, and very much about maturity of the community. 2012/4/16 Juan Pablo Santos Rodríguez juanpablo.san...@gmail.com: Hi Ross, no worries, community voting is also meant to bring up this kind of conversations too. I will try to -briefly- express my opinion. You are quoting the discussion started at [1], followed up at [2]. I would like to highlight Florian's comments on first thread at [3], which summarize pretty well the state of the project. We took Roller as an example of a succesful Apache project, which is close to what happens to JSPWiki: mature project + small numbers of committers, with little time. So, as a community, we decided to proceed with graduation (thread at [2]). In that sense, is not that I have championed anything, just proceeded with what we decided previously. JSPWiki, unlike most Apache projects, is backed by several individuals who work on it only on their free time, so the absence of committers is felt deeper than in other projects. The first thing we should do after we graduate is to somehow ease the initial jump-in into the project. We have postponed this step after graduation because we needed to set a line somewhere in our long journey through incubation, and we felt that current trunk is mature enough to be considered as an Apache TLP ([2] again, heavily summarized). kind regards, juan pablo [1] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3C24918B2E-766A-4F7D-9C8D-F16EA030F392%40ecyrd.com%3E [2] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3CCABp47Es8BGj5jcx6ysP7RxFxBw7_zkrHb8Rbz-Fn7noueutA%3DQ%40mail.gmail.com%3E [3] http://mail-archives.apache.org/mod_mbox/incubator-jspwiki-dev/201201.mbox/%3Cbdd708d4-057d-4d20-acc2-24cc55cb3782%40vm103%3E On Mon, Apr 16, 2012 at 2:42 PM, Ross Gardler rgard...@opendirective.comwrote: Looking at the community activity this project looks like it lacks the diversity required. For example, on the vote thread on the projects own dev list there were only three +1 votes, one of which came from someone who has only ever posted to the dev list on two other occasions. Furthermore I'm worried that in Janne said: The point of Apache Incubation is to incubate a community of people who can create good software. So far our community seems to be dwindling more than increasing (and I accept the blame for that - I just haven't had the time nor the interest to put into this project). So I don't think it's wrong to say that our incubation has essentially failed, and that we should consider some other avenue, and go away from messing up the Apache Incubator. and Harry said: We simply can't get people interested in doing the necessary things, both the tech work and the non-tech work, and I personally do not have that much time for the project either anymore. So moving over to github is fine for me. (what will be the starting point in github BTW, the current trunk, or 2.8.4 ?) Now we have this proposal to graduate. Juan Pablo didn't like the idea of saying incubation had failed and has championed graduation. Can I ask for someone more aware of JSPWiki activities please provide a summary of why the proposals to declare failure in Jan were rejected and what activities have been undertaken to turn this failure to graduation. Please don't feel you need to defend the proposal, I'm just looking for information to support my vote and also to help me think about the discussions a couple of months ago about different styles of incubation activity. Ross On 15 April 2012 23:46, Juan Pablo Santos Rodríguez juanpa...@apache.org wrote: Hello all, The Apache JSPWiki project entered Incubator in October of 2007. Since then we have added two new committers from diverse organizations. The codebase of our product has been growing slowly but surely, and we think is mature enough to go through graduation; also, we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Given these milestones, I feel that JSPWiki is ready to graduate from Incubator. The first step towards graduation is to vote as a community that JSPWiki is ready to graduate. If the vote is successful, we will draft
[VOTE] Graduate JSPWiki from Incubator
Hello all, The Apache JSPWiki project entered Incubator in October of 2007. Since then we have added two new committers from diverse organizations. The codebase of our product has been growing slowly but surely, and we think is mature enough to go through graduation; also, we have made two releases following the ASF policies and guidelines. Thanks to the mentorship we have received through this period, we have learnt to self-govern and grow our community using accepted Apache practices. Given these milestones, I feel that JSPWiki is ready to graduate from Incubator. The first step towards graduation is to vote as a community that JSPWiki is ready to graduate. If the vote is successful, we will draft a board resolution proposal and call it to vote on the general Incubator list. The complete graduation process is described [1]. Please cast your votes: [ ] +1 Graduate JSPWiki from Incubator [ ] +0 Indifferent to graduation status of JSPWiki [ ] +1 Reject graduation of JSPWiki from Incubator This vote will remain open for at least 72 hours from now. [1] http://incubator.apache.org/guides/graduation.html Thanks, juan pablo
