[seagrant-dev] BSG Project Update and Weekly Coordination

Carr, Justin Justin.Carr at oregonstate.edu
Tue Jul 29 20:08:56 UTC 2014

Hi Carrie,

We had our backlog item planning meeting yesterday to make sure that everyone was on the same page. Here’s what we have prepared (meeting attendees, feel free to chime in if I forget anything) :

·         Public-visible Trello board for requirements tracking<https://trello.com/b/nyYBMXFP/working-waterfronts-what-s-fresh>. This should let Mark and Jamie follow along tomorrow and explore some of our backlog items while we talk about them.

·         High-level requirements backlog organized by screens. Each requirement implies tasks and sub-tasks for the BSG and the OSL to execute on, these are tracked separately.

·         I’m not sure what is meant by “full”; our backlog items describe a delieverable that could satisfy the client but we will need to check with the client to find out more about how to handle and display certain data items

From: seagrant-dev-bounces at osuosl.org [mailto:seagrant-dev-bounces at osuosl.org] On Behalf Of Hertel, Carrie - BSG
Sent: Tuesday, July 29, 2014 10:06 AM
To: seagrant-dev at osuosl.org
Subject: Re: [seagrant-dev] BSG Project Update and Weekly Coordination

Hi Team –

We had talked about having a Sprint 1 kickoff meeting with Sea Grant on the 30th (tomorrow) with a full sprint plan ready to go and ready to review with Sea Grant for prioritization.

Where do we stand on this?


Carrie Hertel, PMP
Director – Business Solutions Group
Oregon State University

From: seagrant-dev-bounces at osuosl.org<mailto:seagrant-dev-bounces at osuosl.org> [mailto:seagrant-dev-bounces at osuosl.org] On Behalf Of Lance Albertson
Sent: Tuesday, July 29, 2014 10:03 AM
To: seagrant-dev at osuosl.org<mailto:seagrant-dev at osuosl.org>
Subject: Re: [seagrant-dev] BSG Project Update and Weekly Coordination

On Tue, Jul 29, 2014 at 9:35 AM, Carr, Justin <Justin.Carr at oregonstate.edu<mailto:Justin.Carr at oregonstate.edu>> wrote:
So far, setting up our Linux environments has been pretty smooth. I think the simple act of making that pseudo-script has ironed out some of the pain points in getting Sencha and Phonegap set up properly.

​That sounds good.​

A github community/etiquette question for you: I would like to make this script visible and editable for any of our student interns to reference quickly but it seems too small and informal for a github repository. Would this make sense as a Gist or is it best to keep this kind of stop-gap solution out of public view?

​That's a good question. I actually just had our team push the cookbook as it stood to github [1]. I asked Jordan what we should do and he suggested we open an issue for it on the cookbook repo and attach the file there. But if you're wanting to make updates I suggest you do that but make a gist and reference it in the issue.

That way we can reference the current version when we get to getting this cookbook ironed out.

[1] ​https://github.com/osuosl-cookbooks/sencha-sdk

Lance Albertson
Oregon State University | Open Source Lab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/seagrant-dev/attachments/20140729/19e1a6ca/attachment-0001.html>

More information about the seagrant-dev mailing list