| Where are the collaborators? [message #4264] |
Mon, 10 March 2008 13:20  |
|
[Mik Kersten said]
Under Organization, it’s usually good to see the companies involved.
Looks like right now it’s only Etish, but you should list that.
Getting another company interested in contributing to the
implementation can help.
[Harm Sluiman said]
I also think it would be good if you can identify some other parties
that are going to collaborate with you day 1. This can only be a plus
for the project, but it will also address concerns some have about a
potential code dumping form one group to feed a private open source
effort. I am sure this is not your intent, but the community will
appreciate seeing your commitment to making sure this is not going to
be the case.
[Shaun Smith said]
The best advice I can give you is to build your list of interested
parties and get committers from more than one company involved. This
is something I put my focus on for EclipseLink and Dali.
[Richard Gronback said]
The most important aspect of a successful Eclipse project, imo, is
dedication to maturing it and building all 3 communities: committers,
consumers, and commercial product companies that build upon it (2 or
more).
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: Where are the collaborators? [message #4335 is a reply to message #4264] |
Mon, 10 March 2008 13:23  |
|
On 2008-03-10 13:20:37 +0000, Joel Rosi-Schwartz
<Joel.Rosi-Schwartz@Etish.org> said:
> [Mik Kersten said]
> Under Organization, it’s usually good to see the companies involved.
> Looks like right now it’s only Etish, but you should list that.
> Getting another company interested in contributing to the
> implementation can help.
>
> [Harm Sluiman said]
> I also think it would be good if you can identify some other parties
> that are going to collaborate with you day 1. This can only be a plus
> for the project, but it will also address concerns some have about a
> potential code dumping form one group to feed a private open source
> effort. I am sure this is not your intent, but the community will
> appreciate seeing your commitment to making sure this is not going to
> be the case.
>
> [Shaun Smith said]
> The best advice I can give you is to build your list of interested
> parties and get committers from more than one company involved. This
> is something I put my focus on for EclipseLink and Dali.
>
> [Richard Gronback said]
> The most important aspect of a successful Eclipse project, imo, is
> dedication to maturing it and building all 3 communities: committers,
> consumers, and commercial product companies that build upon it (2 or
> more).
We absolutely agree with the importance of getting more parties
interested, collaborating and contributing. This was one of the driving
forces when we decided to propose the project. Barbara and I have been
working for five years on Useme, and while we have made considerable
progress for two people working as time allowed and without a budget,
it is obvious that the vision will never be fulfilled this way.
The problem is how to motivate people to stand up and be counted. Any
suggestions in this regard will be very much appreciated.
B. and Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: Where are the collaborators? [message #561605 is a reply to message #4264] |
Mon, 10 March 2008 13:23 |
|
On 2008-03-10 13:20:37 +0000, Joel Rosi-Schwartz
<Joel.Rosi-Schwartz@Etish.org> said:
> [Mik Kersten said]
> Under Organization, it’s usually good to see the companies involved.
> Looks like right now it’s only Etish, but you should list that.
> Getting another company interested in contributing to the
> implementation can help.
>
> [Harm Sluiman said]
> I also think it would be good if you can identify some other parties
> that are going to collaborate with you day 1. This can only be a plus
> for the project, but it will also address concerns some have about a
> potential code dumping form one group to feed a private open source
> effort. I am sure this is not your intent, but the community will
> appreciate seeing your commitment to making sure this is not going to
> be the case.
>
> [Shaun Smith said]
> The best advice I can give you is to build your list of interested
> parties and get committers from more than one company involved. This
> is something I put my focus on for EclipseLink and Dali.
>
> [Richard Gronback said]
> The most important aspect of a successful Eclipse project, imo, is
> dedication to maturing it and building all 3 communities: committers,
> consumers, and commercial product companies that build upon it (2 or
> more).
We absolutely agree with the importance of getting more parties
interested, collaborating and contributing. This was one of the driving
forces when we decided to propose the project. Barbara and I have been
working for five years on Useme, and while we have made considerable
progress for two people working as time allowed and without a budget,
it is obvious that the vision will never be fulfilled this way.
The problem is how to motivate people to stand up and be counted. Any
suggestions in this regard will be very much appreciated.
B. and Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
Powered by
FUDForum. Page generated in 0.02197 seconds
] 
Search
Help
Register
Login
Home
