Closed
Bug 886456
Opened 13 years ago
Closed 12 years ago
Define process for locating and viewing good Makes (1) for Staff and (2) Public
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: replica.young, Unassigned)
Details
No description provided.
Comment 1•13 years ago
|
||
* Rebeccah: for the public part, we're working on documenting this as a blog post on Webmaker blog here:
https://bugzilla.mozilla.org/show_bug.cgi?id=884862
Comment 2•13 years ago
|
||
* Still useful to document the "(1) for staff" piece.
| Reporter | ||
Comment 3•13 years ago
|
||
Matt - we're hacking the backend tool by which Makes are visible in this bug.
| Reporter | ||
Comment 4•13 years ago
|
||
Backend Makes Filter feature requests:
blockers?
- connect with Michelle Thorne re: intern availability
Features needed:
- Provide access to interns + Erika D + Rebeccah + (Jacob already has one)
- Add filter by more than one option (eg. user name + date published)
- Thumbnail view would be useful
- Option to save Viewed Makes to 'accepted' zone/page/area so that content team can use list for comms
Comment 5•13 years ago
|
||
I've distilled and added some notes to this etherpad here - https://webmakers.etherpad.mozilla.org/MakeEditor for our needs to have the Make Editor be a functional tool for surfacing makes.
Going to go over this with Cade & Brett on a call this week, likely Thursday
| Reporter | ||
Comment 6•12 years ago
|
||
Can we close this bug? Or is it still needing refinement/action?
Comment 7•12 years ago
|
||
There hasn't been any activity in 2 months, so I feel like this is safe to close for now. Feel free to re-open or re-file if features has been missed!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 8•12 years ago
|
||
also @Rebeccah: I just saw "likes" demoed in today's product demo session. So that combined with the better tagging we just shipped should go a long way towards this.
Look for more soon.
| Reporter | ||
Comment 9•12 years ago
|
||
Nice. Would love for these short report-outs on product to regularly play out either in internal email or weekly calls.
It's super helpful for planning general landmarks in long and short arc campaigns (eg. long arc over the year under "Product Updates: What's new with Webmaker.org" down to "Social Making Campaign: Battle of Mixes" where we rely on certain features being clearly explained, etc.
Even better? Dear Diary for Webmaker.org:
"Tuesday Sept 10th: Dear Diary - today I feel really wonderful since it's easy for people to LIKE all my content now! Our Sign-in buttons make more sense, and Amira can see all the Events in a simpler view! Hooray! Also, I now speak Russian. Next week - they'll be taking away all my Python, once and for all!"
:)
Comment 10•12 years ago
|
||
There are weekly demos every Friday at 4pm ET. Can you come to those?
Comment 11•12 years ago
|
||
The weekly demos are good. We've also talked about having a webmaker.org/status page to give an easy rundown on what's new and what's next.
Would love to move on that
| Reporter | ||
Comment 12•12 years ago
|
||
I'd be happy to attend, and yes, I'll eventually be finding ways to share out the new things on the social side - but I agree with Jacob that public facing 'on-site' stuff would be worthwhile for those folks who don't care to learn about this stuff from social.
The blog might be a notion - but that would require an 'interpreter' to frame it for a more consumer audience.
There's a developer/technical specs audience out there too for this info in it's original state - don't know if that is something the @popcornjs folks could to plug into if it was a pubic facing specs update as well?
You need to log in
before you can comment on or make changes to this bug.
Description
•