Re: GSoC 2015 with Apache any23
Great Nisala, I had a quick look at your latest commit and you did a very good catch. Thanks for the refactoring. Best Michele On 28 June 2015 at 19:20, Nisala Mendis nisal...@gmail.com wrote: hi michele, i have made changes according to your instructions and added feather test cases.[1] added another weekly report to the wiki. i already started implementing rest of the microformats2 extractors. [1] https://github.com/nisalanirmana/any23/commits/gsoc_2015 On Mon, Jun 22, 2015 at 2:07 PM, Nisala Mendis nisal...@gmail.com wrote: Hi Michele, I must really thankful for you taking time to review my work. Thanks for the suggestions too, I will improve my code and try to write code as much as generic possible using identifying prefixes. Thanks again. Regards Nisala On Mon, Jun 22, 2015 at 1:36 PM, Michele Mostarda michele.mosta...@gmail.com wrote: Hi All, On 22 June 2015 at 04:12, Nisala Mendis nisal...@gmail.com wrote: Hi all, Here with I have attached a detailed analysis of diference between microfrmats 1 and 2. see this link [1]. As a sample I have implemented extractors HAdr and HGeo with relavant unit test cases. According to the Microformats 2 spec HAdr can have HGeo as a nested property. I have includes the sample test cases to cover this scenario. See my fork under gsoc_2015 branch [2] please see the recent commit added HAdr and HGeo Extractors support. I can basically cover the rest of the using this approach. I am expecting a feedback so that I can move forward. Also note I have added week 2 and week 3 reports to the wiki [1] https://docs.google.com/document/d/17DXcr8jv7D41FOuR1Rba0Ex-4VVheMNInmBSygkih5E/edit?usp=sharing Really interesting report, I added a small comment on it. [2] https://github.com/nisalanirmana/any23/commits/gsoc_2015 core/src/main/java/org/apache/any23/extractor/html/microformats2/HAdrExtractor.java Quick suggestion based on a really superficial analysis of your code: isn't better to write a general logic to manage property extraction based on the identification of prefixes? First identify a node h-* and then identify children p-* u-*, dt-* and so on. You would write less, more robust and more maintainable code. regards,nisala Best Michele On Monday, June 15, 2015, Michele Mostarda michele.mosta...@gmail.com wrote: Great job Nisala! Best Michele On 13 June 2015 at 20:28, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Excellent Nisala. I committed your patch and your report looks good for now I am making some comments. Lewis On Mon, Jun 8, 2015 at 10:36 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, Please note that I have added week 1 report and added a comment attached patch to the jira[1]. [1]https://issues.apache.org/jira/browse/ANY23-185 Regards Nisala On Mon, Jun 1, 2015 at 12:45 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code#GoogleSummerofCode-ProjectReports On Sun, May 31, 2015 at 12:09 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Nisala, On Sun, May 31, 2015 at 11:10 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, I really apologize for not sending any updates via private mails, I had uploaded my proposal already even before the GSoC selection period, Once again I apologize for not informing you by mail this since I assumed you noticed it. Thanks for the update and no problems at all. It was just a bit concerning that around a month had gone by and we hadn't heard from you :) I started working things bit out waited to give you an update some concrete work. You can find my proposal in [1]. [1] https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code I've added a section for your reports. Please begin to populate the page based upon anything you've been doing. Thank you for writing to us, it's very much appreciated. Lewis -- *Lewis* -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it
Re: GSoC 2015 with Apache any23
Hi All, On 22 June 2015 at 04:12, Nisala Mendis nisal...@gmail.com wrote: Hi all, Here with I have attached a detailed analysis of diference between microfrmats 1 and 2. see this link [1]. As a sample I have implemented extractors HAdr and HGeo with relavant unit test cases. According to the Microformats 2 spec HAdr can have HGeo as a nested property. I have includes the sample test cases to cover this scenario. See my fork under gsoc_2015 branch [2] please see the recent commit added HAdr and HGeo Extractors support. I can basically cover the rest of the using this approach. I am expecting a feedback so that I can move forward. Also note I have added week 2 and week 3 reports to the wiki [1] https://docs.google.com/document/d/17DXcr8jv7D41FOuR1Rba0Ex-4VVheMNInmBSygkih5E/edit?usp=sharing Really interesting report, I added a small comment on it. [2] https://github.com/nisalanirmana/any23/commits/gsoc_2015 core/src/main/java/org/apache/any23/extractor/html/microformats2/HAdrExtractor.java Quick suggestion based on a really superficial analysis of your code: isn't better to write a general logic to manage property extraction based on the identification of prefixes? First identify a node h-* and then identify children p-* u-*, dt-* and so on. You would write less, more robust and more maintainable code. regards,nisala Best Michele On Monday, June 15, 2015, Michele Mostarda michele.mosta...@gmail.com wrote: Great job Nisala! Best Michele On 13 June 2015 at 20:28, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Excellent Nisala. I committed your patch and your report looks good for now I am making some comments. Lewis On Mon, Jun 8, 2015 at 10:36 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, Please note that I have added week 1 report and added a comment attached patch to the jira[1]. [1]https://issues.apache.org/jira/browse/ANY23-185 Regards Nisala On Mon, Jun 1, 2015 at 12:45 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code#GoogleSummerofCode-ProjectReports On Sun, May 31, 2015 at 12:09 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Nisala, On Sun, May 31, 2015 at 11:10 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, I really apologize for not sending any updates via private mails, I had uploaded my proposal already even before the GSoC selection period, Once again I apologize for not informing you by mail this since I assumed you noticed it. Thanks for the update and no problems at all. It was just a bit concerning that around a month had gone by and we hadn't heard from you :) I started working things bit out waited to give you an update some concrete work. You can find my proposal in [1]. [1] https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code I've added a section for your reports. Please begin to populate the page based upon anything you've been doing. Thank you for writing to us, it's very much appreciated. Lewis -- *Lewis* -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it
Re: GSoC 2015 with Apache any23
Great job Nisala! Best Michele On 13 June 2015 at 20:28, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Excellent Nisala. I committed your patch and your report looks good for now I am making some comments. Lewis On Mon, Jun 8, 2015 at 10:36 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, Please note that I have added week 1 report and added a comment attached patch to the jira[1]. [1]https://issues.apache.org/jira/browse/ANY23-185 Regards Nisala On Mon, Jun 1, 2015 at 12:45 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code#GoogleSummerofCode-ProjectReports On Sun, May 31, 2015 at 12:09 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Nisala, On Sun, May 31, 2015 at 11:10 AM, Nisala Mendis nisal...@gmail.com wrote: Hi Lewis, I really apologize for not sending any updates via private mails, I had uploaded my proposal already even before the GSoC selection period, Once again I apologize for not informing you by mail this since I assumed you noticed it. Thanks for the update and no problems at all. It was just a bit concerning that around a month had gone by and we hadn't heard from you :) I started working things bit out waited to give you an update some concrete work. You can find my proposal in [1]. [1] https://cwiki.apache.org/confluence/display/ANY23/Google+Summer+of+Code I've added a section for your reports. Please begin to populate the page based upon anything you've been doing. Thank you for writing to us, it's very much appreciated. Lewis -- *Lewis* -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda phone: +39 327 01 86 259 twitter: micmos email: m...@michelemostarda.it website: http://michelemostarda.it
[jira] [Created] (ANY23-254) Demo frontend should provide interactive CLI usage examples
Michele Mostarda created ANY23-254: -- Summary: Demo frontend should provide interactive CLI usage examples Key: ANY23-254 URL: https://issues.apache.org/jira/browse/ANY23-254 Project: Apache Any23 Issue Type: Improvement Reporter: Michele Mostarda Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ANY23-202) Add analytics on any23.org landing page
[ https://issues.apache.org/jira/browse/ANY23-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343014#comment-14343014 ] Michele Mostarda commented on ANY23-202: The privacy is not guaranteed anyway, we could even watch at the content of the data sent to the demo service (despite we don't obviously). The collected informations are for the entire community, I will add you as manager and I invite you to understand how to share the more information as possible to the community, like understanding if it is possible to publish such data via a public widget. I just added the privacy policy. Because as far as I know individuals can be added singularly. If you know a better approach to this solution please suggest. Other Apache projects use the same tracker into their pages, anyway I found them in documentation pages not in demo ones. Add analytics on any23.org landing page --- Key: ANY23-202 URL: https://issues.apache.org/jira/browse/ANY23-202 Project: Apache Any23 Issue Type: Improvement Components: service Reporter: Michele Mostarda Assignee: Michele Mostarda Priority: Minor Fix For: 1.2 I would be helpful to collect usage statistics of the online service to measure project visibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ANY23-202) Add analytics on any23.org landing page
[ https://issues.apache.org/jira/browse/ANY23-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343004#comment-14343004 ] Michele Mostarda commented on ANY23-202: Ok, added disclaimer in README, centralized ID configuration and instructions to disable the tracker. https://github.com/apache/any23/commit/304e9d442af0089a82db925f0a746279970eab0c Add analytics on any23.org landing page --- Key: ANY23-202 URL: https://issues.apache.org/jira/browse/ANY23-202 Project: Apache Any23 Issue Type: Improvement Components: service Reporter: Michele Mostarda Assignee: Michele Mostarda Priority: Minor Fix For: 1.2 I would be helpful to collect usage statistics of the online service to measure project visibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ANY23-202) Add analytics on any23.org landing page
[ https://issues.apache.org/jira/browse/ANY23-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343018#comment-14343018 ] Michele Mostarda commented on ANY23-202: Meanwhile some useful references: https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+Privacy+Policy https://www.google.com/webhp?ie=UTF-8#q=site%3Aapache.org%20google%20analytics Add analytics on any23.org landing page --- Key: ANY23-202 URL: https://issues.apache.org/jira/browse/ANY23-202 Project: Apache Any23 Issue Type: Improvement Components: service Reporter: Michele Mostarda Assignee: Michele Mostarda Priority: Minor Fix For: 1.2 I would be helpful to collect usage statistics of the online service to measure project visibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ANY23-249) Update all W3C and other Standards Compliance within Any23
[ https://issues.apache.org/jira/browse/ANY23-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324016#comment-14324016 ] Michele Mostarda commented on ANY23-249: I completely agree. Do you need help to write the GSoC proposal? Update all W3C and other Standards Compliance within Any23 -- Key: ANY23-249 URL: https://issues.apache.org/jira/browse/ANY23-249 Project: Apache Any23 Issue Type: Improvement Components: api, core, extractors, microdata, nquads Reporter: Lewis John McGibbney Labels: gsoc2015 Fix For: 1.3 [~michele.mostarda] and [~lewismc] have been [discussing|http://www.mail-archive.com/dev%40any23.apache.org/msg01517.html] what would work well for an Any23 Google Summer of Code Project for 2015. It turns out that in order to rebuild confidence with the Any23 standards compliance (in light of new W3c standards which may be emerged or advanced) an in light of new non-W3C emerging standards such as [microformats2|http://microformats.org/wiki/microformats-2] it would be a very worthwhile effort to have one or more student(s) engage on * initially evaluating all of the existing standards compliance within Any23 * uncovering which aspects of the compiled list require attention e.g. updating, overhauling, re-implementation, extension or otherwise * progress on executing the above under supervision of one or more of the assigned mentors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ANY23-202) Add analytics on any23.org landing page
[ https://issues.apache.org/jira/browse/ANY23-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Mostarda resolved ANY23-202. Resolution: Fixed Closed at cab71ae64a6b3fa0ce01ff8c11464ed1f802f43d Added also lewis.mcgibb...@gmail.com as tracker administrator. Add analytics on any23.org landing page --- Key: ANY23-202 URL: https://issues.apache.org/jira/browse/ANY23-202 Project: Apache Any23 Issue Type: Improvement Components: service Reporter: Michele Mostarda Priority: Minor Fix For: 1.2 I would be helpful to collect usage statistics of the online service to measure project visibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ANY23-249) Update all W3C and other Standards Compliance within Any23
[ https://issues.apache.org/jira/browse/ANY23-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316364#comment-14316364 ] Michele Mostarda commented on ANY23-249: Microdata extractor is still at version written at 2011 (specification still in beta) while the latest specification has been updated at 2013 [1]. Verification needed. RDFa1.1 core also has been written in 2011 but latest specification is of 2013, also this requires verification. [1] http://www.w3.org/TR/microdata/ [2] http://www.w3.org/TR/rdfa-core/ Update all W3C and other Standards Compliance within Any23 -- Key: ANY23-249 URL: https://issues.apache.org/jira/browse/ANY23-249 Project: Apache Any23 Issue Type: Bug Components: api, core, extractors, microdata, nquads Reporter: Lewis John McGibbney Labels: gsoc2015 Fix For: 1.3 [~michele.mostarda] and [~lewismc] have been [discussing|http://www.mail-archive.com/dev%40any23.apache.org/msg01517.html] what would work well for an Any23 Google Summer of Code Project for 2015. It turns out that in order to rebuild confidence with the Any23 standards compliance (in light of new W3c standards which may be emerged or advanced) an in light of new non-W3C emerging standards such as [microformats2|http://microformats.org/wiki/microformats-2] it would be a very worthwhile effort to have one or more student(s) engage on * initially evaluating all of the existing standards compliance within Any23 * uncovering which aspects of the compiled list require attention e.g. updating, overhauling, re-implementation, extension or otherwise * progress on executing the above under supervision of one or more of the assigned mentors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Any23 GSoC
Added couple of notes about RDFa and Microdrata extractors in Jira issue. Mic On 11 February 2015 at 15:51, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Peter, On Wed, Feb 11, 2015 at 3:34 AM, dev-digest-h...@any23.apache.org wrote: Sergio has been arranging for an Apache licenced Sesame-compatible HDT implementation to be created, as part of a GSOC, and I suggested that either Marmotta or Any23 would be good areas for that, with me as a likely mentor for it. https://issues.apache.org/jira/browse/MARMOTTA-593 I am very interested in compressed serde formats and this suggestion is by no means no exception. It looks like a really interesting project. I think it would be excellent if we could leverage this within Any23 if it was made available as a consumable artifact(s). Thank you for the heads up Peter, I am watching the issue. Lewis -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com
Re: Context Aware Extraction
Hi Folks, Any23 has been already prepared for the extraction context, see org.apache.any23.extractor.ExtractionResult org.apache.any23.extractor.ExtractionContext And the main extractors already add information about the position of extracted triples in pages and the nesting relationship of extracted subgraphs. The most part of this information ATM can be accessed activating the Annotate flag which include such information within comments. The missing part is the inclusion of this information in RDF renderization. Best Michele On 6 June 2014 15:30, Giovanni Tummarello g.tummare...@gmail.com wrote: the main motivation for this is to make sure data is really relevant and is put together HTML elements (e.g. like scraping) with metadata. Sometime one has a metadata description (e.g. name) but not the phone number which is just in html. how about a Json output that a configurably large surrounding html but also the triples e.g. in standardized/normalized as much as possible json LD ? i think this could be useful to better understand web pages but you're right with you point 3) i personally dont have any specific need just now so wouldnt feel like pushing for develoment this direction just yet Gio On Fri, Jun 6, 2014 at 11:51 AM, Szymon Danielczyk danielczyk.szy...@gmail.com wrote: Hi Lewis, Guys Just to understand this better. Does this mean that if some info was extracted from http://example.org/path let say from head section of the page A) the graph part become http://example.org/path#head but if from let say html5 article tag it will be http://example.org/path#article B) Or it is more like s p o http://example.org/path . s hasContext http://example.org/path#context http://example.org/path . http://example.org/path#context foundInside html/head http://example.org/path . http://example.org/path#context foundAtDate 01-May-2014 http://example.org/path . http://example.org/path#context foundBy http://example.org/path . etc .. I would like ask: 1) Where you thinking more like A or B approach ? 2) what tags will this feature support, maybe some subset like body,head plus some of the new html5 ones: article, aside, header, footer etc. ? or maybe you thought of giving the full xpath to the section like html/body/article/div[1] 3) Did you guys thought about some practical use case already ? How this information could be useful to someone ? Cheers Szymon On 6 June 2014 00:35, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Folks, Giovanni and myself were recently discussing the concept of context-aware triples extraction. An example of this would be the 'where' the triples came from (within the WebPage) as well as the triple itself. This of course bares close resemblance to N-Quads, however we substitute the additional graph constituent with the 'context' one suggested above. Does anyone have comments and/or suggestions on how we could implement a context-aware extractor model/API on top of what we currently have? Lewis -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: RoadMap for Any23 1.0 Release
Hi Lewis, as I replied on the issue, I was thinking to add a google analytics script into the Any23 frontend page to track all the user activity, provenance and other page usage statistics. Best Michele On 1 May 2014 08:32, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Michele, On Mon, Apr 28, 2014 at 3:54 PM, dev-digest-h...@any23.apache.org wrote: I agree, a newer version of the RDFa parser is a must for the project. I also would suggest ANY23-202 for the 1.0 release (add analytics to the landing page). Please see my comments on this issue. wdyt? Thanks Lewis -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: [VOTE] Apache Any23 Release 1.0
+1 and good luck Best Michele On 13 May 2014 21:05, Davide Palmisano dpalmis...@gmail.com wrote: +1 and sincere thanks Lewis for finalising this release! On Tue, May 13, 2014 at 7:33 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Folks, I apologize for taking a while to get this release candidate together. I found some bus in Maven plugins and it took a while to debug where they were and which aspects of the release procedure they affected. Now however it is fixed so that is all good. Please VOTE below on releasing Apache Any23 1.0 (notice the jump from 0.9.1 -- 1.0). This will represent a MAJOR release for Any23. We solved N issues: *http://s.apache.org/Ull http://s.apache.org/Ull* Git source tag (aae5baf3eb28e9c4bdffdbb4eab69ec012dc11a0): *http://s.apache.org/O4S http://s.apache.org/O4S* Staging repo: https://repository.apache.org/content/repositories/orgapacheany23-1000/ Staging artifacts: https://dist.apache.org/repos/dist/dev/any23/1.0/ PGP release keys (signed using 48BAEBF6): https://dist.apache.org/repos/dist/dev/any23/KEYS I would like to keep the vote open for at least 72 hours. Thank you to everyone who is able to review this release candidate. Thank you also to EVERYONE who has been monitoring, contributing towards and using Apache Any23. The 1.0 release candidate signifies a major step forward for the project and we are on the way up again :) [ ] +1, let's get it rmblee!!! [ ] +/-0, fine, but consider to fix few issues before... [ ] -1, nope, because... (and please explain why) p.s. Here's my +1 -- Davide Palmisano http://davidepalmisano.com http://twitter.com/dpalmisano -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: RoadMap for Any23 1.0 Release
On 26 April 2014 22:59, Lewis John Mcgibbney lewis.mcgibb...@gmail.comwrote: Hi, OK I've gone ahead and pushed on a number of issues to 1.1. I propose to release 1.0 once the RDFa proposal is pulled in... I'll get around to this beginning of next week hopefully as I've had little time recently. I agree, a newer version of the RDFa parser is a must for the project. I also would suggest ANY23-202 for the 1.0 release (add analytics to the landing page). Best Michele You can see the 1.0 and 1.1 road map's respectivley here *http://s.apache.org/Ugmi* http://s.apache.org/Ugmi Thanks Lewis On Thu, Apr 17, 2014 at 3:26 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Folks, I think it would be great to get a release of Any23 1.0. This involves bumping all artifacts to major release 1.0 as oppose to 0.9.1 which we are currently sitting at. I would really like for us to pull in the work done on ANY23-137 https://issues.apache.org/jira/browse/ANY23-137 Any comments? Best Lewis -- *Lewis* -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: [VOTE] Change Apache Any23 Project Chair
+1 for me. Best Michele On 17 March 2014 10:55, Lewis John Mcgibbney lewis.mcgibb...@gmail.comwrote: Good Afternoon, In the intentions of moving on the Any23 project I am opening a VOTE thread to propose myself as project chair to take over from where Michele has got us to. His work (amongst others') in getting the Any23 codebase first into, then on towards graduation from the Apache Incubator has ensured that we were able to make subsequent releases ensuring that Any23 becomes a better open source product for the masses. I personally feel slightly uncomfortable with proposing this VOTe myself, however it is with Any23 and the community in mind that I do so. Thanks Michele for your work to date. So I therefore propose the following VOTE and propose the following resolution which we will pass to the board upon election of a new PMC Chair. ## Resolution to change the chair of a project A. Change the Apache Any23 Project Chair WHEREAS, the Board of Directors heretofore appointed Michele Mostarda to the office of Vice President, Apache Any23, and WHEREAS, the Board of Directors is in receipt of the resignation of Michele Mostarda from the office of Vice President, Apache Foo, and WHEREAS, the Project Management Committee of the Apache Foo project has chosen by vote to recommend Lewis John McGibbney as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Michele Mostarda is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Any23, and BE IT FURTHER RESOLVED, that Lewis John Mcibbney be and hereby is appointed to the office of Vice President, Apache Any23, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. [ ] +1 I agree with the above [ ] +0 I really don't care [ ] -1 I do not agree with the above (please state reason) Thanks in advance folks Best Lewis -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: [DISCUSS] Next Steps
Hi everybody, sorry for delay. I'm onboard again and I would like to be operative ASAP. I suggest to have a skype call with you Lewis next week to quickly update my view and be more effective. The we can write a post to propose next actions. Is it ok for you? Best Michele On 21 November 2013 18:53, Lewis John Mcgibbney lewis.mcgibb...@gmail.comwrote: Hi Gio, On Thu, Nov 21, 2013 at 5:29 PM, dev-digest-h...@any23.apache.org wrote: i have discussed internally, yes the project is interesting and we will be putting efforts from Michele Mostarda, they cannot be full time efforts however, but more like 1-2 days a week according to other projects This is good, actually great to hear :) The way I see this working is for us (Any23 dev user community) to initiate a serious discussion on what parts of Any23 we are proposing to move in to Tika... then approach dev@tika with a draft proposal. The reason I propose this is that there is no way one or two of us can go ahead and propose a bulk patch for integration into Tika... they will not accept it + there are better ways of going about it. I'm going to have a look at both trunk codebases over the weekend and begin putting something together. I'll write to this thread over the weekend folks. Thanks Lewis -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: move to git
+1 Mic On 10 February 2013 17:59, Lewis John Mcgibbney lewis.mcgibb...@gmail.comwrote: Hi all, There didn't seem to be any objection regarding the git convo Iinitiated last week. I wonder if (given that on a per contribution basis) we should move to git as the primary repository for any23 code? If it is a problem for even for pmc members never mind developers contributing then this should be recognised, discussed and addressed. -- *Lewis* -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
Re: Patches for any23
Dear Richard, thanks a lot for your support. The best way to submit a patch is to open an issue on the any23 issue tracker[1] (anybody can register) describing the bugs fixed / features implemented and attach the patch file(s). The best solution would be to have atomic patches, one for any bug fixed and feature added so to speed up the integration process. The best. Michele [1] https://issues.apache.org/jira/browse/ANY23 On 8 November 2012 13:34, RICHARD Sébastien sebastien.rich...@3ds.comwrote: Hello, I used lately any23 and fixed some bugs and added some functionalities to it: Microdata: _ fixed extraction for embedded objects _ added a list of prop containing url to disambiguate between href attribute and content for a tags Microformats: _ added HReviewAggregate extractor _ handled value-title class name What is the best way to submit my patches ? Regards, Sebastien This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged. If you are not one of the named recipients or have received this email in error, (i) you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this email and all attachments, (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email. For other languages, go to http://www.3ds.com/terms/**email-disclaimerhttp://www.3ds.com/terms/email-disclaimer -- Michele Mostarda Senior Software Engineer skype: michele.mostarda twitter: micmos mail: m...@michelemostarda.com site : http://www.michelemostarda.com
