Closed Bug 752698 Opened 12 years ago Closed 12 years ago

QA Needed on new webmaker events platform

Categories

(Testing Graveyard :: WebQA, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bsimon, Assigned: mozwebqa)

References

(Depends on 1 open bug, )

Details

We're building is an events platform for our webmaker initiative,
to allow users to:

a) create an event, collect rsvps & communicate with attendees
b) list a pre-existing webmaking event in our map/calendar
c) discover and RSVP for events created by others

Different pieces of this are in different stages of completion, which is
why we have not yet filed a bug. QA probably can't begin til later this week, but launch is currently scheduled for May 15th.

Existing documentation for where we are so far is below. Will chime in more on this bug as there's progress.

Privacy/Legal bug (including links to mock-ups & data safety
documentation): https://bugzilla.mozilla.org/show_bug.cgi?id=749296

Security bug: https://bugzilla.mozilla.org/show_bug.cgi?id=735075

Current in-progress site: https://make-dev.mozillalabs.com/en-US/events/
Severity: normal → major
THere's some more info and context on the wiki here: https://wiki.mozilla.org/Webmakers/Event_Platform
Assignee: nobody → mozwebqa
OS: Mac OS X → All
Hardware: x86 → All
Thanks, Ben; a few questions:

1) Where we do file bugs in Bugzilla?
2) Which milestone should we use?
3) Who should we cc by default on the bugs?
4) Who should we assign bugs to?
5) Whom from IT set up the site and we can contact?
6) What critical features are "stop-ship" blockers?

Any other details as you begin to answer these would be truly beneficial as we do our best to turn-around testing.
Not sure about all of these (I'd think Ross or Ryan are best-suited to answer the others), but:

 
> 1) Where we do file bugs in Bugzilla?

I don't think our webmaker site exists yet on its own; probably best bet for now is under websites --> donate.mozilla.org

> 2) Which milestone should we use?

I'm not sure. I don't believe it's on the normal mozilla.org release timeline. Ross, thoughts?

> 3) Who should we cc by default on the bugs?

Me, Ross Bruniges, Ryan Merkley, Michelle Thorne, and Erin Knight (the 5 who are on this bug).

> 4) Who should we assign bugs to?

Me, and I can reassign as needed.

> 5) Whom from IT set up the site and we can contact?

Ross Bruniges has worked a bit with David Ascher and Gozer to get the site up.

> 6) What critical features are "stop-ship" blockers?

The 3 mission critical functions at this stage are:
-Create a new event
-Add an existing event (so, get an eventbrite/lanyrd/etc event that exists already into our calendar)
-Find and RSVP for events
> 
> Any other details as you begin to answer these would be truly beneficial as
> we do our best to turn-around testing.

Let me know if there are any functions or uses that would be helpful to walk through.
OS: All → Mac OS X
Hardware: All → x86
Depends on: 753151
OS: Mac OS X → All
Hardware: x86 → All
7) Are any of you available in IRC?  If so, which channel(s), and can we commit to hanging out in #webmaker, for faster/real-time communication?
(In reply to Stephen Donner [:stephend] from comment #4)
> 7) Are any of you available in IRC?  If so, which channel(s), and can we
> commit to hanging out in #webmaker, for faster/real-time communication?

When online, we're all in #foundation, which would be fine to have this convo as part of it.

One factor worth noting is that Ross, who is leading the dev on this, is UK-based, so is normally only around for a couple of west-coast working hours.
Depends on: 753480
Depends on: 753486
Depends on: 753489
Depends on: 753491
Depends on: 753500
Depends on: 753509
Depends on: 753514
Depends on: 753519
Depends on: 753537
Depends on: 753538
Depends on: 753591
Depends on: 753593
Depends on: 753676
Depends on: 753977
Depends on: 754354
Depends on: 754367
Depends on: 754688
Depends on: 754948
Depends on: 753506
Ben, when is this planned to ship?  What are the criteria for launch?  Thanks.
We're hoping to go live today as a soft-launch, though Ross can chime in if that's still plausible. Remaining blockers that I know of are:

--Getting all the legal docs & language up on the site (we got final text yesterday evening) & updating privacy policy checkboxes
--Getting a frontpage of webmaker.org up

Of the three remaining bugs on here now, the posters are done but just need to be hooked up, it looks like the "auto-sent to main donate page" is actually fine, and I think the integer overflow is likely to be a won't fix.

Are there any other issues outstanding from your all's perspective?

Thanks so much for chewing through this so thoroughly -- it was really a sight to see.
Heya guys, 

So yeah as Ben says there are a few little things to do.

Ben - from my understanding the frontpage of webmaker.org in the state that we're looking to launch it is there. At the moment it redirects to events because that is all the site actually contains. This will change when we add in tools and projects in the future.

I've done the legal pages - looking to upload them to stage within the hour, hopefully the same for the posters if Chris can get us the stuff in time.

And I must second Ben's thanks - thank you all for being so thorough - hope it wasn't too painful a process for you guys.
(In reply to Ben Simon from comment #7)
> We're hoping to go live today as a soft-launch, though Ross can chime in if
> that's still plausible. Remaining blockers that I know of are:
> 
> --Getting all the legal docs & language up on the site (we got final text
> yesterday evening) & updating privacy policy checkboxes
> --Getting a frontpage of webmaker.org up
> 
> Of the three remaining bugs on here now, the posters are done but just need
> to be hooked up, it looks like the "auto-sent to main donate page" is
> actually fine, and I think the integer overflow is likely to be a won't fix.
> 
> Are there any other issues outstanding from your all's perspective?

From ours, no; we want to reiterate that we're not the gatekeepers here, just advisors of what we see, quality-wise.
 
> Thanks so much for chewing through this so thoroughly -- it was really a
> sight to see.

We're happy to help when we can!  In the future, we'd prefer more development-complete lead time, but it looks like it worked out :-)

Cheers.
> 
> We're happy to help when we can!  In the future, we'd prefer more
> development-complete lead time, but it looks like it worked out :-)
> 
Me too :)
We shipped, and my team is done, here; cheers!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You guys did a great job!

Thanks very much, looking forward to working with you again soon.
Status: RESOLVED → VERIFIED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.