I can contact the vendor. Note that the version downloaded through the eclipse marketplace does include the functionality we use as part of its free license.
(The paid for license removes a watermark on generated images).
Still these are "only" documentation, responsible for generating some of the pictures used for UI design they can be removed from the codebase.
Indeed the pice of the app has increased greatly (as indeed have its capabilities).
--
Jody Garnett
On Wednesday, 29 May 2013 at 12:30 AM, Wayne Beaton wrote:
With regard to the WireframeSketcher software, I think that this bit in the policy is the blocker: "Vendors must agree to provide free licenses for all Eclipse committers, plus those individuals identified by name by a project leader, for use on the project." I don't see any obvious "free for open source projects" licensing options. However, if you contact the vendor directly and they agree to the terms, then we can work with them.
Can we make a reasonable argument that the files are otherwise useful without the WireframeSketcher software?
Again, I defer to the IP team regarding the nature of the license of the generated artefacts.
HTH,
Wayne
On 05/28/2013 03:04 AM, Frank Gasdorf wrote:
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>If you feel that these files have continuing value, you should check with the IP team before just removing them.
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?
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
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects
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.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?
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
_______________________________________________User-friendly Desktop Internet GIS (uDig)
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
