Thanks, for the responses everyone, it was incredibly helpful! :)

On Thursday, November 12, 2015 at 9:21:33 AM UTC, Viral Shah wrote:
>
> Attching the github traffic data. Doesn't have history though, but the 
> numbers were bigger than what I expected when I first saw this.
>
>
> Some other interesting numbers:
>
> 1. ~10,000 pageviews on the website daily
>
> 2. 1.7M "users" and 8.6M pageviews over the lifetime of julialang.org - 
> as per google analytics
>
> 3. The mailing lists have ~4000 subscribers combined
>
> 4. Github page gets 74000 views every fortnight, ~10,000 uniques. ~3000 
> clones every fortnight, with ~700 uniques.
>
>
> Iain posted the packages data, and the github stars and watch data is 
> visible to everyone. 
>
>
> -viral
>
>
>
>
>
> <https://lh3.googleusercontent.com/-5gwVYZ8G6n8/VkRYc84fcEI/AAAAAAAAJnY/Xv_TBpMXM3U/s1600/Screen%2BShot%2B2015-11-12%2Bat%2B2.43.48%2BPM.png>
> On Thursday, November 5, 2015 at 12:57:22 AM UTC+5:30, Patrick O'Leary 
> wrote:
>>
>> It's not in the repo, it's a GitHub feature. But it may only be visible 
>> if you have Collaborator or Owner status on the repository.
>>
>> On Wednesday, November 4, 2015 at 10:51:34 AM UTC-6, Ben Ward wrote:
>>>
>>> I don't think the /graphs folder is part of the julia repo any-more :(
>>>
>>> On Wed, Nov 4, 2015 at 4:48 PM, Tony Kelman <to...@kelman.net 
>>> <javascript:>> wrote:
>>>
>>>> There are some interesting numbers at 
>>>> https://github.com/JuliaLang/julia/graphs/traffic
>>>>
>>>> Elliot Saba also did some scraping of the AWS download logs for 
>>>> binaries and shared the aggregate numbers (broken down by platform) 
>>>> privately with a few people, it may be worth sharing those publicly.
>>>>
>>>>
>>>> On Wednesday, November 4, 2015 at 8:26:19 AM UTC-8, Ben Ward wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I was wondering are there any metrics or stats available that show how 
>>>>> the user-base of Julia has grown over the last few years, and what it's 
>>>>> size is now?
>>>>>
>>>>> Many Thanks,
>>>>> Ben W.
>>>>>
>>>>
>>>

Reply via email to