Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rap-dev] Contributions Policy

Austin, the demo is pretty impressive. I'd love to see something like that in the incubator.

Rüdiger, regarding the structure, I'm +1 for your suggestion. We should not go down the same path as we did in the sandbox by pushing all bundles into one common directory.

Regards,
  Benny

Rüdiger Herrmann wrote:
On 28.01.2010 18:59, Austin Riddle wrote:
Hello Rüdiger,

What you propose sounds fine to me. After the Google visualizations are
committed I would like to offer a basic integration of the JIT
(Javascript InfoVis Toolkit) as RAP custom widgets: http://thejit.org/
The demos look real cool. I would welcome such a component.


It is BSD so there shouldn't be an IP problem.
This is good news:)


Discussion open.

Anyone have any comments or questions?
I am asking myself how to structure the incubator code repository. My current thinking is to have a separate folder for each "component" like so:
incubaor
  spreadsheet
    o.e.spreadsheet
    o.e.spreadsheet.tests
    ...
  infovis
    o.e.infovis
    ...
  themeeditor
    o.e.themeeditor
    o.e.themeeditor.tests
Any thoughts on this?


Thanks.

Rüdiger Herrmann wrote:
Hello Austin,

thanks for asking. As we haven't had many contributions from "outside"
there is no real policy established so far.
However, I think it makes sense to discuss contributions on the
mailing list first.
Once a contribution has made it into CVS, the newsgroup would be a
good place to announce its availability. Currently there is a simple
page on the project home page, that lists all available components in
the incubator/sanbox (former "incubator") [1]. To have it extended,
please open bug with an image and the description attached. For
further documentation or other content, we thought the wiki would do.
Please let us know if that suits your needs.

Regards
Rüdiger

[1]

On 27.01.2010 16:37, Austin Riddle wrote:
Hello Rudiger,

I have been working the Google visualizations contribution with the IP
team and I was wondering if the RAP team had some policy about
discussing/negotiating contributions in general before CQs are opened.

For instance, I am working on another contribution and I want to know if
it needs to be discussed/announced on the mailing list first, or if I
can just start the CQ for them outright.

Thanks,


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



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


Back to the top