Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [mobile-iwg] Weekly (Technical) Pulsar Call - Thursday, April 9th

Title: Re: [mobile-iwg] Weekly (Technical) Pulsar Call - Thursday, April 9th

Gustavo,

 

Thanks for pulling in the bugzilla updates. I'll second the notion that for this release we use the MTJ bugzilla for technical discussions, bugs, patches, etc. As for the repository, I also agree that due to the short timelines we should commit to using MTJ as the vehicle for Galileo development.

 

I'm not sure if you were the one who created the SDK provider guidelines, but I'd like to get some feedback on req3; network access. It lists the site must be available via HTTPS, is that a hard req, if so what's the background? We can discuss in the call tomorrow if preferred.

 

Regards,

Ronnie

 

From: mobile-iwg-bounces@xxxxxxxxxxx [mailto:mobile-iwg-bounces@xxxxxxxxxxx] On Behalf Of ext Paula Gustavo-WGP010
Sent: Wednesday, April 08, 2009 9:20 AM
To: Mobile Industry Working Group
Subject: RES: [mobile-iwg] Weekly (Technical) Pulsar Call - Thursday, April 9th

 

Hi,

 

I just created a component in MTJ bugzilla called “Pulsar”. If you guys want, we can use it to open bugs, attach patches, etc. (the main URL to file bugs is: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=MTJ. Just select “Pulsar” component). It is also possible to use the working group wiki. It is open to everyone to add / edit pages.

 

Since there is no pulsar specific repository right now, we can also use MTJ. We can adapt MTJ build to generate a Pulsar specific feature with all code that will be part of Pulsar distribution (at least that’s what we initially imagined). So if anyone ants to contribute code on pulsar, he needs to follow a usual eclipse contribution process:

-       File a bug on MTJ/Pulsar

-       Attach the contribution

-       MTJ committers will review and commit the code to the SVN that will be available on the next nightly build

 

Does that make sense?

 

J

gep

 


De: mobile-iwg-bounces@xxxxxxxxxxx [mailto:mobile-iwg-bounces@xxxxxxxxxxx] Em nome de Ronnie.King@xxxxxxxxx
Enviada em: terça-feira, 7 de abril de 2009 22:38
Para: mobile-iwg@xxxxxxxxxxx
Assunto: Re: [mobile-iwg] Weekly (Technical) Pulsar Call - Thursday, April 9th

 

Todd,

Thanks for jumping in with this, the p2 api’s are the area that we have the most concern with right now. Any information you could provide would be really appreciated. Since we do not have a bugzilla to track this with, for simplicity I’d say let’s just use email for now.

Regards,
Ronnie


On 4/7/09 6:39 PM, "ext Christian Kurzke" <christian@xxxxxxxxxxxx> wrote:

Hi Todd, Ronnie,

Thanks for stepping up so quickly!

Todd,

Depending on the type of write-up your team has done, you can either
update (or create a new page) on the Wiki site.
Or, if it is easier - just mail out an attachment to this list, we can
use it as a basis for discussion in the call on Thursday.

Unfortunately we dont yet have a proper "document repository" for Pulsar.

-Christian



Todd Williams wrote:
> Christian & Ronnie
> I asked my some of my Pulse <http://www.poweredbypulse.com> team for
> guidance on how you could implement the SDK delivery requirements
> using native p2. They wrote up a quick set up steps and a bit of
> example code to illustrate the points. I was going to ask on the
> Thursday call what you thought would be the best way to contribute the
> information to the group. However, I saw Ronnie's message and didn't
> want his team to waste time if the information I had would give them a
> headstart. So, would updating the wiki be the best way to communicate
> this information?
> Regards,
> Todd
>
>     ----- Original Message -----
>     *From:* Ronnie.King@xxxxxxxxx <mailto:Ronnie.King@xxxxxxxxx>
>     *To:* mobile-iwg@xxxxxxxxxxx <mailto:mobile-iwg@xxxxxxxxxxx>
>     *Sent:* Tuesday, April 07, 2009 5:35 PM
>     *Subject:* Re: [mobile-iwg] Weekly (Technical) Pulsar Call -
>     Thursday, April 9th
>
>     Hi Christian,
>
>     I have allocated two developers on my team to start research on
>     the p2 engine and viewer requirements as of today. I’ll work on
>     updating the wiki pages to reflect the areas that we are planning
>     on contributing to.
>
>     Some areas that would be helpful to clarify:
>
>         * Are we tracking the feature discussions in MTJ’s bugzilla as
>           we do in other projects such as CDT? If so, should there be
>           a Pulsar component added?
>         * Do you have a location in MTJ svn for hosting the code?
>
>
>     Regards,
>     Ronnie
>
>
>     On 4/6/09 6:42 PM, "ext Christian Kurzke" <christian@xxxxxxxxxxxx>
>     wrote:
>
>         Hello Everyone,
>
>         After a very busy EclipseCon meeting, I would like to resume the
>         Bi-Weekly Pulsar Meeting Schedule.
>
>         The main focus of this meeting is to review the list of tasks
>         which need
>         to be accomplished by working group members before the Galileo
>         deadline.
>
>         For an overview, please see:
>         http://wiki.eclipse.org/EMIWG/GalileoExecutionPlan
>
>         This diagram shows a large number of tasks currently are NOT
>         STAFFED.
>         On the right side I included a column with my best judgment
>         which company
>         would posses the right skills for this task.
>         A more detailed description of the expected skills can be
>         found here:
>         http://wiki.eclipse.org/EMIWG/GalileoPulsarWorkItems
>
>         I ask every company to review those items and for the meeting
>         make a
>         decision if they can contribute engineering headcount for any
>         of those
>         tasks.
>         (Please note: My assignment of company names to tasks is only a
>         suggestion, and of course not binding!)
>
>         The full agenda with dial-in information is here:
>
>         http://wiki.eclipse.org/EMIWG/MembersCall-09-April-2009
>
>         Best Regards,
>
>         Christian Kurzke
>
>
>         _______________________________________________
>         mobile-iwg mailing list
>         mobile-iwg@xxxxxxxxxxx
>         https://dev.eclipse.org/mailman/listinfo/mobile-iwg
>
>     ------------------------------------------------------------------------
>     _______________________________________________
>     mobile-iwg mailing list
>     mobile-iwg@xxxxxxxxxxx
>     https://dev.eclipse.org/mailman/listinfo/mobile-iwg
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> mobile-iwg mailing list
> mobile-iwg@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mobile-iwg
>  

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


Back to the top