Should a scotty github group be made? about scotty HOT 33 CLOSED

Which repositories do you think could be hosted there?

from scotty.

I would move https://github.com/dmjio/scotty-tls there. And for more in the future, like scotty-clientsession (just a thought).

from scotty.

Yeah this could be a nice idea. Maybe we can have repository for
contributed code, repository for examples, like the @sinatra guys are doing

On Sun, Nov 24, 2013 at 7:27 PM, David Johnson [email protected]:

I would move https://github.com/dmjio/scotty-tls there. And for more in
the future, like scotty-clientsession (just a thought).

—
Reply to this email directly or view it on GitHubhttps://github.com/xich/scotty/issues/56#issuecomment-29157723
.

Sincerely yours,
-- Daniil

from scotty.

Would we need a logo?

from scotty.

(Note: I'm just a random Scotty user, not a dev)

It wouldn't need one, by default it would be given an identicon. That said, it might be fun to have a logo that we could throw around when we talk/write/present/whatever about Scotty.

I think this is a neat idea. Some other projects (Idris, for example) have GitHub orgs for this purpose.

from scotty.

Up to @xich

from scotty.

In principle I'm for this! I'd like to encourage anyone to contribute, either to Scotty itself or by creating packages like scotty-tls.

I guess enough people are using Scotty at this point that we should probably come up with some sort of policy of "what goes where". I've been hesitant in the past to add features willy-nilly to Scotty itself, as I'd like to keep the API as simple as possible, and not depend on every package under the sun. I realize that latter bit is somewhat of a losing battle, because the WAI ecosystem is fragmented into a lot of packages, and Scotty depends on WAI. To that end, here are my (somewhat disorganized) thoughts on things that need to be done:

• I created a Web.Scotty.Helpers module recently, for non-essential (but useful!) functions that didn't require new dependencies. Now I am thinking it'd be better to spin this into its own package (scotty-extra?) and let pretty much anything fly. The new package could be released frequently, and the core Scotty package could be more stable. Thoughts?
• There are a couple aspects of Scotty itself I'd like to improve.
  1. Re-examine the choice of raise/rescue. I'd like the error type to be user-extensible, rather than just Text, but still be simple to use for novices. Also consider the names themselves, and ideas like a user-defined global error handler.
  2. Consider extracting the required bits for file uploads from wai-extra. Uploads are the only reason we depend on that package, and that may considerably reduce the package footprint for Scotty.
  3. Explore better typed-route guarantees. I know @AndrewRademacher was interested in pursuing this... and someone started a project called Geordi (https://github.com/liamoc/geordi) to explore some ideas.
• It'd be great to have some sort of benchmark suite (as its own repo) that compares Scotty, Snap, Yesod, Sinatra, and whatever other web frameworks are hot. I'm thinking simple things like a pong benchmark and/or a RESTful JSON web-service. The goal is not so much to toot any horns (I certainly haven't even thought about performance, and Scotty is only fast because GHC/WAI/warp are) but to catch any bad behavior. If I make a change that cuts performance in half, it'd be nice to know.
• Creating some sort of slick Scotty homepage (and logo) with github pages would be great! I am not artistically inclined enough for this, so would welcome anyone who wants to run with that.
• Tests! Some little app that exercises all the features and a script that made curl calls to automatically check valid pages are generated would be more than enough, and much better than what we currently have (which is nothing).

So anyway, back to the original topic. Do I need to just create an organization and start giving people permissions? What other repos should we create? One for tutorials? Do other people have project ideas or requests?

I've got a few cycles to spend on this through the holidays, but this spring is slated for "Dissertation Writing", so I may disappear into a cave for long periods. As such, I'd love to get things set up and running smoothly before the new year!

from scotty.

The new package could be released frequently, and the core Scotty package could be more stable. Thoughts?

This sounds win-win to me, I like the idea.

Creating some sort of slick Scotty homepage (and logo) with github pages would be great! I am not artistically inclined enough for this, so would welcome anyone who wants to run with that.

I'd be happy to work on a site (with Bootstrap or similar), but someone else would probably need to do the logo - I'm not well versed in Inkscape. :(

So for that, it would just be a matter of creating a scotty org and a repo called scotty.github.io, I think, and giving some people access to it.

I'm wondering if tutorials might be better on the website instead of in a repo - or even using the GitHub wiki on a repo (maybe this repo?) so that anyone can add info to it/make corrections as they inevitably become outdated with API changes in later versions.

from scotty.

On 01 Dec 2013, at 08:01, Andrew Farmer [email protected] wrote:

In principle I'm for this! I'd like to encourage anyone to contribute, either to Scotty itself or by creating packages like scotty-tls.

Cool, I would like to move Scotty-hastache there if you think that it's acceptable

I guess enough people are using Scotty at this point that we should probably come up with some sort of policy of "what goes where". I've been hesitant in the past to add features willy-nilly to Scotty itself, as I'd like to keep the API as simple as possible, and not depend on every package under the sun. I realize that latter bit is somewhat of a losing battle, because the WAI ecosystem is fragmented into a lot of packages, and Scotty depends on WAI. To that end, here are my (somewhat disorganized) thoughts on things that need to be done:

I created a Web.Scotty.Helpers module recently, for non-essential (but useful!) functions that didn't require new dependencies. Now I am thinking it'd be better to spin this into its own package (scotty-extra?) and let pretty much anything fly. The new package could be released frequently, and the core Scotty package could be more stable. Thoughts?

Sounds like a great idea!

There are a couple aspects of Scotty itself I'd like to improve.

Re-examine the choice of raise/rescue. I'd like the error type to be user-extensible, rather than just Text, but still be simple to use for novices. Also consider the names themselves, and ideas like a user-defined global error handler.
Consider extracting the required bits for file uploads from wai-extra. Uploads are the only reason we depend on that package, and that may considerably reduce the package footprint for Scotty.
Explore better typed-route guarantees. I know @AndrewRademacher was interested in pursuing this... and someone started a project called Geordi (https://github.com/liamoc/geordi) to explore some ideas.
It'd be great to have some sort of benchmark suite (as its own repo) that compares Scotty, Snap, Yesod, Sinatra, and whatever other web frameworks are hot. I'm thinking simple things like a pong benchmark and/or a RESTful JSON web-service. The goal is not so much to toot any horns (I certainly haven't even thought about performance, and Scotty is only fast because GHC/WAI/warp are) but to catch any bad behavior. If I make a change that cuts performance in half, it'd be nice to know.

Creating some sort of slick Scotty homepage (and logo) with github pages would be great! I am not artistically inclined enough for this, so would welcome anyone who wants to run with that.

We can use Hakyll to generate the website. That way the documentation (including tutorials) can be easily accessible and patched if necessary.

So anyway, back to the original topic. Do I need to just create an organization and start giving people permissions? What other repos should we create? One for tutorials? Do other people have project ideas or requests?

I've got a few cycles to spend on this through the holidays, but this spring is slated for "Dissertation Writing", so I may disappear into a cave for long periods. As such, I'd love to get things set up and running smoothly before the new year!

—
Reply to this email directly or view it on GitHub.

from scotty.

It'd be great to have some sort of benchmark suite (as its own repo) that compares Scotty, Snap, Yesod, Sinatra, >and whatever other web frameworks are hot. I'm thinking simple things like a pong benchmark and/or a RESTful >JSON web-service. The goal is not so much to toot any horns (I certainly haven't even thought about performance, >and Scotty is only fast because GHC/WAI/warp are) but to catch any bad behavior. If I make a change that cuts >performance in half, it'd be nice to know.

It would probably be a good idea to separate internal benchmarks from benchmarks that compare Scotty to other frameworks. A benchmark suite can be added directly to the Scotty project just as unit tests are, then just use the cabal bench-marking system to manage it.

For comparing Scotty to other frameworks (i.e. Yesod, Snap, Node, Rails, etc.) we can just tack on to Tech Empower's benchmark suite. These benchmarks are fairly general, but it gives us a comparison to something like 200 other frameworks, without actually having to implement the benchmarks for 200 other frameworks.

EDIT: Not 200 frameworks-- 84 frameworks with 200 permutations (whatever that means).

from scotty.

@AndrewRademacher That sounds great (the Tech Empower suite). I'll create a separate repo for those benchmarks.

I haven't forgotten about this thread, but WAI 2.0 broke Scotty, so that is where my energy is going at the moment.

from scotty.

Issue #60: Better Type-Safety when routing.

from scotty.

Ok, organization created...

https://github.com/scotty-web

Who wants to be the guinea pig for putting their repo in? I've never managed an organization before, but it seems like there are two ways to go about it:

1. I add you as an organization member, you transfer the repo to the organization, then I make you admin on that repo after the transfer.
2. I fork your repo under the organization, then add you as an admin on that repo. (In this case, you still have your private version.)

Does that sound right?

@AndrewRademacher are you interested in working on the Tech Empower benchmarks? If so, I'll add you to that repo when I create it.

from scotty.

Sign me up. I'll drag scotty-tls over.

from scotty.

The group icon is pretty apt (=

from scotty.

http://jasonbyrne.files.wordpress.com/2011/02/montgomery_scott_enjoying_a_glass_of_scotch.jpg

from scotty.

@dmjio Alright I created a team for tls and gave you push/pull/admin. Are you planning to transfer ownership or should I fork your repo?

from scotty.

I'll transfer ownership, seems to be what other haskell web frameworks do as well.

from scotty.

Actually I'm going to do that as well so the Issues and such are migrated over. Sorry if I'm about to break everyone's email links!

from scotty.

@dmjio Looks like that worked. I made you admin on that repo.

Who's next?

from scotty.

@xich if you want to start a "scotty-web.github.io" repo and add some of us, maybe we can start experimenting with coming up with a static/Hakyll based site?

from scotty.

I'd like to transfer scotty-hastache there

On Fri, Dec 6, 2013 at 1:15 PM, Andrew Farmer [email protected]:

@dmjio https://github.com/dmjio Looks like that worked. I made you
admin on that repo.

Who's next?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-29973643
.

Sincerely yours,
-- Daniil

from scotty.

@codeblock Will do... let me read up on github pages a bit, and I'll get back to you.

@co-dan Added... go ahead and transfer. Update: I added you as admin to that repo.

from scotty.

@xich. I'm up for doing the tech empower benchmarks.

from scotty.

@AndrewRademacher Thanks! I added you as admin on:

https://github.com/scotty-web/scotty-benchmarks

Feel free to go to town on that, though I'm happy to help.

from scotty.

@xich Digg!

from scotty.

@codeblock I created the pages repo and made you admin on it. Let me know if you want me to add anyone else to the permissions list.

Anyone else that wants to help Ricky out with the pages stuff, feel free to speak up!

from scotty.

It'd be great to have some sort of benchmark suite (as its own repo) that compares Scotty, Snap, Yesod, Sinatra, and whatever other web frameworks are hot.

@xich: While the Halcyon “Hello, world!” shootout is not exactly the kind of benchmark you had in mind, I hope you will find it interesting.

from scotty.

This has already been done

from scotty.

@chessai (cc @xich) everybody was kicked out of the group though.

from scotty.

@dmjio i'm not sure what happened there. i tried to add you back but i can't. perhaps @xich knows what's up.

from scotty.

@dmjio I cleaned house, because almost everyone was inactive for years. I reinstated you.

I'd also like to clean up the various repos that have been dormant. I think anything with no commits in last three years can probably go. Objections?

from scotty.

@xich you're the best, thanks! :) I'm fine with the house getting cleaned. It seems people still download the scotty-starter project. I could upgrade things to the latest to make it easier for newcomers.

Otherwise, I have no objections whatsoever to anything. Cheers !

from scotty.