📚 Agora node [[source]] ☆
Agora nodes contain community contributions with titles or topics that match your search. x
📜 File source.md by @agora@botsin.space ☆ 📎 ⛶
📜 File source.md by @an_agora@twitter.com ☆ 📎 ⛶
📜 File source.md by @flancian@twitter.com ☆ 📎 ⛶

[[cryptpad]], an E2E encrypted open source office suite:

h/t [[pesho]]


Loading pushes...

✨ AI Synthesis Mistral Gemini ChatGPT Claude x

Expanding this section will automatically generate an AI synthesis of the contributions in this node.

🌌 Agora context for [[source]]

Rendering context...

📚 Agora node [[arguments against open source]] (pulled by the Agora)
📜 File arguments against open source.md by @flancian ☆ 📎 ️🔗 ✍️

arguments against open source§

📚 Agora node [[attention is your scarcest resource]] (pulled by the Agora)
📜 File Attention is your scarcest resource.md by @binnyva ☆ 📎

Attention is your scarcest resource§

Source

  • To be reliably able to focus on something, you need to be intuitively, emotionally invested in the outcome.
  • Make sure that you are only ever working on one thing at a time. Even if I got stuck on that one thing.
  • Have one obligation to other people.
  • Employ a “bullshit timebox”—a one-hour period a few times a week when I do all the things life is too short for.

Tags§

#attention #focus #behavior #productivity

📚 Agora node [[bvp roadmap opensource]] (pulled by the Agora)
📜 File _notes/bvp-roadmap-opensource.md by @bmann ☆ 📎

We are open sourcing our OSS roadmap so other can see exactly how we evaluate OSS companies and why we are so excited about this space: https://www.bvp.com/atlas/roadmap-open-source [[@BessemerVP::https://twitter.com/bessemervp]] #opensource

[[pull?s=20” title=”[[@amitkarp::https://twitter.com/amitkarp/status/1308428755602472962 ?s=20]]” class=”wikilink”>@amitkarp::https://twitter.com/amitkarp/status/1308428755602472962 ?s=20]]

[[Bessemer Venture Partners]] publishes Roadmap: Open Source, on how they look at venture investing in [[Open Source]]. Timed with investment in Netdata.

One major development is worth emphasizing: once considered the cheaper version of closed source software, open-source software is now viewed as the superior alternative offering higher quality, better support, and more flexibility.

By [[Amit Karp]], [[Mike Droesch]], [[Ariel Sterman]], [[Jenny Gao]], [[Ethan Kurzweil]]


For investing in open source companies, BVP looks at these six areas and ranks each one across good, better, best.

  1. Team
  2. Origin
  3. Early Adopters
  4. Project ownership
  5. Monetization
  6. Community
📚 Agora node [[crowdsource]] (pulled by the Agora)
📜 File crowdsource.md by @agora@botsin.space ☆ 📎
📚 Agora node [[elements ressource]] (pulled by the Agora)
📜 File en/Images/elements-ressource.png by @communecter ☆ 📎


📜 File Images/elements-ressource.png by @communecter ☆ 📎


📚 Agora node [[ethical source]] (pulled by the Agora)
📜 File ethical source.md by @vera ☆ 📎
📚 Agora node [[experience projet open source]] (pulled by the Agora)
📜 File 06 - Open Atlas/experience projet open source.md by @communecter ☆ 📎

experience projet open source§

retour et partage de l’organisation et du fonctionnement d’open Atlas dans son developpement de projet Open Source

OCECO : Proposer - Decider - Financer - Suivre§

https://docs.google.com/presentation/d/1tXM5WJK2PsWIvBNCpCwNJiTKwij40X3_LFnvg_8Hxn8/edit?usp=sharing

Proposer§

Une idée§

Faire une demande de prestation§

Décider§

Financement§

Suivre§

Process de Priorisation des taches§

Comment établir la Roadmap§

Gestion des ressources humaines§

COTEAM§

Période de Bénévolats§

open door contribution§

https://chat.communecter.org/channel/codev_open_en

Stagiaires§

COTeam§

COre dev§

Partenariats§

Incubateur Social§

we help social projects§

📜 File en/06 - Open Atlas/experience projet open source.md by @communecter ☆ 📎

experience projet open source§

retour et partage de l’organisation et du fonctionnement d’open Atlas dans son developpement de projet Open Source

OCECO : Proposer - Decider - Financer - Suivre§

https://docs.google.com/presentation/d/1tXM5WJK2PsWIvBNCpCwNJiTKwij40X3_LFnvg_8Hxn8/edit?usp=sharing

Proposer§

Une idée§

Faire une demande de prestation§

Décider§

Financement§

Suivre§

Process de Priorisation des taches§

Comment établir la Roadmap§

Gestion des ressources humaines§

COTEAM§

Période de Bénévolats§

open door contribution§

https://chat.communecter.org/channel/codev_open_en

Stagiaires§

COTeam§

COre dev§

Partenariats§

Incubateur Social§

we help social projects§

📚 Agora node [[general intellect unit 066 post open source]] (pulled by the Agora)
📜 File general-intellect-unit-066-post-open-source.md by @neil ☆ 📎 ️🔗 ✍️

General Intellect Unit 066 - Post Open Source§

http://generalintellectunit.net/e/066-post-open-source/

Looking at Melody Ward’s article on [[Post-Open Source]].

📚 Agora node [[great open source]] (pulled by the Agora)
📜 File great open source.md by @flancian ☆ 📎 ️🔗 ✍️

great open source§

https://twitter.com/LucidBrot/status/1375547478095900681

📚 Agora node [[how a local government migrated to open source]] (pulled by the Agora)
📜 File how-a-local-government-migrated-to-open-source.md by @neil ☆ 📎 ️🔗 ✍️

How a local government migrated to open source§

URL : https://opensource.com/article/20/8/linux-government

Eyüpsultan Municipality in Turkey gained flexibility, cost savings, performance, and independence by transitioning its entire workforce to GNU Linux and other open source software.

I believe that regular training during our open source migration project was the single most significant reason for its success.

Providing training throughout the migration was one of our key strategies. We did not stop after delivering training; we checked back with our users to verify that the training produced the expected results. It took us a year to uncover all the things people struggled with after switching from Office to LibreOffice, but we welcomed these issues and helped to solve them whenever they arose.

We didn’t just do technical analysis at this stage; we did psychological analysis at the same time. By talking to people, we tried to find out their anxiety points. We learned that there was a common fear of an "encounter with the unknown."

📚 Agora node [[installing emacs from source]] (pulled by the Agora)
📜 File installing-emacs-from-source.md by @neil ☆ 📎 ️🔗 ✍️

Installing Emacs from source§

Resources§

Log§

[2021-03-21 Sun]§

I want to upgrade to [[Emacs]] 27. I’m currently on 26.3 on Mint.

I could get it from a PPA, but a couple suggestions here suggest that building it from source is fairly quick and straightforward. And possibly Emacs runs quicker if built for your own machine. So I might do that.

  git clone --depth=1 --single-branch 
--branch emacs-27 https://github.com/emacs-mirror/emacs.git

cd emacs/

sudo apt install -y autoconf make gcc texinfo libgtk-3-dev libxpm-dev \
     libjpeg-dev libgif-dev libtiff5-dev libgnutls28-dev libncurses5-dev \
     libjansson-dev libharfbuzz-dev libharfbuzz-bin libmagickwand-dev libxaw7-dev

./autogen.sh

./configure --with-json --with-modules --with-harfbuzz --with-compress-install \
            --with-threads --with-included-regex --with-x-toolkit=lucid --with-zlib --without-sound \
            --without-xpm --with-jpeg --without-tiff --without-gif --with-png \
            --without-rsvg --with-imagemagick  --without-toolkit-scroll-bars \
            --without-gpm --without-dbus --without-makeinfo --without-pop \
            --without-mailutils --without-gsettings --without-pop
make
sudo make install

[2021-03-27 Sat]§

When compiling, you need to set compiler flags. So I kind of want to know what the current version I’m using was compiled with, so I can reuse those again.

You can get this by inspecting system-configuration-options (info here).

For me it was

"–build=x8664-linux-gnu –prefix=/usr ‘–includedir=\({prefix}/include’ ‘—mandir=\){prefix}/share/man’ ‘–infodir=\({prefix}/share/info’ —sysconfdir=/etc —localstatedir=/var —disable-silent-rules ‘—libdir=\){prefix}/lib/x8664-linux-gnu’ ‘–libexecdir=${prefix}/lib/x8664-linux-gnu’ –disable-maintainer-mode –disable-dependency-tracking –prefix=/usr –sharedstatedir=/var/lib –program-suffix=26 –with-modules –with-file-notification=inotify –with-mailutils –with-x=yes –with-x-toolkit=gtk3 –with-xwidgets –with-lcms2 ‘CFLAGS=-g -O2 -fdebug-prefix-map=/build/emacs26-TP6iDo/emacs26-26.3~1.git96dd019=. -fstack-protector-strong -Wformat -Werror=format-security -no-pie’ ‘CPPFLAGS=-Wdate-time -DFORTIFYSOURCE=2’ ‘LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro -no-pie’"

All of that looks fine, although -fdebug-prefix-map is pointing at an emacs26 specific directory. I notice also that the recommended one from reddit has –with-harfbuzz, which I think is new for 27.

Someone else recommends the following config options:

./configure --with-sound=alsa --without-gconf --with-mailutils --with-json --with-modules --prefix=/usr/local

don’t skip the json and modules flags […] . If you do, you’ll be wondering why LSP is slow as balls and why vterm doesn’t work.

Bit of a faff, really, figuring out which configuration flags are needed. I wonder what they all mean. And presumably there are some defaults if you don’t select them all?

This article has a wealth of info here: What’s New in Emacs 27.1? - Mastering Emacs. It gives some info as to what is default and what isn’t.

I think I’ll just keep it simple and see what happens. There’s a part of me that thinks I should just get it from the PPA - that would definitely be simpler - but I think I’ll enjoy compiling it from source. Takes me back to the early days of my Linux usage.

"
'--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' --sysconfdir=/etc 
--localstatedir=/var --disable-silent-rules 
'--libdir=${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=${prefix}/lib/x86_64-linux-gnu' 
--disable-maintainer-mode 
--disable-dependency-tracking --prefix=/usr 
--sharedstatedir=/var/lib
--with-file-notification=inotify 
--with-mailutils 
--with-x=yes 
--with-x-toolkit=gtk3 
--with-xwidgets
"

configure: error: xwidgets requested but WebKitGTK+ not found.

OK, installed libwebkit2gtk-4.0-dev.

configure: WARNING: unrecognized options: –disable-maintainer-mode, –disable-dependency-tracking

OK, removed them from the config.

[2021-03-27 Sat]§

OK! All seemed to compile fine and startup with no problems. Packages were all pulled in.

On 27, had to change the time-stamp-format.

The following obsolescent time-stamp-format construct(s) were found:

"%04y" – use %Y

Fair enough.

📚 Agora node [[open source]] (pulled by the Agora)
📜 File open source.md by @flancian ☆ 📎 ️🔗 ✍️

Open Source§

📜 File open source.md by @goldfishlaser ☆ 📎 ️🔗

open source§

Core idea§

📜 File open source.md by @agora@botsin.space ☆ 📎
📜 File open source.md by @an_agora@twitter.com ☆ 📎
📜 File open source.md by @anagora@matrix.org ☆ 📎
📜 File open-source.md by @anagora@matrix.org ☆ 📎
📜 File open source.md by @flancian@social.coop ☆ 📎
📜 File open source.md by @flancian@twitter.com ☆ 📎

One of the beautiful things about [[open source]] is that, if you dream of software, you can make it come true at least in principle. It is a shared space for dreaming, writing, coding together.


But you can also help improve it! It’s the beauty of [[open source]].

And sometimes, almost always really, just waiting is enough. As other people are fixing it with you.


See also: [[gitlab]], [[gitea]], [[codeberg]] and coops like [[https://t.co/oE2HApAFPH]], all in the same space and building or provisioning [[open source]].


See also: [[gitlab]], [[gitea]], [[codeberg]] and coops like [[https://t.co/oE2HApAFPH]], all in the same space and building and provisioning [[open source]].


[[karrot]], a free and [[open source]] tool for "#grassroots initiatives and groups of people that want to coordinate face-to-face activities on a local, autonomous and voluntary basis."

https://t.co/B1LdbCn1Vt


📚 Agora node [[opensource]] (pulled by the Agora)
📜 File 15 - Présentations/opensource.md by @communecter ☆ 📎

Le choix de l’Open source !§

Nos épices, nos recettes et notre code source sont libres d’utilisation et d’amélioration.

L’Open Source§

Une méthodologie de développement encadré juridiquement par des licences qui contribuent à un cercle vertueux d’amélioration d’une technologie.

L’Open Source repose sur : une vision profondément humaniste, de l’innovation collaborative, la reconnaissance par le partage des savoirs.

Richard Stallman, initiateur du mouvement du logiciel libre, définissait le logiciel comme suit :

“le logiciel est, à la manière de la connaissance scientifique, une forme de patrimoine de l’humanité, un bien commun que nous enrichissons collectivement, pour le bien être de tous”.

📜 File en/14 - Présentations/opensource.md by @communecter ☆ 📎

Le choix de l’Open source !§

Nos épices, nos recettes et notre code source sont libres d’utilisation et d’amélioration.

L’Open Source§

Une méthodologie de développement encadré juridiquement par des licences qui contribuent à un cercle vertueux d’amélioration d’une technologie.

L’Open Source repose sur : une vision profondément humaniste, de l’innovation collaborative, la reconnaissance par le partage des savoirs.

Richard Stallman, initiateur du mouvement du logiciel libre, définissait le logiciel comme suit :

“le logiciel est, à la manière de la connaissance scientifique, une forme de patrimoine de l’humanité, un bien commun que nous enrichissons collectivement, pour le bien être de tous”.

📜 File OpenSource.md by @agora@botsin.space ☆ 📎
📜 File opensource.md by @agora@botsin.space ☆ 📎
📜 File opensource.md by @an_agora@twitter.com ☆ 📎
📚 Agora node [[post open source]] (pulled by the Agora)
📜 File post-open-source.md by @neil ☆ 📎 ️🔗 ✍️

Post-Open Source§

Post-Open Source | boringcactus.

📚 Agora node [[the bystander effect in open source]] (pulled by the Agora)
📜 File The-Bystander-Effect-in-Open-Source.md by @enki ☆ 📎

The Bystander Effect in Open Source§

Big projects with thriving communities are how non-developers (and surprisingly many developers) picture open source, but it’s hard to…


The Bystander Effect in Open Source§

Big projects with thriving communities are how non-developers (and surprisingly many developers) picture open source, but it’s hard to square these kinds of projects with ESR’s idea that source visibility & the ability to submit patches results in a substantially greater number of fixed bugs. Certainly, these kinds of projects benefit core maintainers socially, and certainly, source visibility helps with organized audits & makes it easier for individuals to fix bugs, on top of making drive-by fixes possible, but this conventionalized structure does not optimize for drive-by fixes.

When a project is large — especially when it is non-modular or when modules have complex interrelations — it takes a lot of effort just to understand things like project structure, dependency graphs, and control flow. These things need to be understood to a certain extent in order to produce a bug fix. If a project is visibly maintained — when it has a named maintainer & a high commit rate, and especially if it has a community of active developers around it — there is the sense that fixing a bug is somebody else’s job. After all, the drive-by developer doesn’t already have deep knowledge of the codebase, while all these active contributors do.

On top of that, the drive-by developer isn’t necessarily aware of or comfortable with the social structure built around especially large projects: complex norms around code style and best practices (rarely shared between unrelated projects), formal and informal social hierarchies among developers, tacit knowledge that maintainer X is a jerk or caustic or that maintainer Y is generally OK but has a hangup about licenses or maintainer Z will reject any patch that has an enum in it due to early life trauma. Actually fixing the bug means learning all these things or dealing with a waste of time & effort on both sides as the results of not learning them get negotiated. So the drive-by developer submits a bug report.

But wait! It gets worse! Because some bugs are really features. One must have an even deeper understanding of the code base and the community around it in order to determine whether some apparent bug is actually an intentional behavior, or an obscure joke kept for lore reasons, or bug-for-bug compatibility with something else, or the best of several bad possibilities necessitated by structural or dependency decisions made early in the project’s development. Or, it may be a perverse manifestation of some author or maintainer’s personal philosophy. So maybe even reporting the bug is a waste of everybody’s time. Checking would involve trying to find similar reported bugs & reading the discussion around them, and the drive-by developer has better things to do than to read thirty pages of semi-related bug reports on the off chance that it’s been filed before and marked not-a-bug.

Reporting the bug might be a waste of time for other reasons as well. If I installed the application from my distribution’s package manager rather than building from source, [it might have been fixed upstream years ago](https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping- xscreensaver/), or it might have actually been introduced by a distro maintainer. Checking would require building from source, which would require getting the right versions of dev packages for all dependencies & maybe building other things from source too, and the drive-by developer would do that as part of constructing a bug fix but is not willing to do that for a bug report.

The worst case scenario here looks like an apache project — the bane of all drive-by bug-fixes. Apache projects are typically former internal corporate projects that were at some point dumped on the apache foundation. Apache projects are big and tangled and have complex interdependencies. They often have decades of mailing list & bug tracker discussion, involving the same approximately one hundred core developers whose tangled interpersonal history is preserved in bureaucratic amber. Apache projects are highly actively maintained, but not by anyone you know, and you have a hard time imagining the mind of a being who can fully understand the class hierarchy of some of these projects. The tangled weeds of apache projects are full of strange counterproductive decisions — slow code, counterintuitive behavior — protected by a dense web of complicated dependencies and tight coupling between seemingly unrelated classes. No mortal drive-by developer can contribute to an apache project and live — or at least, that’s the impression any drive-by developer gets upon investigating whether or not to fix (or even report) a bug for about ten minutes.

It’s possible to have a full-featured and complex project that is inviting to drive-by developers, though.

A project that looks unmaintained will encourage forks (which can be selectively merged — you don’t need to wait for a push request, and can simply grab good-looking diffs). Seemingly-unmaintained projects also are poison to corporate users (who are looking for somebody to do free labor & who generally won’t contribute back changes made in-house), so while your code may get fewer users in total, those users it does get are more likely to be meaningful contributors.

A project that’s highly modular, and where the modules are simple and very loosely coupled, will be inviting to drive-by developers. Not only is identifying bugs easier, but the fact that identifying bugs will be easier is obvious before one even starts. There are fewer opportunities for complications like bugs-that-are-really-features, and those cases can be more easily explained.

If maintainers must be visible, a casual structure for talking to all the maintainers helps. Formalized bug tracking mechanisms lower the labor on maintainers to deal with large numbers of bugs by putting the onus on those filing the bugs to obey complex and often opaque rules. Such systems are absolutely necessary when you have hundreds or thousands of bug reports a day, but they make it impossible to say “hey, I noticed this weird behavior — do you guys already know about it?” in a way that doesn’t look like an atomized task on somebody’s plate.

A project that handles this quite well is my favorite linux distro, Lunar. Despite being a full-featured linux distribution, Lunar is really just a handful of fairly-readable short shell scripts; the maintainers & developers number less than ten and hang out on IRC. I do not use Lunar as my primary distribution (only because it lacks multilib support, which I very occasionally need for running binaries), but the environment and the community always feels like home, in part because I know that with only a little bit of effort I could not only have a complete understanding of the entire distro’s code & its policies, but get to know everybody involved on a first name basis too. This kind of situation is only really possible because Lunar is fringe and its user base small, but I’ve seen plenty of projects with substantially smaller user bases that have substantially larger barriers to entry for casual contributors.

By John Ohno on January 10, 2020.

[Canonical link](https://medium.com/@enkiv2/the-bystander-effect-in-open- source-598430de16a7)

Exported from Medium on September 18, 2020.

📚 Agora node [[toot expirator source]] (pulled by the Agora)
📜 File toot_expirator_source.myco by @melanocarpa ☆ 📎 ️🔗 ✍️

This is the source code for toot expirator. The code is in public domain, except for the little part which I found on Stack Overflow. The first and the only version so far was published on 2022-05-08.

Code

This program in Python prints the preserved toot text with all the stuff to stdout. Do what you must with the output.

Replace all-caps word with your data.

#!/usr/bin/python3
import sys

if len(sys.argv) < 2:
	print("Error: No URL")
	sys.exit(0)

URL = sys.argv[1]

if "ADDRESS" not in URL:
	print("Error: Wrong URL")
	sys.exit(0)

from mastodon import Mastodon
import html

mastodon = Mastodon(
    access_token = 'GET YOUR OWN',
    api_base_url = 'https://ADDRESS'
)
id = int(URL.split("/")[-1])
toot = mastodon.status(id)

text = "* " + html.unescape(toot['content'].replace('<p>', '').replace('</p>', ''))
text += " — " + toot['created_at'].strftime('%Y-%m-%d %H:%M %Z')
if toot['favourites_count'] > 0:
	text += " ⭐️" + str(toot['favourites_count'])
print(text)
with open('LOG FILE', 'a') as f:
	f.write(text+"\n")

# Snippet from https://stackoverflow.com/a/25802742 {
import subprocess

def write_to_clipboard(output):
    process = subprocess.Popen(
        'pbcopy', env={'LANG': 'en_US.UTF-8'}, stdin=subprocess.PIPE)
    process.communicate(output.encode('utf-8'))
# }
write_to_clipboard(text)

mastodon.status_delete(id)
📚 Agora node [[tpu resource]] (pulled by the Agora)
📜 File Artificial Intelligence/Introduction to AI/Week 3 - Introduction/Definitions/Tpu_Resource.md by @KGBicheno ☆ 📎

TPU resource§

Go back to the [[AI Glossary]]

#TensorFlow #GoogleCloud

A TPU entity on Google Cloud Platform that you create, manage, or consume. For example, TPU nodes and TPU types are TPU resources.

📚 Agora node [[windows terminal is open source]] (pulled by the Agora)
📜 File pages/windows terminal is open source.org by @vera ☆ 📎

https://github.com/microsoft/terminal