At the moment the GSOC topics web page is hosted on github: http://pharo-project.github.io/pharo-project-proposals/ <https://github.com/pharo-project/pharo-project-proposals/tree/gh-pages> and gsoc.pharo.org <http://gsoc.pharo.org/> simply points there. This was done because it was the easiest way to automate the process and not ask someone for credentials.
I’d suggest to keep it like it is for the time of GSOC decision making time. After that I support the idea of moving it to the pharo hosting, but I’d keep the current CI architecture. If you haven’t seen you can propose a pull request, and CI will validate it and mark directly in the request whether everything is ok. Cheers Uko > On 18 Feb 2016, at 22:34, stepharo <steph...@free.fr> wrote: > > Sven > > We will migrate the html file to file.pharo.inria.fr > As well as the consultants.pharo.org. > > Stef > > > Le 17/2/16 09:52, Sven Van Caekenberghe a écrit : >> Last year a CI job was created: >> >> https://ci.inria.fr/pharo-contribution/job/GeneratePharoTopicsPage/ >> >> I tried to revive it, but I can't find the config/settings, or so it seems. >> >> Yes, it used to be STON, but it was changed to .st - in any case, the idea >> was that it were just objects. >> >> I totally agree this process is not good. >> >> The AWS bucket is under my private key, cannot share that. >> >>> On 17 Feb 2016, at 00:50, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: >>> >>> Sorry, I’m a bit confused. The Topics.st is not a STON file, it’s a >>> smalltalk code file. Sven, can you please guide me on how to generate the >>> page, because I was not able to figure it out from PharoPeople package. >>> Also I guess that I’ll be able to automate the process if you give me AWS >>> Access Keys and the bucket name, but let’s come back to this later. >>> >>> Cheers. >>> Uko >>> >>>> On 12 Feb 2016, at 13:20, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>>> >>>> The whole process is not automatic. >>>> >>>> The code to convert the .ston file to the .html is in >>>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople/ >>>> >>>> Maybe you can try to run it yourself. >>>> >>>> Once there is a new .html file, I have to put into some AWS S3 bucket of >>>> mine. >>>> >>>> If you send me the .html I will do copy it to the right place. >>>> >>>>> On 12 Feb 2016, at 12:57, Serge Stinckwich <serge.stinckw...@gmail.com> >>>>> wrote: >>>>> >>>>> The sync with the http://gsoc.pharo.org/ is not working ... >>>>> Can we fix that and put GSOC 2016 on the front page ? >>>>> >>>>> Thank you >>>>> >>>>> On Thu, Feb 11, 2016 at 3:29 PM, stepharo <steph...@free.fr> wrote: >>>>>> Good initiative. >>>>>> I will clean some of them too. >>>>>> Stef >>>>>> >>>>>> Le 11/2/16 15:20, Damien Cassou a écrit : >>>>>> >>>>>>> Serge Stinckwich <serge.stinckw...@gmail.com> writes: >>>>>>> >>>>>>>> I reuse the list of the last year : >>>>>>>> >>>>>>>> https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics.st >>>>>>> I've just removed everything git-related because it was old. I hope >>>>>>> someone else will write a new one because support of existing DVCS is >>>>>>> very >>>>>>> important. >>>>>>> >>>>>>> I've also updated my projects. >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Serge Stinckwich >>>>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>>>> Every DSL ends up being Smalltalk >>>>> http://www.doesnotunderstand.org/ >>>>> >>>> >>> >> >> > >
