The meeting log of today can be found as usual in the organization documents repo: https://github.com/protontypes/organization-documents
Here some logo ideas for our new project: Continuous Offset.
Just noticed that the colors make more sense when the carbon is blackish and the oxygen bluish...
Created with: https://soilgrids.org/
Hey @/all. We will meet again on Thursday 29.4. 18:30 CET to discuss the next step for OpenSustain.tech and the C³ project. Everyone interested is welcome to join: https://meet.jit.si/protontypes
Or like this
both...
Hey @/all. We will meet again on Thursday 6.5. 18:30 CET to discuss the next step for OpenSustain.tech . Everyone interested is welcome to join: https://meet.jit.si/protontypes
@Ly0n i used to work for them in Italy. in 20 years of activity they installed over 50k domestic photovoltaic systems all over Italy and with NWG Energia they deliver energy to the Italian families with 100% green energy mix.
@Ly0n www.nwgitalia.com
3 replies
Hi! I am looking for other devs who would like to join me working on https://github.com/pogopaule/awesome-sustainability-jobs.
With this project I try to lower the barrier for devs to switch to a green tech company by listing those companies that have vacancies for devs. There are thousands (maybe millions?) of dev jobs out there but only a tiny percentage of them are in green tech companies, so there are preeetty hard to find (speaking from own experience)
I'm especially looking for contributors from non-English/non-German speaking countries because this is my blind spot at the moment. I cannot search for positions in e.g. France or Indonesia. But any help is welcome. The backlog is full with companies that are yet to be screened...
I just found out about OpenSustain.tech and was happy to do so, but a problem has already emerged: the landscape is so large and complicated that it's not clear where (or if) I can focus my efforts effectively from just the list. Are there any recommendations on how to solve that problem with existing resources? Alternatively, would others be interested in creating resources to help with that? That is, trying to match skills/perspectives with effective projects/tasks?
@kentcr If you would like to you can join us doing so.
@Ly0n I don't see the issue as being search or design alone. It's a lack of information about which projects need help, the skills required, the relationship (e.g. volunteer vs. employee, on-site vs. remote, etc.). It's also complicated by the fact that some organizations have multiple projects with different objectives/needs. This could all be incorporated into better search/design, but it could also be more like a issue tracking system.
Based on all the information we can gather the goal is to create a database that is constantly been updated. With this we are going to create a new website.
I hope that we can fulfill some of the points you raise. It looks like we have similar ideas about this. When we created the first prototype we can tell more about what information the GitHub API can give us about the projects. The "Good First Issue" labels could help us find projects that need support.
@Ly0n Yes, very much in accord with my thinking, though to my mind being dependent on GitHub is very limiting. I've been thinking towards forking/upstreaming GitLab server, which could allow things like an interface for non-programmers and global searches for tags/criteria ("Good First Issue"), while still allowing symbiosis with GitHub and others. I started thinking about this in the context of Effective Altruism, where other cause areas (poverty, animal welfare, etc.) are important to a lot of people as well.
e.g. Something like https://github.com/samrocketman/gitlab-mirrors for mirroring (which includes wikis since they're just repos themselves) and https://github.com/IQAndreas/github-issues-import or https://github.com/coreos/issue-sync to include issues
@kentcr The restriction to GitHub is also something I don't like, but unfortunately most of the active projects are on GitHub. We can get the metadata for over 95% of the projects through GitHub's API. This is helpful for our case, but the dependency on this one platform is of course a fundamental problem. However, I think that we can manually add the metadata of the other projects for the time being.
This could include tools that makes commits to relevant projects even if the user in question doesn't know how to use git. The awesome-sustainability-jobs list mentioned earlier could be maintained this way, for example. I'd actually think pretty much anything that can be crowdsourced like Amazon Mechanical Turk would work.
@Ly0n have you scanned sourcehut already? https://sourcehut.org/ https://sr.ht/projects
that's the idea behind it https://drewdevault.com/2019/05/24/What-is-a-fork.html
that's the idea behind it https://drewdevault.com/2019/05/24/What-is-a-fork.html
@kentcr I tried this also at the last company I was working at. The problem is that many important information like user names etc got lost in this way.