imp-dev

[imp-dev] Project meta data is out of date for technology.imp

emo@xxxxxxx (portal on behalf of emo) — Tue, 05 Feb 2013 05:00:08 GMT

Robert,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* There is no next/future release of this project. All Eclipse projects
must have a "next release" planned and scheduled.

Re: [imp-dev] status quo in move to github

Jurgen.Vinju@xxxxxxx (Jurgen Vinju) — Sat, 17 Nov 2012 09:53:21 GMT

Hi Wayne

Thanks for looking into this. Its much appreciated.

Jurgen

On Friday, November 16, 2012, Wayne Beaton wrote:

The Guidelines for Eclipse Logos and Trademarks [1] states (in part):

"The Eclipse Project Naming Policy allows for Eclipse projects to have a descriptive name, optional nickname and acronym. These names, e.g. Higgins, and acronyms, e.g. BIRT, can be become effective identifiers of certain technologies, therefore it is important to establish proper usage guidelines. All project names, nicknames and acronyms are, to the extent possible, trademarks of the Eclipse Foundation and should be identified as such. (Please see proper notice and attribution below.)"

So the Eclipse Foundation asserts trademark of "IMP".

I'll look into options regarding reassignment of the trademark.

Wayne

[1] http://www.eclipse.org/legal/logo_guidelines.php

On 11/14/2012 06:10 PM, Jurgen Vinju wrote:
Hi Wayne,

Ok thanks. In case eclipse.org owns "IMP" in any way, I think we may propose to transfer it back to us in the near future. The potential loss to eclipse.org is virtually non-existent, while IMP would definitely be significantly harmed by a name change. Thanks for checking this out!

Cheers,

Jurgen

On Thu, Nov 15, 2012 at 12:06 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

I will have to check with folks more knowledgeable in trademark issues regarding "IMP".

In terms of time, a couple of months is fine. I will get a little more anxious about terminating the project if it remains dormant for too long.

Wayne

On 11/14/2012 05:57 PM, Jurgen Vinju wrote:
Hi Wayne,

Yes, we are changing the names of the projects during the move, to remove the org.eclipse prefix. We do need some time to refactor the internal package names afterwards. Is that ok? Can we still call the project just "IMP", or am I to understand that we need to rebrand that too? Where is the IMP trademark registered?

The move could take several months, if that's ok. We have now moved half a dozen key components, but there are many more and we need to find time to sift through these and do proper triage. Is there any issue with a long time path you think?

When IMP will be terminated completely, we would be happy to request a termination review of course.

Cheers and thanks for your help,

Jurgen

On Wed, Nov 14, 2012 at 11:48 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:

Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju

Re: [imp-dev] status quo in move to github

wayne@xxxxxxx (Wayne Beaton) — Fri, 16 Nov 2012 19:29:17 GMT

The Guidelines for Eclipse Logos and Trademarks [1] states (in part):

"The Eclipse Project Naming Policy allows for Eclipse projects to have a descriptive name, optional nickname and acronym. These names, e.g. Higgins, and acronyms, e.g. BIRT, can be become effective identifiers of certain technologies, therefore it is important to establish proper usage guidelines. All project names, nicknames and acronyms are, to the extent possible, trademarks of the Eclipse Foundation and should be identified as such. (Please see proper notice and attribution below.)"

So the Eclipse Foundation asserts trademark of "IMP".

I'll look into options regarding reassignment of the trademark.

Wayne

[1] http://www.eclipse.org/legal/logo_guidelines.php

On 11/14/2012 06:10 PM, Jurgen Vinju wrote:

Hi Wayne,

Ok thanks. In case eclipse.org owns "IMP" in any way, I think we may propose to transfer it back to us in the near future. The potential loss to eclipse.org is virtually non-existent, while IMP would definitely be significantly harmed by a name change. Thanks for checking this out!

Cheers,

Jurgen
On Thu, Nov 15, 2012 at 12:06 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
I will have to check with folks more knowledgeable in trademark issues regarding "IMP".

In terms of time, a couple of months is fine. I will get a little more anxious about terminating the project if it remains dormant for too long.

Wayne
On 11/14/2012 05:57 PM, Jurgen Vinju wrote:
Hi Wayne,

