Re: [dash-dev] Office release of the Eclipse Dash License Tool
Okay. I think that I got it. And it only took me two more tries :-/
Try version 1.0.2.
Wayne
On Fri, May 19, 2023 at 6:29 PM Matthias Sohn
wrote:
> On Fri, May 19, 2023 at 11:54 PM Wayne Beaton via dash-dev <
> dash-dev@eclipse.org> wrote:
>
>> Greetings Dash committers and community.
>>
>> I've pushed a version 1.0.0 of the Eclipse Dash License Tool to
>> repo.eclipse.org
>>
>> I've updated the documentation accordingly.
>>
>> https://github.com/eclipse/dash-licenses
>>
>
> I tried to update jgit to use license-tool-plugin 1.0.0, the build fails
> with this error:
>
> Plugin org.eclipse.dash:license-tool-plugin:1.0.0 or one of its
> dependencies could not be resolved: Failed to read artifact descriptor for
> org.eclipse.dash:license-tool-plugin:jar:1.0.0: The following artifacts
> could not be resolved:
> org.eclipse.dash:dash-licenses-parent:pom:${revision} (absent):
> org.eclipse.dash:dash-licenses-parent:pom:${revision} was not found in
> https://repo.eclipse.org/content/repositories/cbi-releases/ during a
> previous attempt.
>
> Looks like you missed to publish the project's parent pom and to set its
> version number.
>
> See https://git.eclipse.org/r/c/jgit/jgit/+/201959
>
> -Matthias
>
>
>> My next push will update the pom files for a 1.0.1 snapshot.
>>
>> Wayne
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation
>>
>>
>> My working day may not be your working day! Please don’t feel obliged to
>> read or reply to this e-mail outside of your normal working hours.
>> ___
>> dash-dev mailing list
>> dash-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/dash-dev
>>
>
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation
My working day may not be your working day! Please don’t feel obliged to
read or reply to this e-mail outside of your normal working hours.
___
dash-dev mailing list
dash-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Office release of the Eclipse Dash License Tool
Greetings Dash committers and community. I've pushed a version 1.0.0 of the Eclipse Dash License Tool to repo.eclipse.org I've updated the documentation accordingly. https://github.com/eclipse/dash-licenses My next push will update the pom files for a 1.0.1 snapshot. Wayne -- Wayne Beaton Director of Open Source Projects | Eclipse Foundation My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours. ___ dash-dev mailing list dash-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Clean up Eclipse Dash Committers
I've removed the inactive committers who did not respond to this note (along with Dave and Nick). Thanks to everybody for your service to the project. Wayne On Wed, Dec 6, 2017 at 5:13 PM, Wayne Beaton < wayne.bea...@eclipse-foundation.org> wrote: > Greetings Eclipse Dash project. > > I'd like to clean up our committer list. It seems like a lot of us have > not contributed to this project in a while. > > If you wish to remain as a committer on Eclipse Dash, please respond to > this note. No explanation is required (just say "keep me" or something). > > I'll interpret silence to mean that you're no longer able to work on the > project. > > I'll start retiring folks during the week of December 18. > > Thanks! > > Wayne > > -- > Wayne Beaton > Director of Open Source Projects > The Eclipse Foundation > -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation ___ dash-dev mailing list dash-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Clean up Eclipse Dash Committers
Greetings Eclipse Dash project. I'd like to clean up our committer list. It seems like a lot of us have not contributed to this project in a while. If you wish to remain as a committer on Eclipse Dash, please respond to this note. No explanation is required (just say "keep me" or something). I'll interpret silence to mean that you're no longer able to work on the project. I'll start retiring folks during the week of December 18. Thanks! Wayne -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation ___ dash-dev mailing list dash-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Moving the Project Handbook and EDP sources into Dash
Actually, no. But you're still on the mailing list, so that's something. Unless I virtually hear great virtual screams in protest, I'm going to start this move early next week. Wayne On 09/09/15 09:59 PM, Anne Jacko wrote: +1 I guess I’m still a Dash committer! Anne On Sep 9, 2015, at 12:47 PM, Wayne Beaton <wa...@eclipse.org <mailto:wa...@eclipse.org>> wrote: Greetings Dash project folks! I've used Asciidoc to build the Eclipse Project Handbook, and am thinking of using the technology for a revision of the EDP that I'm working on. With this, there are build scripts and the opportunity to implement CI. I've started working on a Maven-based build to replace the makebuild that I'm using now. Right now, the sources for the handbook are in the /projects website Git repository. https://waynebeaton.wordpress.com/2015/08/11/technology-behind-the-new-eclipse-project-handbook/ I'm thinking that I'd like to move them to the Dash project and treat them like a proper project with formal releases. I think that this fall within the project's scope. Good idea? Bad idea? Thoughts? Wayne -- Wayne Beaton @waynebeaton The Eclipse Foundation <http://www.eclipsecon.org/europe2015> ___ dash-dev mailing list dash-dev@eclipse.org <mailto:dash-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dash-dev -- Wayne Beaton @waynebeaton The Eclipse Foundation EclipseCon Europe 2015 <http://www.eclipsecon.org/europe2015> ___ dash-dev mailing list dash-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Time to clean up the committer list
If you are a Dash committer, please let me know (by responding to this note) that you'd like to remain a committer on Dash. FWIW, the Dashboard, what most people tend to think of as "Dash", is actually a separate subproject (technology.dash.dashboard). The Dash project itself has three Git repositories containing mostly Maven-related stuff: org.eclipse.dash.m4e.tools.git org.eclipse.dash.maven.git org.eclipse.dash.test.git While we're at it... what is the status of the Maven-related stuff? Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
IP questions are kept private. Wayne On 04/25/2012 02:42 PM, Aaron Digulla wrote: Am 24.04.2012 15:53, schrieb Wayne Beaton: Question is posted. Thanks a lot. Is there a way I can follow the discussion? The search doesn't show up anything :-/ https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advancedshort_desc_type=allwordssubstrshort_desc=long_desc_type=substringlong_desc=bug_file_loc_type=allwordssubstrbug_file_loc=keywords_type=allwordskeywords=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=chfieldfrom=2012-04-23chfieldto=Nowchfield=%5BBug+creation%5Dchfieldvalue=cmdtype=doitorder=Reuse+same+sort+as+last+timefield0-0-0=nooptype0-0-0=noopvalue0-0-0= Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
On 04/24/2012 05:43 AM, Aaron Digulla wrote: Zitat von Wayne Beaton wa...@eclipse.org: Right. That functionality is limited to Project Leads and PMC members. Sorry about that. What have we learned yesterday? open source isn't that open after all ;-) Sorry... hot button item. What is your definition of open? We invite participation in the project. We have a level playing field for those who want to participate. We balance that with a well-defined policy for managing intellectual property. How is this not open? Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Question is posted. Wayne On 04/24/2012 05:43 AM, Aaron Digulla wrote: Zitat von Wayne Beaton wa...@eclipse.org: Right. That functionality is limited to Project Leads and PMC members. Sorry about that. What have we learned yesterday? open source isn't that open after all ;-) I guess that I'll have to pose the question. Thanks. Can you give me some words to start from? Sure: -- cut -- There was a request on the dash-dev mailing list how to handle the following situation: Copying code from public sources like Wikipedia, Stackoverflow or private blogs. To limit the scope of the discussion and kind of create a precedent, let's start with copying code from Stackoverflow. Stackoverflow.com is a site where all kinds of software developers share their knowledge. According to the rules of the site, all user contributions licensed under cc-wiki with attribution required (see the bottom of each page on http://stackoverflow.com/). cc-wiki means: You are free to share - to copy, distribute and transmit the work -, to remix - to adapt the work - and to make commercial use of the work (https://creativecommons.org/licenses/by-sa/3.0/) attribution required means You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Details can be found in this blog post: http://blog.stackoverflow.com/2009/06/attribution-required/ The four rules mentioned there apply if you copy (republish this content) the whole stackoverflow site - answers, questions, user data, everything. They don't make that much sense when just a piece of code is copied. For me, only the second rule makes sense in the context of using code from stackoverflow.com in Eclipse projects: Hyperlink directly to the original question I read that as: Add a comment with a link to the place where you found the code that you copied/used as a template. Can you please verify this for any code published on stackoverflow.com? My main goal is to get a single all-time approval for code so Eclipse developers can use this great resource without causing thousands of tiny CQ requests. If this works well, I'd like to file similar requests for other public developer resources like, for example, Wikipedia. -- cut -- Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
I'm just happy to see all this open communication on the Dash dev list. Wayne On 04/24/2012 01:23 PM, Andrew Overholt wrote: OK, I'll be the first to point out that you can't *ever* copy code from GPL'd projects, and that GPL isn't OSS. ;) Hahahahahaha. Andrew ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
The copied code is intellectual property and as such is subject to the Eclipse IP Due Diligence process. It can only be distributed from eclipse.org (e.g. a source code repository) if we have clear license from the author to do so. Yes, it's a small bit of code, but the full IP process still applies. The easiest way to make this work is to ask the original author to contribute the code as an attachment on a Bugzilla record with the following assertions in the comment: I authored 100% the content they are contributing; have the rights to donate the content to EPL; and contribute the content under the EPL. With this in place, you can add the code into the repository, flip the iplog+ flag, and be off to the races. Alternatively, I think we can make the case that Stack Overflow contributions are CC-licensed [1] and treat the code similar to a third-party library. However, I believe that license compatibility will be complicated. HTH, Wayne [1] http://creativecommons.org/licenses/by-sa/3.0/ On 04/23/2012 09:25 AM, Aaron Digulla wrote: Hello, I've stumbled over one of these corner cases: I copied 7 lines of code from stackoverflow.com (http://stackoverflow.com/a/3758880/34088) The code isn't an OSS project, it's not under a specific license and I feel that it's not worth the effort to run this through the standard IP process. What are the rules when you copy a code example from a blog? I tried to find some guidelines in the committer rules and IP process, etc, but everything there is more suitable for we want to fork some big OSS project. Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Sounds like a plan. Wayne On 04/23/2012 01:47 PM, Aaron Digulla wrote: How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Good question. Go to the portal, select any project (it doesn't matter) in the Eclipse Projects component. Click on the [pose] a question about general legal issue option. That'll take you to the right place. (or just go here: https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion) Wayne On 04/23/2012 02:40 PM, Aaron Digulla wrote: Am 23.04.2012 19:59, schrieb Wayne Beaton: Sounds like a plan. Since this is my first attempt to do this: That means I should open a CQ request on ipzilla, right? What project should I select? eclipse.platform? How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] IP Cleanliness question
Right. That functionality is limited to Project Leads and PMC members. Sorry about that. I guess that I'll have to pose the question. Can you give me some words to start from? Thanks, Wayne On 04/23/2012 04:01 PM, Aaron Digulla wrote: Am 23.04.2012 21:01, schrieb Wayne Beaton: Good question. Go to the portal, select any project (it doesn't matter) in the Eclipse Projects component. Click on the [pose] a question about general legal issue option. That'll take you to the right place. (or just go here: https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion https://dev.eclipse.org/ipzilla/enter_bug.cgi?product=IPcomponent=IP_Discussion) Thanks a lot for your help! Only, I get nowhere... :-) When I click new in ipzilla, I get page has moved, go to the portal. I did but there is nothing obviously related to CQ or IP processes on https://dev.eclipse.org/portal/myfoundation/portal/portal.php. When I try your link, I get: Sorry, either the product IP does not exist or you aren't authorized to enter a CQ into it. ... :-P Regards, On 04/23/2012 02:40 PM, Aaron Digulla wrote: Am 23.04.2012 19:59, schrieb Wayne Beaton: Sounds like a plan. Since this is my first attempt to do this: That means I should open a CQ request on ipzilla, right? What project should I select? eclipse.platform? How about I open an IP request so the lawyers can give a nod to the rule? This would create a simple, safe solution for all Eclipse developers because I bet that I wasn't the first one to wonder - I was just the first one who dared to ask :-) Regards, -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Maven Signing plug-in
Is the Maven signing plug-in information captured in the wiki somewhere? Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] where's /opt/public/cbi going?
There are still some projects that build using Athena. But it does seem that discussion traffic on the topic has dropped down to zero. We should start socializing the retirement. Athena is a project, so we'll have to run a termination review. I'm pretty sure Nick is in agreement (he'll speak up if otherwise). I'll add this to my list for September. In the meantime, we should start tweeting and blogging this to make sure that projects are thinking about the move to something like Tycho. Wayne On 07/28/2011 12:29 PM, David Carver wrote: Not sure, but the Athena project itself probably needs to go the Attic. It's not being actively maintained any longer. There are better alternatives now for setting up a build at eclipse. Dave On 07/28/2011 11:31 AM, Denis Roy wrote: I've renamed the cbi directory. Apologies -- I didn't think this was still being used. Who 'owns' it? Seems like there's some pretty old stuff in there. /shared/cbi/build # du * -sh 785Mdownloads 605Mgef 2.1Glinuxtools 58M org.eclipse.releng.basebuilder_R36_M3 67M org.eclipse.releng.basebuilder_R36_M4 61M org.eclipse.releng.basebuilder_R36_RC4 46M org.eclipse.releng.basebuilder_r35x_v20090811 37M org.eclipse.releng.basebuilder_r35x_v20090811.zip 64M org.eclipse.releng.basebuilder_releng_test_36p2api Denis On 07/28/2011 10:52 AM, Roy Ganor wrote: Hi Denis, what's up. Per Jacek and Dave discussion could you please revert this deletion? We can't process our builds anymore. Thanks for your time, Roy On Jul 28, 2011, at 3:45 PM, Denis Roy denis@eclipse.org mailto:denis@eclipse.org wrote: Is anyone still using that? I checked, and there are not many files in there that are less than 1 year old. Most of what's in there seems to date back to 2008. Denis On 07/28/2011 06:09 AM, Jacek Pospycha?a wrote: hi, I just noticed that /opt/public/cbi has moved to /opt/public/cbi.deleteme on build.eclipse.org can anybody shed some light on what's happening? thanks! Jacek ___ dash-dev mailing list dash-dev@eclipse.org mailto:dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Welcome Chris Aniszczyk as a new technology.dash Committer
technology.dash Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Chris Aniszczyk. Chris Aniszczyk is a new full Committer on the technology.dash project. Welcome! ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Welcome Jesse McConnell as a new technology.dash Committer
technology.dash Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Jesse McConnell. Jesse McConnell is a new full Committer on the technology.dash project. Welcome! ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Dash Dev Repo Maven Release Tools
Good to go if you've gotten your committer access. Wayne David Carver d_a_car...@yahoo.com wrote: Wayne, Are we good to go for setting up the Maven Release tools git repo? The initial purpose is to house the signing plugin, but I also want to get in there as well the overall eclipse-parent pom, that all other projects should inherit from. Dave ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Dash Dev Repo Maven Release Tools
My vote is for separate repos for separate functional areas. Wayne Chris Aniszczyk caniszc...@gmail.com wrote: On Tue, May 10, 2011 at 5:27 PM, Jesse McConnell jesse.mcconn...@gmail.com wrote: my election status appears to be 'waiting for webmaster provisioning' in the portal.. do we envision the repo do be just one repo? org.eclipse.dash/ m4e/ minerva/ maven-eclipse-signing-plugin/ ... pom.xml ? -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719 ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Committer vote for Jesse McConnell has concluded successfully
technology.dash Committers, This automatically generated message marks the successful completion of voting for Jesse McConnell to receive full Committer status on the technology.dash project. The next step is for the PMC to approve this vote, followed by the EMO processing the paperwork and provisioning the account. Vote summary: 6/0/0 with 6 not voting +1 Wayne Beaton ? Alex Blewitt ? Nick Boldt ? Janet Campbell +1 Sharon Corbett +1 Aaron Digulla ? Thomas Hallgren ? Anne Jacko ? Kim Moir +1 Andrew Niefer +1 Andrew Overholt +1 Denis Roy If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Committer vote for Chris Aniszczyk has concluded successfully
technology.dash Committers, This automatically generated message marks the successful completion of voting for Chris Aniszczyk to receive full Committer status on the technology.dash project. The next step is for the PMC to approve this vote, followed by the EMO processing the paperwork and provisioning the account. Vote summary: 6/0/0 with 6 not voting +1 Wayne Beaton ? Alex Blewitt ? Nick Boldt ? Janet Campbell +1 Sharon Corbett +1 Aaron Digulla ? Thomas Hallgren ? Anne Jacko ? Kim Moir +1 Andrew Niefer +1 Andrew Overholt +1 Denis Roy If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Vote for Committer status for Chris Aniszczyk was started by Wayne Beaton
technology.dash Committers, This automatically generated message signals that Wayne Beaton has nominated Chris Aniszczyk as a Committer on the technology.dash project. The reason given is as follows: With bug 342336 [1], we have accepted a chunk of code that provides signing support for Eclipse plug-ins built using Maven/Tycho. Chris needs to be a committer on Dash to help maintain this contribution. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 The vote is being held via the MyFoundation portal: voters *must* use the portal for the votes to be properly recorded. The voting will continue until either all 12 existing Committers have voted or until they have been given enough time to vote, even if they do not do so (defined as at least one week). Chris Aniszczyk must receive at least three +1s and no -1s for a successful election. Eligible Committers must cast their votes through their My Foundation portal page (do NOT just reply to this email; your vote will not be correctly recorded unless you use the portal): http://portal.eclipse.org/ The project Committers eligible to vote are: Wayne Beaton Alex Blewitt Nick Boldt Janet Campbell Sharon Corbett Aaron Digulla Thomas Hallgren Anne Jacko Kim Moir Andrew Niefer Andrew Overholt Denis Roy *NOTE*: Successful elections are left open for a maximum of 120 days to allow for processing of paperwork. After that time the election will be expired, regardless of its current status. Should papework processing on the part of the candidate take more time than allowed, a new election will have to be held. If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Vote for Committer status for David Carver was started by Wayne Beaton
technology.dash Committers, This automatically generated message signals that Wayne Beaton has nominated David Carver as a Committer on the technology.dash project. The reason given is as follows: With bug 342336 [1], we have accepted a chunk of code that provides signing support for Eclipse plug-ins built using Maven/Tycho. Dave needs to be a committer on Dash to help maintain this contribution. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 The vote is being held via the MyFoundation portal: voters *must* use the portal for the votes to be properly recorded. The voting will continue until either all 12 existing Committers have voted or until they have been given enough time to vote, even if they do not do so (defined as at least one week). David Carver must receive at least three +1s and no -1s for a successful election. Eligible Committers must cast their votes through their My Foundation portal page (do NOT just reply to this email; your vote will not be correctly recorded unless you use the portal): http://portal.eclipse.org/ The project Committers eligible to vote are: Wayne Beaton Alex Blewitt Nick Boldt Janet Campbell Sharon Corbett Aaron Digulla Thomas Hallgren Anne Jacko Kim Moir Andrew Niefer Andrew Overholt Denis Roy *NOTE*: Successful elections are left open for a maximum of 120 days to allow for processing of paperwork. After that time the election will be expired, regardless of its current status. Should papework processing on the part of the candidate take more time than allowed, a new election will have to be held. If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Welcome Aaron Digulla as a new technology.dash Committer
technology.dash Committers, This automatically generated message marks the completion of all the legal paperwork and webmaster provisioning for Aaron Digulla. Aaron Digulla is a new full Committer on the technology.dash project. Welcome! ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] eclipse signing plugin
How do we want to proceed with this? Chris, is this part of Minerva? How is that proposal coming along? Wayne On 04/08/2011 05:37 PM, Jesse McConnell wrote: Dave Carver bugged me incessantly enough to send a few minutes to fix a couple of jetty specific things with the eclipse signing plugin we use in jetty and contribute it here. The README.txt in the tarball has the usage example...Its not pretty but its worked for us for over a year now. I can help clean it up as needed if there is desire https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 cheers, jesse -- jesse mcconnell jesse.mcconn...@gmail.com ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] upgrade eclipse3.6 to eclipse3.7M6, the junit test could not find junit
This mailing is list is probably not the right place for your question. I recommend that you pose this question on the eclipse.platform forum: http://www.eclipse.org/forums/eclipse.platform You should provide more information. What build.xml file are you asking about? What, specificially, is the error reported? HTH, Wayne On 03/24/2011 08:31 PM, 赵忠伟 wrote: hi, when I upgrade eclipse3.6 to eclipse3.7M6,the junit test could not find junit,and I found the generated build.xml for the test project is: pathelement path=../org.junit_3.8.2.v3_8_2_v20100427-1100.jar/ but before it was: pathelement path=../org.junit_3.8.2.v3_8_2_v20100427-1100/junit.jar/ Does anyone know what is wrong,thanks very much! -- Thanks! Best Regards! Zhao ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Git repo for m4e tools
There was a header in the first file I looked at. I didn't notice the missing headers in the rest. Nice catch. FWIW, I include you in our when I say our intellectual property backsides. It's not only you that we're trying to protect; potential adopters of the software need protections as well. :-) Wayne On 03/18/2011 12:07 PM, Aaron Digulla wrote: Zitat von Wayne Beaton wa...@eclipse.org: Honestly, I think you're doing a better job than most Eclipse projects :-) Thanks. I've started the AROS project (www.aros.org) which is a clean room implementation of the Amiga OS. That started in 1993 and I learned a lot about international copyright law, IP laws, etc. So I've been there, done that. Bear in mind that--owing to the fact that you're not a committer yet--we're going to have to run this as a contribution through the IP process. That shouldn't be a big deal, except that the IP team is running pretty hard with Indigo stuff right now. The fact that you've got the right headers, and all the right files in the right places should make this a lot easier/faster. I forgot the headers in the first commits; I hope that's not a problem. [...] Hopefully, this doesn't sound scary. We just need to cover our intellectual property ownership backsides... Looking at Sony vs. Hotz, or on groklaw, it does sound scary. But I have no intention to ever visit the US - so you can sue me as much as you like. Switzerland doesn't deport for copyright crimes. Regards, ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Naming the Maven effort
I am concerned that naming your efforts m4e is potentially confusing for the community as it seems awfully close to m2e [1]. m2e comes from Maven 2 Plug-in for Eclipse and, apparently, some folks from the Maven community are already asking about m3e for Maven 3. Thoughts? Wayne [1] http://www.eclipse.org/m2e ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Project Dash m4e Tools
Nah. You just need a Bugzilla ID. Wayne On 03/18/2011 03:31 PM, Aaron Digulla wrote: Am 18.03.2011 17:45, schrieb Wayne Beaton: Can we make sure that this sort of information eventually finds a home in the wiki? Can I already access the wiki? I thought I need to wait for my committer accolade. Regards, ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
Re: [dash-dev] Maven Repository at Eclipse
I am on the dash-dev mailing list. I'm not sure what help I'll be, but I'm there. Wayne On 03/11/2011 04:30 AM, Alex Blewitt wrote: I've added my SSH public key to ~/.ssh/authorized_keys in order to log on without requiring a password, as described here: http://help.github.com/set-up-git-redirect/ I've also subscribed to the dash-dev list. Once we've confirmed we have all joined that list, we should move discussions there. Presumably Denis and Wayne are already on it? Some things we probably need to decide on: * What version of Nexus to use - I have heard of an issue with 1.9 and indexes being incompatible with Maven 2 clients; it might be good to stick with 1.8 for the time being * What set of repositories to create, for example 'milestones', 'nightly', 'release' After the initial set up is available, we probably want to also consider how to structure the contents in the repository. At least initially, we probably want to invite those generating Maven artefacts (ECF, JGit, EclipseLink, Virgo, Gemini) to put their content in directly. I think we could have a good interim milestone by making these available. Looking further ahead, we probably want to consider other things: * Should we create a top-level POM like Apache? http://repo1.maven.org/maven2/org/apache/apache/9/apache-9.pom * Documentation of naming groups - a pre-existing Eclipse bug suggested org.eclipse.nextlevel as the groupId and the full name as artifact, so org.eclipse.jdt.ui would be a GAV of org.eclipse.jdt:org.eclipse.jdt.ui:1.2.3. The nextlevel would be a regex of the existing name rather than any relation to the project, so org.eclipse.osgi.* would have a group of org.eclipse.osgi rather than attempting to line up with any project ownership like RT or Equinox. From a permissioning perspective, there's probably a 1-1 mapping between project and group id in most cases (ECF - org.eclipse.ecf) though some groups (Equinox/RT) may have multiple groupIds. * Version mapping - as well as the _ and - difference separating the name and version, we probably ought to drop the build id. Virgo (and other SpringSource components) use -M01, -M02, -M3 ... and .RELEASE as their suffixes. This has the property that the versions are short, understandable, and are lexicographically sorted so will work appropriately when deployed into an OSGi runtime. http://www.eclipse.org/virgo/download/milestones.php http://www.eclipse.org/virgo/download/ 2.1.0.M01 2.1.0.M02 ... 2.1.0.RELEASE We probably want to rename (or symlink?) the files produced by the build process (rather than rebuilding) but changing the names only. As a result, we could wait for (say) Indigo -M3 to spin up, then use the contents of the repository to generate a ver.M03 Maven version number. Please let me know your thoughts and to confirm that we're all on the dash-dev mailing list. Alex ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Committer vote for Aaron Digulla has concluded unsuccessfully
technology.dash Committers, This automatically generated message marks the completion of the committer vote for Aaron Digulla. Unfortunately, the vote did not gather enough +1s in the voting period, thus the vote was not successful. Vote summary: 2/0/0 with 7 not voting ? Nick Boldt ? Janet Campbell ? Sharon Corbett ? Thomas Hallgren ? Anne Jacko ? Kim Moir ? Andrew Niefer +1 Andrew Overholt +1 Denis Roy If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Vote for Committer status for Alex Blewitt was started by Wayne Beaton
technology.dash Committers, This automatically generated message signals that Wayne Beaton has nominated Alex Blewitt as a Committer on the technology.dash project. The reason given is as follows: For Bug 337068, we are getting a team together to kickstart a effort to provide a Maven repository of Eclipse artefacts, maven.eclipse.org. Webmaster is rightly concerned that the folks involved should be committers. At this point, creating a new project doesn't feel like the right thing to do at this point in time. Alex, who is well-known to our community, has stepped up to help with this effort, but is not a committer. Since this effort is about providing a service to projects and committers, Dash--the Tools for Commmitter project--is the most natural place for him to be a committer. FWIW, the Dash project itself does not have much in terms of resources (there is no source repository, for example), so we're not going to be giving him access to very much :-( * https://bugs.eclipse.org/bugs/show_bug.cgi?id=337068 The vote is being held via the MyFoundation portal: voters *must* use the portal for the votes to be properly recorded. The voting will continue until either all 9 existing Committers have voted or until they have been given enough time to vote, even if they do not do so (defined as at least one week). Alex Blewitt must receive at least three +1s and no -1s for a successful election. Eligible Committers must cast their votes through their My Foundation portal page (do NOT just reply to this email; your vote will not be correctly recorded unless you use the portal): http://portal.eclipse.org/ The project Committers eligible to vote are: Nick Boldt Janet Campbell Sharon Corbett Thomas Hallgren Anne Jacko Kim Moir Andrew Niefer Andrew Overholt Denis Roy *NOTE*: Successful elections are left open for a maximum of 120 days to allow for processing of paperwork. After that time the election will be expired, regardless of its current status. Should papework processing on the part of the candidate take more time than allowed, a new election will have to be held. If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Vote for Committer status for Wayne Beaton was started by Wayne Beaton
technology.dash Committers, This automatically generated message signals that Wayne Beaton has nominated Wayne Beaton as a Committer on the technology.dash project. The reason given is as follows: The Dash project has been without a project lead, or any activity for some time. Given the nature of the project (intended to provide tools for committers) and the fact that nobody else has stepped up to take on important roles, and the fact that Wayne has demonstrated a certain amount of knowledge in the area of providing tools for committers (he is the project lead for eclipse.dash.dashboard and the sole maintainer of the /projects directory on www), this seems a natural fit. Please vote for Wayne. A chicken in every pot. The vote is being held via the MyFoundation portal: voters *must* use the portal for the votes to be properly recorded. The voting will continue until either all 9 existing Committers have voted or until they have been given enough time to vote, even if they do not do so (defined as at least one week). Wayne Beaton must receive at least three +1s and no -1s for a successful election. Eligible Committers must cast their votes through their My Foundation portal page (do NOT just reply to this email; your vote will not be correctly recorded unless you use the portal): http://portal.eclipse.org/ The project Committers eligible to vote are: Nick Boldt Janet Campbell Sharon Corbett Thomas Hallgren Anne Jacko Kim Moir Andrew Niefer Andrew Overholt Denis Roy *NOTE*: Successful elections are left open for a maximum of 120 days to allow for processing of paperwork. After that time the election will be expired, regardless of its current status. Should papework processing on the part of the candidate take more time than allowed, a new election will have to be held. If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Committer vote for Wayne Beaton has concluded successfully
technology.dash.dashboard Committers, This automatically generated message marks the successful completion of voting for Wayne Beaton to receive full Committer status on the technology.dash.dashboard project. The next step is for the PMC to approve this vote, followed by the EMO processing the paperwork and provisioning the account. Vote summary: 1/0/0 with 0 not voting +1 Nick Boldt If you have any questions, please do not hesitate to contact your project lead, PMC member, or the EMO e...@eclipse.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
[dash-dev] Including Orbit Bundles in generated update site
I need three JARs from Orbit in my update site. Athena doesn't seem to want to put them there, so I'm wondering what magic is required. My feature.xml lists the Orbit bundles. They're referenced in my map file. Everything seems to build. My build scripts are in CVS: /cvsroot/technology org.eclipse.epp/releng/org.eclipse.epp.usagedata.releng.athena Google hasn't been very helpful, I'm afraid. I've tried to locate other projects doing this, but haven't had any luck. Can somebody give me a pointer? Wayne -- Wayne Beaton, The Eclipse Foundation http://www.eclipse.org I'm going to EclipseCon! http://www.eclipsecon.org ___ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
