Not sure, whether I understood correctly.. It seems to be allowed to use 3rd-party tools, if the project itself (and maybe others) have a benefit from using it. That's great. It seems to me that its allowed to use free tools as well as tool which require a license to use the tool. Later would possible if the license is sponsored to individuals/organisations from the tool provider /other organization.
In this case some of use got a I guess personal/individual license (like Jody) and some others not. I would prefer to keep the screen definitions in codebase because its a good way to communicate RFC's with a visual sketch. What do you think about contacting Peter Severin (WireframeSketcher founder) to provide some license for LocationTech uDig'ers. Like listed in Eclipse guidelines we could mention the tool in our release notes. I guess Eclipse Foundation would be a great platform from wireframesketchers (using Eclipse Platform) from a commercial point of view. However, is's also possible for Non-Profit organizations like the Eclipse Foundation to save 50% (at the moment). As an other option to create UI-Mockups I like to mention balsamiq ( balsamiq.com). There we could get a free license as a Non-Profit Organization (http://support.balsamiq.com/customer/portal/articles/105924) Great descriptions of free awailable Mockup-Tools : http://speckyboy.com/2011/02/23/10-completely-free-wireframing-and-mockup-tools/ Thoughts? IMHO if the IP Team accept the *.screen contributions, we should take it with us... - Frank 2013/5/27 Wayne Beaton <wa...@eclipse.org> > > On 05/27/2013 03:43 AM, Frank Gasdorf wrote: > > Question: > * How do we handle *-screen files (created with WireframeSketchers). These > are ecore-model files but are not required at runtime. We used it to > document RFC's initial UI ideas. Remove these? > > If you feel that these files have continuing value, you should check with > the IP team before just removing them. > > I believe that this introduces an implied proprietary tool dependency on > WireframeSketchers. As you have no-doubt guessed already, we have a policy: > > http://eclipse.org/org/documents/Eclipse_Using_Proprietary_Tools_Final.php > > HTH, > > Wayne > -- > Wayne Beaton > Director of Open Source Projects, The Eclipse > Foundation<http://www.eclipse.org> > Learn about Eclipse Projects <http://www.eclipse.org/projects> > [image: EclipseCon France 2013] <http://www.eclipsecon.org/france2013> > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > >Title: Re: [udig-devel] location tech initial contribution update
|
On 05/27/2013 03:43 AM, Frank Gasdorf
wrote:
If you feel that these files have continuing value, you should check with the IP team. They have experience with code generators. My understanding is that the licensing of the tool used does not necessarily imply the license of the content generated from that tool. Likewise, it would be worth checking with them regarding screenshots and what-not generated from those ecore files. I believe that this introduces an implied proprietary tool dependency on WireframeSketchers. As you have no-doubt guessed already, we have a policy: http://eclipse.org/org/documents/Eclipse_Using_Proprietary_Tools_Final.php HTH, Wayne --
Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects |
