qeef @qeef@en.osm.town

When websites say "use our app, it's much better", they mean better for them, not you.

Did you miss any speakers from last Friday's #PistaNgMapa conference?

Worry not!

Watch the Day 2 playlist of presenters from our channel: http://youtube.com/playlist?list=PL_Y0WtqwYrIgNHr79zEEUHzinQHQl6hN4 or watch the live stream itself: http://youtu.be/aqQ5tbwrbTs

#OpenStreetMap #PnM20 #FOSS4G

Did you miss any of our #PistangMapa speakers yesterday?

The day 1 playlist is now available for your convenience: http://youtube.com/playlist?list=PL_Y0WtqwYrIjgOMn5xWV_uXABcEHxoOi_

Subscribe to our YouTube channel for updates, or watch this space for announcements.

#OpenStreetMap #PistangMapa #foss4g #PnM20
---
RT @pistangmapa
DAY 1 DONE!

Thank you for attending Day 1 of Pista ng Mapa 2020.

See you next Friday!

You may visit …
https://twitter.com/PistaNgMapa/status/1327237276599021568

@sir I'm starting a linux community in my hometown. I already created a mailing list on sourcehat with the intent of teaching my fellow citizens how to use it and then using it for technical support and discussions.

LIVE NOW!

Join us at http://bit.ly/pnm20live 14:00 UTC+8

You may visit http://pistangmapa.github.io/2020/
for more information.

#openstreetmap #PnM20 #foss4g #freeconference #opensource

This is definitely worth a read. #OpenStreetMap

(Warning, it's hosted on Medium)

https://joemorrison.medium.com/openstreetmap-is-having-a-moment-dcc7eef1bb01

The argument against the word "master" is based on the unproven assumption that the term is loaded with racist connotations, and the mandate for change is based on the fact that the possibility of the assumption's truth is nonzero and that the side-effects of the change are small.

If that were true, I would be on board with it. However, it's plainly clear that the impact of git upstream switching the default branch name to "main" is going to be huge. Many scripts with the "master" hard-coded are going to break, scripts written on the valid assumption that the name "master" was an intrinsic, unchanging property of git.

Every programmer who works with repositories before and after the change are going to constantly mis-remember which is which, and we'll have to guess at the default when working with new or unfamiliar repositories.

This event is going to establish a new epoch in git. We should take that seriously.

Which means we have to confront the fact that the assumption (that inherent racism is present in the word "master" and is causing harm to those who have suffered under racism) may not actually be true. The claims do not hold up well under scrutiny. And, as far as I can tell, the cause is championed disproportionately by white people.

The moralized nature of the question puts an external pressure on decision makers on the git project, which is normally not present for other patches. They have to consider, if they review these changes negatively, will it affect their personal reputation? Their careers? If there's even a slight chance of this, is it better not to argue the matter at all, and rubber-stamp the patches? I don't think this change is being developed under the right conditions.

On the left, we have a tendency to rubber-stamp social causes with a lesser degree of scrutiny. I think that this is a testament to how much we value empathy and solidarity, but I don't think it's a healthy way to approach our problems. Software breakage has a social cost, too.

oh no

Jan 2019: Travis CI acquired by private equity
Feb 2019: Travis CI senior engineering staff laid off
Nov 2020: Travis CI pricing changes

SourceHut: We don't take outside investments™

$ npm install