Re: [Snowdrift-dev] snowdrift workshop

[Stephen Michel]

On Thu, Mar 10, 2016 at 8:57 PM, Aaron Wolf  
wrote:

On 03/10/2016 03:44 PM, Răzvan Panda wrote:

 Hi

 I've been busy lately studying other technologies so I temporarly
 abandoned study of Haskell, that's why I have not been on IRC.
 For this month's Haskell Dublin meetup I am thinking it would be a 
good
 idea to do a snowdrift workshop, basically working on different 
tickets

 for it. Any opinions/suggestions on this? I will have to create the
 meetup event soon and provide links relevant to the project. Meetup 
will

 probably be betwen 28 and 31 this month. I'm hoping people will get
 involved in the project before the meetup as we will only have 2-3 
hours

 at disposition to work on stuff.

 Cheers


Nice to hear from you. I'm posting this reply to the dev list, you
should consider at least temporarily re-joining that if you aren't 
still

subscribed.

The news (among lots of it) for us is that we're paring back to focus 
on

core MVP stuff to try to really launch. We do have improved docs and
build stuff, although still won't build on Windows.

There's definitely tickets worth doing, although we're pushing off the
wiki and discussion/ticketing to be outside of the MVP core focus. 
We're

also moving to different approaches to project management.

It would be nice to identify the most appropriate things for people to
hack on, so maybe other folks can weigh in on how we should do this 
best.


Cheers,
Aaron


Probably the best way to do this is through our project management 
tool. Once it is set up, it should be pretty clear what our priorities 
are.


Unless I hear a convincing argument in favor of OpenProject in the next 
~12 hours, I will begin to set up Taiga for this purpose tomorrow. I'll 
make sure to keep you and the ML updated.
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev

Re: [Snowdrift-dev] Code reboot going into master

[fr33domlover]

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

Re: [Snowdrift-dev] Mechanism implementation

[Bryan Richter]

On Tue, Mar 15, 2016 at 09:13:53AM -0600, Peter Harpending wrote:
> On 03/15/2016 12:50 AM, Peter Harpending wrote:
> > code that requires one to use the feature, so I vote that
> 
> Silly me, I forgot to mention how I vote. I vote that we leave it for
> now, because it's unlikely to cause any problems. We can always remove
> it if it does.

I feel like it already has caused problems; namely, questions and
confusion. It also creates additional maintenance and testing burden.
All these problems compound with time. I feel strongly that unused
features must be removed. (This is the same exact thing Snowdrift is
grappling with as a whole.)

We can always reach into git history and bring it back if we need it.


signature.asc
Description: Digital signature
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev