Where to post a long monologue for feedback?

357 views
Skip to first unread message

Tim Holy

unread,
Mar 27, 2016, 7:28:35 PM3/27/16
to julia-dev
Hi all,

I have a "julep" (julia enhancement proposal) nearly ready, and it's long.
About 85% of it essentially presents "the problem" and it's written so as to
attempt to catch people up who may not have been following every last
discussion on GitHub. (This adds considerably to its length.) The rest is a
proposal for a possible solution, which I am certain will be modified by
feedback from the community.

On http://julialang.org/community/standards/, under the "Be concise" request I
notice that it says "Consider writing a blog post if you feel that you have
enough to say on a particular subject." I am therefore contemplating
submitting the "background" (the first 85%) as a blog post, and the proposed
solution as a GitHub issue. Alternatives seem to be submitting the whole thing
as a blog post, or submitting the whole thing as a GitHub issue. On balance, I
find myself liking the "split" approach best because (1) many core contributors
won't need to read the long background section to be able to intelligently
comment on the proposed solution, and (2) GitHub is where most design
decisions are made.

Does this seem reasonable? Does anyone have a better idea?

Best,
--Tim

Jeffrey Sarnoff

unread,
Mar 27, 2016, 9:20:59 PM3/27/16
to julia-dev
reasonable

Elliot Saba

unread,
Mar 28, 2016, 10:31:26 AM3/28/16
to Julia Dev
I agree, sounds pretty reasonable.  I always enjoy blog posts about Julia in any case, so I vote for the split approach.
-E

Stefan Karpinski

unread,
Mar 28, 2016, 10:57:19 AM3/28/16
to juli...@googlegroups.com
+1. The split approach sounds good to me.

Tim Holy

unread,
Mar 28, 2016, 11:22:40 AM3/28/16
to juli...@googlegroups.com
OK, draft blog post is here:
https://github.com/JuliaLang/julialang.github.com/pull/366
and GitHub issue is here:
https://github.com/JuliaLang/julia/issues/15648

If upon reading you decide this format doesn't work, just let me know.

--Tim
Reply all
Reply to author
Forward
0 new messages