We need to draft up some requirements for this

[smy2748]

At some point we need to see who all is interested and draft up some requirements and user stories and then prioritize them.

On a related note, will we be trying to traffic everything related to the project through GitHub or will we be spanning out to Trello for PM stuffz and some Redmine server for bugz?

[RGood]

All this is really up to you. My opinion on these issues however would be as follows: Make a preliminary draft of requirements that you think are necessary and do some emailing or g+'ing to gather interest. The rest will be done at some point in the fall for the projects workshop. Also, I think Trello is a good idea because you can task certain people to certain parts of the project and get status updates there, but until you get a project group together, all you can really do is set up certain sections of the project. Figure out what needs to get done. Figure out what dependencies each thing needs, and proceed from there. Thanks for keeping me... posted (Trello Joke). :3

[MorganCabral]

Leaning towards using trello for that stuff. That and git wiki for walls of text and stuff.

[kristenmills]

I agreee with all these things.

[smy2748]

See above

[dorreneb]

Where do you plan on hosting the Redmine repo? Do you need an entire setup to track bugs?

[dorreneb]

Another consideration: is this a freshman-friendly project? I'd love to have some projects up and running for the fall to get kids involved. Can you define some roles (testing, design, etc) for some less-experienced people?

[MorganCabral]

I was under the impression that we were going to stick with Github for issue tracking, but if there is demand for it and we can get the logistics worked out I wouldn't be against using Redmine.

As for making this a freshman-friendly project - its certainly doable. We'll want to have lots of documentation and we'll probably want to have some tech talks ready to go for our process and our technology stuff. I wouldn't mind setting aside a Friday evening or two to do a couple of presentations myself.

If we go that route, we should be especially careful not to assign the freshmen boring tasks and/or busy work. Personally I think it would make sense to have a group of freshmen work with a mentor who guides them through building a module or something. We can figure out details about that during meetings at some point.

Speaking of that, we should get some kind of meeting time set up.

Btw, here are the notes I took at the end of Spring Quarter.

[smy2748]

I only threw out Redmine as an example of external tools that we could use. I think that the Github issue tracking will be sufficient, but I wasn't sure as to how much of this is going to be done using the tools built into Github and how much is going to be using separate tools. Thought it would be a good conversation to bring up to see where people fell on this topic and get a list of our tools together.

As for a meeting, would anyone object to meeting sometime soon via the interwebz to lay some of the groundwork? I think it would be a good idea for the project to go into the quarter with some of the basics ready so that we have some structure for anyone who wants to join up to work off of and so that as everyone's lives slowly become consumed with schoolwork and other projects, some of the major stuff can already be done.

[dorreneb]

Oh good! My intent on reopening this issue was to dissuade you guys from using Redmine, so everyone wins!

When do you guys plan on meeting up? I don't think that I'll be of much help dev wise, but Im interested in what's going on :)

[MorganCabral]

Saturday before 7PM and/or all of Sunday works for me. I forgot the name of that service which lets you figure out what times people are available for meetings and such based (the one that was used for Momentum) - we might want to do something like that to figure out when we want to me.

[smy2748]

http://doodle.com/

[kristenmills]

Sounds like a reasonable idea. I'm busy all weekend though.