Page Comparison

Announcements and discussion

Maggie

How to publicize new Ready for Community Developer status?

• How and when?

Dev Pri survey

Old business

Maggie and

Reviewing Ready for Development tickets: Bug kanban board (58 tickets total)

Each person has been assigned 8 tickets from the bug kanban board that currently have the Ready for Dev status. Please review the tickets assigned to you and make recommendations on:

• Candidate for Ready for Community Developer? YES/NO (primary concern)

• Whether the ticket is still relevant, its priority ranking, and the tags (secondary concerns)

We’ll discuss candidates for Ready for Community Developer as a group, and can also address any secondary concerns that arise during the ticket reviews.

Patrick

1. ANW-138

   1. y/n

   2. other concerns?

2. ANW-137

3. ANW-148

4. ANW-164

5. ANW-179

6. ANW-172

7. ANW-162

8. ANW-160
   

Terra

1. ANW-157

2. ANW-156

3. ANW-152

4. ANW-145

5. ANW-149

6. ANW-170

7. ANW-365

8. ANW-369

Alicia

1. ANW-194

2. ANW-205

3. ANW-206

4. ANW-347

5. ANW-234

6. ANW-251

7. ANW-262

8. ANW-261

William

1. ANW-249

2. ANW-276

3. ANW-275

4. ANW-288

5. ANW-345

6. ANW-292

7. ANW-316

8. ANW-308

Julia

1. ANW-323

2. ANW-604

3. ANW-425

4. ANW-635

5. ANW-652

6. ANW-664

7. ANW-665

8. ANW-691

Edgar

1. ANW-694

2. ANW-705

3. ANW-724

4. ANW-736

5. ANW-739

6. ANW-750

7. ANW-751

8. ANW-752

Maggie

1. ANW-757

2. ANW-758

3. ANW-760

4. ANW-782

5. ANW-783

6. ANW-784

7. ANW-787

8. ANW-792

9. ANW-823

10. ANW-880

Next meeting

All

Did this method work well? If so, we’ll do the same for Ready for Dev status tickets in the feature requests kanban board in our June meeting.