Yes, we are changing the names of the projects during the move, to remove the org.eclipse prefix. We do need some time to refactor the internal package names afterwards. Is that ok? Can we still call the project just "IMP", or am I to understand that we need to rebrand that too? Where is the IMP trademark registered?

The move could take several months, if that's ok. We have now moved half a dozen key components, but there are many more and we need to find time to sift through these and do proper triage. Is there any issue with a long time path you think?

When IMP will be terminated completely, we would be happy to request a termination review of course.

Cheers and thanks for your help,

Jurgen
On Wed, Nov 14, 2012 at 11:48 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:
Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

pdb

pdb.values

pdb.ui

pdb.values.test

imp.pom

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
  
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev 
 
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
  
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

Re: [imp-dev] status quo in move to github

Jurgen.Vinju@xxxxxxx (Jurgen Vinju) — Wed, 14 Nov 2012 23:10:55 GMT

Hi Wayne,

Ok thanks. In case eclipse.org owns "IMP" in any way, I think we may propose to transfer it back to us in the near future. The potential loss to eclipse.org is virtually non-existent, while IMP would definitely be significantly harmed by a name change. Thanks for checking this out!

Cheers,

Jurgen

On Thu, Nov 15, 2012 at 12:06 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

I will have to check with folks more knowledgeable in trademark issues regarding "IMP".

In terms of time, a couple of months is fine. I will get a little more anxious about terminating the project if it remains dormant for too long.

Wayne
On 11/14/2012 05:57 PM, Jurgen Vinju wrote:
Hi Wayne,

Yes, we are changing the names of the projects during the move, to remove the org.eclipse prefix. We do need some time to refactor the internal package names afterwards. Is that ok? Can we still call the project just "IMP", or am I to understand that we need to rebrand that too? Where is the IMP trademark registered?

The move could take several months, if that's ok. We have now moved half a dozen key components, but there are many more and we need to find time to sift through these and do proper triage. Is there any issue with a long time path you think?

When IMP will be terminated completely, we would be happy to request a termination review of course.

Cheers and thanks for your help,

Jurgen
On Wed, Nov 14, 2012 at 11:48 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:
Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

pdb

pdb.values

pdb.ui

pdb.values.test

imp.pom

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
  
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev 
 
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

Re: [imp-dev] status quo in move to github

wayne@xxxxxxx (Wayne Beaton) — Wed, 14 Nov 2012 23:06:09 GMT

I will have to check with folks more knowledgeable in trademark issues regarding "IMP".

In terms of time, a couple of months is fine. I will get a little more anxious about terminating the project if it remains dormant for too long.

Wayne

On 11/14/2012 05:57 PM, Jurgen Vinju wrote:

Hi Wayne,

Yes, we are changing the names of the projects during the move, to remove the org.eclipse prefix. We do need some time to refactor the internal package names afterwards. Is that ok? Can we still call the project just "IMP", or am I to understand that we need to rebrand that too? Where is the IMP trademark registered?

The move could take several months, if that's ok. We have now moved half a dozen key components, but there are many more and we need to find time to sift through these and do proper triage. Is there any issue with a long time path you think?

When IMP will be terminated completely, we would be happy to request a termination review of course.

Cheers and thanks for your help,

Jurgen
On Wed, Nov 14, 2012 at 11:48 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:
Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

pdb

pdb.values

pdb.ui

pdb.values.test

imp.pom

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
  
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev 
 
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

Re: [imp-dev] status quo in move to github

Jurgen.Vinju@xxxxxxx (Jurgen Vinju) — Wed, 14 Nov 2012 22:57:28 GMT

Hi Wayne,

Yes, we are changing the names of the projects during the move, to remove the org.eclipse prefix. We do need some time to refactor the internal package names afterwards. Is that ok? Can we still call the project just "IMP", or am I to understand that we need to rebrand that too? Where is the IMP trademark registered?

The move could take several months, if that's ok. We have now moved half a dozen key components, but there are many more and we need to find time to sift through these and do proper triage. Is there any issue with a long time path you think?

When IMP will be terminated completely, we would be happy to request a termination review of course.

Cheers and thanks for your help,

Jurgen

On Wed, Nov 14, 2012 at 11:48 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:
Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

