search

jquery / 2012-dev-summit

Information regarding the 2012 Developer Summit in DC
14 stars 14 forks source link

Use Issues For Summit Todos? #1

Closed ajpiano closed 12 years ago

ajpiano commented 12 years ago

Should we use GitHub issues to track the to-dos on a per-table basis? Even if the issues are just links to issues in other repos, I think it is a neater way of tracking what we want to have done and what's been done than just constantly editing a wiki.

On the other hand, it adds a bit more overhead.

Would like to decide in the next few hours so we can start putting todos in here or the wiki, as I'm about to start onboarding the attendees.

gnarf commented 12 years ago

Issues could be nice - A tag per table --- things that are tracked elsewhere can be links...

ryanneufeld commented 12 years ago

+1

ajpiano commented 12 years ago

Confirm, was planning to set up the tags once we had a little consensus here :)

mikesherov commented 12 years ago

+1

On Tue, Oct 2, 2012 at 5:36 PM, Ryan Neufeld notifications@github.comwrote:

+1

— Reply to this email directly or view it on GitHubhttps://github.com/jquery/2012-dev-summit/issues/1#issuecomment-9087955.

Mike Sherov Lead Developer SNAP Interactive, Inc. Ticker: STVI.OB

Wilto commented 12 years ago

Also +1.

agcolom commented 12 years ago

+1

jaspermdegroot commented 12 years ago

+1

gseguin commented 12 years ago

:+1:

RedWolves commented 12 years ago

Issues + Milestones so we can easily sort by table?

timmywil commented 12 years ago

+1

jaubourg commented 12 years ago

I am jaubourg and I approve this message.

dmethvin commented 12 years ago

me gusta

ajpiano commented 12 years ago

Issues it is, then. I've gone through and created labels for each table. Please set to adding todos for your tables, and may our inboxes forgive us :)

RedWolves commented 12 years ago

Why not use Milestones for the tables and use labels to determine what kind of work it is. JS, Docs, testing, Core, UI, Mobile, etc.?

scottgonzalez commented 12 years ago

We don't need to over-think this. We're creating issues to use for a whopping two days. After that point, these issues will be duplicative and annoying. Let's not worry about milestones. You already know what kind of work it is based on the table.