My partner is doing an incubator program called Social-Digital Innovation Initiative: https://sdinnovation.org
The basic idea is to bring together a person who knows of a specific social issue, and a tech person who wants to help solve it. Together they are the core team and are helped to work on their project, form a non-profit, get conmections etc.
At the moment the program is piloting in Berlin. It's planned to expand to Hungary, Austria and ideally other areas. If you are interested, drop by at one of the barcamp/unconference events or check out the website. :)
If you’re up for contributing a simple timeout or something like that I guess the developers would appreciate that a lot :) https://github.com/fossjobs/fossjobs/
I don't think so, somewhere else in this thread the developer of this job board says that his intention is to keep all listings forever, as this would prove that paid FOSS jobs exists in abundance. IMO a debatable approach.
No. I want to keep them around, sure, but of course they can be styled differently.
I don't know what makes everyone so upset at old listings. They are listed chronologically, there is an RSS feed to follow for fresh things. It's not like it's thousands of mixed jobs where you have to hunt for the recent postings? I definitely don't object to someone adding an archive/expiry functionality that does not completely delete old job listings. If you look at the referenced ticket on github, I created it.
Nobody is suggesting old jobs should be deleted from your database (I doubt any job listing website would do this). Just that the old jobs are too irrelevant to display by default as visitors are generally only interested in current vacancies.
Keeping the old jobs as a separate search option (eg "[ ] include historic items") de-clutters the primary purpose of the site. That matters when you consider that few people enjoy the process of job hunting so will quickly abandon any platform with a poor signal to noise ratio.
I think that's silly. There could have been hundreds of well-paid FOSS jobs in 2013. That doesn't matter at all if there are none in 2017. It doesn't even prove anyone was ever hired for that job, only that it was posted.
There's certainly analytical value in having every FOSS job you could have ever seen, but none for the end user.
Thanks for pointing that out! :) While of course showcasing the community is great, doing it just based on commits inherently skews towards developers and ignores others like designers, translators, documentation writers, community people etc.
Just added Mike and some others of the list to our Open Source Design collective at https://github.com/opensourcedesign – if you want to be part of it as well let me know. :)
Jan from the Nextcloud team here. If you have any questions don’t hesitate to ask. :) We’re very happy with the new release, especially the the improvements on security and performance.
Also I like our new video chat a lot. ;)
As you know it’s all open source, so any contribution is welcome! https://github.com/nextcloud
I have an owncloud instance and want to migrate to nextcloud. Just wanted to know if you have ubuntu/debian ppa like owncloud? I have very little experience with PHP and don't want to install it from source.
Probably the easiest way in your case is to backup the config folder and your data folder, then uninstall the ownCloud packages and install PHP/Apache yourself. Then simply put our newest release into the web root and copy your old config there as well. If you need more help on that I'm sure we have many people in our forums willing to help :)
> Is there a need for such a database? Absolutely. Today, there is no database on Swiss food products that is truly open, free, and - perhaps most importantly - programmatically accessible via an API).
Granted, Open Food Facts needs some design improvements. But why work on a Swiss-only system with nice design when there is a way bigger and more established platform already in place.
Good to know! I use nextcloud, but it is performing TERRIBLY on my raspberry pi 3. I need to see about recreating the setup they use on the nextcloud box.
Is this better than ttrss? or just different? Worth the hassle of migrating things?
