[VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
Hi all guys, after PODLINGNAMESEARCH-12 resolution, it's finally time to vote the graduation resolution and to establish Apache Oltu as TLP, after a period at ASF incubator since 2010-06-01 as Apache Amber. The PPMC already positively voted[1] the resolution in the public dev@ ML, collecting two binding votes from IPMC members Tommaso Teofili and Raymond Feng Vote will be open for at least 72 hours and closes approximately on Mon 24th, 9:40am GMT So IPMC, please cast your votes! Many thanks in advance, all the best! -Simo [ ] +1 graduate! [ ] +0 no opinion [ ] -1 do not graduate (and please provide a reason why) X. Establish the Apache Oltu Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the automatic crawling, parsing and analyzing of RDF triples. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oltu Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oltu Project be and hereby is responsible for the creation and maintenance of software related to OAuth protocol implementation in Java RESOLVED, that the office of Vice President, Apache Oltu be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oltu Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oltu Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oltu Project: * Antonio Sanso asa...@apache.org * Lukasz Moren lmo...@apache.org * Maciej Pawel Machulak mmac...@apache.org * Raymond Feng rfe...@apache.org * Stuart Williams pids...@apache.org * Simone Tripodi simo...@apache.org * Tommaso Teofili tomm...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Antonio Sanso be appointed to the office of Vice President, Apache Oltu 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; and be it further RESOLVED, that the Apache Oltu Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oltu podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oltu podling encumbered upon the Apache Incubator Project are hereafter discharged. [1] http://markmail.org/message/cvhntqngz2qrqree http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
The Maven PMC pushes no plugin releases nor parent poms to /dist. We just leave them on repository.apache.org and of course on Maven central. So, I think this is a pretty safe precedent. On Fri, Dec 21, 2012 at 5:58 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello fellows, with Onami we are currently working to release a parent pom (only). Its just related to maven and so our idea was to spread it via repository.a.o only. Now reading this: All releases must be archived on http://archive.apache.org/dist/. An automated process adds releases to the archive about a day after they first appear on to http://www.apache.org/dist/. Once a release is placed underhttp://www.apache.org/dist/ it will automatically be copied over to http://archive.apache.org/dist/ and held there permanently, even after it is deleted from http://www.apache.org/dist/.; http://www.apache.org/dev/release.html#mirroring it seems we need to push it to /dist, even when its Maven only. Is that correct? I am asking because I could not find the Apache parent pom there (maybe I missed it) and it let me hope that we do not need to commit it to /dist. Thanks Christian - 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: How to use an apache webpage
On Thu, Dec 20, 2012 at 11:15 PM, Christian Grobmeier grobme...@gmail.com wrote: On Fri, Dec 21, 2012 at 1:19 AM, Nick Burch apa...@gagravarr.org wrote: On Thu, 20 Dec 2012, Shane Curcuru wrote: I put the DRAFT on because I originally wrote these for my personal Community Over Code site, and I wanted to ensure the style was appropriate for a path under a.o/foundation, which makes it official. I wonder if a label like work in progress might be better suited, if we want to indicate in future that something is incomplete but input is welcomed? If I follow this thread, the point is that (a) we have no process for formally approving the docs in question, so (b) they always remain W-I-P or DRAFT, so (c) no one knows whether to believe them. The proposal here, to which I am +1, is that all of the docs are subject to patches and vetos. So we need no such marking, but rather the members of the responsible PMC need to act on their responsibility and talk/act if they see something so wrong that someone should *not* believe it. Until then, we trust the committers of these docs to commit things that people should believe. If someone wants to propose a small-print footer that copies this policy, which is already on the incubator 'how to update the website page', someone should, well, commit it. Only if you tell people who is working on it (to submit patches) and if the content of the document can be used (or not). Christian Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - 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: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
+1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? On Fri, Dec 21, 2012 at 4:41 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, after PODLINGNAMESEARCH-12 resolution, it's finally time to vote the graduation resolution and to establish Apache Oltu as TLP, after a period at ASF incubator since 2010-06-01 as Apache Amber. The PPMC already positively voted[1] the resolution in the public dev@ ML, collecting two binding votes from IPMC members Tommaso Teofili and Raymond Feng Vote will be open for at least 72 hours and closes approximately on Mon 24th, 9:40am GMT So IPMC, please cast your votes! Many thanks in advance, all the best! -Simo [ ] +1 graduate! [ ] +0 no opinion [ ] -1 do not graduate (and please provide a reason why) X. Establish the Apache Oltu Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the automatic crawling, parsing and analyzing of RDF triples. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oltu Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oltu Project be and hereby is responsible for the creation and maintenance of software related to OAuth protocol implementation in Java RESOLVED, that the office of Vice President, Apache Oltu be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oltu Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oltu Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oltu Project: * Antonio Sanso asa...@apache.org * Lukasz Moren lmo...@apache.org * Maciej Pawel Machulak mmac...@apache.org * Raymond Feng rfe...@apache.org * Stuart Williams pids...@apache.org * Simone Tripodi simo...@apache.org * Tommaso Teofili tomm...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Antonio Sanso be appointed to the office of Vice President, Apache Oltu 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; and be it further RESOLVED, that the Apache Oltu Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oltu podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oltu podling encumbered upon the Apache Incubator Project are hereafter discharged. [1] http://markmail.org/message/cvhntqngz2qrqree http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Greetings, Marcel On Dec 21, 2012, at 12:53 , Benson Margulies bimargul...@gmail.com wrote: The Maven PMC pushes no plugin releases nor parent poms to /dist. We just leave them on repository.apache.org and of course on Maven central. So, I think this is a pretty safe precedent. On Fri, Dec 21, 2012 at 5:58 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello fellows, with Onami we are currently working to release a parent pom (only). Its just related to maven and so our idea was to spread it via repository.a.o only. Now reading this: All releases must be archived on http://archive.apache.org/dist/. An automated process adds releases to the archive about a day after they first appear on to http://www.apache.org/dist/. Once a release is placed underhttp://www.apache.org/dist/ it will automatically be copied over to http://archive.apache.org/dist/ and held there permanently, even after it is deleted from http://www.apache.org/dist/.; http://www.apache.org/dev/release.html#mirroring it seems we need to push it to /dist, even when its Maven only. Is that correct? I am asking because I could not find the Apache parent pom there (maybe I missed it) and it let me hope that we do not need to commit it to /dist. Thanks Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
Give me a URL where this policy is and I'll edit it. On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Greetings, Marcel On Dec 21, 2012, at 12:53 , Benson Margulies bimargul...@gmail.com wrote: The Maven PMC pushes no plugin releases nor parent poms to /dist. We just leave them on repository.apache.org and of course on Maven central. So, I think this is a pretty safe precedent. On Fri, Dec 21, 2012 at 5:58 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello fellows, with Onami we are currently working to release a parent pom (only). Its just related to maven and so our idea was to spread it via repository.a.o only. Now reading this: All releases must be archived on http://archive.apache.org/dist/. An automated process adds releases to the archive about a day after they first appear on to http://www.apache.org/dist/. Once a release is placed underhttp://www.apache.org/dist/ it will automatically be copied over to http://archive.apache.org/dist/ and held there permanently, even after it is deleted from http://www.apache.org/dist/.; http://www.apache.org/dev/release.html#mirroring it seems we need to push it to /dist, even when its Maven only. Is that correct? I am asking because I could not find the Apache parent pom there (maybe I missed it) and it let me hope that we do not need to commit it to /dist. Thanks Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
On Fri, Dec 21, 2012 at 1:01 PM, Benson Margulies bimargul...@gmail.com wrote: Give me a URL where this policy is and I'll edit it. http://www.apache.org/dev/release.html Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
+1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? LOL, Oltu stone[1] is a type of Amber, just to keep in the topic :P I found anyway that Oltu is a Turkish town[2] as well :) -Simo [1] http://en.wikipedia.org/wiki/List_of_types_of_amber [2] http://en.wikipedia.org/wiki/Oltu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
On Fri, Dec 21, 2012 at 7:19 AM, Simone Tripodi simonetrip...@apache.org wrote: +1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? LOL, Oltu stone[1] is a type of Amber, just to keep in the topic :P I found anyway that Oltu is a Turkish town[2] as well :) In my own defense, [3].. [3] https://www.google.com/search?q=otlu+cheesehl=entbo=utbm=ischsource=univsa=Xei=FVrUUP2MGsH90gHCloGACQved=0CEEQsAQbiw=1230bih=756 -Simo [1] http://en.wikipedia.org/wiki/List_of_types_of_amber [2] http://en.wikipedia.org/wiki/Oltu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
On Fri, Dec 21, 2012 at 7:05 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Fri, Dec 21, 2012 at 1:01 PM, Benson Margulies bimargul...@gmail.com wrote: Give me a URL where this policy is and I'll edit it. http://www.apache.org/dev/release.html While I agree that the page has a lot to say about putting releases on /dist, I could not find any point in which it said, in so many words, that /dist was required. I do, however, see how people would take that implication. So, I edited it to say the opposite for this case. I'm not pushing the publish button; rather, I've started a thread on infra@ (which seems to supervise this content) inviting people to tell me that I am wrong. If I am still wearing my head tonight on the subject, I'll push the publish button. Martijn - 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: Do all releases need to go to /dist?
On Fri, Dec 21, 2012 at 7:54 AM, Ross Gardler rgard...@opendirective.com wrote: You ought to leave it for 72 hours, a half day is not enough time for infra to respond. Ross is completely right. Stay tuned, the discussion on whether I'm right or not has already begun, and quite aside from his good counsel of caution, could well go on for some time. In the mean time, it can't hurt to copy that bundle from Onami to /dist if you all want to get on with your lives. Ross On 21 December 2012 12:52, Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:05 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Fri, Dec 21, 2012 at 1:01 PM, Benson Margulies bimargul...@gmail.com wrote: Give me a URL where this policy is and I'll edit it. http://www.apache.org/dev/release.html While I agree that the page has a lot to say about putting releases on /dist, I could not find any point in which it said, in so many words, that /dist was required. I do, however, see how people would take that implication. So, I edited it to say the opposite for this case. I'm not pushing the publish button; rather, I've started a thread on infra@ (which seems to supervise this content) inviting people to tell me that I am wrong. If I am still wearing my head tonight on the subject, I'll push the publish button. Martijn - 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 -- 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: Do all releases need to go to /dist?
On Dec 21, 2012, at 13:52 , Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:05 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Fri, Dec 21, 2012 at 1:01 PM, Benson Margulies bimargul...@gmail.com wrote: Give me a URL where this policy is and I'll edit it. http://www.apache.org/dev/release.html While I agree that the page has a lot to say about putting releases on /dist, I could not find any point in which it said, in so many words, that /dist was required. I do, however, see how people would take that implication. It does state that all releases must be archived on http://archive.apache.org/dist/ so I think that more or less implies that all releases must be put on /dist. I just feel that as soon as we start making exceptions, we will end up with many, and I really don't understand why this exception is necessary in the first place. In fact, I think it's a great benefit that all releases can be found in one single location, no exceptions. So, I edited it to say the opposite for this case. I'm not pushing the publish button; rather, I've started a thread on infra@ (which seems to supervise this content) inviting people to tell me that I am wrong. If I am still wearing my head tonight on the subject, I'll push the publish button. I objected there as well, to me this is a big policy change, and one that I don't understand the reason of. Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
On Fri, Dec 21, 2012 at 8:10 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Dec 21, 2012, at 13:52 , Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:05 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Fri, Dec 21, 2012 at 1:01 PM, Benson Margulies bimargul...@gmail.com wrote: Give me a URL where this policy is and I'll edit it. http://www.apache.org/dev/release.html While I agree that the page has a lot to say about putting releases on /dist, I could not find any point in which it said, in so many words, that /dist was required. I do, however, see how people would take that implication. It does state that all releases must be archived on http://archive.apache.org/dist/ so I think that more or less implies that all releases must be put on /dist. I just feel that as soon as we start making exceptions, we will end up with many, and I really don't understand why this exception is necessary in the first place. In fact, I think it's a great benefit that all releases can be found in one single location, no exceptions. So, I edited it to say the opposite for this case. I'm not pushing the publish button; rather, I've started a thread on infra@ (which seems to supervise this content) inviting people to tell me that I am wrong. If I am still wearing my head tonight on the subject, I'll push the publish button. I objected there as well, to me this is a big policy change, and one that I don't understand the reason of. I think one thread of debate on this is enough, so I won't reply further here. Greetings, Marcel - 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: [VOTE] retire photark
+ 1 Suresh On Dec 19, 2012, at 8:52 PM, Benson Margulies bimargul...@gmail.com wrote: Having received no traffic on the discussion thread, and in particular no traffic at all from the PPMC, I hereby call a vote to retire photark. [+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
[jira] [Commented] (PODLINGNAMESEARCH-12) Establish whether Apache Oltu is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13537856#comment-13537856 ] Shane Curcuru commented on PODLINGNAMESEARCH-12: USPTO search directly at TESS shows no hits. Google Oltu software shows no pertinent hits in our area of software products, namely that Apache Oltu will be an OAuth protocol implementation in Java. Establish whether Apache Oltu is a suitable name -- Key: PODLINGNAMESEARCH-12 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-12 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Antonio Sanso We have to do some investigations to ensure that Apache Amber is a suitable name for a TLP. Here are some resources related to this issue: http://incubator.apache.org/guides/names.html http://www.apache.org/foundation/marks/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
NOTE: Oltu has *not* taken their name search to trademarks@, which is a *requirement* before resolving the actual name search. This is understandable, since the docs don't clearly specify this. I've taken a quick look and commented on the JIRA, so they seem to have a fine name, so please feel free to vote away. If Oltu is actually the name of some specific kind of cheese, please let me know if there's any way I can get some here in the eastern US (I love cheese). The bad news is that there is another software project with Oltu in the name (google oltu software, since trademarks are only important within general categories of products). The good news is it seems to simply be a streaming app for some Turkish (?) radio station - so I'm confident we have nothing to fear from confusion with them. The point is that it's important to include trademarks@ in your podling name searches. - Shane rhetoricalCan someone remind me how to update the incubator docs? Are they fully CMS now?/rhetorical On 12/21/2012 4:41 AM, Simone Tripodi wrote: Hi all guys, after PODLINGNAMESEARCH-12 resolution, it's finally time to vote the graduation resolution and to establish Apache Oltu as TLP, after a period at ASF incubator since 2010-06-01 as Apache Amber. The PPMC already positively voted[1] the resolution in the public dev@ ML, collecting two binding votes from IPMC members Tommaso Teofili and Raymond Feng Vote will be open for at least 72 hours and closes approximately on Mon 24th, 9:40am GMT So IPMC, please cast your votes! Many thanks in advance, all the best! -Simo [ ] +1 graduate! [ ] +0 no opinion [ ] -1 do not graduate (and please provide a reason why) X. Establish the Apache Oltu Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the automatic crawling, parsing and analyzing of RDF triples. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oltu Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oltu Project be and hereby is responsible for the creation and maintenance of software related to OAuth protocol implementation in Java RESOLVED, that the office of Vice President, Apache Oltu be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oltu Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oltu Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oltu Project: * Antonio Sanso asa...@apache.org * Lukasz Moren lmo...@apache.org * Maciej Pawel Machulak mmac...@apache.org * Raymond Feng rfe...@apache.org * Stuart Williams pids...@apache.org * Simone Tripodi simo...@apache.org * Tommaso Teofili tomm...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Antonio Sanso be appointed to the office of Vice President, Apache Oltu 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; and be it further RESOLVED, that the Apache Oltu Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oltu podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oltu podling encumbered upon the Apache Incubator Project are hereafter discharged. [1] http://markmail.org/message/cvhntqngz2qrqree http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
Hi Shane, thanks a lot for this. I conducted a US Trademark Search, this shows no results for Oltu http://www.trademarkia.com/trademarks-search.aspx?tn=oltu as per PODLINGNAMESEARCH-12 (Evidence Of Registration) but thanks for double checking! Regards Antonio http://www.trademarkia.com/trademarks-search.aspx?tn=oltu On Dec 21, 2012, at 2:36 PM, Shane Curcuru wrote: NOTE: Oltu has *not* taken their name search to trademarks@, which is a *requirement* before resolving the actual name search. This is understandable, since the docs don't clearly specify this. I've taken a quick look and commented on the JIRA, so they seem to have a fine name, so please feel free to vote away. If Oltu is actually the name of some specific kind of cheese, please let me know if there's any way I can get some here in the eastern US (I love cheese). The bad news is that there is another software project with Oltu in the name (google oltu software, since trademarks are only important within general categories of products). The good news is it seems to simply be a streaming app for some Turkish (?) radio station - so I'm confident we have nothing to fear from confusion with them. The point is that it's important to include trademarks@ in your podling name searches. - Shane rhetoricalCan someone remind me how to update the incubator docs? Are they fully CMS now?/rhetorical On 12/21/2012 4:41 AM, Simone Tripodi wrote: Hi all guys, after PODLINGNAMESEARCH-12 resolution, it's finally time to vote the graduation resolution and to establish Apache Oltu as TLP, after a period at ASF incubator since 2010-06-01 as Apache Amber. The PPMC already positively voted[1] the resolution in the public dev@ ML, collecting two binding votes from IPMC members Tommaso Teofili and Raymond Feng Vote will be open for at least 72 hours and closes approximately on Mon 24th, 9:40am GMT So IPMC, please cast your votes! Many thanks in advance, all the best! -Simo [ ] +1 graduate! [ ] +0 no opinion [ ] -1 do not graduate (and please provide a reason why) X. Establish the Apache Oltu Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the automatic crawling, parsing and analyzing of RDF triples. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oltu Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oltu Project be and hereby is responsible for the creation and maintenance of software related to OAuth protocol implementation in Java RESOLVED, that the office of Vice President, Apache Oltu be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oltu Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oltu Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oltu Project: * Antonio Sanso asa...@apache.org * Lukasz Moren lmo...@apache.org * Maciej Pawel Machulak mmac...@apache.org * Raymond Feng rfe...@apache.org * Stuart Williams pids...@apache.org * Simone Tripodi simo...@apache.org * Tommaso Teofili tomm...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Antonio Sanso be appointed to the office of Vice President, Apache Oltu 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; and be it further RESOLVED, that the Apache Oltu Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oltu podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oltu podling encumbered upon the Apache Incubator Project are hereafter discharged. [1] http://markmail.org/message/cvhntqngz2qrqree http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgmailto:general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.orgmailto:general-h...@incubator.apache.org - To unsubscribe, e-mail:
Re: [VOTE] retire photark
+1 Dan On Dec 19, 2012, at 8:52 PM, Benson Margulies bimargul...@gmail.com wrote: Having received no traffic on the discussion thread, and in particular no traffic at all from the PPMC, I hereby call a vote to retire photark. [+1] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
no needs to defense, it was nice reading something curious! :) http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Dec 21, 2012 at 1:47 PM, Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:19 AM, Simone Tripodi simonetrip...@apache.org wrote: +1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? LOL, Oltu stone[1] is a type of Amber, just to keep in the topic :P I found anyway that Oltu is a Turkish town[2] as well :) In my own defense, [3].. [3] https://www.google.com/search?q=otlu+cheesehl=entbo=utbm=ischsource=univsa=Xei=FVrUUP2MGsH90gHCloGACQved=0CEEQsAQbiw=1230bih=756 -Simo [1] http://en.wikipedia.org/wiki/List_of_types_of_amber [2] http://en.wikipedia.org/wiki/Oltu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
Benson Margulies wrote on Fri, Dec 21, 2012 at 07:01:03 -0500: On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Give me a URL where this policy is and I'll edit it. The way to change a policy is to obtain consensus on the new policy, not to edit the web page that documents the existing policy --- particularly when someone just expressed an opinion in favour of the documented policy. You're setting a good counter-example to podlings. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
Shane Curcuru wrote on Fri, Dec 21, 2012 at 08:36:58 -0500: The bad news is that there is another software project with Oltu in the name (google oltu software, since trademarks are only important within general categories of products). The good news is it seems to simply be a streaming app for some Turkish (?) radio station - so I'm confident we have nothing to fear from confusion with them. The point Is Oltu a Turkish word? What does it mean? is that it's important to include trademarks@ in your podling name searches. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
Hi Daniel On Dec 21, 2012, at 4:18 PM, Daniel Shahaf wrote: Shane Curcuru wrote on Fri, Dec 21, 2012 at 08:36:58 -0500: The bad news is that there is another software project with Oltu in the name (google oltu software, since trademarks are only important within general categories of products). The good news is it seems to simply be a streaming app for some Turkish (?) radio station - so I'm confident we have nothing to fear from confusion with them. The point Is Oltu a Turkish word? What does it mean? quoting Simone Oltu stone[1] is a type of Amber, just to keep in the topic... Regards Antonio [1] http://en.wikipedia.org/wiki/List_of_types_of_amber is that it's important to include trademarks@ in your podling name searches. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgmailto:general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.orgmailto:general-h...@incubator.apache.org
Re: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
Turkish speakers: Google translate says that 'otlu', with no diacritics, is an adjective meaning grassy or herby. Thus, the cheese is cheese with herbs in it. Just for my education, how does Amber come into it? Is there supposed to be an diacritic? Is google just bewildered? On Fri, Dec 21, 2012 at 9:15 AM, Simone Tripodi simonetrip...@apache.org wrote: no needs to defense, it was nice reading something curious! :) http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Dec 21, 2012 at 1:47 PM, Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:19 AM, Simone Tripodi simonetrip...@apache.org wrote: +1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? LOL, Oltu stone[1] is a type of Amber, just to keep in the topic :P I found anyway that Oltu is a Turkish town[2] as well :) In my own defense, [3].. [3] https://www.google.com/search?q=otlu+cheesehl=entbo=utbm=ischsource=univsa=Xei=FVrUUP2MGsH90gHCloGACQved=0CEEQsAQbiw=1230bih=756 -Simo [1] http://en.wikipedia.org/wiki/List_of_types_of_amber [2] http://en.wikipedia.org/wiki/Oltu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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: [VOTE] Apache Oltu (formerly Apache Amber) graduation resolution
I've answered my own question in part. Oltu taşı means 'jet', a black form of Amber. The humorous question for any Turkish readers of this thread is this: when a Turkish reader sees 'otlu' by itself, do they think, 'jet', 'aux fine herbs', or 'cheese'? On Fri, Dec 21, 2012 at 11:03 AM, Benson Margulies bimargul...@gmail.com wrote: Turkish speakers: Google translate says that 'otlu', with no diacritics, is an adjective meaning grassy or herby. Thus, the cheese is cheese with herbs in it. Just for my education, how does Amber come into it? Is there supposed to be an diacritic? Is google just bewildered? On Fri, Dec 21, 2012 at 9:15 AM, Simone Tripodi simonetrip...@apache.org wrote: no needs to defense, it was nice reading something curious! :) http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Dec 21, 2012 at 1:47 PM, Benson Margulies bimargul...@gmail.com wrote: On Fri, Dec 21, 2012 at 7:19 AM, Simone Tripodi simonetrip...@apache.org wrote: +1, binding, but would some kind soul please clue me in as to why you want to be named after a Turkish Cheese? LOL, Oltu stone[1] is a type of Amber, just to keep in the topic :P I found anyway that Oltu is a Turkish town[2] as well :) In my own defense, [3].. [3] https://www.google.com/search?q=otlu+cheesehl=entbo=utbm=ischsource=univsa=Xei=FVrUUP2MGsH90gHCloGACQved=0CEEQsAQbiw=1230bih=756 -Simo [1] http://en.wikipedia.org/wiki/List_of_types_of_amber [2] http://en.wikipedia.org/wiki/Oltu http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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: Do all releases need to go to /dist?
My belief is that the policy changed a long time ago but was not properly edited into the document. If I didn't believe that, I'd be taking a different approach here. My secondary belief is that the existing document is an ambiguous writing job, and I'm as entitled to my opinion as to the actual intention as anyone else with rights to edit it. And, as such, I think that the right thing to do is to put up the edits and see who complains. I am perfectly happy to set the example of boldly editing documents to state the policy as I understand it, and then inviting people to comment. I am in part inspired by the other thread about the uselessness of DRAFT and suchlike markings. If you are so convinced that I am entirely changing, as opposed to clarifying, a Foundation invariant, then you should say as much on the thread over on infra. If you feel strongly enough, you should revert my commit. On Fri, Dec 21, 2012 at 10:16 AM, Daniel Shahaf d...@daniel.shahaf.name wrote: Benson Margulies wrote on Fri, Dec 21, 2012 at 07:01:03 -0500: On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Give me a URL where this policy is and I'll edit it. The way to change a policy is to obtain consensus on the new policy, not to edit the web page that documents the existing policy --- particularly when someone just expressed an opinion in favour of the documented policy. You're setting a good counter-example to podlings. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
Hi I agree about how policy should change. But when it comes to apply on this case I believe we have to read the release rules carefully and we will see that we don't need policy change we just need to add more details and hence make it more clear The release rules assume you are release source code not just a pom file (s) which for sure people will not use it by downloading a dist from anywhere. They either will svn co the tag and build it locally or use the one deployed in Nexus It is just a different situation not an exception Christian and I already discussed that offline and kindly took the effort to bring it to the list :) Sent from my Samsung Galaxy S3 Apologies for any typos On Dec 21, 2012 5:12 PM, Benson Margulies bimargul...@gmail.com wrote: My belief is that the policy changed a long time ago but was not properly edited into the document. If I didn't believe that, I'd be taking a different approach here. My secondary belief is that the existing document is an ambiguous writing job, and I'm as entitled to my opinion as to the actual intention as anyone else with rights to edit it. And, as such, I think that the right thing to do is to put up the edits and see who complains. I am perfectly happy to set the example of boldly editing documents to state the policy as I understand it, and then inviting people to comment. I am in part inspired by the other thread about the uselessness of DRAFT and suchlike markings. If you are so convinced that I am entirely changing, as opposed to clarifying, a Foundation invariant, then you should say as much on the thread over on infra. If you feel strongly enough, you should revert my commit. On Fri, Dec 21, 2012 at 10:16 AM, Daniel Shahaf d...@daniel.shahaf.name wrote: Benson Margulies wrote on Fri, Dec 21, 2012 at 07:01:03 -0500: On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Give me a URL where this policy is and I'll edit it. The way to change a policy is to obtain consensus on the new policy, not to edit the web page that documents the existing policy --- particularly when someone just expressed an opinion in favour of the documented policy. You're setting a good counter-example to podlings. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] retire photark
+1 On Fri, Dec 21, 2012 at 6:11 AM, Daniel Kulp dk...@apache.org wrote: +1 Dan On Dec 19, 2012, at 8:52 PM, Benson Margulies bimargul...@gmail.com wrote: Having received no traffic on the discussion thread, and in particular no traffic at all from the PPMC, I hereby call a vote to retire photark. [+1] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do all releases need to go to /dist?
Given how the discussion on other closed lists is proceeding, as chair of this committee, I feel compelled to contribute the following: The current stated policy of the Foundation is that releases go onto /dist. If you are using Maven tooling to make your releases, you should first of all be sure to produce real, buildable, releases using the profiles in the ASF POM, and secondly, you should copy those zip files to /dist after a vote passes. If this policy changes, I'll be quite sure to make this list aware of it, if someone else doesn't beat me to it. In short, I misjudged the historical context of this particular issue. On Fri, Dec 21, 2012 at 2:28 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi I agree about how policy should change. But when it comes to apply on this case I believe we have to read the release rules carefully and we will see that we don't need policy change we just need to add more details and hence make it more clear The release rules assume you are release source code not just a pom file (s) which for sure people will not use it by downloading a dist from anywhere. They either will svn co the tag and build it locally or use the one deployed in Nexus It is just a different situation not an exception Christian and I already discussed that offline and kindly took the effort to bring it to the list :) Sent from my Samsung Galaxy S3 Apologies for any typos On Dec 21, 2012 5:12 PM, Benson Margulies bimargul...@gmail.com wrote: My belief is that the policy changed a long time ago but was not properly edited into the document. If I didn't believe that, I'd be taking a different approach here. My secondary belief is that the existing document is an ambiguous writing job, and I'm as entitled to my opinion as to the actual intention as anyone else with rights to edit it. And, as such, I think that the right thing to do is to put up the edits and see who complains. I am perfectly happy to set the example of boldly editing documents to state the policy as I understand it, and then inviting people to comment. I am in part inspired by the other thread about the uselessness of DRAFT and suchlike markings. If you are so convinced that I am entirely changing, as opposed to clarifying, a Foundation invariant, then you should say as much on the thread over on infra. If you feel strongly enough, you should revert my commit. On Fri, Dec 21, 2012 at 10:16 AM, Daniel Shahaf d...@daniel.shahaf.name wrote: Benson Margulies wrote on Fri, Dec 21, 2012 at 07:01:03 -0500: On Fri, Dec 21, 2012 at 6:58 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: Well, I don't think it's fine. As long as our release policy states that all releases must be archived on /dist we should do exactly that. Or change the policy. Give me a URL where this policy is and I'll edit it. The way to change a policy is to obtain consensus on the new policy, not to edit the web page that documents the existing policy --- particularly when someone just expressed an opinion in favour of the documented policy. You're setting a good counter-example to podlings. - 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
