Re: [Vote] accept Droids into incubation
+1 On Oct 2, 2008, at 4:00 PM, Thorsten Scherler wrote: Please vote on accepting Droids into incubation. The proposal can be found at: http://wiki.apache.org/incubator/DroidsProposal The text of the proposal = Droids, an intelligent standalone robot framework = === Abstract === Droids aims to be an intelligent standalone robot framework that allows to create and extend existing droids (robots). === Proposal === As a standalone robot framework Droids will offer infrastructure code to create and extend existing robots. In the future it will offer as well a web based administration application to manage and controll the different droids which will communicate with this app. Droids makes it very easy to extend existing robots or write a new one from scratch, which can automatically seek out relevant online information based on the user's specifications. Since the flexible design it can reuse directly all custom business logic that are written in java. In the long run it should become umbrella for specialized droids that are hosted as sub-projects. Where an ultimate goal is to integrate an artificial intelligence that can control a swarm of droids and actively plan/react on different tasks. === Background === The initial idea for the Droids project was voiced in February 2007 from Thorsten Scherler mainly because of personal curiosity and developed as a labs project. The background of his work was that Cocoon trunk (2.2) did not provide a crawler anymore and Forrest was based on it, meaning we could not update anymore till we found a crawler replacement. Getting more involved in Solr and Nutch he saw the request for a generic standalone crawler. For the first version he took nutch, ripped out and modified the plugin/extension framework. However the second version were not based on it anymore but was using Spring instead. The main reason was that Spring has become a standard and helped to make Droids as extensible as possible. Soon the first plugins and sample droids had been added to the code based. === Rationale === There is ever more demand for tools that automatically do determinate tasks. Search engines such as Nuts are normally very focused on a specific functionality and are not focused on extensibility. Furthermore there are manly focused on crawling, requesting certain pages and extract links to other pages, which in our opinion is only one small area for automated robots. While there are a number of existing crawler libraries for various task, each of them comes with a custom API and there are no generic interface for automatically determining which crawler (droids) to use for a specific task. The Droids project attempts to remove this duplication of efforts. We believe that by pooling the efforts of multiple projects we will be able to create a generic robot framework that exceeds the capabilities and quality of the custom solutions of any single project. The focus of Droids is not a single crawler but more to offer different reusable components that custom droids (robots) can use to automate certain tasks. An intelligent standalone robot framework project will not only provide common ground for the developers of crawler but as well for any other automated application (robots) libraries. === Initial Goals === The initial goals of the proposed project are: * Viable community around the Droids codebase * Active relationships and possible cooperation with related projects and communities (e.g. reusing Tika for text extraction) * Generic robot API for crawling, extracting structured text content and/or new task, filtering task and handle the content * Flexible extension and plugin development to create a wide range of functionality * Fuel develop of various droids and bring the current wget style crawler to state-of-the-art level == Current Status == === Meritocracy === All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source codebases. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is not yet a clear Droids community. Instead we have a number of people and related projects with an understanding that an intelligent standalone robot framework project would best serve everyone's interests. The primary goal of the incubating project is to build a self-sustaining community around this shared vision. === Core Developers === The initial set of developers comes from various backgrounds, with different but compatible needs for the proposed project. === Alignment === As a generic robot framework Droids will likely be widely used by various open source and commercial projects both together with and independent of other Apache tools. Apache projects like Cocoon, Lenya and Forrest are potential candidates for using different droids as an embedded component. == Known Risks == === Orphaned products === Till now
[jira] Commented: (INCUBATOR-85) Request Mailing lists from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636864#action_12636864 ] Brett Porter commented on INCUBATOR-85: --- just the same addresses as the others. I thought it was odd that no mentors were included but forgot to ask. Should I add someone else? > Request Mailing lists from INFRA > > > Key: INCUBATOR-85 > URL: https://issues.apache.org/jira/browse/INCUBATOR-85 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Doug Cutting > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] accept Droids into incubation
+1 Paul On Sat, Oct 4, 2008 at 2:55 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Fri, Oct 3, 2008 at 4:00 AM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: >> Please vote on accepting Droids into incubation. > > +1 > > Cheers > Niclas Hedhman > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] accept Droids into incubation
On Fri, Oct 3, 2008 at 4:00 AM, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > Please vote on accepting Droids into incubation. +1 Cheers Niclas Hedhman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
On Sat, Oct 4, 2008 at 12:45 AM, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > Color me confused again, but during setup and formation of the Incubator, > a podling had to graduate before doing a release. It was rather well > established before this rule was modified, but it seems that this change > resulted in a number of different interpretations, some of which aren't > compatible with the ASF license. I will support the "initial intent" of no releases out of Incubator. This not only puts an end to this discussion, incl Maven's stance that policy enforcement is not their responsibility, but also accelerates the need to graduate for podlings and hopefully make incubation periods shorter. I would also move for requirement that Mentors remain PMC members of the graduated project and overseas the initial releases. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-85) Request Mailing lists from INFRA
[ https://issues.apache.org/jira/browse/INCUBATOR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636821#action_12636821 ] Niclas Hedhman commented on INCUBATOR-85: - Who becomes the initial Moderator for the [EMAIL PROTECTED] list?? > Request Mailing lists from INFRA > > > Key: INCUBATOR-85 > URL: https://issues.apache.org/jira/browse/INCUBATOR-85 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Doug Cutting > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-88) Add podling to reporting schedule
[ https://issues.apache.org/jira/browse/INCUBATOR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated INCUBATOR-88: Description: New podlings report every month for the first 3 months, then every quarter. The Reporting Schedule is at; http://wiki.apache.org/incubator/ReportingSchedule was:New podlings report every month for the first 3 months, then every quarter. > Add podling to reporting schedule > - > > Key: INCUBATOR-88 > URL: https://issues.apache.org/jira/browse/INCUBATOR-88 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > New podlings report every month for the first 3 months, then every quarter. > The Reporting Schedule is at; > http://wiki.apache.org/incubator/ReportingSchedule -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Deleted: (INCUBATOR-96) Add etch-developers group to JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman deleted INCUBATOR-96: > Add etch-developers group to JIRA > - > > Key: INCUBATOR-96 > URL: https://issues.apache.org/jira/browse/INCUBATOR-96 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Deleted: (INCUBATOR-92) Add Etch-Notification scheme in JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman deleted INCUBATOR-92: > Add Etch-Notification scheme in JIRA > > > Key: INCUBATOR-92 > URL: https://issues.apache.org/jira/browse/INCUBATOR-92 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > > Once the mailing lists are set up, JIRA notifications should go to the > developer list. This requires a Notification scheme in Jira, and that the > ETCH project is tied to that scheme. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-96) Add etch-developers group to JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-96. --- Resolution: Fixed This issue is folded into the "Create Jira project" sub-task, and should never been created. > Add etch-developers group to JIRA > - > > Key: INCUBATOR-96 > URL: https://issues.apache.org/jira/browse/INCUBATOR-96 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-90) Create a Etch project in JIRA under Incubator category
[ https://issues.apache.org/jira/browse/INCUBATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman updated INCUBATOR-90: Description: * Create "Etch Notification" scheme. * Create the project * Add etch-developers group * Set the "Permission Scheme" to Incubator. * Set the "Notification Scheme" to "Etch Notification" * Add Project Roles; - Committers = etch-developers - PMC = the individual mentors (i.e. no group) > Create a Etch project in JIRA under Incubator category > -- > > Key: INCUBATOR-90 > URL: https://issues.apache.org/jira/browse/INCUBATOR-90 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman > > * Create "Etch Notification" scheme. > * Create the project > * Add etch-developers group > * Set the "Permission Scheme" to Incubator. > * Set the "Notification Scheme" to "Etch Notification" > * Add Project Roles; > - Committers = etch-developers > - PMC = the individual mentors (i.e. no group) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
The discussions are taking place on the Maven PMC list. If you are a member you can join the list. On 4-Oct-08, at 8:31 AM, Gilles Scokart wrote: 2008/10/3 Jason van Zyl <[EMAIL PROTECTED]>: On 2-Oct-08, at 9:19 PM, Noel J. Bergman wrote: Emmanuel Lecharny wrote: Better a bad decision than no decision, otherwise, soon, nobody will vote anymore... Not really. Consider that there appears to be a clear consensus that if Maven were to fix the download situation, requiring that users approve the user of Incubator artifacts, rather than transparently use them, many of the -1 would be +1. That's unlikely to happen. We're not going to be implementing policy enforcement for you. Our opinion is forming in the Maven PMC that we will not enforce third party policy but will adhere to the legal distribution rights set forth by the license. All PMC members who have voiced an opinion thus far have this opinion, Where does this dicussion took places? Is there a thread we can read? but we are scheduling a call for next week and we will have a decision and stated policy shortly. We will keep you posted when we reach a decision. It appears that the Maven community is finally getting a clue, and we can hope for a resolution, perhaps 6 months out or less if they don't falter. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gilles Scokart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-96) Add etch-developers group to JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636818#action_12636818 ] Niclas Hedhman commented on INCUBATOR-96: - And add the initial committers to that group. > Add etch-developers group to JIRA > - > > Key: INCUBATOR-96 > URL: https://issues.apache.org/jira/browse/INCUBATOR-96 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-96) Add etch-developers group to JIRA
Add etch-developers group to JIRA - Key: INCUBATOR-96 URL: https://issues.apache.org/jira/browse/INCUBATOR-96 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-96) Add etch-developers group to JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-96: --- Assignee: Niclas Hedhman > Add etch-developers group to JIRA > - > > Key: INCUBATOR-96 > URL: https://issues.apache.org/jira/browse/INCUBATOR-96 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-92) Add Etch-Notification scheme in JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-92. --- Resolution: Fixed Current Assignee, All Watchers, [EMAIL PROTECTED] and Reporter receives notifications, except for Work Started/Stopped and work log edits. Tuning can be discussed on dev list. > Add Etch-Notification scheme in JIRA > > > Key: INCUBATOR-92 > URL: https://issues.apache.org/jira/browse/INCUBATOR-92 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > > Once the mailing lists are set up, JIRA notifications should go to the > developer list. This requires a Notification scheme in Jira, and that the > ETCH project is tied to that scheme. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-92) Add Etch-Notification scheme in JIRA
[ https://issues.apache.org/jira/browse/INCUBATOR-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-92: --- Assignee: Niclas Hedhman > Add Etch-Notification scheme in JIRA > > > Key: INCUBATOR-92 > URL: https://issues.apache.org/jira/browse/INCUBATOR-92 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > > Once the mailing lists are set up, JIRA notifications should go to the > developer list. This requires a Notification scheme in Jira, and that the > ETCH project is tied to that scheme. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository
2008/10/3 Jason van Zyl <[EMAIL PROTECTED]>: > > On 2-Oct-08, at 9:19 PM, Noel J. Bergman wrote: > >> Emmanuel Lecharny wrote: >> >>> Better a bad decision than no decision, otherwise, soon, nobody will >>> vote anymore... >> >> Not really. Consider that there appears to be a clear consensus that if >> Maven were to fix the download situation, requiring that users approve the >> user of Incubator artifacts, rather than transparently use them, many of >> the -1 would be +1. >> > > That's unlikely to happen. We're not going to be implementing policy > enforcement for you. > > Our opinion is forming in the Maven PMC that we will not enforce third party > policy but will adhere to the legal distribution rights set forth by the > license. All PMC members who have voiced an opinion thus far have this > opinion, Where does this dicussion took places? Is there a thread we can read? > but we are scheduling a call for next week and we will have a > decision and stated policy shortly. We will keep you posted when we reach a > decision. > >> It appears that the Maven community is finally getting a clue, and we can >> hope for a resolution, perhaps 6 months out or less if they don't falter. >> >>--- Noel >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > -- > > A man enjoys his work when he understands the whole and when he > is responsible for the quality of the whole > > -- Christopher Alexander, A Pattern Language > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Gilles Scokart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-94) Add project to /projects/index.html
[ https://issues.apache.org/jira/browse/INCUBATOR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman closed INCUBATOR-94. --- Resolution: Fixed > Add project to /projects/index.html > --- > > Key: INCUBATOR-94 > URL: https://issues.apache.org/jira/browse/INCUBATOR-94 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > > Etch needs to add a small description of the project to the Incubator's > "projects" page, site-author/projects/index.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-94) Add project to /projects/index.html
[ https://issues.apache.org/jira/browse/INCUBATOR-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niclas Hedhman reassigned INCUBATOR-94: --- Assignee: Niclas Hedhman > Add project to /projects/index.html > --- > > Key: INCUBATOR-94 > URL: https://issues.apache.org/jira/browse/INCUBATOR-94 > Project: Incubator > Issue Type: Sub-task >Reporter: Niclas Hedhman >Assignee: Niclas Hedhman > > Etch needs to add a small description of the project to the Incubator's > "projects" page, site-author/projects/index.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] accept Droids into incubation
+1 On Oct 2, 2008, at 4:00 PM, Thorsten Scherler wrote: Please vote on accepting Droids into incubation. The proposal can be found at: http://wiki.apache.org/incubator/DroidsProposal The text of the proposal = Droids, an intelligent standalone robot framework = === Abstract === Droids aims to be an intelligent standalone robot framework that allows to create and extend existing droids (robots). === Proposal === As a standalone robot framework Droids will offer infrastructure code to create and extend existing robots. In the future it will offer as well a web based administration application to manage and controll the different droids which will communicate with this app. Droids makes it very easy to extend existing robots or write a new one from scratch, which can automatically seek out relevant online information based on the user's specifications. Since the flexible design it can reuse directly all custom business logic that are written in java. In the long run it should become umbrella for specialized droids that are hosted as sub-projects. Where an ultimate goal is to integrate an artificial intelligence that can control a swarm of droids and actively plan/react on different tasks. === Background === The initial idea for the Droids project was voiced in February 2007 from Thorsten Scherler mainly because of personal curiosity and developed as a labs project. The background of his work was that Cocoon trunk (2.2) did not provide a crawler anymore and Forrest was based on it, meaning we could not update anymore till we found a crawler replacement. Getting more involved in Solr and Nutch he saw the request for a generic standalone crawler. For the first version he took nutch, ripped out and modified the plugin/extension framework. However the second version were not based on it anymore but was using Spring instead. The main reason was that Spring has become a standard and helped to make Droids as extensible as possible. Soon the first plugins and sample droids had been added to the code based. === Rationale === There is ever more demand for tools that automatically do determinate tasks. Search engines such as Nuts are normally very focused on a specific functionality and are not focused on extensibility. Furthermore there are manly focused on crawling, requesting certain pages and extract links to other pages, which in our opinion is only one small area for automated robots. While there are a number of existing crawler libraries for various task, each of them comes with a custom API and there are no generic interface for automatically determining which crawler (droids) to use for a specific task. The Droids project attempts to remove this duplication of efforts. We believe that by pooling the efforts of multiple projects we will be able to create a generic robot framework that exceeds the capabilities and quality of the custom solutions of any single project. The focus of Droids is not a single crawler but more to offer different reusable components that custom droids (robots) can use to automate certain tasks. An intelligent standalone robot framework project will not only provide common ground for the developers of crawler but as well for any other automated application (robots) libraries. === Initial Goals === The initial goals of the proposed project are: * Viable community around the Droids codebase * Active relationships and possible cooperation with related projects and communities (e.g. reusing Tika for text extraction) * Generic robot API for crawling, extracting structured text content and/or new task, filtering task and handle the content * Flexible extension and plugin development to create a wide range of functionality * Fuel develop of various droids and bring the current wget style crawler to state-of-the-art level == Current Status == === Meritocracy === All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source codebases. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is not yet a clear Droids community. Instead we have a number of people and related projects with an understanding that an intelligent standalone robot framework project would best serve everyone's interests. The primary goal of the incubating project is to build a self-sustaining community around this shared vision. === Core Developers === The initial set of developers comes from various backgrounds, with different but compatible needs for the proposed project. === Alignment === As a generic robot framework Droids will likely be widely used by various open source and commercial projects both together with and independent of other Apache tools. Apache projects like Cocoon, Lenya and Forrest are potential candidates for using different droids as an embedded component. == Known Risks == === Orphaned products === Till now o
Re: status of PGP support in Maven
On Fri, Oct 3, 2008 at 10:02 PM, sebb <[EMAIL PROTECTED]> wrote: > On 03/10/2008, Bruce Snyder <[EMAIL PROTECTED]> wrote: >> On Fri, Oct 3, 2008 at 8:50 AM, Noel J. Bergman <[EMAIL PROTECTED]> wrote: >> >> > Moved to the thread it belongs in ... >> > >> > Jason van Zyl wrote: >> >> Noel J. Bergman wrote: >> >> > Emmanuel Lecharny wrote: >> Better a bad decision than no decision, otherwise, soon, nobody will >> vote anymore... >> >>> Not really. Consider that there appears to be a clear consensus >> >>> that if Maven were to fix the download situation, requiring that users >> >>> approve the user of Incubator artifacts, rather than transparently use >> >>> them, many of the -1 would be +1. >> > >> >> That's unlikely to happen. We're not going to be implementing policy >> >> enforcement for you. >> > >> > We don't need for you to implement any "policy" other than the requirement >> > for users to approve authorized signing keys. You simply need to >> implement >> > artifact signing and mandatory authorization, which is why I've moved this >> > to the thread Brett started for purposes of discussing signing. >> >> >> I'm trying to understand why authorization should be mandatory? To my >> knowledge, only some of the Linux package management tools (apt, port, >> rpm, yum) verify signatures by default and in the event of failure, >> they allow you to continue without the key verification. >> >> Also, I've actually spoken to a number of folks about GPG verification >> of artifacts over the last year and very few folks actually use this >> today. GPG is very good for certain purposes. downstream packagers should check signatures (and know how to do so safely) but for normal users, checking SHA sums against the main site is probably better. >> > Did you not see what just happened to Redhat with respect to Fedora? They >> > take artifact security seriously. For a long time, it has appeared that >> > Maven does not, but I am hopeful now that mandatory authorization will >> > appear, so that I and others will not have to increase lobbying efforts to >> > have the Maven repository closed, at least with respect to ASF projects. >> >> >> Please explain what happened to RedHat with respect to Fedora. I'm not >> familiar with the situation. > > http://rtfa.net/2008/08/25/fedora-package-signing-server-compromise-crls-and-trust/ > > and > > http://rhn.redhat.com/errata/RHSA-2008-0855.html silver bullets don't work :-) single key, single point of failure, single compromise required sounds like it was picked up by their auditing system, though BTW the RAT auditing stuff seems to be working ok now for the incubator releases. if anyone wants to extend auditing to other projects, i'd be happy to help. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