pdb

pdb.values

pdb.ui

pdb.values.test

imp.pom

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

Re: [imp-dev] status quo in move to github

wayne@xxxxxxx (Wayne Beaton) — Wed, 14 Nov 2012 22:48:48 GMT

The project name is a trademark of the Eclipse Foundation. If you're moving the project out of Eclipse, you'll have to change the name.

Further, the org.eclipse namespace belongs to the Eclipse Foundation. That will also have to change.

What is the timeframe for completion of the move? Will you request a termination review?

Wayne

On 11/14/2012 05:32 PM, Jurgen Vinju wrote:

Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

imp.runtime

imp.runtime.feature

pdb

pdb.values

pdb.ui

pdb.values.test

imp.pom

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

www: http://jurgen.vinju.org, http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

[imp-dev] status quo in move to github

Jurgen.Vinju@xxxxxxx (Jurgen Vinju) — Wed, 14 Nov 2012 22:32:21 GMT

Dear IMPs and Rascals,

Today we have migrated some parts of IMP to github:

Please do not immediately start to push/fork/clone/commit and give this some time to settle down (a few days, until Monday). We need to find out if everything was transferred correctly and is building and testing, and the authors are correctly linked etc. etc. If some problem would be detected, then we should re-migrate to fix issues and your work would be lost.

Please use the project set on the wiki to check out the projects and test whether it is working for you as expected? https://github.com/eclipse-imp/imp.runtime/wiki

Our plan is to start with this hot bunch and try to work on the rest of IMP incrementally. The old SVN locations have been moved to trunk/moved_to_github/ to prevent accidental commits.

Cheers,

Jurgen & Bob

Re: [imp-dev] IMP project moving to github

anya@xxxxxxx (Anya Helene Bagge) — Tue, 13 Nov 2012 21:09:17 GMT

On 11/13/2012 09:49 PM, Jurgen Vinju wrote:

Hi Wayne,

I think it would be a bit strong to say that Eclipse has "too much
overhead". Eclipse goes for a high quality, well reviewed process that is
particularly good in supporting due diligence in the copyright department.
Also, I think the Eclipse process works well for high quality
infra-structure, stable API and plugins that people depend on. No complaints.

For continuing the IMP project, which currently has no supported staff
working on it, we are looking to support a more automatic and more informal,
yet still clearly traceable, way of allowing others to contribute. We
currently work in an environment where students and other contributors come
and go (i.e. are attached for only a few months). Each of these people
contribute interesting experiments and additions while they are not eligible
(yet) to have Eclipse committer status. From experience we know that github
can support this more dynamic and informal situation. Github is also more
inviting in that sense, since it has lower social and technological barriers
for contributing code.

In short: no complaints about Eclipse.org, but we are wanting to try
something new to boost participation for the IMP project. It also matters
that Rascal is hosted at github, which makes heavy use of IMP, and we have
good experiences so far.

I might add that, as a non-committer, I've felt somewhat discouraged from submitting small bugfixes and patches, given the amount of administration work/nagging involved. This may be easier at Github, where patch created and submission using pull requests is nearly free (no idea of whether nagging would still be involved, though).

-anya

Cheers!

Jurgen

P.S. sorry for the delay in answering your good question.


On Mon, Sep 24, 2012 at 2:57 AM, Wayne Beaton mailto:wayne@xxxxxxxxxxx>> wrote:

    __
    Hi Bob.

    Can you be specific in terms of what parts of the Eclipse process are
    too much overhead?

    Wayne

