Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
Sorry Rich, that extra information in the "mailing lists" section cannot be parsed by Clutch. Perhaps move it to the "News" section. -David rbo...@apache.org wrote: > Author: rbowen > Date: Wed Jun 27 20:22:36 2012 > New Revision: 1354707 > > URL: http://svn.apache.org/viewvc?rev=1354707&view=rev > Log: > Provide helpful links, prior to move to ASF infra. > > Modified: > incubator/public/trunk/content/projects/allura.xml > > Modified: incubator/public/trunk/content/projects/allura.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/allura.xml?rev=1354707&r1=1354706&r2=1354707&view=diff > == > --- incubator/public/trunk/content/projects/allura.xml [utf-8] (original) > +++ incubator/public/trunk/content/projects/allura.xml [utf-8] Wed Jun 27 > 20:22:36 2012 > @@ -56,34 +56,40 @@ > >. >wiki > - . > + href="http://sourceforge.net/p/allura/wiki/Allura%20Wiki/";>http://sourceforge.net/p/allura/wiki/Allura%20Wiki/ > > >Mailing list >dev > - id="mail-dev">allura-dev@incubator.apache.org > + id="mail-dev">allura-dev@incubator.apache.org > +See href="https://issues.apache.org/jira/browse/INFRA-4967";>INFRA_4967 > + > > >. >commits > - id="mail-commits">allura-commits@incubator.apache.org > + id="mail-commits">allura-commits@incubator.apache.org > + See href="https://issues.apache.org/jira/browse/INFRA-4967";>INFRA_4967 > + > > >. >users > - id="mail-commits">allura-users@incubator.apache.org > + id="mail-commits">allura-users@incubator.apache.org > + See href="https://issues.apache.org/jira/browse/INFRA-4967";>INFRA_4967 > + > > >Bug tracking >. > > -[ provide expected link ] > + href="http://sourceforge.net/p/allura/tickets/";>http://sourceforge.net/p/allura/tickets/ > > > >Source code >Git > - > + href="http://sourceforge.net/p/allura/git";>http://sourceforge.net/p/allura/git > > > > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
On 28/06/2012 01:48, Jukka Zitting wrote: > [...] > > Speaking of the wiki page, now that the reporting schedule has been > migrated from the wiki [2] to the podlings.xml file [3], we > unfortunately no longer have the nice per-group listing of podlings > that I used for pre-filling the report wiki page. It would be great if > someone with XSLT skills could adjust the stylesheet [4] to output a > list of the podlings expected to report next month. Jukka, I've drafted a couple of XSLTs for this need: 1. podlings-report-per-month.xsl taking as input parameter the full name of the month for which you want the list of podlings expected to report in that month; this version doesn't have any requirement on XSLT processor. 2. podlings-report-per-month-exslt.xsl this will derive next month via EXSLT datetime and output the list of podlings expected to report in that month; Which version would you prefer? How should I provide the file(s)? How are you going to make this available? Do you need a Cocoon instance? ;-) Regards. > [...] > [1] http://wiki.apache.org/incubator/July2012 > [2] http://wiki.apache.org/incubator/ReportingSchedule > [3] http://incubator.apache.org/podlings.xml > [4] http://incubator.apache.org/podlings.xsl > [5] http://wiki.apache.org/incubator/IncubatorShepherds -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
David Crossley wrote: > Sorry Rich, that extra information in the "mailing lists" section > cannot be parsed by Clutch. Perhaps move it to the "News" section. Also, the "tracker" is the eventual ASF tracker that is intended. Suggest looking at some other podling status pages. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
Francesco Chicchiriccò wrote: > On 28/06/2012 01:48, Jukka Zitting wrote: > > [...] > > > > Speaking of the wiki page, now that the reporting schedule has been > > migrated from the wiki [2] to the podlings.xml file [3], we > > unfortunately no longer have the nice per-group listing of podlings > > that I used for pre-filling the report wiki page. It would be great if > > someone with XSLT skills could adjust the stylesheet [4] to output a > > list of the podlings expected to report next month. > > Jukka, > I've drafted a couple of XSLTs for this need: > > 1. podlings-report-per-month.xsl > taking as input parameter the full name of the month for which you want > the list of podlings expected to report in that month; this version > doesn't have any requirement on XSLT processor. > > 2. podlings-report-per-month-exslt.xsl > this will derive next month via EXSLT datetime and output the list of > podlings expected to report in that month; > > Which version would you prefer? > How should I provide the file(s)? > How are you going to make this available? Do you need a Cocoon instance? ;-) > > Regards. Sounds great. Note that Seb had already done a simple one. See http://incubator.apache.org/report-groups.txt The XSL is at https://svn.apache.org/repos/asf/incubator/public/trunk See report-groups.xsl The CMS magically generates stuff. See the ant "build.xml" file the with the "report-groups" target. Follow his svn trail. You might be able to install yours similarly. -David > > > [...] > > [1] http://wiki.apache.org/incubator/July2012 > > [2] http://wiki.apache.org/incubator/ReportingSchedule > > [3] http://incubator.apache.org/podlings.xml > > [4] http://incubator.apache.org/podlings.xsl > > [5] http://wiki.apache.org/incubator/IncubatorShepherds > > -- > Francesco Chicchiriccò > > ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member > http://people.apache.org/~ilgrosso/ > > > - > 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: Preparing for July report
On 28/06/2012 09:38, David Crossley wrote: > Francesco Chicchiriccò wrote: >> On 28/06/2012 01:48, Jukka Zitting wrote: >>> [...] >>> >>> Speaking of the wiki page, now that the reporting schedule has been >>> migrated from the wiki [2] to the podlings.xml file [3], we >>> unfortunately no longer have the nice per-group listing of podlings >>> that I used for pre-filling the report wiki page. It would be great if >>> someone with XSLT skills could adjust the stylesheet [4] to output a >>> list of the podlings expected to report next month. >> Jukka, >> I've drafted a couple of XSLTs for this need: >> >> 1. podlings-report-per-month.xsl >> taking as input parameter the full name of the month for which you want >> the list of podlings expected to report in that month; this version >> doesn't have any requirement on XSLT processor. >> >> 2. podlings-report-per-month-exslt.xsl >> this will derive next month via EXSLT datetime and output the list of >> podlings expected to report in that month; >> >> Which version would you prefer? >> How should I provide the file(s)? >> How are you going to make this available? Do you need a Cocoon instance? ;-) >> >> Regards. > Sounds great. Note that Seb had already done a simple one. > See http://incubator.apache.org/report-groups.txt > > The XSL is at https://svn.apache.org/repos/asf/incubator/public/trunk > See report-groups.xsl > The CMS magically generates stuff. See the ant "build.xml" > file the with the "report-groups" target. > Follow his svn trail. You might be able to install yours similarly. Hi David, thanks for the info: I've taken a quick look. However, I need to know which version to install and, in case of (2), how the target month parameter can be provided. Regards. >>> [...] >>> [1] http://wiki.apache.org/incubator/July2012 >>> [2] http://wiki.apache.org/incubator/ReportingSchedule >>> [3] http://incubator.apache.org/podlings.xml >>> [4] http://incubator.apache.org/podlings.xsl >>> [5] http://wiki.apache.org/incubator/IncubatorShepherds -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
On 28/06/2012 09:53, Francesco Chicchiriccò wrote: > On 28/06/2012 09:38, David Crossley wrote: >> Francesco Chicchiriccò wrote: >>> On 28/06/2012 01:48, Jukka Zitting wrote: [...] Speaking of the wiki page, now that the reporting schedule has been migrated from the wiki [2] to the podlings.xml file [3], we unfortunately no longer have the nice per-group listing of podlings that I used for pre-filling the report wiki page. It would be great if someone with XSLT skills could adjust the stylesheet [4] to output a list of the podlings expected to report next month. >>> Jukka, >>> I've drafted a couple of XSLTs for this need: >>> >>> 1. podlings-report-per-month.xsl >>> taking as input parameter the full name of the month for which you want >>> the list of podlings expected to report in that month; this version >>> doesn't have any requirement on XSLT processor. >>> >>> 2. podlings-report-per-month-exslt.xsl >>> this will derive next month via EXSLT datetime and output the list of >>> podlings expected to report in that month; >>> >>> Which version would you prefer? >>> How should I provide the file(s)? >>> How are you going to make this available? Do you need a Cocoon instance? ;-) >>> >>> Regards. >> Sounds great. Note that Seb had already done a simple one. >> See http://incubator.apache.org/report-groups.txt >> >> The XSL is at https://svn.apache.org/repos/asf/incubator/public/trunk >> See report-groups.xsl >> The CMS magically generates stuff. See the ant "build.xml" >> file the with the "report-groups" target. >> Follow his svn trail. You might be able to install yours similarly. > Hi David, > thanks for the info: I've taken a quick look. > > However, I need to know which version to install and, in case of (2), > how the target month parameter can be provided. In case of (1), I mean... > Regards. > [...] [1] http://wiki.apache.org/incubator/July2012 [2] http://wiki.apache.org/incubator/ReportingSchedule [3] http://incubator.apache.org/podlings.xml [4] http://incubator.apache.org/podlings.xsl [5] http://wiki.apache.org/incubator/IncubatorShepherds -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
Francesco Chicchiriccò wrote: > David Crossley wrote: > > Francesco Chicchiriccò wrote: > >> Jukka Zitting wrote: > >>> [...] > >>> > >>> Speaking of the wiki page, now that the reporting schedule has been > >>> migrated from the wiki [2] to the podlings.xml file [3], we > >>> unfortunately no longer have the nice per-group listing of podlings > >>> that I used for pre-filling the report wiki page. It would be great if > >>> someone with XSLT skills could adjust the stylesheet [4] to output a > >>> list of the podlings expected to report next month. > >> Jukka, > >> I've drafted a couple of XSLTs for this need: > >> > >> 1. podlings-report-per-month.xsl > >> taking as input parameter the full name of the month for which you want > >> the list of podlings expected to report in that month; this version > >> doesn't have any requirement on XSLT processor. > >> > >> 2. podlings-report-per-month-exslt.xsl > >> this will derive next month via EXSLT datetime and output the list of > >> podlings expected to report in that month; > >> > >> Which version would you prefer? > >> How should I provide the file(s)? > >> How are you going to make this available? Do you need a Cocoon instance? > >> ;-) > >> > >> Regards. > >> > > Sounds great. Note that Seb had already done a simple one. > > See http://incubator.apache.org/report-groups.txt > > > > The XSL is at https://svn.apache.org/repos/asf/incubator/public/trunk > > See report-groups.xsl > > The CMS magically generates stuff. See the ant "build.xml" > > file the with the "report-groups" target. > > Follow his svn trail. You might be able to install yours similarly. > > Hi David, > thanks for the info: I've taken a quick look. > > However, I need to know which version to install and, in case of (2), > how the target month parameter can be provided. Wait, no, i did not mean installing Cocoon. Just showing that Seb has already done a simple job which will keep Jukka going. If people want to add more then follow Seb/Joe clever example of using the Apache CMS in conjunction with Ant to do the processing. -David > Regards. > > >>> [...] > >>> [1] http://wiki.apache.org/incubator/July2012 > >>> [2] http://wiki.apache.org/incubator/ReportingSchedule > >>> [3] http://incubator.apache.org/podlings.xml > >>> [4] http://incubator.apache.org/podlings.xsl > >>> [5] http://wiki.apache.org/incubator/IncubatorShepherds - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
Jukka - I'm happy to do the usual shepherd work but given the fact that you expect some US people to report late (seems reasonable) I need to point out that I will be unable to review reports after July 5th. So any that are assigned to me that come in later than that will need to be reassigned. Thanks Ross On 28 June 2012 00:48, Jukka Zitting wrote: > Hi, > > It's a week until the next podling report deadline on July 4th. > > The day is a probably a bit inconvenient for many people in the US, so > I think we should be prepared for some podlings reporting a bit late > this time. Of course if you already know that you'll be otherwise > occupied at that time there's no stopping a podling submitting its > report already a few days before the deadline. Or alternatively, if > you know your podling can't submit the report in time, you can let us > know by replying here or adding a short note about the delay to the > report wiki page [1]. > > Speaking of the wiki page, now that the reporting schedule has been > migrated from the wiki [2] to the podlings.xml file [3], we > unfortunately no longer have the nice per-group listing of podlings > that I used for pre-filling the report wiki page. It would be great if > someone with XSLT skills could adjust the stylesheet [4] to output a > list of the podlings expected to report next month. > > Finally, I'll assign shepherds for podling reports tomorrow evening > after we list of expected reports in place. Meanwhile please check > that the list of volunteer shepherds [5] is up to date. If you want to > volunteer but aren't on the list yet, feel free to add yourself. And > if you already volunteered but want to resign or take a temporary > break, please update the page accordingly. > > [1] http://wiki.apache.org/incubator/July2012 > [2] http://wiki.apache.org/incubator/ReportingSchedule > [3] http://incubator.apache.org/podlings.xml > [4] http://incubator.apache.org/podlings.xsl > [5] http://wiki.apache.org/incubator/IncubatorShepherds > > BR, > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- 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: Preparing for July report
On 28/06/2012 10:04, David Crossley wrote: > Francesco Chicchiriccò wrote: >> David Crossley wrote: >>> Francesco Chicchiriccò wrote: Jukka Zitting wrote: > [...] > > Speaking of the wiki page, now that the reporting schedule has been > migrated from the wiki [2] to the podlings.xml file [3], we > unfortunately no longer have the nice per-group listing of podlings > that I used for pre-filling the report wiki page. It would be great if > someone with XSLT skills could adjust the stylesheet [4] to output a > list of the podlings expected to report next month. Jukka, I've drafted a couple of XSLTs for this need: 1. podlings-report-per-month.xsl taking as input parameter the full name of the month for which you want the list of podlings expected to report in that month; this version doesn't have any requirement on XSLT processor. 2. podlings-report-per-month-exslt.xsl this will derive next month via EXSLT datetime and output the list of podlings expected to report in that month; Which version would you prefer? How should I provide the file(s)? How are you going to make this available? Do you need a Cocoon instance? ;-) Regards. >>> Sounds great. Note that Seb had already done a simple one. >>> See http://incubator.apache.org/report-groups.txt >>> >>> The XSL is at https://svn.apache.org/repos/asf/incubator/public/trunk >>> See report-groups.xsl >>> The CMS magically generates stuff. See the ant "build.xml" >>> file the with the "report-groups" target. >>> Follow his svn trail. You might be able to install yours similarly. >> Hi David, >> thanks for the info: I've taken a quick look. >> >> However, I need to know which version to install and, in case of (2), >> how the target month parameter can be provided. > Wait, no, i did not mean installing Cocoon. > > Just showing that Seb has already done a simple job which > will keep Jukka going. If people want to add more then > follow Seb/Joe clever example of using the Apache CMS > in conjunction with Ant to do the processing. "I don't know which version to install" was meaning between the two options provided above: don't worry, I didn't mean to install Cocoon only for this :) I am not sure whether it is more handy to have the month report produced based on current date (1) or on provided input parameter, but I interpreted your initial suggestion to replicate what done by Sebb, i.e. ANT-based transformation triggered by someone (the CMS?) on podlings.xml publish. Regards. > [...] > [1] http://wiki.apache.org/incubator/July2012 > [2] http://wiki.apache.org/incubator/ReportingSchedule > [3] http://incubator.apache.org/podlings.xml > [4] http://incubator.apache.org/podlings.xsl > [5] http://wiki.apache.org/incubator/IncubatorShepherds -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Stanbol Entityhub 0.10.0-incubating
Hi, please vote for releasing Apache Stanbol 0.10.0-incubating (RC3). This release has already passed the PPMC vote [1] with +1 : 4 votes (including 3 PPMC votes and 1 IPMC vote) 0 : 0 votes -1 : 0 votes So, we need at least 2 more votes from IPMC members. [1] http://markmail.org/thread/grjbimzq4x77o37e The release consists of the following components, fixing the listed issues. When verifying the release, you have to build the components in the given order because of dependencies. - source-assembly-0.10.0-incubating-source-release.zip MD5 8ce4336700b3967c210f406f0dcc618e fixed issues: * [STANBOL-645] - Rename source release assembly descriptor * [STANBOL-640] - Create Stanbol source release assembly descriptor - stanbol-parent-1-incubating-source-release.zip MD5 19d29a59b3e1eb324feb0f2ba5b8be27 fixed issues: * [STANBOL-553] - Remove dependency management for org.apache.stanbol components from parent POM * [STANBOL-666] - Missing DISCLAIMER file in artifacts - org.apache.stanbol.commons.solr.core-0.10.0-incubating-source-release.zip MD5 e5a51b7df302896203b590d2dbf6841c fixed issues: * [STANBOL-606] - Language prefixes are added to non TextConstraint in queries for the Entityhub - org.apache.stanbol.commons.web.base-0.10.0-incubating-source-release.zip MD5 c2d5ca5bf5c058577a38453a48e89376 fixed issues: * [STANBOL-555] - Remove test dependency of commons.web.base to enhancer.servicesapi * [STANBOL-606] - Language prefixes are added to non TextConstraint in queries for the Entityhub * [STANBOL-607] - SolrYard should use quotes instead of AND for multi word TextConstraints - org.apache.stanbol.data.parent-0.10.0-incubating-source-release.zip MD5 3134e99eb72f3bb0bf5ea46e9c2d627f fixed issues: * [STANBOL-637] - Build warns for downloaded OpenNLP models when instead a DBPedia index is downloaded - org.apache.stanbol.data.sites.dbpedia-1.0.4-incubating-source-release.zip MD5 e66249489c978e8305f68340c337890b fixed issues: * [STANBOL-638] - Make DBPedia data bundle releaseable - apache-stanbol-entityhub-0.10.0-incubating-source-release.zip MD5 1741c62f4850d5c3b00a962112c6a2dd fixed issues: * [STANBOL-590] - LDPath processor operating on the IndexingSource and Implementation for the JenaTDB based indexing source. * [STANBOL-592] - LDPath processor operating on the IndexingDestination in the post-processing phase * [STANBOL-598] - Support Reconciliation properties on the full text field of entities * [STANBOL-599] - Support Reconcilliation properties on the semantic context * [STANBOL-568] - Entityhub indexing tool is not able to initialise if the path contains a space * [STANBOL-606] - Language prefixes are added to non TextConstraint in queries for the Entityhub * [STANBOL-610] - Indexing Directory parameter does not work for the genericrdf Indexing Tool * [STANBOL-616] - Wrong CORS Response * [STANBOL-654] - The SolrYard does not correcly enclose multi word query terms in quotes * [STANBOL-589] - Allow usage of SimilarityConstraints via the RESTful API of the Entityhub * [STANBOL-595] - Add support for ValueConstraints with multiple values * [STANBOL-600] - Update the namespaces used by the Entityhub to stanbol.apache.org URIs * [STANBOL-607] - SolrYard should use quotes instead of AND for multi word TextConstraints * [STANBOL-556] - LdPath processor for Entityhub Indexing * [STANBOL-591] - Add support for post-processing to the Entityhub Indexing Tool * [STANBOL-593] - EntityIterator implementation based on Jena TDB that allows to filter Entities based on Triple Filters * [STANBOL-594] - Google Refine Reconciliation Service support * [STANBOL-596] - Add support for full text searches to FieldQuery * [STANBOL-597] - Add support for semantic context queries to FieldQuery The released artifacts can be downloaded from the staging repository: https://repository.apache.org/content/repositories/orgapachestanbol-257 Keys are at: http://www.apache.org/dist/incubator/stanbol/KEYS Please note, that the staging repository also contains additional Maven artifacts and binaries of the Entityhub (and of the other components). However, the source release of the Entityhub is located in the 'apache-stanbol-entityhub-0.10.0-incubating' folder. The Maven artifacts and binaries are only deployed for convenience and were automatically created from the source release. The source release packages to verify are always named '*.source-release.[zip|tar.gz]'. To check and verify the release, you can use two utility scripts that are available in the Apache Stanbol SVN trunk [2]. Usage: $ check_staged_release.sh 257 /tmp $ check_release_matches_tag.sh 257 /tmp [2] https://svn.apache.org/repos/asf/incubator/stanbol/trunk/ This vote is open for at least 72 hours. Best, - Fabian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional com
Re: [VOTE] Retire Kato
+1... I'd say at least the normal 72 hours. On Jun 26, 2012, at 7:29 PM, Benson Margulies wrote: > Based on the status of this podling as reported in the June board > report, I propose that the IPMC retire the Kato podling. > > I'm not sure how long a vote for this should remain open. > > here is my +1. > > - > 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: svn commit: r1354971 - /incubator/public/trunk/content/guides/graduation.xml
On 28 June 2012 13:12, wrote: > Author: twilliams > Date: Thu Jun 28 12:12:43 2012 > New Revision: 1354971 > > URL: http://svn.apache.org/viewvc?rev=1354971&view=rev > Log: > typo > > Modified: > incubator/public/trunk/content/guides/graduation.xml > > Modified: incubator/public/trunk/content/guides/graduation.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/graduation.xml?rev=1354971&r1=1354970&r2=1354971&view=diff > == > --- incubator/public/trunk/content/guides/graduation.xml [utf-8] (original) > +++ incubator/public/trunk/content/guides/graduation.xml [utf-8] Thu Jun 28 > 12:12:43 2012 > @@ -72,7 +72,7 @@ > > > > - The road to graduation pretty clear: depending on wether your > + The road to graduation pretty clear: depending on whether > your Missing verb in first phrase? > project wants to become a top level project, or join as a > subproject under an already existing project the steps are > fairly simple but do take time and effort. This document > > > > - > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1354971 - /incubator/public/trunk/content/guides/graduation.xml
On Thu, Jun 28, 2012 at 8:38 AM, sebb wrote: > On 28 June 2012 13:12, wrote: >> Author: twilliams >> Date: Thu Jun 28 12:12:43 2012 >> New Revision: 1354971 >> >> URL: http://svn.apache.org/viewvc?rev=1354971&view=rev >> Log: >> typo >> >> Modified: >> incubator/public/trunk/content/guides/graduation.xml >> >> Modified: incubator/public/trunk/content/guides/graduation.xml >> URL: >> http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/graduation.xml?rev=1354971&r1=1354970&r2=1354971&view=diff >> == >> --- incubator/public/trunk/content/guides/graduation.xml [utf-8] (original) >> +++ incubator/public/trunk/content/guides/graduation.xml [utf-8] Thu Jun 28 >> 12:12:43 2012 >> @@ -72,7 +72,7 @@ >> >> >> >> - The road to graduation pretty clear: depending on wether >> your >> + The road to graduation pretty clear: depending on whether >> your > > Missing verb in first phrase? I was actually fixing the "wether" mispelling - I didn't even catch that one:) --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Syncope 1.0.0-RC2-incubating
Hi All, I've created a 1.0.0-RC2-incubating release, with the following artifacts up for a vote: SVN source tag (r1353427): https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-RC2-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-272/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-272/org/apache/syncope/syncope-root/1.0.0-RC2-incubating/syncope-root-1.0.0-RC2-incubating-source.tar.gz https://repository.apache.org/content/repositories/orgapachesyncope-272/org/apache/syncope/syncope-root/1.0.0-RC2-incubating/syncope-root-1.0.0-RC2-incubating-source.zip Staging site: http://incubator.apache.org/syncope/1.0.0-RC2-incubating/ PGP release keys (signed using B1F055C1): http://www.apache.org/dist/incubator/syncope/KEYS This has been voted through on the syncope-...@incubator.apache.org mailing list [1], and now requires a vote on general@incubator.apache.org Votes already cast (on syncope-dev): +1 (PPMC / binding) * Francesco Chicchiriccò * Fabio Martelli * Massimiliano Perrone * Colm O hEigeartaigh (IPMC member) * Emmanuel Lécharny (IPMC member) +1 (non binding) none 0 none -1 none Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Best regards. F. [1] http://syncope-dev.1063484.n5.nabble.com/VOTE-Apache-Syncope-1-0-0-RC2-incubating-td5709897.html
Re: Preparing for July report
Hi, On Thu, Jun 28, 2012 at 9:38 AM, David Crossley wrote: > Note that Seb had already done a simple one. > See http://incubator.apache.org/report-groups.txt Thanks! I missed that one. I've now added placeholders for all incoming podling reports and assigned shepherds as follows: * Benson Margulies - Chukwa, DirectMemory, Mesos * Dave Fisher - Any23, EasyAnt * Jukka Zitting- AWF, JSPWiki, Tashi * Matt Franklin- Celix, Kafka, VXQuery * Matt Hogstrom- DeviceMap, Oozie * Mohammad Nour- Kitty * Ross Gardler - ODF Toolkit I decided to leave the podlings that are still getting started (Allura, CloudStack, Crunch and cTAKES) without shepherds since they're unlikely to exhibit the issues that the shepherd model has so far been most useful in addressing. Of course anyone is still welcome to review their reports and provide feedback where needed. That left us with 15 podling reports that I distributed among the seven volunteer shepherds based on the expressed interests, the number of podlings they're mentoring and other available constraints. The result is 1-3 reports to review per shepherd. Let me know if any updates or changes are needed. And as usual, anyone is of course very much welcome to participate in the report-review-feedback loop! PS. Ross, the ODF Toolkit report got already submitted, so no need to worry about a potentially late report. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
Hi, On Thu, Jun 28, 2012 at 9:04 AM, Francesco Chicchiriccò wrote: > I've drafted a couple of XSLTs for this need: Great! > 2. podlings-report-per-month-exslt.xsl > this will derive next month via EXSLT datetime and output the list of > podlings expected to report in that month; This seems pretty powerful! Could you also make the script include not just the podling names, but also their descriptions, current mentors and whether a podling is just starting (first three months in Incubator)? Those are the key details I'm currently using when assigning shepherds. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Preparing for July report
Hi, On Thu, Jun 28, 2012 at 1:48 AM, Jukka Zitting wrote: > It's a week until the next podling report deadline on July 4th. Podlings, when preparing your reports, please pay special attention to the things you've done (and/or plan to do) to resolve the key issues identified in April [1]: No release: Any23, DirectMemory, JSPWiki, Mesos Low activity: AWF, Celix, EasyAnt, Kitty, VXQuery Low diversity: Chukwa, Kafka, ODF Toolkit, Oozie, Tashi I'm looking forward to reading plenty of reports that show progress towards graduation! :-) [1] http://wiki.apache.org/incubator/April2012 BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
David Crossley wrote: > > Sorry Rich, that extra information in the "mailing lists" section > cannot be parsed by Clutch. Perhaps move it to the "News" section. In fact it did handle it as-is. Anyway the News section is still useful to encourage your community about progress. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
On Jun 28, 2012 3:26 AM, "David Crossley" wrote: > > David Crossley wrote: > > Sorry Rich, that extra information in the "mailing lists" section > > cannot be parsed by Clutch. Perhaps move it to the "News" section. > > Also, the "tracker" is the eventual ASF tracker that is intended. There is no requirement to run the issue tracker on ASF hardware, so the link to SF.net is just fine. Only source control *must* be on ASF hardware. The rest is merely advised, but left to communities. Cheers, -g
Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
Greg Stein wrote: > David Crossley wrote: > > > > Also, the "tracker" is the eventual ASF tracker that is intended. > > There is no requirement to run the issue tracker on ASF hardware, so the > link to SF.net is just fine. Ah sorry, i assumed that they were intending to move it. -David > Only source control *must* be on ASF hardware. > > The rest is merely advised, but left to communities. > > Cheers, > -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
On Jun 28, 2012 9:18 PM, "David Crossley" wrote: > > Greg Stein wrote: > > David Crossley wrote: > > > > > > Also, the "tracker" is the eventual ASF tracker that is intended. > > > > There is no requirement to run the issue tracker on ASF hardware, so the > > link to SF.net is just fine. > > Ah sorry, i assumed that they were intending to move it. Goal is to self-host tracking/wiki/etc in an Allura instance in a VM. Necessarily, though... that entails some Infra discussion and planning. Until that is figured out, the supporting project facilities can hang out on SF.net. Cheers, -g
