Hi all,
a quick status report:
Projects: we currently have 7 project ideas. I've sent a request on the Seaside mailing list for some Seaside-related ideas, and I've asked Andreas, Tim, and John for some Croquet- and VM-related ideas. Keith, if you want to propose a Pier related project, you should do that now. Likewise, if anyone else wishes to propose a project should speak now. I think we should aim for about 10/12 project ideas, covering a wide range of Squeak-related topics.
Students: right now we have 8 students interested in partecipating, with possibly one more that still has to confirm.
Mentors: we have 8 mentors (nine with me, in case a ninth student joins us). I'd like to have a couple more spare mentors, as defined here: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors , section "Allocating Resources".
Any comments?
Giovanni
On 28.02.2007, at 19:10, Giovanni Corriga wrote:
Hi all,
a quick status report:
Projects: we currently have 7 project ideas. I've sent a request on the Seaside mailing list for some Seaside-related ideas, and I've asked Andreas, Tim, and John for some Croquet- and VM-related ideas. Keith, if you want to propose a Pier related project, you should do that now. Likewise, if anyone else wishes to propose a project should speak now.
I will do a pass over the project stef proposed on the compiler tommorrow.
Another idea that would be perfect student project would be a code server for Squeak that has *all* code ever done, were all the images can get old version of the system...
"The goal of this Project is to develop a server based service that has the complete history of Squeak available. This then can be queried by different tools, from the normal Squeak history facilities to new analysis tools. As part of the project, one such analysis tools should be developed for analyszing code ownership for helping with the re-licensing of Squeak."
Marcus
I think we should aim for about 10/12 project ideas, covering a wide range of Squeak-related topics.
Students: right now we have 8 students interested in partecipating, with possibly one more that still has to confirm.
Mentors: we have 8 mentors (nine with me, in case a ninth student joins us). I'd like to have a couple more spare mentors, as defined here: http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors , section "Allocating Resources".
Any comments?
Giovanni
Soc mailing list Soc@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/soc
On 2/28/07, Marcus Denker denker@iam.unibe.ch wrote:
"The goal of this Project is to develop a server based service that has the complete history of Squeak available. This then can be queried by different tools, from the normal Squeak history facilities to new analysis tools. As part of the project, one such analysis tools should be developed for analyszing code ownership for helping with the re-licensing of Squeak."
I'm hoping to have some students do part of this project by May. In particular, they will have a complete history of Squeak on a server that can be accessed by the Squeak history facilities. This will allow us to make a release with an empty changes file without losing any history. People who do not want to be connected to the internet can get their own copy of the history database. I was not planning on building any new analysis tools, but it should be easy to build them.
-Ralph
On 28.02.2007, at 19:52, Ralph Johnson wrote:
On 2/28/07, Marcus Denker denker@iam.unibe.ch wrote:
"The goal of this Project is to develop a server based service that has the complete history of Squeak available. This then can be queried by different tools, from the normal Squeak history facilities to new analysis tools. As part of the project, one such analysis tools should be developed for analyszing code ownership for helping with the re-licensing of Squeak."
I'm hoping to have some students do part of this project by May. In particular, they will have a complete history of Squeak on a server that can be accessed by the Squeak history facilities. This will allow us to make a release with an empty changes file without losing any history. People who do not want to be connected to the internet can get their own copy of the history database. I was not planning on building any new analysis tools, but it should be easy to build them.
Very nice! So we don't need this as a project for SoC.
Marcus
soc@lists.squeakfoundation.org