sequoyah-dev

[sequoyah-dev] Project meta data is out of date for tools.sequoyah

emo@xxxxxxx (portal on behalf of emo) — Sat, 05 May 2012 04:00:14 GMT

Eric,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* The date for release "2.0.2" is in the past, but the release is not
marked as completed. If it is completed, it should be marked as completed;
if it has been postponed, it should be given a new target date.
* There is no next/future release of this project. All Eclipse projects
must have a "next release" planned and scheduled.

Re: [sequoyah-dev] Status of Mobile Tools for Java

wayne@xxxxxxx (Wayne Beaton) — Tue, 24 Apr 2012 19:48:27 GMT

I'm not too concerned about a 1.0.2 *tag*. What I'm wondering about is the ./tag/1.0.2 directory and siblings in the master branch. It looks like a tag, but it's really a directory

Wayne

On 04/24/2012 03:45 PM, Jon Dearden wrote:

Wayne,

I supplied a patch to MTJ to support a feature where we allowed SDK providers to plug in toolkits into MTJ. The 1.0.2* tag was applied to mark the code before this rather large change was added.

Cheers,

Jon

Jon Dearden
Senior Software Developer - Advanced Tooling

Research In Motion Limited

Office:

(519) 597-5463 x75463

Mobile:

(519) 500-2167

