So, what's the next step here?

On 23 July 2017 at 02:16, Colin Fleming <colin.mailingl...@gmail.com> wrote:

> Are you saying the contrib process is deliberatly made to be difficult for
>> the community to contribute to it?
>
>
> No, not at all, just that it's deliberately designed to be exactly the way
> it is, so dedicating a lot of time to trying to change that is likely to be
> frustrating and fruitless.
>
> I agree about the confusion of a lot of the contrib projects, I'm often
> unsure if they're abandoned or just mature. I don't know if the expectation
> or the reality is that they should all be in a working state.
>
> On 23 July 2017 at 09:17, Didier <didi...@gmail.com> wrote:
>
>> > The contrib process is in place because some want it that way - it's
>> very deliberately by design and AFAICT unlikely to change.
>>
>> Are you saying the contrib process is deliberatly made to be difficult
>> for the community to contribute to it?
>>
>> If so, maybe if it had more obvious tenets, I find its difficult as a
>> user to understand what the contribs are for, who maintains them, what
>> their status are, and how they differ to the standards library, or other
>> community projects.
>>
>> I can't contribute to OSS, because of my current employment, but as a non
>> contributing Clojure user, I've always wondered how much I should rely on
>> contribs, some of them seem quasi-abandonned, yet they appear more
>> official, and it makes it hard for me to decide if I want to take a
>> dependency on them or not.
>>
>> In a way, an active project gives me more trust, and if taking nRepl out
>> of contrib makes it more active, that's a good thing. Unless contrib libs
>> come with any official support guarantees, or some form of stronger
>> commitments?
>>
>> --
>> 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.
>

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

Reply via email to