Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nebula-dev] Future of Nebula 
Hi,

Sorry my comments are a bit late (Easter holiday/Spring break).
From the consumer perspective, I agree that a table summarizing the purpose, features and state of widgets is important. I think a table with the following contents would be a good start: 

- widget name
- one-liner describing purpose
- SWT support (yes/no)
- RWT/RAP support (yes/no)
- JFace requirement (yes/optional/no)
- CSS support, i.e. can be styled with CSS
- lead maintainer
- (separate) indication of maturity (e.g. alpha, beta, released, mature) and activity (e.g. inactive (dead?), stable (mainly bug-fixing), active (new features in development)) 
- links to example page, bugzilla, source repo, ...
From the maintainer perspective I think it is important to allow for several models, from simple widget in common repo and little or no overhead, to separate project with own repo, releases and site. This ensures a low threshold for contributing, while allowing more complex projects to manage on their own without burdening the Nebula lead. 

Hallvard

On 09.04.13 10.40, Wim Jongman wrote:

Thanks for the input and the offer for help Edwin. I agree with most of
your ideas but I'm happy with the current state of our build and repo.
Mickael?


    2. Revamp the widget catalog. This is the first thing prospective
    users of Nebula will see, and it should convey accurate and useful
    information to them.


+1 does anyone care to propose a format?

         a. Indicate who the lead maintainer is for each widget and
    provide contact info, or if there is no active maintainer indicate
    this as well. It's great that we have identified this already, but
    we should put this info into the catalog because it tells users how
    they can get support. Users are not going to dig through our wiki to
    find this info.


I'm fine with this. Anyone objections?


         b. Provide links to the widget's source repo and ci build (see #1)

         c. Provide links to the bugzilla for each widget so users know
    how to submit bug reports and maintainers can see what needs to be done.


sounds good.
I think revamping the widget list and providing more info per widget is
the next step.

Regards,

Wim


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



--
Hallvard Traetteberg, Visiting Scholar at EECS, Univ. of California, Berkeley

Back to the top