Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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.
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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-development+unsub...@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.
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.
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.
--
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.
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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-development+unsub...@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.
To unsubscribe from this group and stop receiving emails from it, send an email to grinnellplans-deve...@googlegroups.com.
[fullmers] - That's great, I'm delighted that you're volunteering for that. It would be wonderful to have an Android app, and you're absolutely right that it would be difficult and unpleasant given the site's current state. A real API is definitely near the top of the wishlist once we move to Rails, but unfortunately we can't start on new stuff until we've finished rewriting the existing things. I will definitely post here once I'm thinking about building an API, so I really hope you're still available and interested when the time comes.
On Sat, Sep 26, 2015, at 01:58 AM, [FullmerS] wrote:
Hi! I just want to throw in my two cents in from from an Android developer perspective.It would be great if there was a Android app for Plans (iOS too of course, but I cannot easily help with that). However, as the back-end currently stands, creating an Android app would be... unnecessarily difficult. If you guys decided to make some well-documented API end points with Rails, I would love to make an Android app for Plans.On Thursday, September 24, 2015 at 6:45:41 PM UTC+2, Ian Young wrote:
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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.
--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.
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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-development+unsub...@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.
- Eric
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.
--
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.
I'm open to discussion, but first asking a question about why a decision was made and the refusing to read the meeting notes that we collaboratively documented after the meeting is not a good way to start off the discussion.
The primary reason that we were motivated to rewrite plans is that it is/was a big hot mess of code (disclaimer: I haven't looked at the php plans in a while).
The web has evolved immensely since the days that plans was started and we would benefit greatly from a framework.
It's been an off-and on hobby project for a few of us, but I think we could knock it out quickly with some dedication.
The starting point of the discussion was that there were a lot of bug reports in google code and no one was willing to address them
because the php codebase was too unwieldy.
Looks like that's still the case https://github.com/grinnellplans/grinnellplans-php/issues. Picking a framework, any framework makes it easier for people to jump in and help write code.
At the time we picked RoR because there were a number of experienced and enthusiastic people.
On Friday, September 25, 2015, stjohns <saul....@gmail.com> wrote:
Gonna be honest, I didn't read the whole IRC discussion, because a chat log does not a design doc make. Maybe someone who participated wants to write up a summary of what was discussed and the decisions that were made that's accessible to the community at large?Here's what I'm getting at. A rewrite in Ruby is a cool hack, and the experiential value to the dozen or so involved developers is apparent. But what is the value of this project to the six-thousand-odd end-users who are not developers? What are the risks? Is the balance in the their interest?What's more, the existing community of Plans developers are necessarily comfortable with PHP. That may not be true of Ruby. Is the potential alienation of existing developers in pursuit of this project justified?-s
On Thursday, September 24, 2015 at 11:45:41 AM UTC-5, Ian Young wrote:
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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-development+unsub...@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.
--
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-development+unsub...@googlegroups.com.
To post to this group, send email to grinnellplans-development@googlegroups.com.
Visit this group at http://groups.google.com/group/grinnellplans-development.
For more options, visit https://groups.google.com/d/optout.
I'm open to discussion, but first asking a question about why a decision was made and the refusing to read the meeting notes that we collaboratively documented after the meeting is not a good way to start off the discussion.
The primary reason that we were motivated to rewrite plans is that it is/was a big hot mess of code (disclaimer: I haven't looked at the php plans in a while). The web has evolved immensely since the days that plans was started and we would benefit greatly from a framework. It's been an off-and on hobby project for a few of us, but I think we could knock it out quickly with some dedication. The starting point of the discussion was that there were a lot of bug reports in google code and no one was willing to address them because the php codebase was too unwieldy. Looks like that's still the case https://github.com/grinnellplans/grinnellplans-php/issues. Picking a framework, any framework makes it easier for people to jump in and help write code. At the time we picked RoR because there were a number of experienced and enthusiastic people.
Gonna be honest, I didn't read the whole IRC discussion, because a chat log does not a design doc make. Maybe someone who participated wants to write up a summary of what was discussed and the decisions that were made that's accessible to the community at large?Here's what I'm getting at. A rewrite in Ruby is a cool hack, and the experiential value to the dozen or so involved developers is apparent. But what is the value of this project to the six-thousand-odd end-users who are not developers? What are the risks? Is the balance in the their interest?What's more, the existing community of Plans developers are necessarily comfortable with PHP. That may not be true of Ruby. Is the potential alienation of existing developers in pursuit of this project justified?-s
On Thursday, September 24, 2015 at 11:45:41 AM UTC-5, Ian Young wrote:
Hi Saul,In short, Ruby because:1) It's fun,2) Rails is an extremely solid and capable framework3) Experience in Rails is pretty valuable to anyone looking to get a web dev jobIf you want more details on the thought process, I believe it's covered in the meeting minutes from when we started the project several years ago.On Thu, Sep 24, 2015, at 01:25 AM, stjohns wrote:
Why Ruby?On Wednesday, September 16, 2015 at 1:45:52 AM UTC-5, Ian Young wrote: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.
--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-development+unsub...@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.
--
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-development+unsub...@googlegroups.com.
To post to this group, send email to grinnellplans-development@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to grinnellplans-development+unsub...@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.
--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-development+unsub...@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.
--
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-development+unsub...@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.
--
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-development+unsub...@googlegroups.com.
--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.