Thanks for the quick response in changing the workflow, now it's more at my 
(and hopefully others') level.

Den torsdag 22 september 2016 kl. 17:56:13 UTC+2 skrev Stefan Karpinski:
>
> I didn't realize that there was a README that actually tells you to do all 
> of that. I've opened an issue 
> <https://github.com/JuliaLang/julialang.github.com/issues/421> since 
> there's no reason someone should have to install Jekyll in order to submit 
> a publication that uses Julia – that's way over the top.
>
> On Thu, Sep 22, 2016 at 11:48 AM, Stefan Karpinski <ste...@karpinski.org 
> <javascript:>> wrote:
>
>> You don't need Jekyll installed to edit markdown files. You can even edit 
>> files directly in the web and preview the rendering. Admittedly, installing 
>> Jekyll is a pain and seems to have gotten worse over time somehow, but you 
>> don't need to do any of that to submit a publication.
>>
>> On Thu, Sep 22, 2016 at 8:08 AM, Magnus Röding <magnus...@gmail.com 
>> <javascript:>> wrote:
>>
>>> I have now made a new attempt, ending up having everything installed and 
>>> seemingly working on an Ubuntu 16.04 system. My workflow so far is:
>>>
>>> - git clone https://.... to local repo (I have a github account)
>>> - edit julia.bib and _EDIT_ME_index.md according to instructions
>>> - run 'make' in publications directory
>>> - run 'bundle exec jekyll build' in main repo directory
>>> - adding the modified files by 'git add *'
>>>
>>> So, off-topic question as far as Julia goes, but what to do now? I 
>>> realize I'm supposed to commit, annotate, request-pull, and go nuts, but in 
>>> which order?
>>>
>>> Thanks in advance, not my cup of tea this, so if anyone can help tx :-)
>>>
>>> Den tisdag 20 september 2016 kl. 21:14:21 UTC+2 skrev Tony Kelman:
>>>
>>>> What do you propose? Github is about as simple as we can do, 
>>>> considering also the complexity of maintaining something from thr project 
>>>> side. There are plenty of people around the community who are happy to 
>>>> walk 
>>>> you through the process of making a pull request, and if it's not 
>>>> explained 
>>>> in enoug detail then we can add more instructions if it would help. What 
>>>> have you tried so far?
>>>
>>>
>>
>

Reply via email to