Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Veronica Andreo]

Ciao Lu,

2017-09-28 7:53 GMT+02:00 Luca Delucchi :

> On 25 September 2017 at 18:25, Veronica Andreo 
> wrote:
> > Ciao Lu,
> >
>
> Ciao Vero,
>
> > I signed in and will attend the meeting tonight through IRC chat. I had
> some
> > ideas in mind:
> >
>
> thanks to follow it
>
> > - Design the t-shirt for the next code-sprint
> > - Add examples to xx manual pages
> > - Make a promo video for GRASS GIS
> > - Make new tutorial videos for GRASS GIS
> > - Enhance the visual index
> > - Make screenshots for release pages (eg.
> > https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
> > - Create screenshot for the next 74 release announcement
> >
> > what do you think? too simple? too complicated?
> >
>
> +1, could you start a wiki page (on GRASS wiki) with ideas please?
>

Done :)

Draft page here: https://grasswiki.osgeo.org/wiki/GRASS_GCI_Ideas_2017

more info and details to be added.

Importantly, what we need the most now is more mentors. Then, we need to
transform ideas into tasks. Note that translations in transifex are not
allowed as tasks.

cheers,
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Luca Delucchi]

On 25 September 2017 at 18:25, Veronica Andreo  wrote:
> Ciao Lu,
>

Ciao Vero,

> I signed in and will attend the meeting tonight through IRC chat. I had some
> ideas in mind:
>

thanks to follow it

> - Design the t-shirt for the next code-sprint
> - Add examples to xx manual pages
> - Make a promo video for GRASS GIS
> - Make new tutorial videos for GRASS GIS
> - Enhance the visual index
> - Make screenshots for release pages (eg.
> https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
> - Create screenshot for the next 74 release announcement
>
> what do you think? too simple? too complicated?
>

+1, could you start a wiki page (on GRASS wiki) with ideas please?

> cheers,
> Vero
>



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Margherita Di Leo]

Hi,

On Mon, Sep 25, 2017 at 9:47 PM, Helmut Kudrnovsky  wrote:

> Veronica Andreo wrote
> > Ciao Lu,
> >
> > I signed in and will attend the meeting tonight through IRC chat. I had
> > some ideas in mind:
> >
> > - Design the t-shirt for the next code-sprint
> > - Add examples to xx manual pages
> > - Make a promo video for GRASS GIS
> > - Make new tutorial videos for GRASS GIS
> > - Enhance the visual index
> > - Make screenshots for release pages (eg.
> > https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
> > - Create screenshot for the next 74 release announcement
> >
> > what do you think? too simple? too complicated?
>
> looks good to me. it should be tasks doable in just a couple of hours.
>

Actually (3-5 hours)
https://developers.google.com/open-source/gci/how-it-works
All the tasks you listed are just perfect, only we will need a large mentor
capacity, other orgs refer that hundreds of students participate, and even
if tasks review only takes 15 minutes, it needs a large pool of people to
review.

>
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Margherita Di Leo
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Helmut Kudrnovsky]

Veronica Andreo wrote
> Ciao Lu,
> 
> I signed in and will attend the meeting tonight through IRC chat. I had
> some ideas in mind:
> 
> - Design the t-shirt for the next code-sprint
> - Add examples to xx manual pages
> - Make a promo video for GRASS GIS
> - Make new tutorial videos for GRASS GIS
> - Enhance the visual index
> - Make screenshots for release pages (eg.
> https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
> - Create screenshot for the next 74 release announcement
> 
> what do you think? too simple? too complicated?

looks good to me. it should be tasks doable in just a couple of hours.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Moritz Lennert]

Hi Vero,

On 25/09/17 18:25, Veronica Andreo wrote:

Ciao Lu,

I signed in and will attend the meeting tonight through IRC chat. I had 
some ideas in mind:


- Design the t-shirt for the next code-sprint
- Add examples to xx manual pages
- Make a promo video for GRASS GIS
- Make new tutorial videos for GRASS GIS
- Enhance the visual index
- Make screenshots for release pages (eg. 
https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)

- Create screenshot for the next 74 release announcement

>

what do you think? too simple? too complicated?


I don't know how much time they have, but this list seems large enough 
to offer something for everyone. For coders, I think we should add the 
creation of tests, as Luca mentioned.


Thanks for following up on this !

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Veronica Andreo]

Ciao Lu,

I signed in and will attend the meeting tonight through IRC chat. I had
some ideas in mind:

