This is happening (again)

[Ian Young]

Yes! Despite appearing rather dead, the Rails rewrite has just been resting its eyes for a bit. I am firing this thing back up, with the intention of putting in regular amounts of work throughout the next few months and hopefully pushing this project close to the finish line.

Are you interested in helping out? Whether you're a Rails vet looking to do some good for the community, or a newbie looking to gain some experience with the fun and eminently-marketable framework, we can totally use your help. If you are interested but don't know where to start, literally me email me with the words "I want to help with Plans dev" and I will get you set up.

I've pushed a whole ton of updates bringing the project up to Rails 4.2, Ruby 2.2, etc. Hopefully no one had outstanding branches, but if you did and they are now ruined, ping me and I can help you straighten them out. I'll be putting most of my substantive commits from now on into Pull Requests. I'll leave them open for at least a day in case anyone would like to review and comment. If you want to look over a pull request before it gets merged, drop me a comment to let me know you're looking at it, and I'll wait a bit longer.

Let's do this! I want to push Plans forward into the new era of the web, and getting it onto manageable technological footing is the very important first step.

[stjohns]

Why Ruby?

[Betsy Lorton]

Thanks for putting all that work into revamping the project! I'm looking forward to contributing.

One more step that would help: I'm taking the GitHub issue tracker to be a kind of to-do list for the project. Would you (or another person with admin access) mind doing a once-over of that list? It looks like a few of the issues have been finished but not marked as resolved in GH. And a few others are 'assigned' to someone, but haven't been updated in years. It would be nice to have those open, so they can be assigned to someone else. 

OR, if I shouldn't be using that list as a reference, let me know :).

[Ian Young]

Hey Betsy,

 

Yes, you should use the issues as a to-do list, and yes, you're quite right that it's a little out-of-date. I'll take another pass through tonight and try to clean up anything I can find. It's also an incomplete list, unfortunately. In addition to a few open tickets that have been resolved, I'm sure there are outstanding tasks that don't have tickets yet. And to be perfectly honest, I don't have a 100% accurate mental picture of what's finished and what isn't. Such is life when you don't have a dedicated PM.

 

I'll try to clean it up, and if you find anything else that seems wrong, leave a comment on the ticket and I'll check it out. Feel free to pick up any tickets that were assigned years ago and untouched. Anything that was assigned this year, we'll give the owners a little more time to work on :)

--

You received this message because you are subscribed to the Google Groups "GrinnellPlans Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grinnellplans-deve...@googlegroups.com.

To post to this group, send email to grinnellplan...@googlegroups.com.

Visit this group at http://groups.google.com/group/grinnellplans-development.

For more options, visit https://groups.google.com/d/optout.