Re: What is needed in guildhall to include it in Guile?

[Amirouche <amirouche@hypermove.net>]

Le 23/02/2016 à 17:57, Arne Babenhauserheide a écrit :
> So, to summarize the things I can change:
>
> - Add the path to the installed package in guild show <package> or list-packages
> - Add a dynamical site as repository
> - Package guix features
> - Package guildhall in guix
>
> And things I can’t change easily:
> - Package many packages (I hope a site with easy uploads could change that)
> - Add dynamically fetched packages (I’m not sure how to do that right —
>    or whether I actually want to do it, given that this means executing
>    code which is downloaded at runtime…)
>
> Requirements for a guildhall website:
> - easy upload (like marmalade?)

What do you mean by easy?
> - download statistics
This doesn't necessarly mean that the website is not static. I am 
wondering what's best:

- static website
- interactive stuff à la github
> - bug reporting possible (maybe a link to a bugtracker?)
I had that in my todo actually! But I'd like to know more
about how debbugs works to make. Basically outside email
  navigation what make debuggs a crazy good bugtracker.
> Did I miss something?

A Question/Answer system, a pastebin and a search engine :)


>
> Nala Ginrut writes:
>> I may anticipate the packages amount for Guile would be increasing if we
>> done it properly.
> I’d think so, too.
Me too. Really! I think I need to scratch un itch and actually succesfully
contribute something useful... maybe... I will remix my culturia web stuff
into a guildhall website. That said I have an issue with registration/login
stuff anything related with setting cookies I don't find a good abstraction,
for it.

I keep you posted.
> Best wishes,
> Arne
>