Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Kuma Testing and Feedback

11 views
Skip to first unread message

John Karahalis

unread,
Aug 8, 2011, 10:59:19 PM8/8/11
to devengage, dev...@lists.mozilla.org, Stephen Donner
Hey everyone,

Recently, there have been discussions about the difficulty of staying
up-to-date with Kuma, testing it, and providing feedback. I believe
that feedback and transparency are critical (these are two cornerstones
of Scrum), so I would like to propose one possible solution. Nothing is
set in stone, so I would love to hear your feedback (see what I mean?).

*What I will do*

- After each milestone, I will send the Developer Engagement team a
link to the updated software and a list of important updates.
- In each of these emails, I will include a link to an EtherPad that
you can use to provide feedback.
- A few days after sending this email, I will meet with the development
team to plan the next few weeks of work. I will ensure they take your
feedback into consideration while doing so.

*What you can do*

- If you are interested, you can test the newest Kuma features as soon
as you receive my email. If you are not interested, you can disregard
the email.
- If you have any feedback (from "This is great!" to "This is worse
than Clippy!"), you can share those thoughts in the EtherPad I
provide.
- Feel free to share thoughts even after our planning meeting, but
please keep in mind that we will not be able to take a look at them
until the planning meeting after that.
- If you are interested in what features will be landing soon, see the
MDN Milestones page (https://wiki.mozilla.org/MDN/Milestones).

*A few notes*

- All testing will need to happen on a rolling-updates server, so you
may see some features that were added only minutes or hours prior.
It would be nice to provide a version of the site "frozen" at each
milestone, but this would be difficult technically.
- If this workflow is going well after a few weeks, we can consider
opening it up to core MDN contributors and later the wider MDN
community.

As I said, these are all just ideas. Any thoughts?

--
John Karahalis
Developer Engagement Intern
Mozilla Corporation
Public Key: 0x5ED80C4F

Eric Shepherd

unread,
Aug 9, 2011, 8:54:14 AM8/9/11
to John Karahalis, dev...@lists.mozilla.org, devengage, Stephen Donner
John Karahalis wrote:
> As I said, these are all just ideas. Any thoughts?

Sounds fabulous to me.

--
Eric Shepherd
Developer Documentation Lead
Mozilla
Blog: http://www.bitstampede.com/

Janet Swisher

unread,
Aug 23, 2011, 7:51:11 PM8/23/11
to Eric Shepherd, dev...@lists.mozilla.org, Stephen Donner, John Karahalis
On 8/9/11 7:54 AM, Eric Shepherd wrote:
> John Karahalis wrote:
>> As I said, these are all just ideas. Any thoughts?
>
> Sounds fabulous to me.
>
Belatedly, this sounds great to me too.

Jay Patel

unread,
Aug 23, 2011, 8:26:07 PM8/23/11
to Janet Swisher, dev...@lists.mozilla.org, Eric Shepherd, Stephen Donner
We definitely are working towards providing more high-level updates on
new features we implement each release... but with John gone for the
foreseeable future, I will see what we can do starting with 1.1 to get
this process started.

I like etherpads, but I think we may be better off using uservoice for
specific ideas and feedback... if not bugzilla itself so we can track
issues and new ideas in one place with our other stories. That will
make it easier on the dev team to track things and integrate them into
our work flow.

I'll discuss this with the team at our MDN dev meeting tomorrow and kick
something off as we get closer to the 1.1 release in September.

The only issue right now is that we still don't have the ideal staging
servers setup yet... but we have been discussing and they have been
planned for the near future. More on that later.

Thanks for the validation that something like this will help you stay up
on Kuma development and help us test things as we get them out.

- Jay

> ------------------------------------------------------------------------
>
> Janet Swisher <mailto:jswi...@mozilla.com>
> August 23, 2011 4:51 PM


>
>
>
> Belatedly, this sounds great to me too.
>
>
>

> _______________________________________________
> dev-mdn mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdn
> ------------------------------------------------------------------------
>
> Eric Shepherd <mailto:eshe...@mozilla.com>
> August 9, 2011 5:54 AM
>
>
>
>
> Sounds fabulous to me.
>
> ------------------------------------------------------------------------
>
> John Karahalis <mailto:jkara...@mozilla.com>
> August 8, 2011 7:59 PM

Eric Shepherd

unread,
Aug 23, 2011, 8:31:03 PM8/23/11
to Jay Patel, dev...@lists.mozilla.org, Janet Swisher, Stephen Donner
Jay Patel wrote:
> Thanks for the validation that something like this will help you stay up
> on Kuma development and help us test things as we get them out.

This is especially true in the world of the rapid release train system.
I'm barely staying afloat (in fact, I'm teetering on the brink of total
brain failure at the moment), so anything to help filter the incoming
data to what I need to know is always a big help. :)

--
Eric Shepherd
Developer Documentation Lead

Mozilla Corporation
Blog: http://www.bitstampede.com/

John Karahalis

unread,
Aug 27, 2011, 10:28:31 PM8/27/11
to dev...@lists.mozilla.org
Submitting feedback via Bugzilla directly sounds good to me.

I was planning to use EtherPad to make things as easy as possible for
our testers, but I agree that Bugzilla might be a better balance.

On 08/23/2011 08:26 PM, Jay Patel wrote:
> We definitely are working towards providing more high-level updates on
> new features we implement each release... but with John gone for the
> foreseeable future, I will see what we can do starting with 1.1 to get
> this process started.
>
> I like etherpads, but I think we may be better off using uservoice for
> specific ideas and feedback... if not bugzilla itself so we can track
> issues and new ideas in one place with our other stories. That will
> make it easier on the dev team to track things and integrate them into
> our work flow.
>
> I'll discuss this with the team at our MDN dev meeting tomorrow and
> kick something off as we get closer to the 1.1 release in September.
>
> The only issue right now is that we still don't have the ideal staging
> servers setup yet... but we have been discussing and they have been
> planned for the near future. More on that later.
>

> Thanks for the validation that something like this will help you stay
> up on Kuma development and help us test things as we get them out.
>

0 new messages