https://devsummit.aspirationtech.org/api.php?action=feedcontributions&user=Rob&feedformat=atomDevSummit - User contributions [en]2024-03-29T02:31:07ZUser contributionsMediaWiki 1.35.1https://devsummit.aspirationtech.org/index.php?title=Fundraising:_How_foundations_think&diff=3232Fundraising: How foundations think2023-12-11T05:49:33Z<p>Rob: fixed a couple of typos</p>
<hr />
<div>* Money is for solving problems<br />
* Budget and general operating is not a motivating factor<br />
* "Othering" is not good; foundations are peers<br />
* two types of money: "living money" vs "dead money"<br />
* foundations are more risk averse<br />
* the power of program officers at foundations to get things done is almost exclusively to write checks.<br />
* program officers want to push grantees into horizontal grants rather than their specific program area (so that it doesn't come out of their allocation)<br />
* break up the interactions to interactions<br />
** The first interaction should be an offer to help the foundation <br />
** The second or third interaction should be about potentially asking for money<br />
* fundraising from foundations is "sales"<br />
* ask foundations about their strategy (because they love to talk about their strategy)<br />
* business meeetings all have the same structure. Leverage the five minutes in the beginning of the meeting to get them to talk about themselves.<br />
* engagement is in three phases: intellectual; creative; emotional<br />
* cold calls are last resort; seek out warm introductions<br />
* four ways to scope out opportunities<br />
** desk research<br />
** "who else should I talk to" over coffee<br />
** opportunistic<br />
** ???<br />
* meeting foundations at conference<br />
** make sure you are interesting; don't try to get funded<br />
** get someone to say to themselves: "hmmm, that was interesting. how would that work?"<br />
** first rule of pitching: never pitch</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Project_management&diff=3087Project management2022-11-18T07:45:29Z<p>Rob: Adding some links (not entirely indiscriminately)</p>
<hr />
<div>==Project management tools == <br />
<br />
* (open) [https://en.wikipedia.org/wiki/Redmine Redmine]<br />
* (open) [https://en.wikipedia.org/wiki/Bugzilla Bugzilla]<br />
* (open) [https://en.wikipedia.org/wiki/Phabricator Phabricator]<br />
* Jira<br />
* Trello<br />
* Github Issues<br />
* (open) [https://en.wikipedia.org/wiki/Gitlab Gitlab]<br />
* (open) [https://0xACAB.org 0xACAB.org] (“Hexacab”)<br />
* Asana<br />
* Microsoft Project<br />
* Wikis<br />
** (open) [https://en.wikipedia.org/wiki/MediaWiki MediaWiki]<br />
** (open) [https://en.wikipedia.org/wiki/Dokuwiki Dokuwiki]<br />
** Confluence<br />
<br />
<br />
== Systems ==<br />
* [https://en.wikipedia.org/wiki/Gantt Gantt]<br />
* [https://en.wikipedia.org/wiki/Kanban Kanban]<br />
<br />
== Other stuff ==<br />
<br />
* Anchoring role<br />
* Patterns<br />
* Being organized on behalf of unorganized people<br />
* Unsticking the stuck things<br />
* Parallel vs sequential execution of tasks<br />
* Checklists<br />
* [https://en.wikipedia.org/wiki/Checklist_Manifesto Checklist Manifesto] – Atul Gawande<br />
** (see also [https://www.newyorker.com/magazine/2007/12/10/the-checklist "The Checklist"] - Atul Gawande, December 2007, ''The New Yorker'')<br />
* Project management allows offloading brainspace for other people<br />
* Project <br />
* Personal checklists<br />
* “[https://en.wikipedia.org/wiki/Nonviolent_Communication Nonviolent Communication; A language]” – Michael Rosenberg<br />
* Design world has tragic expression of unmet needs<br />
* Is there an open source project that values project management?<br />
* Who is the “decider”?<br />
* It’s possible to “snow” the “facilitator”.<br />
* How important is domain expertise to facilitate?<br />
* Are Gantt charts dead? (No)<br />
* Having agreed metric of success is critical (to distinquish between “is the wireframe started?” and “is the wireframe done?”<br />
* How does the sales process fit in? <br />
* How do legal documents fit in? (having artifacts is important)<br />
* [https://youtu.be/_IxqdAgNJck Van Halen M&Ms story]<br />
* How do we decentralize? ''still unanswered''</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Project_management&diff=3081Project management2022-11-18T00:18:08Z<p>Rob: Rough notes from project management</p>
<hr />
<div>==Project management tools == <br />
<br />
* (open) Redmine<br />
* (open) Bugzilla<br />
* (open) Phabricator<br />
* Jira<br />
* Trello<br />
* Github Issues<br />
* (open) Gitlab<br />
* 0xACAB.org (“Hexacab”)<br />
* Asana<br />
* Microsoft Project<br />
* (open) Wiki (MediaWiki)<br />
<br />
== Systems ==<br />
* Gantt<br />
* Kanban<br />
<br />
== Other stuff ==<br />
<br />
* Anchoring role<br />
* Patterns<br />
* Being organized on behalf of unorganized people<br />
* Unsticking the stuck things<br />
* Parallel vs sequential execution of tasks<br />
* Checklists<br />
* Checklist Manifesto – Atul Gawande<br />
* Project management allows offloading brainspace for other people<br />
* Project <br />
* Personal checklists<br />
* “Non Violent Communication; A language” – Michael Rosenberg<br />
* Design world has tragic expression of unmet needs<br />
* Is there an open source project that values project management?<br />
* Who is the “decider”?<br />
* It’s possible to “snow” the “facilitator”.<br />
* How important is domain expertise to facilitate?<br />
* Are Gantt charts dead? (No)<br />
* Having agreed metric of success is critical (to distinquish between “is the wireframe started?” and “is the wireframe done?”<br />
* How does the sales process fit in? <br />
* How do legal documents fit in? (having artifacts is important)<br />
* Van Halen M&Ms story.<br />
* How do we decentralize? ''still unanswered''</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Technology_and_mental_health&diff=3080Technology and mental health2022-11-18T00:14:14Z<p>Rob: Rought notes from this morning</p>
<hr />
<div>Everyone discussed personal reasons for being at session<br />
<br />
Corpus of psychological help site partnered with for profit<br />
<br />
Discussion of the challenges of free tools (like Facebook or Discord) to emote, and how it can be problematic<br />
<br />
Remote worker mental health.<br />
<br />
Gaggle – suicide prevention tool for kids. - how to moderate without relying on keywords but still self-regulating<br />
<br />
In a meeting or isolated for remote<br />
<br />
Stepping away from tech is helpful, but also hurts remote connection.<br />
<br />
Clearly delineation about where and when to emote with tech is helpful, and providing spaces where emoting is okay is helpful.<br />
<br />
“Professionalism” means “emotions aren’t allowed”<br />
<br />
Stepping away from tech should be allowed and encouraged<br />
<br />
Personal notetaking stuff: https://myndmess.org</div>Robhttps://devsummit.aspirationtech.org/index.php?title=New_and_Emerging_Web_Tech&diff=3054New and Emerging Web Tech2022-01-19T08:42:25Z<p>Rob: /* Javascript frameworks */ linking to a more helpful document</p>
<hr />
<div>Minutes from our 3pm Friday (November 8, 2019) session<br />
<br />
== Introductions ==<br />
We started talking about the technologies that people wanted to talk about. Many people in the room were comfortable with the basic LAMP stack. Some of the folks were working with Rails, Node.js, and other tech. Many had worked with Drupal, Backdrop, Wordpress, Backdrop, CiviCRM, and other tech geared toward smaller organizations.<br />
<br />
Some discussion ensued about the desire from techs in some organization use "what the cool kids are using", and how sensible it is for non-profits with limited budgets to venture out onto the bleeding edge.<br />
<br />
== Outline ==<br />
Here was the proposed outline for the conversation<br />
<br />
* Headless<br />
* Static<br />
* Vue.js<br />
* SMS<br />
* Docker + other container technology<br />
* Hosting services<br />
* Languages/frameworks<br />
<br />
We then started discussing the last one first....<br />
<br />
== Languages folks want to work on ==<br />
Using new ones (Go, Rust) versus older ones like Python?<br />
<br />
Static compiled: Go, Rust, Swift<br />
<br />
Functional: Haskell, Elixir<br />
<br />
== Headless and static websites ==<br />
We discussed the advantages of static websites, which scale really well because the HTML is pregenerated.<br />
<br />
What does "serverless" mean? Server spun up and spun down on a per-request basis. (like what AWS Lambda proports to do)<br />
<br />
What does "headless" mean? Having a client-server split between a simple front-end system and a CMS that is responsible for the database work.<br />
<br />
Distinction between headless-decoupled and static<br />
<br />
* Headless - Website is actually processing data<br />
* Static - no on-request processing. HTML is generated on change.<br />
<br />
== Content management systems vs headless ==<br />
<br />
What's cool about CMS systems: you get all sorts of included bits that implement technology "for free".<br />
<br />
The promise of static websites: Static sites allow the browser compose the data.<br />
<br />
The reality: Are single page Javascript applications worth it? There are serious client-side performance implications of using the browser to render the raw data.<br />
<br />
== Static site generators ==<br />
<br />
Github provides Jekyll-compatible static site hosting<br />
<br />
Tools briefly discussed:<br />
<br />
* Jekyll<br />
* Gatsby<br />
* Hugo<br />
<br />
Static site generators promise greater security.<br />
<br />
Example of a static site generator from 15 years ago: [https://www.perl.com/pub/2004/08/27/bricolage.html/ Bricolage].<br />
<br />
Wordpress has a static site generator now.<br />
<br />
Varnish and other caching proxies have program<br />
<br />
Pantheon offers Varnish<br />
<br />
== Javascript frameworks ==<br />
<br />
(see "[https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f How it feels to learn JavaScript in 2016]")<br />
<br />
* React - maintained/promoted by Facebook<br />
* Vue.js - some folks in the room believe this is overwhelming than others. VueJS is good for custom filterable maps and events scheduling<br />
* Angular - maintained/promoted by Google (see also HTML Web Components)<br />
<br />
Is there an undercurrent we should be paying attention to? We're going through an adolescence as an industry. The good news: newer employees (e.g. interns in programs like GSoC or Outreachy) seem to catch on quickly. Huge companies distort the ecosystem and make it difficult to objectively evaluate options.<br />
<br />
'''UPDATE FOR 2021''': - see https://www.codeinwp.com/blog/angular-vs-vue-vs-react/<br />
<br />
== Containers ==<br />
<br />
We dove into discussion of container management and orchestration technology like Docker, Kubernetes, and Swarm.<br />
<br />
What is a container? VM that has the state saved.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Working_with_neurodiverse_people,_and_tips,_tools,_strategies,_support_for_those_of_us_with_brains_that_need_structure_and_systems&diff=3053Working with neurodiverse people, and tips, tools, strategies, support for those of us with brains that need structure and systems2022-01-12T06:54:46Z<p>Rob: Not linking to User:Rob since that doesn't really work here (even if Special:Contributions/Rob does)</p>
<hr />
<div>Tips, tools, strategies, support for those of us with brains that need structure and systems (RobLa)<br />
<br />
* Fun video to watch while we wait: https://youtu.be/UEkF5o6KPNI<br />
* https://myndmess.org<br />
* https://guillaumepaumier.com/2015/07/29/autistic-wikipedian/<br />
* https://en.wikipedia.org/wiki/Gish_gallop<br />
* https://en.wikipedia.org/wiki/Gaslighting<br />
* https://en.wikipedia.org/wiki/Big_Tech<br />
* We spoke about neurodivergence in the free and open source software community<br />
* We also spoke about the difficulty of working with the "free knowledge community"<br />
** https://en.wikipedia.org/wiki/Definition_of_Free_Cultural_Works<br />
* Mainly, the "session leader" spoke a lot about things that can be described in a few short hours by a half-a-dozen podcast episodes about Wikipedia:<br />
** https://open.spotify.com/show/1q5QW052FV2Paxqj1gweLp<br />
<br />
== Footnotes ==<br />
<references/></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Working_with_neurodiverse_people,_and_tips,_tools,_strategies,_support_for_those_of_us_with_brains_that_need_structure_and_systems&diff=3052Working with neurodiverse people, and tips, tools, strategies, support for those of us with brains that need structure and systems2022-01-12T06:52:44Z<p>Rob: Adding a link to a podcast that sums up a lot of what I ended up talking about</p>
<hr />
<div>Tips, tools, strategies, support for those of us with brains that need structure and systems (RobLa)<br />
<br />
* Fun video to watch while we wait: https://youtu.be/UEkF5o6KPNI<br />
* https://myndmess.org<br />
* https://guillaumepaumier.com/2015/07/29/autistic-wikipedian/<br />
* https://en.wikipedia.org/wiki/Gish_gallop<br />
* https://en.wikipedia.org/wiki/Gaslighting<br />
* https://en.wikipedia.org/wiki/Big_Tech<br />
* We spoke about neurodivergence in the free and open source software community<br />
* We also spoke about the difficulty of working with the "free knowledge community"<br />
** https://en.wikipedia.org/wiki/Definition_of_Free_Cultural_Works<br />
* Mainly, [[User:Rob]] spoke a lot about things that can be described in a few short hours by a half-a-dozen podcast episodes about Wikipedia:<br />
** https://open.spotify.com/show/1q5QW052FV2Paxqj1gweLp<br />
<br />
== Footnotes ==<br />
<references/></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2935Book Recommendations2020-11-20T07:14:55Z<p>Rob: /* Recommendations from past Dev Summits */ using the comment field for "Architecture of Open Source Applications", since each book is an anthology</p>
<hr />
<div>== Book (and other!) Recommendations from 2020 Dev Summit ==<br />
<br />
* ''Your recommendation here!''<br />
* The power of ritual : turning everyday activities into soulful practices / Casper ter Kuile.- thanks to Matt Fitzgerald for the recommendation<br />
* {{Book|title=How to Be an Antiracist|author=Ibram X. Kendi|year=2019|url=https://www.worldcat.org/search?q=isbn%3A9780525509288}}<br />
* {{Book|author=Steve Martin|title=Born Standing Up|url=https://en.wikipedia.org/wiki/Born_Standing_Up|year=2007|comment=all about the banjo!}}<br />
<br />
== Recommendations from past Dev Summits ==<br />
<br />
* Algorithms of Oppression – Safiya Umoja Noble<br />
* Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor – Virginia Eubanks<br />
* Programmed Inequality: How Britain Discarded Women Technologists and Lost Its Edge in Computing – Marie Hicks<br />
* Race After Technology – Ruha Benjamin<br />
* Dark Matters – Simone Browne<br />
* Artificial Unintelligence – Meredith Broussard<br />
* Through Google-Colored Glass(es): Design, Emotion, Class, and Wearables as Commodity and Control – Safiya Umoja Noble, Sarah T. Roberts<br />
* The Intersectional Internet: Race, Sex, Class, and Culture Online – Safiya Umoja Noble, Brendesha M. Tynes<br />
* Behind the Screen: Content Moderation in the Shadows of Social Media – Sarah T.Roberts<br />
* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 2|author=many authors|url=https://aosabook.org/|year=2012|comment=edited by Amy Brown and Greg Wilson}}<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 1|author=many authors|url=https://aosabook.org/|year=2011|comment=edited by Amy Brown and Greg Wilson}}<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2934Book Recommendations2020-11-20T07:11:26Z<p>Rob: /* Book (and other!) Recommendations from 2020 Dev Summit */ using Template:Book for "How to Be an Antiracist" line, and adding comment to "Born Standing Up"</p>
<hr />
<div>== Book (and other!) Recommendations from 2020 Dev Summit ==<br />
<br />
* ''Your recommendation here!''<br />
* The power of ritual : turning everyday activities into soulful practices / Casper ter Kuile.- thanks to Matt Fitzgerald for the recommendation<br />
* {{Book|title=How to Be an Antiracist|author=Ibram X. Kendi|year=2019|url=https://www.worldcat.org/search?q=isbn%3A9780525509288}}<br />
* {{Book|author=Steve Martin|title=Born Standing Up|url=https://en.wikipedia.org/wiki/Born_Standing_Up|year=2007|comment=all about the banjo!}}<br />
<br />
== Recommendations from past Dev Summits ==<br />
<br />
* Algorithms of Oppression – Safiya Umoja Noble<br />
* Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor – Virginia Eubanks<br />
* Programmed Inequality: How Britain Discarded Women Technologists and Lost Its Edge in Computing – Marie Hicks<br />
* Race After Technology – Ruha Benjamin<br />
* Dark Matters – Simone Browne<br />
* Artificial Unintelligence – Meredith Broussard<br />
* Through Google-Colored Glass(es): Design, Emotion, Class, and Wearables as Commodity and Control – Safiya Umoja Noble, Sarah T. Roberts<br />
* The Intersectional Internet: Race, Sex, Class, and Culture Online – Safiya Umoja Noble, Brendesha M. Tynes<br />
* Behind the Screen: Content Moderation in the Shadows of Social Media – Sarah T.Roberts<br />
* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 2|author=edited by Amy Brown and Greg Wilson|url=https://aosabook.org/|year=2012}}<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 1|author=edited by Amy Brown and Greg Wilson|url=https://aosabook.org/|year=2011}}<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book/en&diff=2933Template:Book/en2020-11-20T06:53:13Z<p>Rob: /* Example One */ adding example of the new comment parameter</p>
<hr />
<div><noinclude>'''Template:Book/en''' contains the English-language documentation for [[Template:Book]].</noinclude><br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
|comment=available to borrow from OpenLibrary.org<br />
}}</nowiki></code><br />
<br />
==== Result One ====<br />
<br />
* {{Book <br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
|comment=available to borrow from OpenLibrary.org<br />
}}<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
==== Result Two ====<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
=== Example Three ===<br />
<br />
This template is "forgiving". It's possible to leave all of the parameters off:<br />
<br />
<code>* <nowiki>{{Book}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book}}<br />
<br />
When the "<code>title</code>" parameter is omitted, some filler text (e.g. "some silly book") is inserted. When the "<code>author</code>" parameter is omitted, different filler text is inserted.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2932Template:Book2020-11-20T06:49:17Z<p>Rob: Adding a "comment" parameter which allows for freeform text</p>
<hr />
<div><noinclude>'''Template:Book''' is a [[MediaWiki]] template. To edit the examples below, visit [[Template:Book/en]]. {{Template:Book/en}}</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} (<{{{url|FIXME}}}>, {{{comment|}}})</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2931Book Recommendations2020-11-20T06:44:08Z<p>Rob: /* Recommendations from past Dev Summits */ Fixing the link to "Architecture of Open Source Applications" and noting there are two volumes written in two consecutive years</p>
<hr />
<div>== Book (and other!) Recommendations from 2020 Dev Summit ==<br />
<br />
* ''Your recommendation here!''<br />
* The power of ritual : turning everyday activities into soulful practices / Casper ter Kuile.- thanks to Matt Fitzgerald for the recommendation<br />
* How to Be an Antiracist by Ibram X. Kendi<br />
* {{Book|author=Steve Martin|title=Born Standing Up|url=https://en.wikipedia.org/wiki/Born_Standing_Up|year=2007}}<br />
<br />
== Recommendations from past Dev Summits ==<br />
<br />
* Algorithms of Oppression – Safiya Umoja Noble<br />
* Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor – Virginia Eubanks<br />
* Programmed Inequality: How Britain Discarded Women Technologists and Lost Its Edge in Computing – Marie Hicks<br />
* Race After Technology – Ruha Benjamin<br />
* Dark Matters – Simone Browne<br />
* Artificial Unintelligence – Meredith Broussard<br />
* Through Google-Colored Glass(es): Design, Emotion, Class, and Wearables as Commodity and Control – Safiya Umoja Noble, Sarah T. Roberts<br />
* The Intersectional Internet: Race, Sex, Class, and Culture Online – Safiya Umoja Noble, Brendesha M. Tynes<br />
* Behind the Screen: Content Moderation in the Shadows of Social Media – Sarah T.Roberts<br />
* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 2|author=edited by Amy Brown and Greg Wilson|url=https://aosabook.org/|year=2012}}<br />
* {{Book|title=Architecture of Open Source Applications, Vol. 1|author=edited by Amy Brown and Greg Wilson|url=https://aosabook.org/|year=2011}}<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help:Talk&diff=2930Help:Talk2020-11-20T06:35:17Z<p>Rob: Stub page for Help:Talk</p>
<hr />
<div>'''Help:Talk''' is a help page for the Aspiration Tech wiki. Instructions coming soon! (insert animated gif of construction worker digging a hole)<br />
<br />
<br />
[[Category:Help]]</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2929Template:Book2020-11-20T06:17:55Z<p>Rob: Some fixes that work on a newer version of MediaWiki. This may work on this version of MediaWiki too...</p>
<hr />
<div><noinclude>'''Template:Book''' is a [[MediaWiki]] template. To edit the exmaples below, visit [[Template:Book/en]]. {{Template:Book/en}}</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book/en&diff=2928Template:Book/en2020-11-20T06:14:35Z<p>Rob: Putting the English-language examples in a subpage</p>
<hr />
<div><noinclude>'''Template:Book/en''' contains the English-language documentation for [[Template:Book]].</noinclude><br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
<br />
==== Result One ====<br />
<br />
* {{Book <br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
==== Result Two ====<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
=== Example Three ===<br />
<br />
This template is "forgiving". It's possible to leave all of the parameters off:<br />
<br />
<code>* <nowiki>{{Book}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book}}<br />
<br />
When the "<code>title</code>" parameter is omitted, some filler text (e.g. "some silly book") is inserted. When the "<code>author</code>" parameter is omitted, different filler text is inserted.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2927Template:Book2020-11-20T05:48:24Z<p>Rob: Hardcoding the result of {{Book}}</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
Result<br />
* {{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})<br />
<br />
=== Example Three ===<br />
<br />
This template is "forgiving". It's possible to leave all of the parameters off:<br />
<br />
<code>* <nowiki>{{Book}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{subst:Book}}<br />
<br />
When the "<code>title</code>" parameter is omitted, some filler text (e.g. "some silly book") is inserted. When the "<code>author</code>" parameter is omitted, different filler text is inserted.<br />
<br />
</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})<br />
<br />
<br />
</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2926Template:Book2020-11-20T05:44:41Z<p>Rob: Making the {{Book}} template more forgiving</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
Result<br />
* {{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})<br />
<br />
=== Example Three ===<br />
<br />
This template is "forgiving". It's possible to leave all of the parameters off:<br />
<br />
<code>* <nowiki>{{Book}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book}}<br />
<br />
When the "<code>title</code>" parameter is omitted, some filler text (e.g. "some silly book") is inserted. When the "<code>author</code>" parameter is omitted, different filler text is inserted.<br />
<br />
</noinclude><includeonly><i>{{{title|some silly book}}}</i> ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})<br />
<br />
<br />
</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2925Template:Book2020-11-20T05:29:22Z<p>Rob: Adding a missing squirrelly bracket</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
Result<br />
* {{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
</noinclude><includeonly>Book: "{{{title|}}}" ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2924Template:Book2020-11-20T05:28:32Z<p>Rob: Making the wikitext generated by this template a little more compact</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
Result<br />
* {{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
</noinclude><includeonly>Book: "{{{title|}}" ({{{year|timeless}}}) by {{{author|someone}}} ({{{url|FIXME}}})</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2923Book Recommendations2020-11-20T05:22:12Z<p>Rob: Adding Steve Martin's memoir "Born Standing Up"</p>
<hr />
<div>== Book (and other!) Recommendations from 2020 Dev Summit ==<br />
<br />
* ''Your recommendation here!''<br />
* The power of ritual : turning everyday activities into soulful practices / Casper ter Kuile.- thanks to Matt Fitzgerald for the recommendation<br />
* How to Be an Antiracist by Ibram X. Kendi<br />
* {{Book|author=Steve Martin|title=Born Standing Up|url=https://en.wikipedia.org/wiki/Born_Standing_Up|year=2007}}<br />
<br />
== Recommendations from past Dev Summits ==<br />
<br />
* Algorithms of Oppression – Safiya Umoja Noble<br />
* Automating Inequality: How High-Tech Tools Profile, Police, and Punish the Poor – Virginia Eubanks<br />
* Programmed Inequality: How Britain Discarded Women Technologists and Lost Its Edge in Computing – Marie Hicks<br />
* Race After Technology – Ruha Benjamin<br />
* Dark Matters – Simone Browne<br />
* Artificial Unintelligence – Meredith Broussard<br />
* Through Google-Colored Glass(es): Design, Emotion, Class, and Wearables as Commodity and Control – Safiya Umoja Noble, Sarah T. Roberts<br />
* The Intersectional Internet: Race, Sex, Class, and Culture Online – Safiya Umoja Noble, Brendesha M. Tynes<br />
* Behind the Screen: Content Moderation in the Shadows of Social Media – Sarah T.Roberts<br />
* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* [https://aosabook.org/ Architecture of Open Source Applications] - edited by Amy Brown and Greg Wilson<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=User_talk:Rob&diff=2922User talk:Rob2020-11-20T05:17:00Z<p>Rob: See Template:Book to see the trouble I've caused.</p>
<hr />
<div>Hi, my name is Rob, and this is my talk page! See [[Help:Talk]] to learn more about talk pages.<br />
<br />
== Template:Book ==<br />
<br />
I created a new template on this wiki. See [[Template:Book]] to see the trouble I've caused. -- [[User:Rob|Rob]] ([[User talk:Rob|talk]]) 05:17, 20 November 2020 (UTC)</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template_talk:Book&diff=2921Template talk:Book2020-11-20T05:15:15Z<p>Rob: Noting that many yaks were shaved to create this template....</p>
<hr />
<div>This is a "Talk" page. See [[Help:Talk]] to learn more about talk pages.<br />
<br />
== New template ==<br />
<br />
I see that y'all aren't using templates here. I don't entirely blame you; they're a mindbender. I think I want to try out this newly-created template for the [[Book Recommendations]] page. The creation of this page was result of me doing a lot of "[https://wikipedia.org/wiki/Yak_shaving yak shaving]", but I assure you, no yaks were harmed! -- [[User:Rob|Rob]] ([[User talk:Rob|talk]]) 05:15, 20 November 2020 (UTC)</div>Robhttps://devsummit.aspirationtech.org/index.php?title=MediaWiki&diff=2920MediaWiki2020-11-20T05:08:10Z<p>Rob: #REDIRECT Help:MediaWiki (You're using MediaWiki; you might need some help....)</p>
<hr />
<div>#REDIRECT [[Help:MediaWiki]]<br />
<br />
You're using MediaWiki; you might need some help....</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2919Template:Book2020-11-20T05:06:09Z<p>Rob: Fixed up the "Book" template a little bit</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Examples ==<br />
<br />
=== Example One ===<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}</nowiki></code><br />
Result<br />
* {{Book<br />
|title=MediaWiki<br />
|author=Daniel J. Barrett<br />
|year=2009<br />
|url=https://openlibrary.org/works/OL17309374W/MediaWiki<br />
}}<br />
<br />
<br />
=== Example Two ===<br />
It's even possible to use this template on a single line of wikitext:<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett}}</nowiki></code><br />
<br />
Result:<br />
<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett}}<br />
<br />
Leaving parameters out (as above) will just cause the resulting text to look a little weird. But it's a wiki; things often look weird.<br />
<br />
</noinclude><includeonly>Book: "{{{title|}}}" by {{{author|}}} in the year {{{year|?}}}, available at {{{url|FIXME}}}</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Template:Book&diff=2918Template:Book2020-11-20T04:57:56Z<p>Rob: First attempt at a "Book" template. I need to play with this some more to get it working</p>
<hr />
<div><noinclude><br />
<br />
'''[[Template:Book]]''' is a [[MediaWiki]] template<br />
<br />
== Example ==<br />
<br />
This is an example for using "Template:Book"<br />
<code>* <nowiki>{{Book|title=MediaWiki|author=Daniel J. Barrett|year=2009}}</nowiki></code><br />
Result<br />
* {{Book|title=MediaWiki|author=Daniel J. Barrett|year=2009}}<br />
</noinclude><includeonly>Book: "{{{title|}}}" by {{{author|}}} in the year {{{year|?}}}, available at FIXME https://openlibrary.org/works/OL17309374W/MediaWiki</includeonly></div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help&diff=2917Help2020-11-20T04:35:47Z<p>Rob: Help shouldn't be a redirect. So now it isn't.</p>
<hr />
<div>There are several pages on this website that are about "Help" you may receive.<br />
<br />
== Wiki ==<br />
<br />
This website (<code>devsummit.aspirationtech.org</code>) is a "wiki". <br />
<br />
* '''[https://en.wikipedia.org/wiki/Wiki "Wiki" on Wikipedia]''' - To learn more about wikis, read [https://en.wikipedia.org/wiki/Wiki the Wikipedia article about wikis].<br />
* '''[[Help:MediaWiki]]''' - This website runs MediaWiki. To learn more about using MediaWiki (either as an editor, or as a reader), visit one of the following web pages:<br />
*# [[Help:MediaWiki]] - for MediaWiki help specific to the version of MediaWiki this Aspiration Tech website is running.<br />
*# '''[https://www.mediawiki.org/wiki/Help:Contents User guide for MediaWiki]''' - this is a user guide from the creators and users of MediaWiki, hosted at mediawiki.org. It has been released into the public domain, and is often copied to other wikis that run MediaWiki.<br />
*# '''"[https://www.mediawiki.org/wiki/Manual:What_is_MediaWiki%3F What is MediaWiki?]"''' - this page (from the MediaWiki system administrators guide) describes MediaWiki.<br />
<br />
== Other pages ==<br />
<br />
There are other "Help" pages on this wiki:<br />
<br />
* [[Helping Non-Techies and Techies Collaborate to Make Great Software]] - a page that was created in 2008. As of this writing, the "Helping Non-Techies..." page hasn't been edited since May 2015.<br />
* [[Help build a CiviCRM Ecosystem]] - a page that was created in November 2014. As of this writing, the page about the CiviCRM ecosystem ''also'' hasn't been updated since May 2015.<br />
<br />
== Misc ==<br />
<br />
The page you are reading now ("Help" on <code>devsummit.aspirationtech.org</code>) was created in November 2020. The page history is available at https://devsummit.aspirationtech.org/index.php?title=Help&action=history</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help:MediaWiki&diff=2916Help:MediaWiki2020-11-20T03:46:13Z<p>Rob: Updated the title</p>
<hr />
<div>'''Help:MediaWiki''' is about getting help editing this wiki. This website uses "MediaWiki", which is the same software that is used by [https://wikipedia.org Wikipedia].<br />
<br />
To see the public-domain manual for MediaWiki, visit the MediaWiki.org website at the following address:<br />
<br />
* https://www.mediawiki.org/wiki/Help:Contents<br />
<br />
...or just click on the link above.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help:About&diff=2915Help:About2020-11-20T03:45:27Z<p>Rob: Rob moved page Help:About to Help:MediaWiki: Since this page is about getting help with MediaWiki, then "MediaWiki" should be in the title</p>
<hr />
<div>#REDIRECT [[Help:MediaWiki]]</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help:MediaWiki&diff=2914Help:MediaWiki2020-11-20T03:45:27Z<p>Rob: Rob moved page Help:About to Help:MediaWiki: Since this page is about getting help with MediaWiki, then "MediaWiki" should be in the title</p>
<hr />
<div>'''Help:About''' is about getting help editing this wiki. This website uses "MediaWiki", which is the same software that is used by [https://wikipedia.org Wikipedia].<br />
<br />
To see the public-domain manual for MediaWiki, visit the MediaWiki.org website at the following address:<br />
<br />
* https://www.mediawiki.org/wiki/Help:Contents<br />
<br />
...or just click on the link above.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help&diff=2913Help2020-11-20T03:39:00Z<p>Rob: #REDIRECT Help:About</p>
<hr />
<div>#REDIRECT [[Help:About]]<br />
<br />
This page redirects to [[Help:About]], which includes a link to the public-domain MediaWiki user manual.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Help:MediaWiki&diff=2912Help:MediaWiki2020-11-20T03:37:50Z<p>Rob: Basic "Help" page, toward which Help will be redirected....</p>
<hr />
<div>'''Help:About''' is about getting help editing this wiki. This website uses "MediaWiki", which is the same software that is used by [https://wikipedia.org Wikipedia].<br />
<br />
To see the public-domain manual for MediaWiki, visit the MediaWiki.org website at the following address:<br />
<br />
* https://www.mediawiki.org/wiki/Help:Contents<br />
<br />
...or just click on the link above.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=2020_Agenda&diff=29112020 Agenda2020-11-20T01:33:14Z<p>Rob: /* Social time (14.30 PT / 22.30 UTC) */ adding a fundraiser this evening (PST) for SCRAP to the event list</p>
<hr />
<div>__NOTOC__<br />
Aspiration events are first and foremost convened to strengthen the ties and social networks of activists, organizers, and technology practitioners in the nonprofit/nongovernmental sectors.<br />
<br />
The Dev Summit agenda is designed and facilitated using Aspiration's participatory model, in an environment where powerpoint slides are not a thing, and dialogue and collaboration drive the learning.<br />
<br />
Our philosophy centers around getting participants into small-group discussions where they can discuss topics they are passionate about and get answers to their questions and curiosities. Sessions at Aspiration events have particular traits; we de-emphasize broadcast behaviors and fetishizing expertism, and instead focus on working sessions that are self-organized whenever possible to meet the specific needs of those present, in accessible, inclusive ways.<br />
<br />
Please note: This is a truly dynamic agenda, and sessions are likely to move around and evolve. We thank everyone in advance for the flexibility.<br />
<br />
<br />
<br />
= Wednesday November 18 =<br />
<br />
== Opening Session (9.00 PT / 17.00 UTC) == <br />
<br />
Dev Summit 2020 will be called to order with a friendly and fast-paced kickoff that includes words of welcome, non-verbal participant introductions, along with overviews of the agenda, participation guidelines and meeting logistics.<br />
<br />
== Story sharing from across our community (10.05 PT / 18.05 UTC) == <br />
<br />
We'll start the program by lifting up stories and projects from across our network:<br />
<br />
* Campaigning and organizing for justice in Texas<br />
* What's new and what's happening with Tor Browser and Tor Community<br />
* Fundraising during Covid using open source tools<br />
* Access Now Digital Security Helpline: Supporting security needs of civil society groups & activists, journalists and human rights defenders<br />
* Gender-based violence: the tolls of raising awareness in Mexican online spaces during 2020<br />
* SignalBoost - Lessons from the real world of secure and anonymous organizing and protest<br />
* Organizing to build solidarity across the Decentralized Web community with the DWeb Principles<br />
* OpenStreetMap and the state of open mapping in 2020<br />
<br />
== Break (11.05 PT / 19.05 UTC) ==<br />
<br />
== Working Sessions I (11.20 PT / 19.20 UTC) ==<br />
<br />
Working sessions will invite participants to explore and share knowledge on topics identified in pre-event dialogues. Facilitators will briefly introduce the objective of each session, and participants may then elect to join the session of their choice.<br />
<br />
Confirmed sessions are below, and we look forward to co-creating additional sessions in each Working Sessions time slot!<br />
<br />
* Indigenous opinions on the state of tech: How we can leverage skills and organize within and outside of traditional tech culture<br />
* Moving an organization to a place where we can talk meaningfully about our mission and values<br />
* Leveraging our collective 'sense of crisis' to avoid going back to business-as usual<br />
* Running virtual meetings that have heart and don't suck<br />
* Campaigning for housing rights in East Los Angeles<br />
* Scaling of data portability: what is possible?<br />
* Relational organizing and the tension with technology<br />
<br />
== Closing Session (12.40 PT / 20.40 UTC) ==<br />
<br />
The closing session will invite participants to weigh in on what has been most useful during the course of Day 1, and refine their goals and priorities for the agenda of Day 2.<br />
<br />
== Adjourn (13.00 PT / 21.00 UTC) ==<br />
<br />
== Social time (14.30 PT / 22.30 UTC) ==<br />
<br />
We're still figuring out the plan, but we'll give folks options for hanging in more unstructured and hopefully non-annoying virtual spaces.<br />
<br />
* "'''[https://www.eventbrite.com/e/ruth-asawa-through-the-eyes-of-her-children-tickets-124151619837 Through The Eyes of Her Children]'''" - A virtual discussion about the legacy and impact of San Francisco-based artist Ruth Asawa through the eyes of two of her children. November 19 - 7pm PST - donation appreciated - all proceeds donated to SCRAP.<br />
<br />
= Thursday, November 19 =<br />
<br />
== Opening Session (9.00 PT / 17.00 UTC) ==<br />
<br />
The day will start with a summary of Day 1 reflections and a Day 2 Agenda Overview.<br />
<br />
== Working Sessions II (9.20 PT / 17.20 UTC) ==<br />
<br />
Confirmed sessions are below, and we look forward to co-creating additional sessions in each Working Sessions time slot!<br />
<br />
* Weaving collective care in our work and activism<br />
* Strategy and leadership vs tools: striking a sustainable balance<br />
* The state of press freedom and what you can do to help Freedom of the Press Foundation<br />
* Advocating for health and safety with a "progressive" administration<br />
* Sharing and comparing “believable accountability processes”: Peer sharing on what has worked and what hasn’t worked<br />
* Security practices cross-share<br />
<br />
== Break (10.50 PT / 18.50 UTC) ==<br />
<br />
== Skillshare and Demo Session (11.10 PT / 19.10 UTC) ==<br />
<br />
Participants will be encouraged to share any skill they desire. The session will be structured so as to minimize group size and maximize 1-on-1 sharing opportunities.<br />
<br />
* Add your skill offers or skill requests here: https://pad.riseup.net/p/aspirationdevsummit20-skillshare<br />
<br />
== Closing Session (12.40 PT / 20.40 UTC) ==<br />
<br />
Participants to weigh in on what has been most useful during the course of Day 2, and register their goals and priorities for the agenda of Day 3.<br />
<br />
== Adjourn (13.00 PT / 21.00 UTC) ==<br />
<br />
== Open Mic! (14.30 PT / 22.30 UTC) ==<br />
<br />
Got a musical skill, spoken word to speak, a tall tale, a non-marginalizing joke, or something else you would like to share with the group?<br />
<br />
= Friday, November 20 =<br />
<br />
== Opening Session (9.00 PT / 17.00 UTC) ==<br />
<br />
The day will start with a summary of Day 2 reflections and a Day 3 Agenda Overview.<br />
<br />
== Working Sessions III (9.20 PT / 17.20 UTC) ==<br />
<br />
Confirmed sessions are below, and we look forward to co-creating additional sessions in each Working Sessions time slot!<br />
* Coops Solidarity Session<br />
* Using technology to identify police who refuse to identify themselves<br />
* What EFF is working on and what you can do to support them<br />
* Practicing self care and avoiding burnout in the time of Covid<br />
* Challenges and lessons on moving to work from home with immigrant populations<br />
* Learnings and best practices for working with youth during a global pandemic<br />
<br />
== Break (10.50 PT / 18.50 UTC) ==<br />
<br />
== Working Sessions IV (11.10 PT / 19.10 UTC) ==<br />
<br />
* Facilitating leadership development as a group learning process<br />
* Remote work practices cross-share<br />
* Mentoring and integrating newer tech people on teams (and benefiting from fresh energy)<br />
* How to do malware analysis<br />
* Powermapping and data journalism research<br />
* Product Management for Nonprofits<br />
* Organizing mutual aid and trauma-sensitive support after the fires<br />
<br />
== Closing Session 12.40 PT / 20.40 UTC) ==<br />
<br />
The group will summarize key outcomes from the event, share appreciations and bring the meeting to a close.<br />
<br />
== Adjourn (13.00 PT / 21.00 UTC) ==<br />
<br />
Dev Summit 2020 is done, done and done-r!<br />
<br />
== Self-organized meetups and other fun ==<br />
<br />
We will invite decentralized leadership to create a range of opt-in spaces for socializing and easing into the weekend.<br />
<br />
=Job Board and Book Recommendations=<br />
<br />
Hiring or job seeking?<br />
<br />
* Dev Summit 2020 [[Job Board]]<br />
<br />
Reading or watching something you want others to know about?<br />
<br />
* Dev Summit 2020 [[Book Recommendations]]</div>Robhttps://devsummit.aspirationtech.org/index.php?title=New_and_Emerging_Web_Tech&diff=2890New and Emerging Web Tech2020-11-18T08:30:56Z<p>Rob: Noting that the notes were from 2019....</p>
<hr />
<div>Minutes from our 3pm Friday (November 8, 2019) session<br />
<br />
== Introductions ==<br />
We started talking about the technologies that people wanted to talk about. Many people in the room were comfortable with the basic LAMP stack. Some of the folks were working with Rails, Node.js, and other tech. Many had worked with Drupal, Backdrop, Wordpress, Backdrop, CiviCRM, and other tech geared toward smaller organizations.<br />
<br />
Some discussion ensued about the desire from techs in some organization use "what the cool kids are using", and how sensible it is for non-profits with limited budgets to venture out onto the bleeding edge.<br />
<br />
== Outline ==<br />
Here was the proposed outline for the conversation<br />
<br />
* Headless<br />
* Static<br />
* Vue.js<br />
* SMS<br />
* Docker + other container technology<br />
* Hosting services<br />
* Languages/frameworks<br />
<br />
We then started discussing the last one first....<br />
<br />
== Languages folks want to work on ==<br />
Using new ones (Go, Rust) versus older ones like Python?<br />
<br />
Static compiled: Go, Rust, Swift<br />
<br />
Functional: Haskell, Elixir<br />
<br />
== Headless and static websites ==<br />
We discussed the advantages of static websites, which scale really well because the HTML is pregenerated.<br />
<br />
What does "serverless" mean? Server spun up and spun down on a per-request basis. (like what AWS Lambda proports to do)<br />
<br />
What does "headless" mean? Having a client-server split between a simple front-end system and a CMS that is responsible for the database work.<br />
<br />
Distinction between headless-decoupled and static<br />
<br />
* Headless - Website is actually processing data<br />
* Static - no on-request processing. HTML is generated on change.<br />
<br />
== Content management systems vs headless ==<br />
<br />
What's cool about CMS systems: you get all sorts of included bits that implement technology "for free".<br />
<br />
The promise of static websites: Static sites allow the browser compose the data.<br />
<br />
The reality: Are single page Javascript applications worth it? There are serious client-side performance implications of using the browser to render the raw data.<br />
<br />
== Static site generators ==<br />
<br />
Github provides Jekyll-compatible static site hosting<br />
<br />
Tools briefly discussed:<br />
<br />
* Jekyll<br />
* Gatsby<br />
* Hugo<br />
<br />
Static site generators promise greater security.<br />
<br />
Example of a static site generator from 15 years ago: [https://www.perl.com/pub/2004/08/27/bricolage.html/ Bricolage].<br />
<br />
Wordpress has a static site generator now.<br />
<br />
Varnish and other caching proxies have program<br />
<br />
Pantheon offers Varnish<br />
<br />
== Javascript frameworks ==<br />
<br />
(see "[https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f How it feels to learn JavaScript in 2016]")<br />
<br />
* React - maintained/promoted by Facebook<br />
* Vue.js - some folks in the room believe this is overwhelming than others. VueJS is good for custom filterable maps and events scheduling<br />
* Angular - maintained/promoted by Google (see also HTML Web Components)<br />
<br />
Is there an undercurrent we should be paying attention to? We're going through an adolescence as an industry. The good news: newer employees (e.g. interns in programs like GSoC or Outreachy) seem to catch on quickly. Huge companies distort the ecosystem and make it difficult to objectively evaluate options.<br />
<br />
== Containers ==<br />
<br />
We dove into discussion of container management and orchestration technology like Docker, Kubernetes, and Swarm.<br />
<br />
What is a container? VM that has the state saved.</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2817Book Recommendations2019-11-18T22:08:30Z<p>Rob: http->https on the aosabook.org link</p>
<hr />
<div>* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* [https://aosabook.org/ Architecture of Open Source Applications] - edited by Amy Brown and Greg Wilson<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=Book_Recommendations&diff=2816Book Recommendations2019-11-18T22:03:53Z<p>Rob: link to Architecture of Open Source Applications book</p>
<hr />
<div>* The Many-Headed Hydra (Atlantic Revolutions) - Peter Linebaugh and Marcus Bediker<br />
* Race After Technology - Ruha Benjamin<br />
* Digital Minimalism <br />
* The Spider and the Starfish: the power of leaderless organizations<br />
* Maphead - Ken Jennings<br />
* Out of the Forest - Gregory P Smith<br />
* High School - Tegan and Sara Quin<br />
* The New Jim Crow<br />
* Little Brother - Cory Doctorow<br />
* Emergent Strategy - adrienne maree brown <br />
* Blindsight - Peter Watts<br />
* Witches, Sluts, Feminists <br />
* Pleasure Activism - adrienne maree brown <br />
* How to Change your Mind<br />
* How We Fight White Supremacy<br />
* [http://aosabook.org/ Architecture of Open Source Applications] - edited by Amy Brown and Greg Wilson<br />
* Ishmael</div>Robhttps://devsummit.aspirationtech.org/index.php?title=New_and_Emerging_Web_Tech&diff=2800New and Emerging Web Tech2019-11-14T02:06:15Z<p>Rob: Notes from 3pm Friday session</p>
<hr />
<div>Minutes from our 3pm Friday (November 8) session<br />
<br />
== Introductions ==<br />
We started talking about the technologies that people wanted to talk about. Many people in the room were comfortable with the basic LAMP stack. Some of the folks were working with Rails, Node.js, and other tech. Many had worked with Drupal, Backdrop, Wordpress, Backdrop, CiviCRM, and other tech geared toward smaller organizations.<br />
<br />
Some discussion ensued about the desire from techs in some organization use "what the cool kids are using", and how sensible it is for non-profits with limited budgets to venture out onto the bleeding edge.<br />
<br />
== Outline ==<br />
Here was the proposed outline for the conversation<br />
<br />
* Headless<br />
* Static<br />
* Vue.js<br />
* SMS<br />
* Docker + other container technology<br />
* Hosting services<br />
* Languages/frameworks<br />
<br />
We then started discussing the last one first....<br />
<br />
== Languages folks want to work on ==<br />
Using new ones (Go, Rust) versus older ones like Python?<br />
<br />
Static compiled: Go, Rust, Swift<br />
<br />
Functional: Haskell, Elixir<br />
<br />
== Headless and static websites ==<br />
We discussed the advantages of static websites, which scale really well because the HTML is pregenerated.<br />
<br />
What does "serverless" mean? Server spun up and spun down on a per-request basis. (like what AWS Lambda proports to do)<br />
<br />
What does "headless" mean? Having a client-server split between a simple front-end system and a CMS that is responsible for the database work.<br />
<br />
Distinction between headless-decoupled and static<br />
<br />
* Headless - Website is actually processing data<br />
* Static - no on-request processing. HTML is generated on change.<br />
<br />
== Content management systems vs headless ==<br />
<br />
What's cool about CMS systems: you get all sorts of included bits that implement technology "for free".<br />
<br />
The promise of static websites: Static sites allow the browser compose the data.<br />
<br />
The reality: Are single page Javascript applications worth it? There are serious client-side performance implications of using the browser to render the raw data.<br />
<br />
== Static site generators ==<br />
<br />
Github provides Jekyll-compatible static site hosting<br />
<br />
Tools briefly discussed:<br />
<br />
* Jekyll<br />
* Gatsby<br />
* Hugo<br />
<br />
Static site generators promise greater security.<br />
<br />
Example of a static site generator from 15 years ago: [https://www.perl.com/pub/2004/08/27/bricolage.html/ Bricolage].<br />
<br />
Wordpress has a static site generator now.<br />
<br />
Varnish and other caching proxies have program<br />
<br />
Pantheon offers Varnish<br />
<br />
== Javascript frameworks ==<br />
<br />
(see "[https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f How it feels to learn JavaScript in 2016]")<br />
<br />
* React - maintained/promoted by Facebook<br />
* Vue.js - some folks in the room believe this is overwhelming than others. VueJS is good for custom filterable maps and events scheduling<br />
* Angular - maintained/promoted by Google (see also HTML Web Components)<br />
<br />
Is there an undercurrent we should be paying attention to? We're going through an adolescence as an industry. The good news: newer employees (e.g. interns in programs like GSoC or Outreachy) seem to catch on quickly. Huge companies distort the ecosystem and make it difficult to objectively evaluate options.<br />
<br />
== Containers ==<br />
<br />
We dove into discussion of container management and orchestration technology like Docker, Kubernetes, and Swarm.<br />
<br />
What is a container? VM that has the state saved.</div>Rob