On Wed, Feb 11, 2015 at 10:13 PM, Serge Stinckwich < serge.stinckw...@gmail.com> wrote:
> On Wed, Feb 11, 2015 at 3:07 PM, Martin Bähr > <mba...@email.archlab.tuwien.ac.at> wrote: > > Excerpts from Serge Stinckwich's message of 2015-02-11 10:02:21 +0100: > >> with Uko, we are considering submitting the Pharo project as a > >> mentoring organization for GSOC 2015: > >> > >> We will need your help in order to find ideas of projects. > > > > Is there any effort make a joint application under esug or some other > umbrella? > > We are under the umbrella of the Pharo Consortium. > Now google say... "Umbrella organizations get more slots. If an organization is acting as an umbrella for other projects, chances are we'll allocate more students to you simply because there's a great deal of different types of work to be done, and we're hoping our students will end up with something that appeals to them among this wide offering." [1] The Pharo Consortium might conceivably be considered an umbrella organisation, if a reasonable amount of selected projects relate to applications built on top of Pharo and not "just" improvements in the Pharo release. e.g. SciSmalltalk, PhaROS, Phratch. I guess that is a balance to be determined later. Google also provide some tips [2] for project topics : * Low-hanging fruit: These projects require minimal familiarity with the codebase and basic technical knowledge. They are relatively short, with clear goals. * Risky/Exploratory: These projects push the scope boundaries of your development effort. They might require expertise in an area not covered by your current development team. They might take advantage of a new technology. There is a reasonable chance that the project might be less successful, but the potential rewards make it worth the attempt. * Fun/Peripheral: These projects might not be related to the current core development focus, but create new innovations and new perspective for your project. * Core development: These projects derive from the ongoing work from the core of your development team. The list of features and bugs is never-ending, and help is always welcome. * Infrastructure/Automation: These projects are the code that your organization uses to get its development work done; for example, projects that improve the automation of releases, regression tests and automated builds. This is a category in which a GSoC student can be really helpful, doing work that the development team has been putting off while they focus on core development. * Don't Be That Guy!!! Don't propose projects that neither you nor anyone else wants to mentor. btw, Are all of these topics [http://topics.pharo.org/] still current (maybe some are too big for summer)? btw2, Where is our ideas page going to be hosted? [1] http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/studentallocations [2] http://en.flossmanuals.net/GSoCMentoring/defining-a-project/ cheers -ben > > > there are a few projects on labs.fossasia.org that might fit: > > > > Create a file editor and asset manager solution with smalltalk > > Create a smalltalk application for offline text search > > emulate a PostgreSQL server in Smalltalk > > Smalltalk SQL Parser & Evaluator > > > > i also discussed with craig the idea of doing something with his context > work on pharo. > > essentially i'd like to use context as a tool to remote manage images. > > a gsoc project could be to work out how to set up context for that > usecase > > (while helping to make sure context works with pharo) > > You are from FOSSASIA ? Didn't know you have some interests in Smalltalk > ;-) > If some of your projects are related to Pharo, we could post also your > projects on our lists. > > We will send the link to list of ideas in a few hours. > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >
