Opened 14 years ago

Closed 10 years ago

Last modified 4 years ago

#11 closed task (fixed)

initiate discussion on refining scope of committee

Reported by: ijones Owned by: ijones
Priority: normal Milestone:
Version: Keywords:
Cc: Meta Owner:
State: Section: N/A or multiple
Related Tickets:

Description

Currently we are brainstorming but we will soon need to start to narrow the scope. Open tickets related to that are listed under the "Scope Defined" milestone. Here are some suggestions from Henrik about how to have this discussion:

… Here are some concrete points that could be discussed:

  1. What should the time frame for the Haskell' effort be?
  2. Who are the users, what are their perceived needs, and how do we prioritize?
  3. Informed by 1 and 2, is Haskell' mainly a consolidation effort, or should the scope be wider?
  4. Informed by all of the above, is it possible to agree on some basic criteria that extensions and changes would have to meet in order to somewhat bound the size of the part of the design space that needs to be explored?

Change History (4)

comment:1 Changed 14 years ago by ijones

Type: defecttask

comment:2 Changed 10 years ago by (none)

Milestone: Scope Defined

Milestone Scope Defined deleted

comment:3 Changed 10 years ago by Simon Marlow

Resolution: fixed
Section: N/A or multiple
Status: newclosed

comment:4 Changed 4 years ago by Herbert Valerio Riedel

Priority: majornormal

Set default priority (as this confuses Trac otherwise)

Note: See TracTickets for help on using tickets.