On 09/22/2012 07:09 PM, Robert Fuhrer wrote:

    Hi Folks,

    After careful deliberation with the other major IMP stakeholders,
    we've decided to move the project to github.

    This is due in part to the facts that:
     1) I've voluntarily moved to a job that sadly doesn't provide a
    compelling reason for me to continue working full-time on IMP,
     2) as a consequence, the lion's share of the recent development
    activity has been driven by the Rascal project (http://rascal-mpl.org
    <http://rascal-mpl.org/>), which is hosted at github,
     3) we'd like to open up the IMP project to contributors more widely
    and with less overhead than the Eclipse process permits,
     4) github is a cool place to be :)

    What does this mean for the IMP project and its users?

    First, IMP is alive and well, and will be even more so in the coming
    months.
    Second, this isn't merely a source repository move, it's a *project*
    move. We're still hashing out key details like web/wiki presence, bug
    tracking, mailing lists, releases, and such, but we fully intend that
    IMP continues to be a viable, reliable platform that lots of people
    can build on.
    Third, we (the project leaders, Jurgen Vinju and I) will have much
    more freedom to decide who can contribute, and with a much
    lighter-weight process that should allow more people to contribute
    more easily.

    I hope our reasoning is clear, and encourage you to join us at github,
    once we have the repository and other goodies set up. We'll post here
    again when we have more details on that front.

    Cheers,
     - Bob Fuhrer, IMP project lead


    _______________________________________________
    imp-dev mailing list
    imp-dev@xxxxxxxxxxx  <mailto:imp-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/imp-dev


    --
    Wayne Beaton
    The Eclipse Foundation
    Twitter: @waynebeaton
    Explore Eclipse Projects <http://www.eclipse.org/projects>
    EclipseCon Europe 2012 <http://www.eclipsecon.org/europe2012>

    _______________________________________________
    imp-dev mailing list
    imp-dev@xxxxxxxxxxx <mailto:imp-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/imp-dev


--
Jurgen Vinju
- Centrum Wiskunde & Informatica - SEN1
- INRIA Lille - ATEAMS
- Universiteit van Amsterdam

   www: http://jurgen.vinju.org,
http://www.rascal-mpl.org,http://twitter.com/jurgenvinju
skype: jurgen.vinju


_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev

Re: [imp-dev] IMP project moving to github

Jurgen.Vinju@xxxxxxx (Jurgen Vinju) — Tue, 13 Nov 2012 20:49:58 GMT

Hi Wayne,

I think it would be a bit strong to say that Eclipse has "too much overhead". Eclipse goes for a high quality, well reviewed process that is particularly good in supporting due diligence in the copyright department. Also, I think the Eclipse process works well for high quality infra-structure, stable API and plugins that people depend on. No complaints.

For continuing the IMP project, which currently has no supported staff working on it, we are looking to support a more automatic and more informal, yet still clearly traceable, way of allowing others to contribute. We currently work in an environment where students and other contributors come and go (i.e. are attached for only a few months). Each of these people contribute interesting experiments and additions while they are not eligible (yet) to have Eclipse committer status. From experience we know that github can support this more dynamic and informal situation. Github is also more inviting in that sense, since it has lower social and technological barriers for contributing code.

In short: no complaints about Eclipse.org, but we are wanting to try something new to boost participation for the IMP project. It also matters that Rascal is hosted at github, which makes heavy use of IMP, and we have good experiences so far.

Cheers!

Jurgen

P.S. sorry for the delay in answering your good question.

On Mon, Sep 24, 2012 at 2:57 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

Hi Bob.

Can you be specific in terms of what parts of the Eclipse process are too much overhead?

Wayne

On 09/22/2012 07:09 PM, Robert Fuhrer wrote:
Hi Folks,

After careful deliberation with the other major IMP stakeholders, we've decided to move the project to github.

This is due in part to the facts that:

1) I've voluntarily moved to a job that sadly doesn't provide a compelling reason for me to continue working full-time on IMP,

2) as a consequence, the lion's share of the recent development activity has been driven by the Rascal project (http://rascal-mpl.org), which is hosted at github,

3) we'd like to open up the IMP project to contributors more widely and with less overhead than the Eclipse process permits,

4) github is a cool place to be :)

What does this mean for the IMP project and its users?

First, IMP is alive and well, and will be even more so in the coming months.

Second, this isn't merely a source repository move, it's a *project* move. We're still hashing out key details like web/wiki presence, bug tracking, mailing lists, releases, and such, but we fully intend that IMP continues to be a viable, reliable platform that lots of people can build on.

Third, we (the project leaders, Jurgen Vinju and I) will have much more freedom to decide who can contribute, and with a much lighter-weight process that should allow more people to contribute more easily.

I hope our reasoning is clear, and encourage you to join us at github, once we have the repository and other goodies set up. We'll post here again when we have more details on that front.

Cheers,

- Bob Fuhrer, IMP project lead
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev