I agree a simple static site is all it needs, as Joachim points out I already implemented the basic site generation.
The main question is about where the site lives and what the deployment mechanism is. If it's tied to the ghc-proposal repo then I can't do anything but if it's a subdomain of `haskell.org` then I could be more potent. Cheers, Matt On Fri, May 10, 2019 at 9:34 PM Iavor Diatchki <[email protected]> wrote: > > Having a read-only rendered version of all accepted proposals should > probably be pretty simple---we can even host it in the same repo using > "Github Pages". I don't know that we need anything more complex > than that. > > On Thu, May 9, 2019 at 5:41 AM Joachim Breitner > <[email protected]> wrote: > > > > Hi, > > > > I looked into getting doi’s for our accepted proposals, but it looked > > harder than it should be. > > > > Building a nice web page from our repository and publishing it on > > GitHub pages, which can serve a custom domain like > > ghc-proposals.haskell.org would not be hard. Matthew even started a > > Makefile at some point that produces a reasonably nice output using > > sphinx. > > > > Maybe only reason why I am hesitant to do so is that there is a feature > > creep risk: > > We start with a webpage that shows accepted proposals, > > soon we’ll add functionality to list pending proposals and their status > > (why not? They are just a GitHub API call away), > > then we start using this page to actually drive the proposals (surely > > we can use this to tally the votes), > > and then we end up with a system that no longer has the “you just need > > to know GitHub to use it” property that made us build a Github-centric > > process in the first place. > > > > But maybe I am paranoid, and I should just set up the CI infrastructure > > for Matthew’s sphinx build. > > > > BTW, in hindsight, I regret that we renumber proposals after > > acceptance. It would be easier if they just retained the number of the > > PR (other proposal processes out there do that). But that ship has > > sailed. > > > > Cheers, > > Joachim > > > > Am Donnerstag, den 09.05.2019, 10:45 +0100 schrieb Matthew Pickering: > > > I want to cite a GHC proposal but linking to github for it doesn't > > > seem very official or permanent. > > > > > > Last year you also cited a proposal for your Haskell symposium paper > > > (https://arxiv.org/abs/1806.03476) but instead linked to the pull > > > request which also doesn't seem ideal to me. > > > > > > Matt > > > > > > On Thu, May 9, 2019 at 10:11 AM Simon Peyton Jones > > > <[email protected]> wrote: > > > > Interesting. How would it differ from what we have (i.e. github's RST > > > > viewer)? > > > > > > > > > -----Original Message----- > > > > > From: ghc-devs <[email protected]> On Behalf Of Matthew > > > > > Pickering > > > > > Sent: 09 May 2019 09:40 > > > > > To: GHC developers <[email protected]> > > > > > Subject: Website for viewing proposals > > > > > > > > > > Hi, > > > > > > > > > > It would be useful if there was a canonical way to link and view GHC > > > > > proposals rather than relying on github's RST viewer. > > > > > > > > > > Can we set up a website, `ghc.haskell.org/proposals`, which is > > > > > deployed to > > > > > automatically when a new accepted proposal is merged? > > > > > > > > > > FWIW, if the proposals process was also on gitlab then doing this > > > > > deployment would be easy using our CI infrastructure but I don't > > > > > know how > > > > > to set up something similar on github. > > > > > > > > > > Cheers, > > > > > > > > > > Matt > > > > > _______________________________________________ > > > > > ghc-devs mailing list > > > > > [email protected] > > > > > > > > > > https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.hask > > > > > ell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc- > > > > > > > > > > devs&data=01%7C01%7Csimonpj%40microsoft.com%7C33b5834164a1436bd09308d6 > > > > > > > > > > d459edc0%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=vWx4R2xtV2%2BX7l > > > > > RpM0weHo87NIc7pl0MoIiW76R%2BDdM%3D&reserved=0 > > > _______________________________________________ > > > ghc-devs mailing list > > > [email protected] > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > -- > > Joachim Breitner > > [email protected] > > http://www.joachim-breitner.de/ > > > > _______________________________________________ > > ghc-devs mailing list > > [email protected] > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
