Skip to content

Files

Latest commit

Oct 24, 2014
3f2351c · Oct 24, 2014

History

History
26 lines (17 loc) · 1.23 KB

CriteriaForProposal.md

File metadata and controls

26 lines (17 loc) · 1.23 KB

Criteria for Proposal

a) Project description; how project fits in with previous Testbed work, if applicable

b) Project plan, budget, and timeline (From the RFP: "Regardless of

c) If you plan to use cloud server resources, please indicate what kind of instance you need and how you plan to use it; also, what kind of instance you need, and include the cost to run the instance for the duration of your project in your project budget

d) Names and descriptions of roles for team members

e) Any special skills or intended outcomes that the proposer can bring to the task

f) The ultimate benefit that your solution brings to the ESIP community

Things to do:

  • Clarify project description (needs more details?)
  • How does this fit into other ESIP testbed work? (Don't know...)
  • Make sure the "Ultimate Benefit" isn't buried in text (Make new section specifically for this - even if just a few sentences)
  • Create timeline
  • Where will use cases come from? (Is it enough to say - we'll solicit from the ESIP community?)
  • Create a budget (Why are we asking for money?)
  • Can we use $ for APC of an open access publication? (Earth Science Informatics costs ~ $3k... PLoS One costs ~$2k ... PeerJ - much more affordable, not may be out of scope.