{"action":"created","issue":{"url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/301","labels_url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/301/labels{/name}","comments_url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/301/comments","events_url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/301/events","html_url":"https://github.com/rails-girls-summer-of-code/rgsoc-teams/issues/301","id":102338113,"number":301,"title":"Remove hardcoded dates for seasons?","user":{"login":"F3PiX","id":6314687,"avatar_url":"https://avatars.githubusercontent.com/u/6314687?v=3","gravatar_id":"","url":"https://api.github.com/users/F3PiX","html_url":"https://github.com/F3PiX","followers_url":"https://api.github.com/users/F3PiX/followers","following_url":"https://api.github.com/users/F3PiX/following{/other_user}","gists_url":"https://api.github.com/users/F3PiX/gists{/gist_id}","starred_url":"https://api.github.com/users/F3PiX/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/F3PiX/subscriptions","organizations_url":"https://api.github.com/users/F3PiX/orgs","repos_url":"https://api.github.com/users/F3PiX/repos","events_url":"https://api.github.com/users/F3PiX/events{/privacy}","received_events_url":"https://api.github.com/users/F3PiX/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-21T09:30:41Z","updated_at":"2015-08-21T13:11:13Z","closed_at":null,"body":"RubyNuby here, so proceed with caution! \r\nI think it works like this:\r\nOrga's can add a Season in orga/seasons/new, including starting and closing dates for applications, the coding summer, etc\r\nBut in the code, the dates are hardcoded, AND will always override the input from the new-form (AFAIK).\r\n \r\nI was thinking: what if the Season dates will be set only in the orga/seasons/new form? We can add default dates in the form fields. The orga's won't have to type more letters, because of the defaults. But, if the dates change (as was the case in 2015 submissions), the dates are very easy to update in the form. \r\nSuper nice selfish bonus: I can easily switch seasons so that I can work on the Application Form and on other stuff. \r\n\r\nWhat I do not oversee: if the cure is worse than the problem. \r\n\r\n\r\n(Related to the updated Readme: Quickstart Guide for beginners - setting the season open/close)\r\n\r\n "},"comment":{"url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/comments/133422275","html_url":"https://github.com/rails-girls-summer-of-code/rgsoc-teams/issues/301#issuecomment-133422275","issue_url":"https://api.github.com/repos/rails-girls-summer-of-code/rgsoc-teams/issues/301","id":133422275,"user":{"login":"F3PiX","id":6314687,"avatar_url":"https://avatars.githubusercontent.com/u/6314687?v=3","gravatar_id":"","url":"https://api.github.com/users/F3PiX","html_url":"https://github.com/F3PiX","followers_url":"https://api.github.com/users/F3PiX/followers","following_url":"https://api.github.com/users/F3PiX/following{/other_user}","gists_url":"https://api.github.com/users/F3PiX/gists{/gist_id}","starred_url":"https://api.github.com/users/F3PiX/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/F3PiX/subscriptions","organizations_url":"https://api.github.com/users/F3PiX/orgs","repos_url":"https://api.github.com/users/F3PiX/repos","events_url":"https://api.github.com/users/F3PiX/events{/privacy}","received_events_url":"https://api.github.com/users/F3PiX/received_events","type":"User","site_admin":false},"created_at":"2015-08-21T13:11:13Z","updated_at":"2015-08-21T13:11:13Z","body":"O, it is totally possible that I am confusing two different things. \r\nYes, I found the default values, but the way I (!!) handled it, my new_seasons data were overridden. Not in the lines you linked, I know, because I stubbed them. And maybe not hardcoded, I start to doubt that now.  But they were overridden. \r\n\r\nWhat happened: I created a new season 2016 in the orga/seasons form, with applications dates in Aug 2015.  That makes that the link to Apply Now appears in the menu. That's cool. But when I click the link, I got an error message : Applications 2015 are closed. (I am still figuring this out, and I think it has nothing to do with this issue, but with my teams season.)\r\n\r\nI issued the issue at this point in my search, and found that it would be cool if 'we developers' could easily switch seasons - easily the key word here :-) \r\n\r\nI see the need of a working season. That is also only for development, isn't it? Could that be solved with adding a season seed? \r\n\r\n  \r\n\r\n "}}