Re: [nebula-dev] Nebula Project Review

[Tom Schindl <listom@xxxxxxxxxxxxxxx>]

Hi Chris and Chris,

Chris A. already talked to me before and I'm comfortable getting a
secondary project lead. Like Chris G. I also can't promise how much time
I can devote but I'll do my best to do the paper work, ... .

Maybe we need a mentor helping us with the paperwork, ... thingie
because I've never done it before.

I still think that other nebula committers need to step up and tell if
they agree with this.

Tom Schindl

Christopher J Gross schrieb:
> Hi Tom,Chris,
> 
> I don't really have alot of time to devote to Nebula at the moment.  I'm
> certainly supportive if Tom wants to become a project lead.  
> 
> regards,
> -Chris
> 
> 
> From: 	Tom Schindl <listom@xxxxxxxxxxxxxxx>
> To: 	Nebula Dev <nebula-dev@xxxxxxxxxxx>
> Cc: 	Technology PMC <technology-pmc@xxxxxxxxxxx>
> Date: 	11/03/2008 12:10 PM
> Subject: 	Re: [nebula-dev] Nebula Project Review
> 
> 
> ------------------------------------------------------------------------
> 
> 
> Hi Chris,
> Chris Aniszczyk schrieb:
>> Hi Nebula team, the Technology PMC is reviewing projects and here is
>> the review for your project:
>>
>> The project isn't conforming to the incubation branding
>>
> (http://wiki.eclipse.org/Development_Resources/HOWTO/Conforming_Incubation_Branding).
> 
>> It would be fantastic if the Nebula project could take the initiative
>> and fix this so it can take advantage of the Parallel IP process.
>>
>> The committers appear to come from a diverse group of companies and
>> individuals, this is a good thing.
> Yes and that's why Nebula is a bit different compared to other
> Eclipse-Projects (see Plan Question below).
>>
>> The mailing list isn't really active. Development doesn't seem to
>> reflect this as there is work going on in the source repository. The
>> newsgroups are pretty active which signifies the project has a good
>> user community.
> See above because every widget has only a small number of developers
> (often only one) this is reflected by the low traffic on the
> mailing-list. I also proposed some time ago to add states like
> Apache-Jakarta does. There's a mail from me "CTableTree" from
> "2008-06-17" things like this and more.
>>
>> The project plan [1] is not yet in the standard format... I couldn't
>> really find a plan at all. Should the plan be scoped to each Nebula
>> widget or should it be something higher level like "get nebula widgets
>> on the Galileo train"
> I think that every widget should have its own plan. I also would like to
> change the scope of  Nebula to reflect reality. The current project
> description says:
> 
> "The Nebula project is a source for custom SWT widgets and other UI
> components. Nebula is also an incubator for SWT. Some Nebula widgets
> will graduate into SWT and therefore into the main Eclipse Platform."
> 
> I think this doesn't reflect reality because it's fairly unlikely that
> any of the widget will ever get part of SWT but adds some constraints to
> what Nebula-Widgets (e.g. CDC1.0 support - though its not reality)
> whereas I'd like to allow widget implementors to use Java 1.4/Java 5.
> 
>>
>> The IP Log [2] appears complete, but I'm not sure. The Nebula project
>> should strive to use the Automated IP Log process now [3].
>>
>> I've noticed that the Nebula project has a great website show casing
>> the widgets. However, the widgets available on the website are out of
>> date. This is most likely because Nebula doesn't have an automated
>> build system for the various widgets. Does the Nebula project need
>> help in this regard? I think it would be beneficial to the consumers
>> of the Nebula widgets if there was an automated build system in place.
>> Maybe community members like Nick Boldt can help, or the Nebula could
>> be the guinea pigs for the Common Build Infrastructure work [4].
> 
> Yes we need help and if someone who knows the releng system takes a look
> it is not really hard to get such a build running because we only have
> plain java builds. We even has a bug for this
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=237588.
> 
>>
>> Currently, Chris Gross from IBM is the project lead from Nebula, how
>> about nominating another person from Nebula to join the project
>> leadership? I think Tom Schindl has done a good job in keeping up with
>> the Nebula newsgroup and mailing list. This can help split some of the
>> workload amongst project leads and not only have Chris Gross in a
>> position to approve things.
>>
>> One question the Nebula team can ask themselves is how to make it
>> easier for people to come in and bring in their widgets? I think if an
>> automated build is setup and the project conforms to the IP process,
>> it would be easier for people to come on board.
> Right. IMHO the following things help to get people started easier:
> - Don't enforce Java x
> - Prallel IP
> 
> Tom
>>
>> [1]
>>
> http://www.eclipse.org/projects/project_summary.php?projectid=technology.nebula
>> [2] http://wiki.eclipse.org/Nebula_Gallery_IPLog
>> [3] http://www.eclipse.org/projects/ip_log.php?projectid=technology.nebula
>> [4] http://wiki.eclipse.org/Build_Workshop_3:_Build_Hard_With_A_Purpose
>>
>> Thanks for reading and let us know if you need help.
>>
>> --
>> Cheers,
>>
>> ~ Chris Aniszczyk
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> nebula-dev mailing list
>> nebula-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>  
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev