Home » Eclipse Projects » DTP » Attempt to avoid misuse of Eclipse Foundation trademarks
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38091 is a reply to message #38026] |
Mon, 05 November 2007 11:12   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Jeff,
Have a look at http://www.eclipse.org/legal/logo_guidelines.php. Given
that your intent is to contribute it to Eclipse, I don't imagine anyone
will object to your use of exactly the trademarks that will be used when
the donation process is completed.
If you have multiple people working on the contribution, make sure you
arecarefully tracking everyone who is contributing. You might want to
open a bugzilla already, and add the code as an attachment. Anyone
making updates to it could provide a new attachment. This way you have
a clearly pedigree of contributors tracked in the bugzilla itself. If
the code is more than 250 lines, it will need to be IP reviewed. I'm
not sure if DTP has an incubator project; gosh, the website is still not
in Phoenix format! If it did, that could make use of the parallel IP
process whereby the CQ can be approved to be committed to CVS before the
full IP review is completed. I assume that the DTP folks would be
interested in the contribution, but if not, I could imagine setting this
up as an EMFT project as well (which can take advantage of the parallel
IP processes). It does seem better in DTP though since I'm pretty sure
DTP already depends on EMF while nothing in EMFT currently depends on
DTP. If the contribution does not introduce dependencies on third party
libraries and has a very clear pedigree of who contributed it to EPL,
the review process should be very quick. It's the third party libraries
and tracking down their pedigree and applicable licenses that represents
the most time consume aspect of the IP review.
If there's anything I can do to help, please ask. I'd be interested to
see the code since I know nothing about ODA and like to learn...
Jeff Ramsdale wrote:
> This is not specifically a DTP question, but it does pertain to the
> project. I've been working on an EMF ODA driver and a couple of other
> people have expressed interest in helping out. I'd hope to donate the
> product of my/our work to the Eclipse Foundation but understand the IP
> donation process can be time-consuming. Though only a modest amount of
> code would be involved I suspect it would exceed the size of a typical
> patch donation, thus triggering the more rigorous IP approval process.
> Please correct me if I'm wrong.
>
> The question, then, is whether there are any trademarks involved if I
> name the project something like "EMF ODA Driver" and host it at
> another site. If any trademarks are involved is this an approved
> practice? If they are not involved is there any reason I shouldn't use
> such a name? Any other advice appreciated...
>
> Jeff
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38155 is a reply to message #38091] |
Tue, 06 November 2007 00:12 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Jeff,
>> whether there are any trademarks involved if I name the project
>> something like "EMF ODA Driver" and host it at another site. ... Any
>> other advice appreciated...
Your contribution would indeed fit in the DTP Enablement sub-project:
http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in it
..
As you'd noted, a source level contribution to Eclipse.org would take some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to your
project page. See http://www.eclipse.org/datatools/community.html . You
can see that there are already a variety of DTP adopters, including ODA ones
listed in the Community page, with different levels of contribution.
Linda
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38188 is a reply to message #38155] |
Tue, 06 November 2007 00:32 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------000501060607070706040207
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Linda,
The parallel IP review for the Emfatic component in EMFT took only one
week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
Linda Chan wrote:
> Jeff,
>
>
>>> whether there are any trademarks involved if I name the project
>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>> other advice appreciated...
>>>
>
> Your contribution would indeed fit in the DTP Enablement sub-project:
> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
> kick-start the process, start with creating a Bugzilla entry for the Data
> Tools -> Enablement ODA component, and attach the source contribution in it
> .
>
> As you'd noted, a source level contribution to Eclipse.org would take some
> time, as it involves technical review and an Eclipse IP review. The DTP
> project thus also facilitates direct third-party contribution by any DTP
> adopters. Basically, one will provide your own web page and download site
> for your contribution, which can be either binary only or source as well.
> And the DTP project web site would include a descrption with a link to your
> project page. See http://www.eclipse.org/datatools/community.html . You
> can see that there are already a variety of DTP adopters, including ODA ones
> listed in the Community page, with different levels of contribution.
>
> Linda
>
>
>
--------------000501060607070706040207
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Linda,<br>
<br>
The parallel IP review for the Emfatic component in EMFT took only one
week. <a href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a>
Is the Enablement sub-project of DTP a conforming incubating subproject
that can take advantage of parallel IP? Do you create components in
this subproject and give committer rights to the folks who maintain
will maintain the contributions? Or is this a one time contribution
and you will take over the long term maintenance and support for this?
Jeff, please post the bugzilla number here.<br>
<br>
<br>
Linda Chan wrote:
<blockquote cite="mid:fgobhi$9gt$1@build.eclipse.org" type="cite">
<pre wrap="">Jeff,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> whether there are any trademarks involved if I name the project
something like "EMF ODA Driver" and host it at another site. ... Any
other advice appreciated...
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
Your contribution would indeed fit in the DTP Enablement sub-project:
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/datatools/project_enablement/index.ht ml"> http://www.eclipse.org/datatools/project_enablement/index.ht ml</a> . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in it
..
As you'd noted, a source level contribution to Eclipse.org would take some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to your
project page. See <a class="moz-txt-link-freetext" href="http://www.eclipse.org/datatools/community.html">http://www.eclipse.org/datatools/community.html</a> . You
can see that there are already a variety of DTP adopters, including ODA ones
listed in the Community page, with different levels of contribution.
Linda
</pre>
</blockquote>
<br>
</body>
</html>
--------------000501060607070706040207--
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38254 is a reply to message #38188] |
Tue, 06 November 2007 22:43 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Ed,
I'll have to check on the parallel IP part.
As for on-going maintenance, we certainly require having committers to
provide on-going support. It will depend on whether the original contributor
is ready to commit some development resources on an on-going basis. Or if we
can find existing committers who are willing to take up the contribution.
Another alternative is for the original contributor to provide maintenance
patches, and an existing committer would review and commit them. In other
words, it could vary on a case-by-case basis, and may change over different
stages of a contribution.
Linda
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:fgocj9$ii5$1@build.eclipse.org...
> Linda,
>
> The parallel IP review for the Emfatic component in EMFT took only one
> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
> Enablement sub-project of DTP a conforming incubating subproject that
> can take advantage of parallel IP? Do you create components in this
> subproject and give committer rights to the folks who maintain will
> maintain the contributions? Or is this a one time contribution and you
> will take over the long term maintenance and support for this? Jeff,
> please post the bugzilla number here.
>
>
> Linda Chan wrote:
>> Jeff,
>>
>>
>>>> whether there are any trademarks involved if I name the project
>>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>>> other advice appreciated...
>>>>
>>
>> Your contribution would indeed fit in the DTP Enablement sub-project:
>> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
>> kick-start the process, start with creating a Bugzilla entry for the Data
>> Tools -> Enablement ODA component, and attach the source contribution in
>> it
>> .
>>
>> As you'd noted, a source level contribution to Eclipse.org would take
>> some
>> time, as it involves technical review and an Eclipse IP review. The DTP
>> project thus also facilitates direct third-party contribution by any DTP
>> adopters. Basically, one will provide your own web page and download
>> site
>> for your contribution, which can be either binary only or source as well.
>> And the DTP project web site would include a descrption with a link to
>> your
>> project page. See http://www.eclipse.org/datatools/community.html .
>> You
>> can see that there are already a variety of DTP adopters, including ODA
>> ones
>> listed in the Community page, with different levels of contribution.
>>
>> Linda
>>
>>
>>
>
>
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38385 is a reply to message #38254] |
Wed, 07 November 2007 14:27 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------080305040106040002000601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Linda,
Cool. That's a very flexible approach. Thanks for the info! Note that
the IP folks at Eclipse approved
http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862 for inclusion via
parallel IP in just an hour! I'll be very interested to look at the
contribution so I can learn some new things.
Linda Chan wrote:
> Ed,
>
> I'll have to check on the parallel IP part.
>
> As for on-going maintenance, we certainly require having committers to
> provide on-going support. It will depend on whether the original contributor
> is ready to commit some development resources on an on-going basis. Or if we
> can find existing committers who are willing to take up the contribution.
> Another alternative is for the original contributor to provide maintenance
> patches, and an existing committer would review and commit them. In other
> words, it could vary on a case-by-case basis, and may change over different
> stages of a contribution.
>
> Linda
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:fgocj9$ii5$1@build.eclipse.org...
>
>> Linda,
>>
>> The parallel IP review for the Emfatic component in EMFT took only one
>> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
>> Enablement sub-project of DTP a conforming incubating subproject that
>> can take advantage of parallel IP? Do you create components in this
>> subproject and give committer rights to the folks who maintain will
>> maintain the contributions? Or is this a one time contribution and you
>> will take over the long term maintenance and support for this? Jeff,
>> please post the bugzilla number here.
>>
>>
>> Linda Chan wrote:
>>
>>> Jeff,
>>>
>>>
>>>
>>>>> whether there are any trademarks involved if I name the project
>>>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>>>> other advice appreciated...
>>>>>
>>>>>
>>> Your contribution would indeed fit in the DTP Enablement sub-project:
>>> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
>>> kick-start the process, start with creating a Bugzilla entry for the Data
>>> Tools -> Enablement ODA component, and attach the source contribution in
>>> it
>>> .
>>>
>>> As you'd noted, a source level contribution to Eclipse.org would take
>>> some
>>> time, as it involves technical review and an Eclipse IP review. The DTP
>>> project thus also facilitates direct third-party contribution by any DTP
>>> adopters. Basically, one will provide your own web page and download
>>> site
>>> for your contribution, which can be either binary only or source as well.
>>> And the DTP project web site would include a descrption with a link to
>>> your
>>> project page. See http://www.eclipse.org/datatools/community.html .
>>> You
>>> can see that there are already a variety of DTP adopters, including ODA
>>> ones
>>> listed in the Community page, with different levels of contribution.
>>>
>>> Linda
>>>
>>>
>>>
>>>
>>
>
>
>
--------------080305040106040002000601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Linda,<br>
<br>
Cool. That's a very flexible approach. Thanks for the info! Note
that the IP folks at Eclipse approved
<a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862</a> for inclusion via
parallel IP in just an hour! I'll be very interested to look at the
contribution so I can learn some new things.<br>
<br>
<br>
Linda Chan wrote:
<blockquote cite="mid:fgqqn1$bbh$1@build.eclipse.org" type="cite">
<pre wrap="">Ed,
I'll have to check on the parallel IP part.
As for on-going maintenance, we certainly require having committers to
provide on-going support. It will depend on whether the original contributor
is ready to commit some development resources on an on-going basis. Or if we
can find existing committers who are willing to take up the contribution.
Another alternative is for the original contributor to provide maintenance
patches, and an existing committer would review and commit them. In other
words, it could vary on a case-by-case basis, and may change over different
stages of a contribution.
Linda
"Ed Merks" <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fgocj9$ii5$1@build.eclipse.org">news:fgocj9$ii5$1@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Linda,
The parallel IP review for the Emfatic component in EMFT took only one
week. <a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a> Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
Linda Chan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Jeff,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> whether there are any trademarks involved if I name the project
something like "EMF ODA Driver" and host it at another site. ... Any
other advice appreciated...
</pre>
</blockquote>
</blockquote>
<pre wrap="">Your contribution would indeed fit in the DTP Enablement sub-project:
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/datatools/project_enablement/index.ht ml"> http://www.eclipse.org/datatools/project_enablement/index.ht ml</a> . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in
it
..
As you'd noted, a source level contribution to Eclipse.org would take
some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download
site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to
your
project page. See <a class="moz-txt-link-freetext" href="http://www.eclipse.org/datatools/community.html">http://www.eclipse.org/datatools/community.html</a> .
You
can see that there are already a variety of DTP adopters, including ODA
ones
listed in the Community page, with different levels of contribution.
Linda
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
--------------080305040106040002000601--
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38451 is a reply to message #38188] |
Thu, 08 November 2007 06:11 |
 Jeff Ramsdale
Messages: 122
Registered: July 2009 |
Senior Member |
|
|
Hi Ed,
I've been working with the existing Bugzilla entry:
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if I
should open another entry when the code is ready for a look (it's not, yet).
Which raises the point... Several people have contacted me about helping
to work on this but it's difficult to collaborate without a public code
repository. I could set up a project somewhere else, but the hope would
be to donate it and expedite the IP process anyway. So I'd rather finish
the coding at DTP. Also, up to this point I'm the only dev (except for 1
data file), so it would be easier to track the contributions of others
at DTP than elsewhere.
I'd like to continue to support the contribution after it's promoted,
but once it's released I don't see it being something that would require
a lot of ongoing maintenance.
Thanks for your comments, too, Linda, and let me know what you learn
about parallel IP...
-jeff
Ed Merks wrote:
> Linda,
>
> The parallel IP review for the Emfatic component in EMFT took only one
> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
> Enablement sub-project of DTP a conforming incubating subproject that
> can take advantage of parallel IP? Do you create components in this
> subproject and give committer rights to the folks who maintain will
> maintain the contributions? Or is this a one time contribution and you
> will take over the long term maintenance and support for this? Jeff,
> please post the bugzilla number here.
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38484 is a reply to message #38451] |
Thu, 08 November 2007 12:11 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------070305070207010605080707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Jeff,
I'll bet there is a lot of interest in this. I'm not sure if I
understand correctly, but I think quite a few people want something like
this to feed data into BIRT for example.
What I've been doing with EMFT is creating new components to accommodate
small development teams or even just individuals. Each component is
effectively like a subproject within the EMFT project so access to code
and voting writings are partitioned:
<http://wiki.eclipse.org/Modeling_Project_Organization>
http://wiki.eclipse.org/Modeling_Project_Organization
This givens folks a sense of security (control over their own code),
ownership, and inclusion. Perhaps that type of structure would work for
the DTP's incubator project. I've found that this component approach is
attracting contributors at a very rapid pace of late with these being
very recent examples:
<http://wiki.eclipse.org/EMFT#Proposed_Components>
http://wiki.eclipse.org/EMFT#Proposed_Components
The first three have been approved and are being provisioned. The
approval for Mint will complete today, and the latest one Temporality
will be announced today.
I'm not sure what specifically to suggest for this case. It makes some
sense to set it up in EMFT (which likely could reach the provisioning
stage---CVS modules and parallel IP reviewed code ready to be
committed---in as little as three weeks), but it seems better to be in
DTP. Setting something up a source forge is reasonable too I suppose,
but I'd like to see Eclipse be a great place for collaboration. In any
case, tracking pedigree and ensuring that everyone understands and
agrees they are contributing to EPL is important. Sharing zips via a
bugzilla isn't much fun...
Jeff Ramsdale wrote:
> Hi Ed,
>
> I've been working with the existing Bugzilla entry:
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if
> I should open another entry when the code is ready for a look (it's
> not, yet).
>
> Which raises the point... Several people have contacted me about
> helping to work on this but it's difficult to collaborate without a
> public code repository. I could set up a project somewhere else, but
> the hope would be to donate it and expedite the IP process anyway. So
> I'd rather finish the coding at DTP. Also, up to this point I'm the
> only dev (except for 1 data file), so it would be easier to track the
> contributions of others at DTP than elsewhere.
>
> I'd like to continue to support the contribution after it's promoted,
> but once it's released I don't see it being something that would
> require a lot of ongoing maintenance.
>
> Thanks for your comments, too, Linda, and let me know what you learn
> about parallel IP...
>
> -jeff
>
> Ed Merks wrote:
>> Linda,
>>
>> The parallel IP review for the Emfatic component in EMFT took only
>> one week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is
>> the Enablement sub-project of DTP a conforming incubating subproject
>> that can take advantage of parallel IP? Do you create components in
>> this subproject and give committer rights to the folks who maintain
>> will maintain the contributions? Or is this a one time contribution
>> and you will take over the long term maintenance and support for
>> this? Jeff, please post the bugzilla number here.
--------------070305070207010605080707
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jeff,<br>
<br>
I'll bet there is a lot of interest in this. I'm not sure if I
understand correctly, but I think quite a few people want something
like this to feed data into BIRT for example. <br>
<br>
What I've been doing with EMFT is creating new components to
accommodate small development teams or even just individuals. Each
component is effectively like a subproject within the EMFT project so
access to code and voting writings are partitioned:<a
href="http://wiki.eclipse.org/Modeling_Project_Organization"><br>
</a>
<blockquote><a
href="http://wiki.eclipse.org/Modeling_Project_Organization">http://wiki.eclipse.org/Modeling_Project_Organization</a><br>
</blockquote>
This givens folks a sense of security (control over their own code),
ownership, and inclusion. Perhaps that type of structure would work
for the DTP's incubator project. I've found that this component
approach is attracting contributors at a very rapid pace of late with
these being very recent examples:<a
href="http://wiki.eclipse.org/EMFT#Proposed_Components"><br>
</a>
<blockquote><a href="http://wiki.eclipse.org/EMFT#Proposed_Components">http://wiki.eclipse.org/EMFT#Proposed_Components</a><br>
</blockquote>
The first three have been approved and are being provisioned. The
approval for Mint will complete today, and the latest one Temporality
will be announced today.<br>
<br>
I'm not sure what specifically to suggest for this case. It makes some
sense to set it up in EMFT (which likely could reach the provisioning
stage---CVS modules and parallel IP reviewed code ready to be
committed---in as little as three weeks), but it seems better to be in
DTP. Setting something up a source forge is reasonable too I suppose,
but I'd like to see Eclipse be a great place for collaboration. In any
case, tracking pedigree and ensuring that everyone understands and
agrees they are contributing to EPL is important. Sharing zips via a
bugzilla isn't much fun...<br>
<br>
<br>
Jeff Ramsdale wrote:
<blockquote cite="mid:fgu9al$h71$1@build.eclipse.org" type="cite">Hi
Ed,
<br>
<br>
I've been working with the existing Bugzilla entry:
<a class="moz-txt-link-rfc2396E" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958"><https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958></a>. Let me
know if I should open another entry when the code is ready for a look
(it's not, yet).
<br>
<br>
Which raises the point... Several people have contacted me about
helping to work on this but it's difficult to collaborate without a
public code repository. I could set up a project somewhere else, but
the hope would be to donate it and expedite the IP process anyway. So
I'd rather finish the coding at DTP. Also, up to this point I'm the
only dev (except for 1 data file), so it would be easier to track the
contributions of others at DTP than elsewhere.
<br>
<br>
I'd like to continue to support the contribution after it's promoted,
but once it's released I don't see it being something that would
require a lot of ongoing maintenance.
<br>
<br>
Thanks for your comments, too, Linda, and let me know what you learn
about parallel IP...
<br>
<br>
-jeff
<br>
<br>
Ed Merks wrote:
<br>
<blockquote type="cite">Linda,
<br>
<br>
The parallel IP review for the Emfatic component in EMFT took only one
week. <a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a> Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>
--------------070305070207010605080707--
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38517 is a reply to message #38484] |
Thu, 08 November 2007 18:19 |
| Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
> I'll bet there is a lot of interest in this. I'm not sure if I
> understand correctly, but I think quite a few people want something like
> this to feed data into BIRT for example.
Your right Ed,
EMF now provides the model methodology; the online editing, transaction
processing, navigation, and validation; and with an ODA plugin it will
feature a state of the art OLAP reporting infrastructure.
a Birt enabled EMF will be cool squared,
John
Ed Merks wrote:
> Jeff,
>
> I'll bet there is a lot of interest in this. I'm not sure if I
> understand correctly, but I think quite a few people want something like
> this to feed data into BIRT for example.
> What I've been doing with EMFT is creating new components to accommodate
> small development teams or even just individuals. Each component is
> effectively like a subproject within the EMFT project so access to code
> and voting writings are partitioned:
> <http://wiki.eclipse.org/Modeling_Project_Organization>
>
> http://wiki.eclipse.org/Modeling_Project_Organization
>
> This givens folks a sense of security (control over their own code),
> ownership, and inclusion. Perhaps that type of structure would work for
> the DTP's incubator project. I've found that this component approach is
> attracting contributors at a very rapid pace of late with these being
> very recent examples:
> <http://wiki.eclipse.org/EMFT#Proposed_Components>
>
> http://wiki.eclipse.org/EMFT#Proposed_Components
>
> The first three have been approved and are being provisioned. The
> approval for Mint will complete today, and the latest one Temporality
> will be announced today.
>
> I'm not sure what specifically to suggest for this case. It makes some
> sense to set it up in EMFT (which likely could reach the provisioning
> stage---CVS modules and parallel IP reviewed code ready to be
> committed---in as little as three weeks), but it seems better to be in
> DTP. Setting something up a source forge is reasonable too I suppose,
> but I'd like to see Eclipse be a great place for collaboration. In any
> case, tracking pedigree and ensuring that everyone understands and
> agrees they are contributing to EPL is important. Sharing zips via a
> bugzilla isn't much fun...
>
>
> Jeff Ramsdale wrote:
>> Hi Ed,
>>
>> I've been working with the existing Bugzilla entry:
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if
>> I should open another entry when the code is ready for a look (it's
>> not, yet).
>>
>> Which raises the point... Several people have contacted me about
>> helping to work on this but it's difficult to collaborate without a
>> public code repository. I could set up a project somewhere else, but
>> the hope would be to donate it and expedite the IP process anyway. So
>> I'd rather finish the coding at DTP. Also, up to this point I'm the
>> only dev (except for 1 data file), so it would be easier to track the
>> contributions of others at DTP than elsewhere.
>>
>> I'd like to continue to support the contribution after it's promoted,
>> but once it's released I don't see it being something that would
>> require a lot of ongoing maintenance.
>>
>> Thanks for your comments, too, Linda, and let me know what you learn
>> about parallel IP...
>>
>> -jeff
>>
>> Ed Merks wrote:
>>> Linda,
>>>
>>> The parallel IP review for the Emfatic component in EMFT took only
>>> one week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is
>>> the Enablement sub-project of DTP a conforming incubating subproject
>>> that can take advantage of parallel IP? Do you create components in
>>> this subproject and give committer rights to the folks who maintain
>>> will maintain the contributions? Or is this a one time contribution
>>> and you will take over the long term maintenance and support for
>>> this? Jeff, please post the bugzilla number here.
>
>
|
|
| |
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #38792 is a reply to message #38615] |
Thu, 15 November 2007 01:13 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Jeff,
It's been clarified that the Eclipse parallel IP review process is available
only to incubating projects. But DTP does not have one yet.
At the DTP PMC meeting yesterday (meeting minutes on the DTP wiki page
http://wiki.eclipse.org/DTP_PMC_Meeting_November_13%2C_2007), we decided to
proceed with creating an incubation project in DTP. This would require
going through the normal Eclipse project creation process, and will take
weeks to complete. In the meantime, perhaps you can start with sharing your
contribution as patches in Bugzilla. This would be temporary until the DTP
incubation project is setup. Would this work for you?
The advantage of this route is that we can start with using the eventual DTP
namespace for the project, plus facilitate its IP tracking for the eventual
IP review process.
As for which Bugzilla entry, does your contribution fit into the scope
described in bug 132958? If so, it should be fine to continue use that
entry.
Linda
"Jeff Ramsdale" <jeff.ramsdale@gmail.com> wrote in message
news:fh3imi$2i0$1@build.eclipse.org...
> Hi Linda,
>
> Any news here? Feel free to contact me off-list if you have any questions.
>
> Thanks,
>
> Jeff
>
> Linda Chan wrote:
>> Ed,
>>
>> I'll have to check on the parallel IP part.
>>
>> As for on-going maintenance, we certainly require having committers to
>> provide on-going support. It will depend on whether the original
>> contributor is ready to commit some development resources on an on-going
>> basis. Or if we can find existing committers who are willing to take up
>> the contribution. Another alternative is for the original contributor to
>> provide maintenance patches, and an existing committer would review and
>> commit them. In other words, it could vary on a case-by-case basis, and
>> may change over different stages of a contribution.
>>
>> Linda
|
|
| |
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588437 is a reply to message #38026] |
Mon, 05 November 2007 11:12 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
Jeff,
Have a look at http://www.eclipse.org/legal/logo_guidelines.php Given
that your intent is to contribute it to Eclipse, I don't imagine anyone
will object to your use of exactly the trademarks that will be used when
the donation process is completed.
If you have multiple people working on the contribution, make sure you
arecarefully tracking everyone who is contributing. You might want to
open a bugzilla already, and add the code as an attachment. Anyone
making updates to it could provide a new attachment. This way you have
a clearly pedigree of contributors tracked in the bugzilla itself. If
the code is more than 250 lines, it will need to be IP reviewed. I'm
not sure if DTP has an incubator project; gosh, the website is still not
in Phoenix format! If it did, that could make use of the parallel IP
process whereby the CQ can be approved to be committed to CVS before the
full IP review is completed. I assume that the DTP folks would be
interested in the contribution, but if not, I could imagine setting this
up as an EMFT project as well (which can take advantage of the parallel
IP processes). It does seem better in DTP though since I'm pretty sure
DTP already depends on EMF while nothing in EMFT currently depends on
DTP. If the contribution does not introduce dependencies on third party
libraries and has a very clear pedigree of who contributed it to EPL,
the review process should be very quick. It's the third party libraries
and tracking down their pedigree and applicable licenses that represents
the most time consume aspect of the IP review.
If there's anything I can do to help, please ask. I'd be interested to
see the code since I know nothing about ODA and like to learn...
Jeff Ramsdale wrote:
> This is not specifically a DTP question, but it does pertain to the
> project. I've been working on an EMF ODA driver and a couple of other
> people have expressed interest in helping out. I'd hope to donate the
> product of my/our work to the Eclipse Foundation but understand the IP
> donation process can be time-consuming. Though only a modest amount of
> code would be involved I suspect it would exceed the size of a typical
> patch donation, thus triggering the more rigorous IP approval process.
> Please correct me if I'm wrong.
>
> The question, then, is whether there are any trademarks involved if I
> name the project something like "EMF ODA Driver" and host it at
> another site. If any trademarks are involved is this an approved
> practice? If they are not involved is there any reason I shouldn't use
> such a name? Any other advice appreciated...
>
> Jeff
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588453 is a reply to message #38091] |
Tue, 06 November 2007 00:12 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Jeff,
>> whether there are any trademarks involved if I name the project
>> something like "EMF ODA Driver" and host it at another site. ... Any
>> other advice appreciated...
Your contribution would indeed fit in the DTP Enablement sub-project:
http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in it
..
As you'd noted, a source level contribution to Eclipse.org would take some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to your
project page. See http://www.eclipse.org/datatools/community.html . You
can see that there are already a variety of DTP adopters, including ODA ones
listed in the Community page, with different levels of contribution.
Linda
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588463 is a reply to message #38155] |
Tue, 06 November 2007 00:32 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------000501060607070706040207
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Linda,
The parallel IP review for the Emfatic component in EMFT took only one
week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
Linda Chan wrote:
> Jeff,
>
>
>>> whether there are any trademarks involved if I name the project
>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>> other advice appreciated...
>>>
>
> Your contribution would indeed fit in the DTP Enablement sub-project:
> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
> kick-start the process, start with creating a Bugzilla entry for the Data
> Tools -> Enablement ODA component, and attach the source contribution in it
> .
>
> As you'd noted, a source level contribution to Eclipse.org would take some
> time, as it involves technical review and an Eclipse IP review. The DTP
> project thus also facilitates direct third-party contribution by any DTP
> adopters. Basically, one will provide your own web page and download site
> for your contribution, which can be either binary only or source as well.
> And the DTP project web site would include a descrption with a link to your
> project page. See http://www.eclipse.org/datatools/community.html . You
> can see that there are already a variety of DTP adopters, including ODA ones
> listed in the Community page, with different levels of contribution.
>
> Linda
>
>
>
--------------000501060607070706040207
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Linda,<br>
<br>
The parallel IP review for the Emfatic component in EMFT took only one
week. <a href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a>
Is the Enablement sub-project of DTP a conforming incubating subproject
that can take advantage of parallel IP? Do you create components in
this subproject and give committer rights to the folks who maintain
will maintain the contributions? Or is this a one time contribution
and you will take over the long term maintenance and support for this?
Jeff, please post the bugzilla number here.<br>
<br>
<br>
Linda Chan wrote:
<blockquote cite="mid:fgobhi$9gt$1@build.eclipse.org" type="cite">
<pre wrap="">Jeff,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> whether there are any trademarks involved if I name the project
something like "EMF ODA Driver" and host it at another site. ... Any
other advice appreciated...
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
Your contribution would indeed fit in the DTP Enablement sub-project:
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/datatools/project_enablement/index.ht ml"> http://www.eclipse.org/datatools/project_enablement/index.ht ml</a> . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in it
..
As you'd noted, a source level contribution to Eclipse.org would take some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to your
project page. See <a class="moz-txt-link-freetext" href="http://www.eclipse.org/datatools/community.html">http://www.eclipse.org/datatools/community.html</a> . You
can see that there are already a variety of DTP adopters, including ODA ones
listed in the Community page, with different levels of contribution.
Linda
</pre>
</blockquote>
<br>
</body>
</html>
--------------000501060607070706040207--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588479 is a reply to message #38188] |
Tue, 06 November 2007 22:43 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Ed,
I'll have to check on the parallel IP part.
As for on-going maintenance, we certainly require having committers to
provide on-going support. It will depend on whether the original contributor
is ready to commit some development resources on an on-going basis. Or if we
can find existing committers who are willing to take up the contribution.
Another alternative is for the original contributor to provide maintenance
patches, and an existing committer would review and commit them. In other
words, it could vary on a case-by-case basis, and may change over different
stages of a contribution.
Linda
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:fgocj9$ii5$1@build.eclipse.org...
> Linda,
>
> The parallel IP review for the Emfatic component in EMFT took only one
> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
> Enablement sub-project of DTP a conforming incubating subproject that
> can take advantage of parallel IP? Do you create components in this
> subproject and give committer rights to the folks who maintain will
> maintain the contributions? Or is this a one time contribution and you
> will take over the long term maintenance and support for this? Jeff,
> please post the bugzilla number here.
>
>
> Linda Chan wrote:
>> Jeff,
>>
>>
>>>> whether there are any trademarks involved if I name the project
>>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>>> other advice appreciated...
>>>>
>>
>> Your contribution would indeed fit in the DTP Enablement sub-project:
>> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
>> kick-start the process, start with creating a Bugzilla entry for the Data
>> Tools -> Enablement ODA component, and attach the source contribution in
>> it
>> .
>>
>> As you'd noted, a source level contribution to Eclipse.org would take
>> some
>> time, as it involves technical review and an Eclipse IP review. The DTP
>> project thus also facilitates direct third-party contribution by any DTP
>> adopters. Basically, one will provide your own web page and download
>> site
>> for your contribution, which can be either binary only or source as well.
>> And the DTP project web site would include a descrption with a link to
>> your
>> project page. See http://www.eclipse.org/datatools/community.html .
>> You
>> can see that there are already a variety of DTP adopters, including ODA
>> ones
>> listed in the Community page, with different levels of contribution.
>>
>> Linda
>>
>>
>>
>
>
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588516 is a reply to message #38254] |
Wed, 07 November 2007 14:27 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------080305040106040002000601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Linda,
Cool. That's a very flexible approach. Thanks for the info! Note that
the IP folks at Eclipse approved
http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862 for inclusion via
parallel IP in just an hour! I'll be very interested to look at the
contribution so I can learn some new things.
Linda Chan wrote:
> Ed,
>
> I'll have to check on the parallel IP part.
>
> As for on-going maintenance, we certainly require having committers to
> provide on-going support. It will depend on whether the original contributor
> is ready to commit some development resources on an on-going basis. Or if we
> can find existing committers who are willing to take up the contribution.
> Another alternative is for the original contributor to provide maintenance
> patches, and an existing committer would review and commit them. In other
> words, it could vary on a case-by-case basis, and may change over different
> stages of a contribution.
>
> Linda
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:fgocj9$ii5$1@build.eclipse.org...
>
>> Linda,
>>
>> The parallel IP review for the Emfatic component in EMFT took only one
>> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
>> Enablement sub-project of DTP a conforming incubating subproject that
>> can take advantage of parallel IP? Do you create components in this
>> subproject and give committer rights to the folks who maintain will
>> maintain the contributions? Or is this a one time contribution and you
>> will take over the long term maintenance and support for this? Jeff,
>> please post the bugzilla number here.
>>
>>
>> Linda Chan wrote:
>>
>>> Jeff,
>>>
>>>
>>>
>>>>> whether there are any trademarks involved if I name the project
>>>>> something like "EMF ODA Driver" and host it at another site. ... Any
>>>>> other advice appreciated...
>>>>>
>>>>>
>>> Your contribution would indeed fit in the DTP Enablement sub-project:
>>> http://www.eclipse.org/datatools/project_enablement/index.ht ml . To
>>> kick-start the process, start with creating a Bugzilla entry for the Data
>>> Tools -> Enablement ODA component, and attach the source contribution in
>>> it
>>> .
>>>
>>> As you'd noted, a source level contribution to Eclipse.org would take
>>> some
>>> time, as it involves technical review and an Eclipse IP review. The DTP
>>> project thus also facilitates direct third-party contribution by any DTP
>>> adopters. Basically, one will provide your own web page and download
>>> site
>>> for your contribution, which can be either binary only or source as well.
>>> And the DTP project web site would include a descrption with a link to
>>> your
>>> project page. See http://www.eclipse.org/datatools/community.html .
>>> You
>>> can see that there are already a variety of DTP adopters, including ODA
>>> ones
>>> listed in the Community page, with different levels of contribution.
>>>
>>> Linda
>>>
>>>
>>>
>>>
>>
>
>
>
--------------080305040106040002000601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Linda,<br>
<br>
Cool. That's a very flexible approach. Thanks for the info! Note
that the IP folks at Eclipse approved
<a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1862</a> for inclusion via
parallel IP in just an hour! I'll be very interested to look at the
contribution so I can learn some new things.<br>
<br>
<br>
Linda Chan wrote:
<blockquote cite="mid:fgqqn1$bbh$1@build.eclipse.org" type="cite">
<pre wrap="">Ed,
I'll have to check on the parallel IP part.
As for on-going maintenance, we certainly require having committers to
provide on-going support. It will depend on whether the original contributor
is ready to commit some development resources on an on-going basis. Or if we
can find existing committers who are willing to take up the contribution.
Another alternative is for the original contributor to provide maintenance
patches, and an existing committer would review and commit them. In other
words, it could vary on a case-by-case basis, and may change over different
stages of a contribution.
Linda
"Ed Merks" <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fgocj9$ii5$1@build.eclipse.org">news:fgocj9$ii5$1@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Linda,
The parallel IP review for the Emfatic component in EMFT took only one
week. <a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a> Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
Linda Chan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Jeff,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> whether there are any trademarks involved if I name the project
something like "EMF ODA Driver" and host it at another site. ... Any
other advice appreciated...
</pre>
</blockquote>
</blockquote>
<pre wrap="">Your contribution would indeed fit in the DTP Enablement sub-project:
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/datatools/project_enablement/index.ht ml"> http://www.eclipse.org/datatools/project_enablement/index.ht ml</a> . To
kick-start the process, start with creating a Bugzilla entry for the Data
Tools -> Enablement ODA component, and attach the source contribution in
it
..
As you'd noted, a source level contribution to Eclipse.org would take
some
time, as it involves technical review and an Eclipse IP review. The DTP
project thus also facilitates direct third-party contribution by any DTP
adopters. Basically, one will provide your own web page and download
site
for your contribution, which can be either binary only or source as well.
And the DTP project web site would include a descrption with a link to
your
project page. See <a class="moz-txt-link-freetext" href="http://www.eclipse.org/datatools/community.html">http://www.eclipse.org/datatools/community.html</a> .
You
can see that there are already a variety of DTP adopters, including ODA
ones
listed in the Community page, with different levels of contribution.
Linda
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
--------------080305040106040002000601--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588531 is a reply to message #38188] |
Thu, 08 November 2007 06:11 |
Jeff Ramsdale
Messages: 122
Registered: July 2009 |
Senior Member |
|
|
Hi Ed,
I've been working with the existing Bugzilla entry:
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if I
should open another entry when the code is ready for a look (it's not, yet).
Which raises the point... Several people have contacted me about helping
to work on this but it's difficult to collaborate without a public code
repository. I could set up a project somewhere else, but the hope would
be to donate it and expedite the IP process anyway. So I'd rather finish
the coding at DTP. Also, up to this point I'm the only dev (except for 1
data file), so it would be easier to track the contributions of others
at DTP than elsewhere.
I'd like to continue to support the contribution after it's promoted,
but once it's released I don't see it being something that would require
a lot of ongoing maintenance.
Thanks for your comments, too, Linda, and let me know what you learn
about parallel IP...
-jeff
Ed Merks wrote:
> Linda,
>
> The parallel IP review for the Emfatic component in EMFT took only one
> week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is the
> Enablement sub-project of DTP a conforming incubating subproject that
> can take advantage of parallel IP? Do you create components in this
> subproject and give committer rights to the folks who maintain will
> maintain the contributions? Or is this a one time contribution and you
> will take over the long term maintenance and support for this? Jeff,
> please post the bugzilla number here.
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588541 is a reply to message #38451] |
Thu, 08 November 2007 12:11 |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------070305070207010605080707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Jeff,
I'll bet there is a lot of interest in this. I'm not sure if I
understand correctly, but I think quite a few people want something like
this to feed data into BIRT for example.
What I've been doing with EMFT is creating new components to accommodate
small development teams or even just individuals. Each component is
effectively like a subproject within the EMFT project so access to code
and voting writings are partitioned:
<http://wiki.eclipse.org/Modeling_Project_Organization>
http://wiki.eclipse.org/Modeling_Project_Organization
This givens folks a sense of security (control over their own code),
ownership, and inclusion. Perhaps that type of structure would work for
the DTP's incubator project. I've found that this component approach is
attracting contributors at a very rapid pace of late with these being
very recent examples:
<http://wiki.eclipse.org/EMFT#Proposed_Components>
http://wiki.eclipse.org/EMFT#Proposed_Components
The first three have been approved and are being provisioned. The
approval for Mint will complete today, and the latest one Temporality
will be announced today.
I'm not sure what specifically to suggest for this case. It makes some
sense to set it up in EMFT (which likely could reach the provisioning
stage---CVS modules and parallel IP reviewed code ready to be
committed---in as little as three weeks), but it seems better to be in
DTP. Setting something up a source forge is reasonable too I suppose,
but I'd like to see Eclipse be a great place for collaboration. In any
case, tracking pedigree and ensuring that everyone understands and
agrees they are contributing to EPL is important. Sharing zips via a
bugzilla isn't much fun...
Jeff Ramsdale wrote:
> Hi Ed,
>
> I've been working with the existing Bugzilla entry:
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if
> I should open another entry when the code is ready for a look (it's
> not, yet).
>
> Which raises the point... Several people have contacted me about
> helping to work on this but it's difficult to collaborate without a
> public code repository. I could set up a project somewhere else, but
> the hope would be to donate it and expedite the IP process anyway. So
> I'd rather finish the coding at DTP. Also, up to this point I'm the
> only dev (except for 1 data file), so it would be easier to track the
> contributions of others at DTP than elsewhere.
>
> I'd like to continue to support the contribution after it's promoted,
> but once it's released I don't see it being something that would
> require a lot of ongoing maintenance.
>
> Thanks for your comments, too, Linda, and let me know what you learn
> about parallel IP...
>
> -jeff
>
> Ed Merks wrote:
>> Linda,
>>
>> The parallel IP review for the Emfatic component in EMFT took only
>> one week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is
>> the Enablement sub-project of DTP a conforming incubating subproject
>> that can take advantage of parallel IP? Do you create components in
>> this subproject and give committer rights to the folks who maintain
>> will maintain the contributions? Or is this a one time contribution
>> and you will take over the long term maintenance and support for
>> this? Jeff, please post the bugzilla number here.
--------------070305070207010605080707
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jeff,<br>
<br>
I'll bet there is a lot of interest in this. I'm not sure if I
understand correctly, but I think quite a few people want something
like this to feed data into BIRT for example. <br>
<br>
What I've been doing with EMFT is creating new components to
accommodate small development teams or even just individuals. Each
component is effectively like a subproject within the EMFT project so
access to code and voting writings are partitioned:<a
href="http://wiki.eclipse.org/Modeling_Project_Organization"><br>
</a>
<blockquote><a
href="http://wiki.eclipse.org/Modeling_Project_Organization">http://wiki.eclipse.org/Modeling_Project_Organization</a><br>
</blockquote>
This givens folks a sense of security (control over their own code),
ownership, and inclusion. Perhaps that type of structure would work
for the DTP's incubator project. I've found that this component
approach is attracting contributors at a very rapid pace of late with
these being very recent examples:<a
href="http://wiki.eclipse.org/EMFT#Proposed_Components"><br>
</a>
<blockquote><a href="http://wiki.eclipse.org/EMFT#Proposed_Components">http://wiki.eclipse.org/EMFT#Proposed_Components</a><br>
</blockquote>
The first three have been approved and are being provisioned. The
approval for Mint will complete today, and the latest one Temporality
will be announced today.<br>
<br>
I'm not sure what specifically to suggest for this case. It makes some
sense to set it up in EMFT (which likely could reach the provisioning
stage---CVS modules and parallel IP reviewed code ready to be
committed---in as little as three weeks), but it seems better to be in
DTP. Setting something up a source forge is reasonable too I suppose,
but I'd like to see Eclipse be a great place for collaboration. In any
case, tracking pedigree and ensuring that everyone understands and
agrees they are contributing to EPL is important. Sharing zips via a
bugzilla isn't much fun...<br>
<br>
<br>
Jeff Ramsdale wrote:
<blockquote cite="mid:fgu9al$h71$1@build.eclipse.org" type="cite">Hi
Ed,
<br>
<br>
I've been working with the existing Bugzilla entry:
<a class="moz-txt-link-rfc2396E" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958"><https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958></a>. Let me
know if I should open another entry when the code is ready for a look
(it's not, yet).
<br>
<br>
Which raises the point... Several people have contacted me about
helping to work on this but it's difficult to collaborate without a
public code repository. I could set up a project somewhere else, but
the hope would be to donate it and expedite the IP process anyway. So
I'd rather finish the coding at DTP. Also, up to this point I'm the
only dev (except for 1 data file), so it would be easier to track the
contributions of others at DTP than elsewhere.
<br>
<br>
I'd like to continue to support the contribution after it's promoted,
but once it's released I don't see it being something that would
require a lot of ongoing maintenance.
<br>
<br>
Thanks for your comments, too, Linda, and let me know what you learn
about parallel IP...
<br>
<br>
-jeff
<br>
<br>
Ed Merks wrote:
<br>
<blockquote type="cite">Linda,
<br>
<br>
The parallel IP review for the Emfatic component in EMFT took only one
week. <a class="moz-txt-link-freetext" href="http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842">http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842</a> Is the
Enablement sub-project of DTP a conforming incubating subproject that
can take advantage of parallel IP? Do you create components in this
subproject and give committer rights to the folks who maintain will
maintain the contributions? Or is this a one time contribution and you
will take over the long term maintenance and support for this? Jeff,
please post the bugzilla number here.
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>
--------------070305070207010605080707--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588552 is a reply to message #38484] |
Thu, 08 November 2007 18:19 |
| Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
> I'll bet there is a lot of interest in this. I'm not sure if I
> understand correctly, but I think quite a few people want something like
> this to feed data into BIRT for example.
Your right Ed,
EMF now provides the model methodology; the online editing, transaction
processing, navigation, and validation; and with an ODA plugin it will
feature a state of the art OLAP reporting infrastructure.
a Birt enabled EMF will be cool squared,
John
Ed Merks wrote:
> Jeff,
>
> I'll bet there is a lot of interest in this. I'm not sure if I
> understand correctly, but I think quite a few people want something like
> this to feed data into BIRT for example.
> What I've been doing with EMFT is creating new components to accommodate
> small development teams or even just individuals. Each component is
> effectively like a subproject within the EMFT project so access to code
> and voting writings are partitioned:
> <http://wiki.eclipse.org/Modeling_Project_Organization>
>
> http://wiki.eclipse.org/Modeling_Project_Organization
>
> This givens folks a sense of security (control over their own code),
> ownership, and inclusion. Perhaps that type of structure would work for
> the DTP's incubator project. I've found that this component approach is
> attracting contributors at a very rapid pace of late with these being
> very recent examples:
> <http://wiki.eclipse.org/EMFT#Proposed_Components>
>
> http://wiki.eclipse.org/EMFT#Proposed_Components
>
> The first three have been approved and are being provisioned. The
> approval for Mint will complete today, and the latest one Temporality
> will be announced today.
>
> I'm not sure what specifically to suggest for this case. It makes some
> sense to set it up in EMFT (which likely could reach the provisioning
> stage---CVS modules and parallel IP reviewed code ready to be
> committed---in as little as three weeks), but it seems better to be in
> DTP. Setting something up a source forge is reasonable too I suppose,
> but I'd like to see Eclipse be a great place for collaboration. In any
> case, tracking pedigree and ensuring that everyone understands and
> agrees they are contributing to EPL is important. Sharing zips via a
> bugzilla isn't much fun...
>
>
> Jeff Ramsdale wrote:
>> Hi Ed,
>>
>> I've been working with the existing Bugzilla entry:
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=132958>. Let me know if
>> I should open another entry when the code is ready for a look (it's
>> not, yet).
>>
>> Which raises the point... Several people have contacted me about
>> helping to work on this but it's difficult to collaborate without a
>> public code repository. I could set up a project somewhere else, but
>> the hope would be to donate it and expedite the IP process anyway. So
>> I'd rather finish the coding at DTP. Also, up to this point I'm the
>> only dev (except for 1 data file), so it would be easier to track the
>> contributions of others at DTP than elsewhere.
>>
>> I'd like to continue to support the contribution after it's promoted,
>> but once it's released I don't see it being something that would
>> require a lot of ongoing maintenance.
>>
>> Thanks for your comments, too, Linda, and let me know what you learn
>> about parallel IP...
>>
>> -jeff
>>
>> Ed Merks wrote:
>>> Linda,
>>>
>>> The parallel IP review for the Emfatic component in EMFT took only
>>> one week. http://dev.eclipse.org/ipzilla/show_bug.cgi?id=1842 Is
>>> the Enablement sub-project of DTP a conforming incubating subproject
>>> that can take advantage of parallel IP? Do you create components in
>>> this subproject and give committer rights to the folks who maintain
>>> will maintain the contributions? Or is this a one time contribution
>>> and you will take over the long term maintenance and support for
>>> this? Jeff, please post the bugzilla number here.
>
>
|
|
| |
| Re: Attempt to avoid misuse of Eclipse Foundation trademarks [message #588631 is a reply to message #38615] |
Thu, 15 November 2007 01:13 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Jeff,
It's been clarified that the Eclipse parallel IP review process is available
only to incubating projects. But DTP does not have one yet.
At the DTP PMC meeting yesterday (meeting minutes on the DTP wiki page
http://wiki.eclipse.org/DTP_PMC_Meeting_November_13%2C_2007), we decided to
proceed with creating an incubation project in DTP. This would require
going through the normal Eclipse project creation process, and will take
weeks to complete. In the meantime, perhaps you can start with sharing your
contribution as patches in Bugzilla. This would be temporary until the DTP
incubation project is setup. Would this work for you?
The advantage of this route is that we can start with using the eventual DTP
namespace for the project, plus facilitate its IP tracking for the eventual
IP review process.
As for which Bugzilla entry, does your contribution fit into the scope
described in bug 132958? If so, it should be fine to continue use that
entry.
Linda
"Jeff Ramsdale" <jeff.ramsdale@gmail.com> wrote in message
news:fh3imi$2i0$1@build.eclipse.org...
> Hi Linda,
>
> Any news here? Feel free to contact me off-list if you have any questions.
>
> Thanks,
>
> Jeff
>
> Linda Chan wrote:
>> Ed,
>>
>> I'll have to check on the parallel IP part.
>>
>> As for on-going maintenance, we certainly require having committers to
>> provide on-going support. It will depend on whether the original
>> contributor is ready to commit some development resources on an on-going
>> basis. Or if we can find existing committers who are willing to take up
>> the contribution. Another alternative is for the original contributor to
>> provide maintenance patches, and an existing committer would review and
>> commit them. In other words, it could vary on a case-by-case basis, and
>> may change over different stages of a contribution.
>>
>> Linda
|
|
| |
Goto Forum:
Current Time: Tue Apr 16 20:33:09 GMT 2024
Powered by FUDForum. Page generated in 2.58021 seconds |
] 
Search
Help
Register
Login
Home
