1151008 - Updating Contributor Stories

Status: RESOLVED DUPLICATE of bug 1189120

(www.mozilla.org :: General, defect)

Description

[shine [:shine]]

https://mozilla.org/contribute/stories/ have been left un-attended after the initial introduction. It was a good initiative by the CBT under Larissa, but then got obsolete and un-updated after the CBT got disbanded and the team was re-assigned elsewhere.

The initiative was a good one to bring out the cool stories of the mozillians all over the world. It would be good if someone (preferably the participation team) to take this initiative over and continue telling the stories of the many great mozillians all over the world.

As I see it, this can be implemented in 2 ways :

1. We have monthly recognitions at different levels (contributor, reps, FSA, etc) within mozilla, we could use these people's stories to update the stories on a monthly basis.

2. We could identify active volunteers who haven't been recognized in any of the above mentioned categories and tell their stories. This would give more people a chance to tell their stories. But identifying such people would be difficult, so hence, we could update the stories on a quarterly basis if this option is chosen.

If you have a better idea, go ahead and comment. Let's have an open discussion.

Comment 1

[Jennifer Bertsch [:jbertsch]]

Hi-

Thanks for filing.  The team that built this page with Larissa is in fact very interested in continuing to maintain it, we just aren't able to prioritize this work at this time.

It is our intention to work on this page again in the future.  I personally don't think the page is "obsolete".

Best,
Jennifer

Comment 2

[shine [:shine]]

Well, not prioritized, not in active development almost means 'obsolete'. And I feel that if it is not on your priority list, at least updating the least once a month (the first option I suggested) would be very easy, since we're posting on the blog anyways, taking a few more steps to publish it to this page would not be that hard. 

That said, it isn't hard to update / maintain 4 names and their stories on an interval basis. Give me that job and I'd happily do it. It doesn't even need more than 2 people to get that done - I mean the updating part. Identifying the people to feature on that page would be difficult, but if the participation team is participating with communities enough, that wouldn't be hard a job either. That's why I suggested to let the participation team handle it from where the CBT left off.

I feel that this does not need a team to maintain it. The page is well matured enough to stand on its own and requires only the updating of the stories which is a one-man's job (maybe a couple more to support in case of emergencies).

Comment 3

[Craig Cook (:craigcook)]

The original plan was to have 7 to 10 stories but we were only able to get 4 completed for the initial launch and we just haven't had time or resources to add more since then, especially with all the changes on the community building end. If we can put together a batch of additional stories I'd love to get them added in the very near future, but we still don't want more than 10 (it allows for 1 'selected' and 9 others; more than that makes for a crowded page). 

Aiming for monthly updates is more complicated than you might think. These pages are localized in numerous languages so it's not just a case of adding new content on a regular basis, it also entails *translating* that new content and that takes time by a lot of volunteer localizers. Adding a new one every month would put the pages in a perpetual state of "not fully translated" which leads to a lot of tricky shuffling of code to show different content in different locales. It's much better to do this sort of thing in big batches that change less frequently.

I propose using this bug as a springboard for collecting 3-6 more Mozillian stories to add to the site in the coming weeks. We should make sure it's an appropriately diverse group of people from around the world (not skewed too heavily to one region), who contribute in different areas (so we don't skew too heavily to just code contributors, or just campus reps, etc).

Comment 4

[shine [:shine]]

(In reply to Craig Cook (:craigcook) from comment #3)
> Aiming for monthly updates is more complicated than you might think. These
> pages are localized in numerous languages so it's not just a case of adding
> new content on a regular basis, it also entails *translating* that new
> content and that takes time by a lot of volunteer localizers. Adding a new
> one every month would put the pages in a perpetual state of "not fully
> translated" which leads to a lot of tricky shuffling of code to show
> different content in different locales. It's much better to do this sort of
> thing in big batches that change less frequently.

I agree. I didn't consider the localization factor before commenting. I guess localization is a very large factor that hinders updating frequently. But then we can use the second suggestion, or somthing along those lines updating is less frequently, maybe quarterly or half-yearly. I suggested using the first suggestion because I thought this wasn't going to be updated at all because it was not "prioritized".

(In reply to Craig Cook (:craigcook) from comment #3)
we still don't want more than
> 10 (it allows for 1 'selected' and 9 others; more than that makes for a
> crowded page).
I feel even 10 would be too crowded. According to me 4-6 is the most ideal state.

(In reply to Craig Cook (:craigcook) from comment #3)
> I propose using this bug as a springboard for collecting 3-6 more Mozillian
> stories to add to the site in the coming weeks. We should make sure it's an
> appropriately diverse group of people from around the world (not skewed too
> heavily to one region), who contribute in different areas (so we don't skew
> too heavily to just code contributors, or just campus reps, etc).
Can't the participation team take that up? 

Another suggestion regarding localization, we can have a queue of volunteer stories to be updated to the page. We could use the Contributor / Rep / FSA of the Month too for this. So, as and when a new story pops up, the localization volunteers can get localizing and when it has been completely localized, we can push it to production. So, that way, we could update more frequently too.