|Gord Tanner||Jul 20, 2012 4:20 pm|
|Filip Maj||Jul 21, 2012 3:12 pm|
|Ross Gardler||Jul 21, 2012 8:00 pm|
|gtan...@gmail.com||Jul 22, 2012 9:41 am|
|Laurent Hasson||Jul 22, 2012 10:02 am|
|eduardo pelegri-llopart||Jul 22, 2012 10:15 am|
|Ross Gardler||Jul 22, 2012 10:18 am|
|Paul Plaquette||Jul 23, 2012 2:26 am|
|Laurent Hasson||Jul 24, 2012 6:15 pm|
|Filip Maj||Jul 25, 2012 10:44 am|
|Dan Silivestru||Jul 25, 2012 11:02 am|
|Michael Brooks||Jul 25, 2012 5:11 pm|
|Paul Plaquette||Jul 26, 2012 6:57 am|
|gtan...@gmail.com||Jul 26, 2012 7:06 am|
|Jukka Zitting||Jul 26, 2012 7:25 am|
|Ross Gardler||Jul 26, 2012 7:52 am|
|Filip Maj||Jul 26, 2012 10:04 am|
|Ken Wallis||Jul 26, 2012 10:50 am|
|Filip Maj||Jul 26, 2012 11:10 am|
|gtan...@gmail.com||Jul 26, 2012 11:18 am|
|Ross Gardler||Jul 26, 2012 11:36 am|
|Brian LeRoux||Jul 26, 2012 11:49 am|
|Filip Maj||Jul 26, 2012 1:28 pm|
|Ross Gardler||Jul 26, 2012 1:58 pm|
|Jukka Zitting||Jul 30, 2012 6:53 am|
|Ross Gardler||Jul 30, 2012 7:04 am|
|Jukka Zitting||Jul 30, 2012 7:05 am|
|Ross Gardler||Jul 30, 2012 7:30 am|
|Michael Brooks||Jul 30, 2012 8:56 am|
|Ross Gardler||Jul 30, 2012 9:21 am|
|Gord Tanner||Jul 30, 2012 2:17 pm|
|Ross Gardler||Jul 31, 2012 7:49 am|
|Jukka Zitting||Jul 31, 2012 10:02 am|
|Dan Silivestru||Jul 31, 2012 10:06 am|
|Gord Tanner||Aug 2, 2012 8:57 am|
|Ross Gardler||Aug 3, 2012 12:52 am|
|Dan Silivestru||Aug 3, 2012 5:23 am|
|Subject:||Re: [ATTN MENTOR] Re: DISCUSS: Ripple as a sub-project of Cordova|
|From:||Filip Maj (fi...@adobe.com)|
|Date:||Jul 26, 2012 10:04:34 am|
In my mind the core issue is about community, not about development.
With that in mind, and taking Ross' point below, I think it makes sense to have it as a stand-alone project.
So in conclusion: both are viable paths IMO, and we do not get to a conclusion haha.
What about the idea of introducing Ripple into Cordova for the start, and then later splitting it out? Seems like then we could kick-start Ripple's exposure and community/committer interaction by leveraging what Cordova already has. If that sounds acceptable, then my question would be, at what point does it make sense to put Ripple into its own top-level project?
On 7/26/12 7:53 AM, "Ross Gardler" <rgar...@opendirective.com> wrote:
+1 to everything Jukka said below.
Another way of looking at it is "will the Ripple community be a sub-set of the Cordova community", if yes then sub-project is probably best. If not, i.e. there will be members of the Ripple community who are not also members of the Cordova community, then it probably ought to be a separate project to maximise its visibility as a separate community.
On 26 July 2012 15:25, Jukka Zitting <jukk...@gmail.com> wrote:
On Thu, Jul 26, 2012 at 4:06 PM, <gtan...@gmail.com> wrote:
There is a lot of overlap between the cordova and ripple communities and I was originally hoping to foster their community into ours ;)
I guess the main question here is whether Cordova committers will be working on / looking at Ripple code and vice versa on a regular basis. If that's the case (i.e. there's significant overlap in actual development activity), then having the codebases in one project is a good approach. weinre is a good example of such a case.
If not (for example if separate mailing lists are needed, etc.), then it's best for both codebases to have their own projects even if there's overlap on the level of individual committers.
The decision on this doesn't need to be final, as projects can always split or merge projects later on, but starting with at least a good approximation of the ultimate or ideal community/project structure will of course make things much easier.
-- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com