<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/assets/atom.xsl" type="text/xsl"?><feed
	xmlns="http://www.w3.org/2005/Atom"
	xmlns:thr="http://purl.org/syndication/thread/1.0"
	xml:lang="en-US"
	><title>Sacha Chua - tag - braindump</title>
	<subtitle>Emacs, sketches, and life</subtitle>
	<link rel="self" type="application/atom+xml" href="https://sachachua.com/blog/tag/braindump/feed/atom/index.xml" />
  <link rel="alternate" type="text/html" href="https://sachachua.com/blog/tag/braindump" />
  <id>https://sachachua.com/blog/tag/braindump/feed/atom/index.xml</id>
  <generator uri="https://11ty.dev">11ty</generator>
	<updated>2013-04-02T07:00:00Z</updated>
<entry>
		<title type="html">Brainstorming ways to help build the Emacs community</title>
		<link rel="alternate" type="text/html" href="https://sachachua.com/blog/2013/04/brainstorming-ways-to-help-build-the-emacs-community/"/>
		<author><name><![CDATA[Sacha Chua]]></name></author>
		<updated>2013-04-01T01:49:26Z</updated>
    <published>2013-04-02T07:00:00Z</published>
    <category term="emacs" />
		<id>https://sachachua.com/blog/?p=24633</id>
		<content type="html"><![CDATA[<p>John Wiegley and I had lots of fun brainstorming ways to help move Emacs forward, particularly as I’m carving out more of my time to focus on Emacs. Here’s what we talked about:</p>
<p><strong>A rough outline of things to flesh out into articles/chapters:</strong></p>
<ul>
<li>productivity, org-mode</li>
<li>development
<ul>
<li>emacs lisp</li>
<li>haskel, rails, java, and other languages…</li>
</ul>
</li>
<li>writing</li>
<li>e-mail</li>
<li>IRC/Twitter/FB</li>
<li>web</li>
<li>games and diversions</li>
<li>documentation</li>
<li>learning and discovery</li>
</ul>
<p><strong>Learning Emacs development:</strong></p>
<ul>
<li>tools</li>
<li>cons cells</li>
<li>macros, quoting</li>
<li>control structures</li>
<li>Emacs structures: windows, buffers, text properties, etc.</li>
<li>lambdas</li>
<li>libraries</li>
</ul>
<p><strong>Ideas for visualizations:</strong></p>
<ul>
<li>#emacs word cloud or URL frequency/analysis</li>
<li>IUseThis for Emacs, maybe with annotations</li>
</ul>
<p><strong>Cookbook: </strong></p>
<ul>
<li>PLEAC for Emacs? Emacs Lisp cookbook?</li>
<li>Coding patterns</li>
</ul>
<p><strong>IDE challenges:</strong></p>
<ul>
<li>IntelliSense</li>
<li>Excellent project browsing</li>
<li>Refactoring</li>
<li>Integrated test harnesses</li>
<li>Asynchronous operation</li>
<li>Performance (especially of code analysis and navigation tools)</li>
</ul>
<p><strong>Target communities/audiences?</strong></p>
<ul>
<li>Emacs beginners: getting more into Emacs, learning more about packages, customizing Emacs; learning path through packages, maybe with time estimates?</li>
<li>Emacs intermediate: tweaking Emacs, getting into Emacs Lisp, contributing upstream; need to update Writing GNU Emacs Extensions</li>
<li>Keyboard enthusiasts: keyboard shortcuts, customizability</li>
<li>Non-developers (writers, scientists, mathematicians, etc.): Context-specific functionality, starter kits, easy installs, articles, screencasts – learn from Aquamacs, Ready Lisp. Pre-built Org starter kits? screencasts, interactive tutorials, games as introductions</li>
<li>Users of defunct editors: migrated features, migration guides</li>
<li>IDE users: integration with other parts of life</li>
<li>Vim users: configurability envy, migration/emulation</li>
</ul>
<p><strong>Emacs performance: </strong>elp, memory-use-counts, garbage collection, algorithms, cookbook, core work</p>
<p><strong>Discovery:</strong></p>
<ul>
<li>packages: popularity, reverse dependency graph, URL log for #emacs, 24 packages for Christmas and other blog series, IUseThis, reminders to be lazier / stories for inspiration</li>
<li>EmacsWiki: guided tour, CSS design</li>
</ul>
<p><strong>Imagining awesomeness in 5 years: </strong>Responsive editor that’s easy to set up; SEO so that people can find useful resources; context/goal-specific documentation; regular virtual show&amp;tell</p>
<p><strong>Imagining nonawesomeness: </strong>Weak async; marginal/niche; people moving away to other editors because of growing gaps; performance issues; unmaintained code; developer burnout</p>
<p><strong>EmacsConf:</strong> mailing list for next year, venue?</p>
<p>&nbsp;</p>
<p>Here’s what I’m looking forward to devoting some of my time to:</p>
<p><strong>Write and draw</strong></p>
<ul>
<li>EmacsWiki page updates</li>
<li>Guided tours</li>
<li>Emacs Lisp cookbook</li>
<li>Package reviews</li>
<li>Interviews with people so that they can share their tips (incl. screencast and transcript)</li>
</ul>
<p><strong>Analyze</strong></p>
<ul>
<li>Package use</li>
<li>Performance</li>
<li>Logs</li>
</ul>
<p><strong>Learn</strong></p>
<ul>
<li>Performance optimization (Emacs Lisp and core)</li>
<li>Package descriptions and use</li>
</ul>
<p><strong>Code</strong></p>
<ul>
<li>Issues</li>
<li>Feature requests</li>
<li>Integration</li>
<li>New code</li>
</ul>
<p>Lots of possibilities!</p>
<p>You can <a href="https://sachachua.com/blog/2013/04/brainstorming-ways-to-help-build-the-emacs-community/#comment">view 19 comments</a> or <a href="mailto:sacha@sachachua.com?subject=Comment%20on%20https%3A%2F%2Fsachachua.com%2Fblog%2F2013%2F04%2Fbrainstorming-ways-to-help-build-the-emacs-community%2F&body=Name%20you%20want%20to%20be%20credited%20by%20(if%20any)%3A%20%0AMessage%3A%20%0ACan%20I%20share%20your%20comment%20so%20other%20people%20can%20learn%20from%20it%3F%20Yes%2FNo%0A">e-mail me at sacha@sachachua.com</a>.</p>]]></content>
		</entry>
</feed>