Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] Request archiving Tools for Mobile Web

Hi Gorkem, Eric -


Did you notice attached E-Mail on cross-project ?


There is some confusion around whether MTJ and Sequoyah should be on the Juno coordinated release or not.

Please check





From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Gorkem Ercan
Sent: Saturday, December 24, 2011 6:06 PM
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Request archiving Tools for Mobile Web



This is actually not a good time to terminate MTJ. I am aware of a project starting by an Eclipse member that is aiming to adopt and extend MTJ further.


Anyway MTJ is a mature project that provides tooling around MIDP for JavaME developers. It is very much in use by the MIDP developers. At this point the work on MTJ is concentrated more on adjusting to platform changes and bug fixing.






On Sat, Dec 24, 2011 at 6:46 PM, ERIC CLONINGER <dcp874@xxxxxxxxxxxx> wrote:

I would like to see how much usage the project has in the last year
before we go to the effort to move the project into Sequoyah vs.
leaving it vs. closing it. After the holidays, it would merit spending
some time to look at downloads. I don't see any activity on the dev
list, but that isn't always an indicator of adoption.

It's a mature project and may not need a lot of hand-holding. But if
it's not seeing a lot of install activity, then that's another matter.
FWIW, Sequoyah may not see direct installs through, but we
have 5-10K per month as a result of MOTODEV Studio. So, it's up to
Gorken to comment on the matter as the project lead.


On Wed, Dec 21, 2011 at 9:51 PM, Schaefer, Doug
<Doug.Schaefer@xxxxxxxxxxxxx> wrote:
> I think we should consider Terminating MTJ as well, or at least move its assets up to Sequoyah. A one part-time person project isn't worth the overhead. Thoughts, Eric?
> :D
>> -----Original Message-----
>> From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-
>> bounces@xxxxxxxxxxx] On Behalf Of David M Williams
>> Sent: Wednesday, December 21, 2011 1:42 PM
>> To: Tools PMC mailing list
>> Subject: Re: [tools-pmc] Request archiving Tools for Mobile Web
>> Sounds good. Thanks for initiating this.
>> I suggest as the next step you write a short "Termination Review" proposal,
>> and send to Wayne, so he can circulate to community and schedule the
>> "review period", just to insure the right processes are followed, all is
>> documented, etc.
>> Here's one example,
>> And some shorter examples on the Technology wiki:
>> (and, a short one definitely seems appropriate for this case).
>> So, I believe that leaves Sequoyah itself (which has its own code and
>> committers, not just a contain project, right?) and one subproject, Mobile
>> Tools for the Java. I  was surprise to see the "incubating" logo on Mobile
>> Tools for Java ... after having several 1.0.x releases, I would have thought
>> they would have graduated. Is this a portal database error ... or, should they
>> initiate a graduation review as well?
>> Thanks again, Eric.
>> From: ERIC CLONINGER <ericc@xxxxxxxxxxxx>
>> To:   Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>,
>> Date: 12/20/2011 10:07 PM
>> Subject:      [tools-pmc] Request archiving Tools for Mobile Web
>> Sent by:      tools-pmc-bounces@xxxxxxxxxxx
>> I would like to propose that the Tools for Mobile Web project (TMW) be
>> archived. TMW is a sub-project of Sequoyah that was proposed in June
>> 2010 and was approved in September 2010. The last commit was in October
>> 2010 and the only activity on the mailing list has been automated submissions
>> from portal informing the project that their metadata is out of date. The
>> people behind the project have moved on and are not interested in the
>> technology, at least in this incarnation, so it needs to be put to rest.
>> Thanks
>> --
>> Eric Cloninger (ericc@xxxxxxxxxxxx)
>> Product Line Manager, MOTODEV Tools
>> Eclipse Sequoyah Project Lead
>> _______________________________________________
>> tools-pmc mailing list
>> tools-pmc@xxxxxxxxxxx
>> _______________________________________________
>> tools-pmc mailing list
>> tools-pmc@xxxxxxxxxxx
> _______________________________________________
> tools-pmc mailing list
> tools-pmc@xxxxxxxxxxx

Eric Cloninger (ericc@xxxxxxxxxxxx)
Product Line Manager, MOTODEV Tools
Eclipse Sequoyah Project Lead
tools-pmc mailing list



--- Begin Message ---

I tried matching up the projects that are participating in Juno, per

with the b3aggrcon files in the project.

Lacking any hope of automation, I hacked together a wiki page to use for

Most were pretty obvious, I guessed about 6, and there are a dozen or so
not really accounted for.

And in both directions:
a few cases where I could not tell what b3aggrcon file went with a known
and some, apparently "extra" b3aggrcon files "left over" that didn't seem
to have a matching project (and not enough "unknown cases" to account for
them all).

It might be the case that some projects, as listed in
might have more than one b3aggrcon file? I guess that is ok, but I'll
need everyone's help to

a) proof read what I have and what I have guessed, and
b) fill in (or edit) the wiki page to make the table complete.

The goal is partially to make sure no b3aggrcon files should be removed (no
longer active?) but also to have a record so issues and bugs can be more
easily opened, if they occur.

I'm sure I could do more detective work and figure out some cases .... but,
would prefer projects provide this info in the first place, so I've just
given you a head start.

Since nothing gets done without a deadline, I'll give two:
please try to get done by Friday, 2/10, but I'll give  a full week (2/15)
before I start removing accounted for files. And, just let me know if those
dates don't work for you, such as if a critical person in on vacation or
something ... but, should be obvious to many in project and take only 5
minutes or so.

Thanks all,

cross-project-issues-dev mailing list

--- End Message ---

Back to the top