Re: [Snowdrift-dev] Code reboot going into master
On March 21, 2016 8:52:47 PM EDT, Bryan Richter wrote: >On Sat, Mar 19, 2016 at 06:12:39PM +0200, fr33domlover wrote: >> >> 4. What about the `/u/username` thing? Do we want it for the reboot, >> should it be taken into account in any way? > >I think this is a separate question; one that I do not know the answer >to. Waiting on product requirements. This is a thing that needs to be decided. I want to talk to mray, msiep about it. ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] Code reboot going into master
On Sat, Mar 19, 2016 at 06:12:39PM +0200, fr33domlover wrote: > > On Fri, 18 Mar 2016 15:01:12 -0700 Bryan Richter wrote: > > > > We *could* keep going, and update the basic scaffold code to the > > latest version coming out of the yesod-scaffold library, but I'm > > not sure it is of the highest priority. > > I started a yesod app recently using the same template, so I'm > familiar with the recent scaffolding. I already examined the > differences. If you like, I can make a patch, but there are a few > issues: In general, there will be a high bar for success for such a patch, since it could possibly impact progress on higher priority items. However, I think it is possible to do. > 1. The new scaffolding uses a new config module, there is no "yesod > exec snowdrift Development" anymore. If you want dev mode, you > either "stack build --flag Snowdrift:dev" or specify "dev: true" in > stack.yml or "default: True" in Snowdrift.cabal . It's fine, just > saying this thing will change a bit. Right, that would be a welcome change. > 2. All that custom runYDB and runSDB and runSYDB - do we even want > it? Yesod has just the simple runDB, I'm not sure we need these > extra functions just for event notifications. Anyway this doesn't > intefere with the scaffold, just adds on top. Yeah, I think more of those are about to go away. In fact, they will probably all go away, back to the scaffolding default. That work would be appreciated. > 3. There are other custom things, like the auth plugins in > Foundation.hs . Need to see (assuming they're in the reboot too) if > we want them or we want to reset them to the default scaffolding's > version They're in the reboot, it's true, but there are some tasks to do to clean up the situation. Our auth needs are still custom. The default scaffold will not work. That will be the next thing to work on after making sure everything is in good shape for the web developers (css framework and templates framework). > 4. What about the `/u/username` thing? Do we want it for the reboot, > should it be taken into account in any way? I think this is a separate question; one that I do not know the answer to. Waiting on product requirements... Thanks! signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] Code reboot going into master
On Fri, 18 Mar 2016 15:01:12 -0700 Bryan Richter wrote: > On Thu, Mar 17, 2016 at 11:20:22AM -0700, Bryan Richter wrote: > > As I may (or may not?) have mentioned earlier on this list, I > > started paring down the codebase to just the features we need for > > MVP. That has been happening on a branch called 'reboot'. > > > > Today I'm going to do the old switcheroo, and merge that branch into > > master. > > K, that branch is merged now. :) > > We *could* keep going, and update the basic scaffold code to the > latest version coming out of the yesod-scaffold library, but I'm not > sure it is of the highest priority. I started a yesod app recently using the same template, so I'm familiar with the recent scaffolding. I already examined the differences. If you like, I can make a patch, but there are a few issues: 1. The new scaffolding uses a new config module, there is no "yesod exec snowdrift Development" anymore. If you want dev mode, you either "stack build --flag Snowdrift:dev" or specify "dev: true" in stack.yml or "default: True" in Snowdrift.cabal . It's fine, just saying this thing will change a bit. 2. All that custom runYDB and runSDB and runSYDB - do we even want it? Yesod has just the simple runDB, I'm not sure we need these extra functions just for event notifications. Anyway this doesn't intefere with the scaffold, just adds on top. 3. There are other custom things, like the auth plugins in Foundation.hs . Need to see (assuming they're in the reboot too) if we want them or we want to reset them to the default scaffolding's version 4. What about the `/u/username` thing? Do we want it for the reboot, should it be taken into account in any way? > > I'm looking forward to working with Stephen Michel to organize > upcoming efforts. signature.asc Description: PGP signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
[Snowdrift-dev] Code reboot going into master
As I may (or may not?) have mentioned earlier on this list, I started paring down the codebase to just the features we need for MVP. That has been happening on a branch called 'reboot'. Today I'm going to do the old switcheroo, and merge that branch into master. We *DON'T* want to put the pared-down website on https://snowdrift.coop yet, since there's still work to do moving data and workflow off the site. So, while that high-priority work is being completed, we devs will instead be deploying the new master code to https://dev.snowdrift.coop. I've created a branch named 'production' that will be used to track the original URL. Hopefully, very little work will be done there. That branch will be laid to rest when all necessary data and workflow is moved off the old site. signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] Code reboot going into master
On Thu, Mar 17, 2016 at 11:20:22AM -0700, Bryan Richter wrote: > As I may (or may not?) have mentioned earlier on this list, I > started paring down the codebase to just the features we need for > MVP. That has been happening on a branch called 'reboot'. > > Today I'm going to do the old switcheroo, and merge that branch into > master. K, that branch is merged now. :) We *could* keep going, and update the basic scaffold code to the latest version coming out of the yesod-scaffold library, but I'm not sure it is of the highest priority. I'm looking forward to working with Stephen Michel to organize upcoming efforts. signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
