Hi Evan,
To be clear I think you have done great work and I apologize if this comes 
across as overly critical. Very aware that you are extremely busy and that 
you are only one person. This is not exactly what Peter said but I think it 
is super critical that you find productive ways to relieve most of your 
burdens so you can better focus your time. I was once told by an old boss 
that you can only write 10,000 lines of code in a week so you better make 
sure that those are the write lines of code to write.

For me I think where I struggle with your answer is that this seems to be a 
solved problem, even for projects that are in pre-release development 
stages like Elm. I started reading the C4 
<https://hintjens.gitbooks.io/social-architecture/content/preface.html>book 
Peter referenced and it presents a possible approach to solving this. Node 
solved this 
<https://medium.com/the-javascript-collection/healthy-open-source-967fa8be7951#.jpmd7zpt4>in
 
a somewhat similar fashion but that was only after much internal conflict 
<https://en.wikipedia.org/wiki/Node.js#History> that resulted in it being 
forked for a time.

I do not want to question your past priorities as I think you have done 
great work and the results definitely speak for themselves. That said going 
forward in my opinion one of the most important aspects of a growing Open 
Source project, that we intend for people to use in production, is how to 
effectively allow people to contribute.

Finally one more thing in the context of the case Peter is discussing. In 
general I would encourage you to be extra careful in the way you 
communicate to people. In another thread some community members were 
arguing over are you the Captain of the ship or the ship builder and I hate 
to say it but your kind of both at the moment. The way you communicate sets 
the tone for others and has a large affect on how others communicate as 
well. In this case your response was not just to the original poster but 
also to Fred who responded with a potential solution. You are the essence 
of this community and I imagine it was pretty frustrating for Fred to see 
his work discounted. In my opinion your response in this thread makes a lot 
more sense and suspect would have been greatly appreciated by Fred.

Thanks for all your great work!
-Justin


On Thursday, June 2, 2016 at 12:29:28 PM UTC-7, Evan wrote:
>
> From http://elm-lang.org/blog/farewell-to-frp#what-is-next-
>
> I know some people are eager to help with creating these libraries. Please 
> give me some time to develop a coherent process for making sure a desire to 
> help can also translate into great results.
>
>
> The message you quote says a similar thing. Lots of things need to happen. 
> It is not possible to do everything at the same time. Seven days is not a 
> long time, especially when they contain a 3 day weekend. Especially when I 
> have a set of goals for the next few weeks based on what *I *think are 
> the most important things to get done.
>
> One of my short term goals is to finally get process bot 
> <https://groups.google.com/forum/#!searchin/elm-dev/process$20bot/elm-dev/SnfGqk5XBgg/c1IpV4UvAgAJ>
>  
> working to help with this. Literally addressing this exact issue because I 
> know it's important and it can be done better. I want process bot to talk 
> about expectations 
> <https://github.com/process-bot/the-process/blob/master/expectations.md> in 
> a way that is very relevant. I wrote that a long time ago, but instead of 
> finishing the project, I worked on "the most important thing" so it is 
> still not communicated clearly.
>
> I think this comment 
> <https://github.com/elm-lang/elm-package/pull/177#issuecomment-220825568> is 
> a nice illustration of this. It turns out (1) I was working on 0.17 which 
> was pretty important and (2) the actual situation was more complicated than 
> everyone thought. When I finally got a chance to give it my full attention, 
> the outcome was pretty great! So yes, it could have been quicker, but I 
> also think it's hard to retroactively disagree with my prioritization 
> decisions once I was able to actually get them out the door.
>
> In the case you are reacting to, I am basically saying: for someone just 
> trying to make something, use ports. That'll be fast and it'll work. Yes, 
> there are things going on that might make it easier *later*, but they are 
> not ready yet. So I read things as "I know you want to achieve X today, but 
> instead of telling you how, I will tell you about something that is not 
> released yet." Everything there is true, but it's not good advice for that 
> person!
>
>
> On Thursday, June 2, 2016 at 8:35:24 AM UTC-7, Justin wrote:
>>
>> +1 on everything your saying here Peter. Thanks for linking the C4 book 
>> really interesting and applicable read so far.
>
>

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to