Update Activity Types and Product Groups

[SmokyBob]

Activity Type

Checking on the Tracking form the GDE Tracking app is missing the activity group GDE Program recruitment, used to track GDE referrals and Interviews.

It's unlikely that GDEs are going to post on Google Plus of this activity, but to keep things consistent I propose the following Tags and descriptions: Tag: #referral Description: You have referred an individual to apply for the GDE program and they were accepted! Woo-hoo! Congrats all around, and also, that's a valued (and valuable) GDE activity

Tag: #interview Description: Interview a candidate to test the technical knowledge of the purposed technology, the community skills and the overall GDEiness of the candidate.

Tag: #development Description: Development on the GDE Tracking App

This 3 Type of activities will be in the #gdeprogram Activity Group

Activity Metadata: activity_group: #gdeprogram title: to store the GDE candidate's name description: to store the GDE candidate's email type: #referral, #interview,#development

Product Group

Seems like the Product Group glass is now Wearables as you can see looking at the list of GDEs. This is causing a minor problem as we are missing the badge image for wearables.

[SmokyBob]

Updated issues with the infos from the discussion in the forum threads

[Scarygami]

I still think we need a #general product group.

Examples:

• Our work on the tracking app can't be really associated with one of the product groups.
• There are several APIs that don't fall into one of the current GDE areas. (but those could maybe be filed under #googleappsapis)
• Organizing GDG events (e.g. I'm heavily involved in devfest orga) which usually aren't product-specific either.

[SmokyBob]

@Scarygami I agree, we should explain it again in tomorrow's call

[patt0]

has it been two weeks already?

Patrick Martinent

On Mon, Aug 25, 2014 at 6:52 PM, Mauro Solcia notifications@github.com wrote:

@Scarygami https://github.com/Scarygami I agree, we should explain it again in tomorrow's call

— Reply to this email directly or view it on GitHub https://github.com/maiera/gde-app/issues/61#issuecomment-53262578.

[Scarygami]

Will also have to discuss how/what to report for #development Each issue fixed/PR separately? Or just a "Hey I worked on the app this month".

[patt0]

If we can get data from API I am in favour of monthly automatic activity extraction.

This can a modus operandi for all API connected activity sources On 25 Aug 2014 20:23, "Gerwin Sturm" notifications@github.com wrote:

Will also have to discuss how/what to report for #development Each issue fixed/PR separately? Or just a "Hey I worked on the app this month".

— Reply to this email directly or view it on GitHub https://github.com/maiera/gde-app/issues/61#issuecomment-53274110.

[Scarygami]

Yup, that should work: https://api.github.com/repos/maiera/gde-app/commits?sha=feature/appengine&page=1 https://api.github.com/repos/maiera/gde-app/commits?sha=feature/material_design&page=1

[Scarygami]

As discussed on Tuesday, we still need to add the "non-product-specific" product group.

Suggestion:

{
   "id": "google",
   "url": "https://developers.google.com/",
   "tag": "#google",
   "description": "Google APIs and SDKs"
}

(not entirely sure what a good description would be)

Also noticed some stray ' in the descriptions, like Google Maps APIs'

[patt0]

Those are my fault :( On 28 Aug 2014 15:01, "Gerwin Sturm" notifications@github.com wrote:

As discussed on Tuesday, we still need to add the "non-product-specific" product group.

Suggestion:

{ "id": "google", "url": "https://developers.google.com/", "tag": "#google", "description": "Google APIs and SDKs", }

(not entirely sure what a good description would be)

Also noticed some stray ' in the descriptions, like Google Maps APIs'

— Reply to this email directly or view it on GitHub https://github.com/maiera/gde-app/issues/61#issuecomment-53694963.

[SmokyBob]

Alex suggested #googleDev as pg; i think fits nicely with the description and URL above.

[Scarygami]

Sure, #googleDev works as well, I just find shorter tags nicer, and 'Dev' is implied with all the other tags as well, e.g. no #youtubeDev

[SmokyBob]

googleDev because #google is a term too broad and used in while referring to Google in general (seen it in rumors about the purchase of Twitch)...

What about #API_SDK? Short and more to the point.

[Scarygami]

Okay, let's just stick with #googleDev then :)

[SmokyBob]

googleDev PG Added.