| Re: [mobile-iwg] Nokia Code Contribution for Pulsar |
Hi David
I just reopened the bug and you can post the code contribution there (https://bugs.eclipse.org/bugs/show_bug.cgi?id=273604).
You only need to attach two files. One is the patch file with the code and the other a zip file containing all the binary files you need. Post any instructions you have about this code contribution in the bug as well.
After that, we from MTJ can post your contribution to IPZilla, and keep you informed about the current status.
If you need anything else, please inform us.
Diego Sandin
MTJ
-----Original Message-----
From: mobile-iwg-bounces@xxxxxxxxxxx on behalf of David.Dubrow@xxxxxxxxx
Sent: Fri 5/1/2009 2:49 PM
To: mobile-iwg@xxxxxxxxxxx
Subject: Re: [mobile-iwg] Nokia Code Contribution for Pulsar
I just realized that I had not sent this reply to the group mail list, but only to Christian! I have to pay better attention when I hit reply.
On 4/30/09 7:45 AM, "David Dubrow" <david.dubrow@xxxxxxxxx> wrote:
Hi Christian,
I am shooting for a first version with a no-frills UI tool to generate the repository metadata before the end of May. I believe we can have functionality including unzipping zipped sdk archives and executing sdk installers done by then. If things go well, maybe we can tackle uninstalling within the Galileo time frame (which I believe is towards the end of June?), but I don't know how things will go given that we're still relatively new to P2. It seems from my initial investigation, that P2 is doing most of the work for us so it's just a matter of creating the QuickInstall view, adding the plumbing between the custom QuickInstall view and the P2 wizards and engine code.
I think we may have a first contribution next week, but it will only be engine code with unit test drivers and no UI and no metadata generator. After that, I would like to see if it would be possible for me to be able to commit directly into the pulsar projects at mtj since it would make it easier to backup ongoing work. Also, binary contributions (e.g., a test zip archive, or test logo image file) are more problematic when it comes to using patches as a primary form of contribution. The binaries would have to be attached separately with instructions on where to put them, etc..
Lastly, the bugzilla below has been marked resolved by Diego because its primary purpose of creating new projects for us is now complete. And also, I can't login to ipzilla - the login page states "Only Eclipse committers can use IPZilla."
BR,
--David
On 4/29/09 5:35 PM, "ext Christian Kurzke" <christian@xxxxxxxxxxxx> wrote:
Hi Ian,
We have created a Bugzilla entry for the Nokia work, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=273604
And a IP-Zilla "CQ" for the work:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=3273
David,
do you have an estimate on when you can deliver a first version, and how
long until you can deliver a final version?
The best "formal" way of delivering would be to attach the code to the
Bug as "attachment".
Can we assume that the work will be completed by May 11th, so our team
has a week time to review and integrate before the "RC1" deadline?
Thanks
Christian
Ian Skerrett wrote:
>
> We should be able to handle the IP review of Nokia's Pulsar code
> contribution to MTJ. This is based on some assumptions:
>
> 1. Nokia is the copyright owner for 100% of the code; ie. it is
> written all by Nokia employees and contains no third party
> libraries.
> 2. The code contribution is not huge.
> 3. The code is not implementing an industry standard that might
> have IP considerations (I am assuming this is not the case)
> 4. The code is submitted in the next 2-3 weeks.
>
> Christian, someone on the MTJ team will need to create a CQ and follow
> the IP process. Please send me the CQ number and I will make the IP
> team aware of it.
>
> Let me know if you have any questions.
>
> Ian
>
> Ian Skerrett
>
> Director of Marketing
>
> Eclipse Foundation
>
> 613-224-9461 ext. 227
>
> blog: ianskerrett.wordpress.com <.wordpress>
>
> twitter: https://twitter.com/ianskerrett
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mobile-iwg mailing list
> mobile-iwg@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mobile-iwg
>