- Design the t-shirt for the next code-sprint
- Add examples to xx manual pages
- Make a promo video for GRASS GIS
- Make new tutorial videos for GRASS GIS
- Enhance the visual index
- Make screenshots for release pages (eg.
https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
- Create screenshot for the next 74 release announcement

what do you think? too simple? too complicated?

cheers,
Vero


2017-09-25 18:12 GMT+02:00 Luca Delucchi :

> Someone interested?
>
> could be useful for testing (and maybe test case),  docs and translation...
>
>
> -- Forwarded message --
> From: Margherita Di Leo 
> Date: 19 September 2017 at 13:48
> Subject: [SoC] Google Code In (GCI) 2017 just announced! And we want
> to participate
> To: OSGeo Discussions ,
> geofor...@lists.osgeo.org, OSGeo-SoC 
> Cc: "gsoc-adminosgeo.org" , atd.schub...@gmail.com
>
>
> Dear Community,
>
> great news! Google Code-in has just been officially announced [1] and
> we are excited to apply for the first time as mentoring organization!
> Google Code In is a program addressed to students aged 13 to 17.
>
> As always, we need your help! We need mentors.
> Mentors for Google code in are not necessarily top developers (they
> are also needed, but not only). Also educators, advocates, researchers
> are much needed, people that normally take care of documentation and
> preparation of educational material, that give presentations, take
> care of web site or wiki etc.
>
> In fact, the tasks for google code in are supposed to take 3 to 5
> hours for students to complete, and entail:
> * coding
> * documentation / training
> * outreach / research
> * quality assurance
> * user interface
>
> See examples here [2].
>
> The idea is to individuate suitable tasks and submit them in the bug
> tracker with a special keyword like "beginner" or something TBD. In
> this way, students can easily find and claim the task they're
> interested in.
>
> Note that the whole "how to" is to be discussed yet, for the moment,
> let's try to create a critical mass of interested volunteers.
>
> Here [3] I created a wiki page with relevant info, instructions,
> timeline etc. Kindly take a look and if you are willing to
> participate, please write an email to gsoc-admin AT osgeo.org, we will
> send you a form to fill with your data. Next step: in less than one
> week from now we'll have the first kickoff meeting on IRC in the
> channel #osgeo-gsoc at Freenode. Everyone that will have filled the
> form will be informed about exact date and time.
>
> Please, do participate, and bring your questions, your ideas and your
> energy with you. We don't have all the answers, but will try to figure
> things out together.. We believe that engaging the young generation
> will bring in OSGeo a breeze of innovation and fresh energy. Don't
> miss the opportunity to be part of the change!
>
> Cheers!!
>
>
> [1] https://opensource.googleblog.com/2017/09/announcing-google-
> code-in-2017.html
> [2] https://developers.google.com/open-source/gci/resources/example-tasks
> [3] https://wiki.osgeo.org/wiki/Google_Code_In_2017
>
> --
> Margherita Di Leo
>
> ___
> SoC mailing list
> s...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/soc
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Luca Delucchi]

Someone interested?

could be useful for testing (and maybe test case),  docs and translation...


-- Forwarded message --
From: Margherita Di Leo 
Date: 19 September 2017 at 13:48
Subject: [SoC] Google Code In (GCI) 2017 just announced! And we want
to participate
To: OSGeo Discussions ,
geofor...@lists.osgeo.org, OSGeo-SoC 
Cc: "gsoc-adminosgeo.org" , atd.schub...@gmail.com


Dear Community,

great news! Google Code-in has just been officially announced [1] and
we are excited to apply for the first time as mentoring organization!
Google Code In is a program addressed to students aged 13 to 17.

As always, we need your help! We need mentors.
Mentors for Google code in are not necessarily top developers (they
are also needed, but not only). Also educators, advocates, researchers
are much needed, people that normally take care of documentation and
preparation of educational material, that give presentations, take
care of web site or wiki etc.

In fact, the tasks for google code in are supposed to take 3 to 5
hours for students to complete, and entail:
* coding
* documentation / training
* outreach / research
* quality assurance
* user interface

See examples here [2].

The idea is to individuate suitable tasks and submit them in the bug
tracker with a special keyword like "beginner" or something TBD. In
this way, students can easily find and claim the task they're
interested in.

Note that the whole "how to" is to be discussed yet, for the moment,
let's try to create a critical mass of interested volunteers.

Here [3] I created a wiki page with relevant info, instructions,
timeline etc. Kindly take a look and if you are willing to
participate, please write an email to gsoc-admin AT osgeo.org, we will
send you a form to fill with your data. Next step: in less than one
week from now we'll have the first kickoff meeting on IRC in the
channel #osgeo-gsoc at Freenode. Everyone that will have filled the
form will be informed about exact date and time.

Please, do participate, and bring your questions, your ideas and your
energy with you. We don't have all the answers, but will try to figure
things out together.. We believe that engaging the young generation
will bring in OSGeo a breeze of innovation and fresh energy. Don't
miss the opportunity to be part of the change!

Cheers!!


[1] 
https://opensource.googleblog.com/2017/09/announcing-google-code-in-2017.html
[2] https://developers.google.com/open-source/gci/resources/example-tasks
[3] https://wiki.osgeo.org/wiki/Google_Code_In_2017

--
Margherita Di Leo

___
SoC mailing list
s...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/soc


-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev