[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nebula-dev] NatTable

Hi Tom,

Yes we are still want to! I have been talking with Sharon Corbett at the Eclipse foundation and we have been going through IP review already. She had contacted us because there was interest in including NatTable as a dependency for some Eclipse projects. This happened about the same time as our initial discussions re Nebula. I was assuming you and Sharon were in sync on this, but just in case you weren't aware of each other I'm mentioning it here. Thanks for the link to your project proposal, I'll have a crack at putting one together for NatTable and send it to you to review. 

Thanks,
Edwin


On Jan 27, 2011, at 4:09 AM, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx> wrote:

> Hi,
> 
> It's been a long time since we talked about this - and I'm the one blame
> that nothing happened since them. Edwin hope you still want to get
> NatTable into Nebula?
> 
> As outlined before my proposal would be that NatTable is going to be a
> subproject of Nebula so that they can do their own releases, ... and
> hopefully once Nebula-Mature (once more I'm the one to blame nothing has
> happened since a long long time) is going into a Stable Release Cycle we
> can redecide if we get them into Nebula-Mature.
> 
> If you are interested in how a project proposal looks like. Here is mine
> for the UFaceKit-Project [1]
> 
> Tom
> 
> [1]http://www.eclipse.org/proposals/ufacekit/
> 
> Am 31.10.10 16:23, schrieb Tom Schindl:
>> Am 30.10.10 20:44, schrieb Wim Jongman:
>>> 
>>> 
>>>   I've already had a short private conversation with Edwin on the process
>>>   and it looks like Nattable would - in contrast to other Nebula
>>>   components - get a subproject of Nebula so that they can follow their
>>>   own release cycles.
>>> 
>>> 
>> 
>>> I am not against it but I do not see the benefit right now. I recognize
>>> that the Nattable is a complex component, but so are e.g. XViewer and
>>> Ganttchart. After the split in incubator and mature, the mature
>>> sub-project will jump onto the Eclipse release train. Apart from this
>> 
>> Size has nothing to do with getting a subproject.
>> 
>>> release cycle, should we decide to bring out extra releases, wouldn't it
>>> be better to release Nebula mature as a whole instead as Nebula mature
>>> and Nattable?
>>> 
>> 
>> My plan is to have Nebula mature having the same release cycle the
>> Eclipse release train but for agil projects who are used to maintain
>> their own release schedule getting the status of a subproject is better.
>> 
>>> Again I am not against so if you want to go ahead, you have my blessing,
>>> but I am curious to know what Nattable can do as a subproject that they
>>> would otherwise not be able to do.
>> 
>> I think it would allow us better to integrate this already released code
>> and align it with Nebula and future release schedules. Please note that
>> even if they are their own subproject we can the released version
>> together with Nebula-Mature 1.0.
>> 
>> We could have a joint release of Nebula-Mature, Nebula-Nattable under a
>> pseudo name like "Nebula xxxxx" where xxxx is something we should be
>> something like names of Greek mythological figures [1].
>> 
>> Tom
>> 
>> [1]http://en.wikipedia.org/wiki/List_of_Greek_mythological_figures
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> 
> -- 
> B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
> ------------------------------------------------------------------------
> tom schindl                                        geschaeftsfuehrer/CEO
> ------------------------------------------------------------------------
> eduard-bodem-gasse 5/1    A-6020 innsbruck      phone    ++43 512 935834
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev