Re: [julia-users] Re: Adding publications easier

[Tony Kelman]

Yeah I didn't realize the readme was suggesting that either, sorry. We should 
automate the complicated part on our side.

Re: [julia-users] Re: Adding publications easier

[Magnus Röding]

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 
>  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  > 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 > > 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?
>>>
>>>
>>
>

Re: [julia-users] Re: Adding publications easier

[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
 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 
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 
> 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?
>>
>>
>

Re: [julia-users] Re: Adding publications easier

[Stefan Karpinski]

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 
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?
>
>

[julia-users] Re: Adding publications easier

[Magnus Röding]

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?

[julia-users] Re: Adding publications easier

[Magnus Röding]

I realize I was very vague. I don't have a concrete suggestion, but 
github/pull request/jekyll/pandoc plus the fact that I'm not well 
acquainted with any of the steps was just too much. If I remember correctly 
I got as far as producing an error message in Jekyll and eventually 
giving up the whole thing.

Chris: If it could boil down to basically editing a .bib in the browser or 
comparable, that would be just amazing.

I'm raising the question, I don't have answers though...

Den tisdag 20 september 2016 kl. 21:48:06 UTC+2 skrev Chris Rackauckas:
>
> I think he's talking about the fact that this specifically is more than 
> Github: it also requires using pandoc and Jekyll: 
> https://github.com/JuliaLang/julialang.github.com/tree/master/publications 
> 
>
> If the repo somehow ran a build script when checking the PR so that way 
> all you had to do was edit the .bib and index.md file, that probably 
> would lower the barrier to entry (and could be done straight from the 
> browser). That would require a smart setup like what's done for building 
> docs, and probably overkill for this. It's probably easier on the 
> maintainer side just to tell people to ask for help. (And it's better to 
> keep it as a .bib instead of directly editing the Markdown/HTML so that way 
> formatting is always the same / correct).
>
> On Tuesday, September 20, 2016 at 12:14:21 PM UTC-7, Tony Kelman wrote:
>>
>> 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?
>
>

[julia-users] Re: Adding publications easier

[Chris Rackauckas]

I think he's talking about the fact that this specifically is more than 
Github: it also requires using pandoc and 
Jekyll: 
https://github.com/JuliaLang/julialang.github.com/tree/master/publications

If the repo somehow ran a build script when checking the PR so that way all 
you had to do was edit the .bib and index.md file, that probably would 
lower the barrier to entry (and could be done straight from the browser). 
That would require a smart setup like what's done for building docs, and 
probably overkill for this. It's probably easier on the maintainer side 
just to tell people to ask for help. (And it's better to keep it as a .bib 
instead of directly editing the Markdown/HTML so that way formatting is 
always the same / correct).

On Tuesday, September 20, 2016 at 12:14:21 PM UTC-7, Tony Kelman wrote:
>
> 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?