Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mobile-iwg] [sequoyah-dev] Mainttaining the Pulsar EPP package

Indigo M5 is rapidly approaching. Unless someone agrees to takeover as a package maintainer for the Pulsar package, I will let the EPP team that we need to pull Pulsar from Indigo.

Ian


On 12/16/2010 2:18 PM, Ian Skerrett wrote:
I agree the packages concept is valuable.   Beyond MTJ what else would you include in the Pulsar package?



On 12/16/2010 12:10 PM, Gorkem Ercan wrote:
I believe Pulsar EPP was actually meant to be a one stop download for mobile
developers. It is recognized as a JavaME package because MTJ is the only
included project that has value for mobile developers without external
dependencies. Actually this role with the ever shrinking contributions to
MTJ was a burden for MTJ project. The main motivation with keeping the MTJ
on the release train was to allow Pulsar to continue (with our current level
of contributions it is a burden to participate on the release train). I was
actually hoping that Pulsar could at some point continue without MTJ.

Packages like pulsar are valuable to developers who are just starting up
with their environment. I think we should try to see if we can bring a
more valuable Pulsar package for mobile developers that do not use JavaME.
Since Pulsar already has mechanisms to bring in vendor pieces, I think we
should actually discuss the possibility to bring vendor specific pieces
beyond SDKs.
--
Gorkem

On Wed, Dec 15, 2010 at 11:16 PM, ERIC CLONINGER <dcp874@xxxxxxxxxxxx>wrote:

Hello,

The Sequoyah team has been maintaining the Pulsar EPP since the
project was formed in December 2009. At the time, it made sense
because the Sequoyah team had their hands in the code and were getting
all the builds working.  However, the Pulsar EPP package is no longer
of interest to Motorola since we aren't focused on Java ME any longer.
I am planning to have our employees focus on things closer to our
commercial interest (e.g. Sequoyah, CDT, DTP, etc.).

If the Pulsar EPP package has value to others in the community, then
we need to transition to new maintainers. There is some amount of
effort in getting new package maintainers established, so this process
should start earlier rather than later. We want this to be an orderly
transition and we will be available to mentor new contributors. We
have Pulsar EPP working with M4, but we won't be building for M5 and
we won't contribute the package to the Indigo train. In the interest
of continuity, if changes are needed for Helios SR2, we will make
those changes, test, and post a new package for download.

To be clear, I'm only talking about the EPP package that is available
on download.eclipse.org. Sequoyah continues to be an active project
and Motorola employees will still commit code to the project. The
Sequoyah project will still be on the Indigo train. The Mobile
Industry Working Group will continue to meet under Ronnie King's
leadership. Other than the maintainers and/or availability of the
package, nothing else will change.

Regards

-E

--
Eric Cloninger (ericc@xxxxxxxxxxxx)
Eclipse Sequoyah Project Lead
_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev


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

--
Ian Skerrett
Director of Marketing
Eclipse Foundation
Tel: 613-224-9461 ext 227
Blog: ianskerrett.wordpress.com
Twitter: IanSkerrett

Save the dates for EclipseCon 2011, March 21-24
www.eclipsecon.org

--
Ian Skerrett
Director of Marketing
Eclipse Foundation
Tel: 613-224-9461 ext 227
Blog: ianskerrett.wordpress.com
Twitter: IanSkerrett

Save the dates for EclipseCon 2011, March 21-24
www.eclipsecon.org

Back to the top