From: sequoyah-dev-bounces@xxxxxxxxxxx [mailto:sequoyah-dev-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Tuesday, April 24, 2012 3:28 PM
To: sequoyah-dev@xxxxxxxxxxx
Subject: [sequoyah-dev] Status of Mobile Tools for Java

I noticed today that the MTJ Git repository has what looks like "branch" directories in the master branch.

e.g.

./tags/1.0RC1/*
./tags/1.0.2_BEFORE_SDK_PROVIDER/*

Does anybody have any idea what's happening here? Is this an artefact from the SVN import? (the root directory structure looks like an SVN repository to me).

Also, is MTJ still active? There hasn't been very much commit activity for a long while.

I've also noticed that the defunct mailing list, dsdp-mtj-dev, is still listed in the project metadata. It's not clear to me what channel I should be using to communicate with MTJ.

Thanks,

Wayne

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

Re: [sequoyah-dev] Status of Mobile Tools for Java

jdearden@xxxxxxx (Jon Dearden) — Tue, 24 Apr 2012 19:45:55 GMT

Wayne,

I supplied a patch to MTJ to support a feature where we allowed SDK providers to plug in toolkits into MTJ. The 1.0.2* tag was applied to mark the code before this rather large change was added.

Cheers,

Jon

Jon Dearden
Senior Software Developer - Advanced Tooling

Research In Motion Limited

Office:	(519) 597-5463 x75463
Mobile:	(519) 500-2167

From: sequoyah-dev-bounces@xxxxxxxxxxx [mailto:sequoyah-dev-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Tuesday, April 24, 2012 3:28 PM
To: sequoyah-dev@xxxxxxxxxxx
Subject: [sequoyah-dev] Status of Mobile Tools for Java

I noticed today that the MTJ Git repository has what looks like "branch" directories in the master branch.

e.g.

./tags/1.0RC1/*
./tags/1.0.2_BEFORE_SDK_PROVIDER/*

Does anybody have any idea what's happening here? Is this an artefact from the SVN import? (the root directory structure looks like an SVN repository to me).

Also, is MTJ still active? There hasn't been very much commit activity for a long while.

I've also noticed that the defunct mailing list, dsdp-mtj-dev, is still listed in the project metadata. It's not clear to me what channel I should be using to communicate with MTJ.

Thanks,

Wayne

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Re: [sequoyah-dev] Status of Mobile Tools for Java

dcp874@xxxxxxx (ERIC CLONINGER) — Tue, 24 Apr 2012 19:45:21 GMT

Wayne,

When I last heard from Gorkem in October, he said MTJ was still
active. I see he's made some commits in the last month but prior to
that, it was last fall.

I haven't had any responses from him about our activities on Sequoyah.
I don't believe he follows this mailing list. I've cc'd him on this
email.

-E

On Tue, Apr 24, 2012 at 2:27 PM, Wayne Beaton  wrote:
> I noticed today that the MTJ Git repository has what looks like "branch"
> directories in the master branch.
>
> e.g.
>
> ./tags/1.0RC1/*
> ./tags/1.0.2_BEFORE_SDK_PROVIDER/*
>
> Does anybody have any idea what's happening here? Is this an artefact from
> the SVN import? (the root directory structure looks like an SVN repository
> to me).
>
> Also, is MTJ still active? There hasn't been very much commit activity for a
> long while.
>
> I've also noticed that the defunct mailing list, dsdp-mtj-dev, is still
> listed in the project metadata. It's not clear to me what channel I should
> be using to communicate with MTJ.
>
> Thanks,
>
> Wayne
> --
> Wayne Beaton
> The Eclipse Foundation
> Twitter: @waynebeaton
> Explore Eclipse Projects
> --
> Wayne Beaton
> The Eclipse Foundation
> Twitter: @waynebeaton
> Explore Eclipse Projects
>
> _______________________________________________
> sequoyah-dev mailing list
> sequoyah-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/sequoyah-dev
>



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

[sequoyah-dev] Status of Mobile Tools for Java

wayne@xxxxxxx (Wayne Beaton) — Tue, 24 Apr 2012 19:27:49 GMT

--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

[sequoyah-dev] Project meta data is out of date for tools.sequoyah

emo@xxxxxxx (portal on behalf of emo) — Thu, 05 Apr 2012 04:00:14 GMT

Eric,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* The date for release "2.0.2" is in the past, but the release is not
marked as completed. If it is completed, it should be marked as completed;
if it has been postponed, it should be given a new target date.
* There is no next/future release of this project. All Eclipse projects
must have a "next release" planned and scheduled.

[sequoyah-dev] Project meta data is out of date for tools.sequoyah

emo@xxxxxxx (portal on behalf of emo) — Mon, 05 Mar 2012 05:00:06 GMT

Eric,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* The date for release "2.0.2" is in the past, but the release is not
marked as completed. If it is completed, it should be marked as completed;
if it has been postponed, it should be given a new target date.

[sequoyah-dev] Sequoyah activities, post Indigo SR2

ericc@xxxxxxx (ERIC CLONINGER) — Tue, 28 Feb 2012 16:32:31 GMT

Hello everyone,

I apologize for the wide distribution. I want to make sure there is
the best chance for this email to be seen by those who need to see it.

Now that Indigo SR2 is released, the Sequoyah project is going to
become less active. The burden of committing code and maintaining the
builds has fallen exclusively on Daniel Pastore. Daniel has new duties
that will not allow him to devote as many hours to maintaining builds
and infrastructure of the project.

We are not abandoning Sequoyah because we still use the components in
MOTODEV Studio. We have bugs in the queue that we intend to fix and we
will still participate as members of the community. But, we aren't
planning new components and the project will not be on the Juno train.
There will not be official releases, but there will be nightly builds
that interested parties can download and use.

I hope the opportunity arises that we can work on Sequoyah more
aggressively in the future. If another group or person wants to become
involved, we will happily help them get up and running. If you have
any questions or concerns about this feel free to address them on
sequoyah-dev or to me directly.

Regards

Eric
ericc@xxxxxxxxxxxx

Re: [sequoyah-dev] GSoC Wrapup

kpqb38@xxxxxxx (Daniel Pastore) — Fri, 27 Jan 2012 16:51:26 GMT

Hi Lucas,

Thanks a lot for your contribution! :)

And you're welcome to keep contributing to Sequoyah and/or any other Eclipse project you want, this is what makes a community!

Best,

On Mon, Jan 9, 2012 at 09:56, Lucas Tiago Castro Jesus <lucastdcj@xxxxxxxxx> wrote:

Hi,

Firstl of all I would like to apologize, these weeks were very hard for me. It was the vacation here in France and I was travelling, I am really sorry.Â

So I will do my best to answer each question, but if you have any further question please do not hesitate.

1) I really appreciated the weekly raports. It gave me a better organization, every week I discussed with my mentors about I have did and what was atented from me for the next week, it was a very good for me.Â

2) The most challenging was get a big project and try to understand a lot of sourcecode, so at beginning ÂIÂhadÂdifficultiesÂto understand the real objective of the proejct, but once I tried some examples and changing the code what was the result. The project came clear and very interesting.

3) When you see that the code is working it's the best feeling.

4) It worked very well for me, every week I could ask my questions and explain better what I did so it was very good to appear others questions and move forwardÂthe project

5) It was the gtalk, because they were available almost every time when I needed

6) Just one word:Âimpeccable

7)ÂSome weeksÂalmost daily, butÂin generalÂwe can sayÂtwice a week

8) I didn't remember any bad interaction, and everyÂinteractions were very good because they were very clear and direct so we didn't lose time.

9) As I said it was very hard to me to understand at the beginning the code and the goal of the project, so I think it would be nice do some tutorials to explain how to use the project.

10) I can certainlyÂsay it wasÂoneÂofÂtheÂbestÂexperience I ever had in my education.Â

11) Perfect,ÂÂÂI recommendÂto everyone. Working on aÂopen sourceÂproject is phenomenal,Âbut whenÂyou get aÂtalented team dedicated toÂhelp you it's justÂreally awesome,ÂsoÂI just have to thankÂyou all for thisÂincredibleÂexperienceÂand IÂhope I canÂhelpÂyou more and more.

So, thank you very much!
Lucas DE CASTRO

2011/12/2 Marcel Gorri <wmg040@xxxxxxxxxxxx>

Hi Lucas!

In order to have a formal wrapup of our GSoC activities here in Sequoyah, can you please answer the following questions? Our intention is to register this experience as a lessons learned for the future.

1) What worked better and what didnât in terms of activities workflow?
2) What difficulties did you have with code and technical understanding?Â
3) What did you like the most in terms of evolving the code?

4) The model of meetings on demand and e-mail orientation worked?
5) What was the best communication channel with your mentors?
6) How responsive was your mentor to you when you had questions or sent communications?

7) How often did you interact with your mentors?Â
8) Give one example of a very good or very bad interaction you had with your mentor.
9) What suggestions do you have for Sequoyah project?
10) Do you think this experience helped you in your education?
11) How would you rate your experience with the program overall?

Thanks a lot!
Marcel

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

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

--
Thanks,

Daniel Pastore

[sequoyah-dev] Fwd: [cross-project-issues-dev] Status and outlook for Indigo SR2 RC1 warm-up build

kpqb38@xxxxxxx (Daniel Pastore) — Fri, 27 Jan 2012 15:42:18 GMT

Hi guys,

just following David Williams advice, this is an email to announce that since we had no bugfixes for Indigo SR2, Sequoyah will be using Indigo's SR1 build for the last release of the Indigo train.

Thanks all for the support!
Any questions, suggestions and contributions are welcome at any time!

Best,

---------- Forwarded message ----------
From: David M Williams <david_williams@xxxxxxxxxx>
Date: Wed, Jan 18, 2012 at 18:55
Subject: Re: [cross-project-issues-dev] Status and outlook for Indigo SR2 RC1 warm-up build
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, cross-project-issues-dev-bounces@xxxxxxxxxxx

No, if nothing changes, you do not need to change versions (in fact, best
not to!)

I know in the past this sometimes it has confusing to adopters ... when
versions do not change ... Âthat might be waiting for your next version ...
but I think a simple announcement on your dev list that your x.y.1 version
will be your contribution to Indigo SR2 suffices to clear that up.

Thanks,

From: Â Daniel Pastore <kpqb38@xxxxxxxxxxxx>
To: Â Â Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date: Â 01/18/2012 03:07 PM
Subject: Â Â Â ÂRe: [cross-project-issues-dev] Status and outlook for Indigo
Â Â Â Â Â ÂSR2 RC1 warm-up build
Sent by: Â Â Â Âcross-project-issues-dev-bounces@xxxxxxxxxxx

Hi David,

Just a quick question: I've seen you kept our SR1 contribution for
Sequoyah, and as we are almost on maintenance, we don't have any bugfixes
for SR2. Do I *need* to generate another build, with a x.y.2 version or can
we keep this x.y.1, since the code will be the same?

And thanks for your quick help over all these warm-up weeks! :)

On Wed, Jan 18, 2012 at 17:58, David M Williams <david_williams@xxxxxxxxxx>
wrote:

Âtick tock

ÂHere we are already at 3 PM on +3 day. Unless someone shouts "wait", I'll
Âconsider the updates for RC1 finished by 5 PM today (Eastern), and what
Âever build is current will then become our "maintenance" staging repo for
ÂRC1.

Âhttp://download.eclipse.org/releases/maintenance/

ÂThere are two contribution files that have disabled features or
Ârepositories ... riena being the largest omission ... last call! :)

Âep.b3aggrcon (see bug 362103)
Âriena.b3aggrcon

ÂMarkus tells me, in keeping with tradition, he will produce the EPP
Âpackages with the same spirit of "warm-up" (not moved to downloads, not
Âmirrored, no official sign-off, but the maintainers (or, anyone) can
Âstill
Âtest from the EPP build site.

ÂIn two short weeks we'll produce RC2 which overlaps with Juno M5! ... so,
Âplan accordingly ... I'm sure we'll be keeping the build machine(s) warm
Âthat week.

ÂIndigo: http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan#SR2
ÂJuno: http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Schedule

ÂThanks,

Â_______________________________________________
Âcross-project-issues-dev mailing list
Âcross-project-issues-dev@xxxxxxxxxxx
Âhttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Thanks,

Daniel Pastore_______________________________________________

cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Thanks,

Daniel Pastore
Sequoyah Team