Ouch. I'm not sure what happened to that email. I blame autocorrect.
There were some scaling problems with npm in the past and they ended
up taking funding. The list of issues you've provided look good.
Perhaps some "newbie" tags in the issues would be good too. I will
join the maintainers list.
Thank you for your effort in providing this essential service.
Lucas
On 5 January 2016 at 11:51, Toby Crawley <t...@tcrawley.org> wrote:
> On Mon, Jan 4, 2016 at 3:31 PM, Lucas Bradstreet
> <lucasbradstr...@gmail.com> wrote:
>> Good info. Now that we've performed the initial clojars drive, which was
>> performed at a very fortuitous time, do you think that the problem is
>> primarily one of money, man poweror, or both? I realise that there's a lot
>> of kI'm happy to help in I'm one of
>> Rikkkkeeee way, because I think we definitely want to avoid some of the past
>> issues in Node JS - which I think they have mostly solved now
>
> I don't quite follow all of that, but I think I get the gist :)
>
> Seriously though, what issues did the Node JS community have? I
> haven't been involved there at all, so haven't paid attention.
>
> The donations have been great, and I appreciate every bit of it. But
> what we primarily need right now is time from others. For the past
> nine months, I've been the only administrator, but today Daniel
> Compton graciously agreed to help out with that[1], so I think we are
> good there. I also need help with some of the bigger issues (moving
> the repo to block storage[2], possibly behind a CDN[3], and
> implementing atomic deploys[4]), which I plan to post bounties[5] for
> (using some of the donations) in the next few days.
>
> Beyond that, we have quite a few other smaller issues that are ready
> for work (marked with the "ready" tag[6], along with a subjective
> rough estimate of effort involved ("small", "medium", "large")), if
> people are looking for other ways to contribute. And, if you are
> wanting to be more involved in and up to date with what is happening
> with Clojars, I urge you to join the clojars-maintainers list[7].
>
> - Toby
>
> [1]:
> https://groups.google.com/d/msg/clojars-maintainers/75VmB2F0VX4/hL6dQZAKCQAJ
> [2]: https://github.com/clojars/clojars-web/issues/433
> [3]: https://github.com/clojars/clojars-web/issues/434
> [4]: https://github.com/clojars/clojars-web/issues/226
> [5]: https://www.bountysource.com/teams/clojars
> [6]: https://github.com/clojars/clojars-web/labels/ready
> [7]: https://groups.google.com/forum/#!forum/clojars-maintainers
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
