Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of jbeard4@cs.mcgill.ca designates
 132.206.51.234 as permitted sender)
MIME-Version: 1.0
Reply-To: jbeard4@cs.mcgill.ca
In-Reply-To: <AANLkTingdPW8s2q9bR865vkZBulhWD8edWKKriITbyrx@mail.gmail.com>
References: <AANLkTilnyAcqDnH_6jT0t1NagWWENOIIp4uer8uqNYSM@mail.gmail.com>
	<AANLkTimZvj0n9skmeFTJLnuVaU9xqDAFy4McZqhgOWkz@mail.gmail.com>
	<AANLkTilQHI1ianEKB-gUowGSc_Rc4pqg7DNfoDe-K6ug@mail.gmail.com>
	<AANLkTingdPW8s2q9bR865vkZBulhWD8edWKKriITbyrx@mail.gmail.com>
From: Jacob Beard <jbeard4@cs.mcgill.ca>
Date: Thu, 15 Jul 2010 10:32:59 -0400
Message-ID: <AANLkTimr1dV6bBiK8oH4snLiI0354mA3k5zWUGXVMf5-@mail.gmail.com>
Subject: Re: [GSoC] Mid-term evaluations next week
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hi Rahul,

Unfortunately, I had configured my email filters to automatically
archive all Apache Commons traffic that was not in [scxml],
[scxml-js], or [all], and so I missed this email which used the [gsoc]
tag. I just now found it while searching through my archives. This was
a mistake, and I hope it will not reflect poorly on my committment to
this project.

I'd be happy to write a mid-term report, if you still think that would
be useful.

Sorry again for the confusion. Let me know what you think. Thanks,

Jake

2010/7/14 Xun Long Gui <ustbcoder@gmail.com>:
> Thanks for your job :-)
>
> On 7/6/10, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
>> 2010/7/5 Xun Long Gui <ustbcoder@gmail.com>:
>>> Hi Rahul,
>>>
>>> By now, everything of GSoC Visual SCXML project is going well with our
>>> initial plan. This project have this function list:
>>> 1. Implement Eclipse GMF based SCXML document visual editor tool;
>>> 2. Implement Eclipse SCXML document export function;
>>> 3. Implement Eclipse SCXML document import function;
>>> 4. Integrate with Commons SCXML, implement basic SCXML document test/de=
bug
>>> function;
>>> 5. Implement corresponding source code generation function.
>>>
>>> We have finish primary development job of function 1,2 and 3, we can us=
e
>>> this tool to help us finish some SCXML document edit job now. But i sti=
ll
>>> need several days to perfect details of them, I can finish this job bef=
ore
>>> 7.15.
>>>
>>> Meanwhile, we have started project website construction job, visiters c=
an
>>> get basic project guide from website content. I will keep on add/update
>>> website content in the coming days.
>>>
>>> I plan to finsih function 4 development job between 7.15-8.15, so this
>>> summer, we may have not enough time to finish function 5 in GSoC period=
,
>>> but
>>> i will start function 5 task when i finish function 4 at 8.15.
>>>
>> <snip/>
>>
>> OK, ofcourse, any effort you put in after the GSoC period should be
>> purely based on your interest. In other words, there is no GSoC
>> requirement to do anything beyond the pencils down date -- 8/16 :-)
>>
>>
>>> Now, this tool can provide SCXML document edit/export and import functi=
on,
>>> i
>>> think it satify many SCXML users' requirement, if possible, i want to m=
ake
>>> a
>>> alpha release version of this tool and supply download link on our
>>> website.
>>> This way, we can get more responses from users, they can help us to
>>> improve
>>> this editor.
>>>
>> <snap/>
>>
>> There is a set process to go through for releasing. Releasing requires
>> promotion out of the Commons Sandbox first, which requires a vote.
>> After promotion, the code needs to be packaged and approved for
>> release by another vote. We can discuss this in more detail when we
>> think the code is ready.
>>
>> -Rahul
>>
>>
>>> 2010/7/5 Rahul Akolkar <rahul.akolkar@gmail.com>
>>>
>>>> Jake, Long -
>>>>
>>>> The GSoC mid-term evaluations are next week.
>>>>
>>>> By July 12th 19:00 UTC, please send an email to this list summarizing
>>>> your project work so far. Think of it as a mid-term report. It can be
>>>> quite brief, but capturing items such as (may point to existing
>>>> resources such blog posts):
>>>>
>>>>  * Salient points of progress so far
>>>>  * Challenges (overcome and anticipated, if any)
>>>>  * Whether original objectived will be met, any stretch goals will be
>>>> achieved
>>>>  * What worked / did not work till date (technical, community-wise etc=
.)
>>>>  * Anything else you want to highlight
>>>>
>>>> In addition to all our interactions so far, this will be quite useful
>>>> to me as one of the tools in filling out the reviews. Thanks in
>>>> advance!
>>>>
>>>> -Rahul
>>>>
>>>
>>> --
>>> Best Regards
>>>
>>> Gui Xun Long (=B9=F0=D1=B5=C1=FA)
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> Best Regards
>
> Gui Xun Long (=B9=F0=D1=B5=C1=FA)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org