Our Essential List of Free Software for Remote Work https://puri.sm/posts/our-essential-list-of-free-software-for-remote-work/ #remotework #remote #WFH #opensource
Despite of the country being on lockdown, we keep getting guests that ain't afraid of anything - and they sure tweet more than I do. #birds
Wow, that was quick: Thanks to Lucas Stach our #etnaviv runtime power managemt fix already landed in linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=range&q=ea4ed4a55f7363ad8db1863bd536548fb7e5c6aa..78f2bfa3181cd7ee134274aa17177dd933c69dc1
The fix hits the #librem5 with the next kernel update.
Oh, and that's of course on the 2000mAh battery. The final model is going to have a 3600mAh one :)
That's with the screen, modem, WiFi and USB off. Modem probably wouldn't influence it that much though.
The next merge request will make #phosh cross the 1000 commit boundary:
$ git log --pretty=oneline | wc -l
Multiple GTK apps open in the same environment and all fitting nice in the screen.
Thank you #libhandy
After adding proximity sensor-support to #iio-sensor-proxy (https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298) and adding runtime-pm support for the chip used in the #librem5 (and it's devkit) (https://email@example.com/) we can now wire it up to #phosh to fade the screen and prevent keyboard input:
A lot of people are confused by git. Most of these people, I reckon, learned it from the outside in - from the command-line interface down. If you started with git by asking "how do I sync up my changes with my peers", then you might get the answer, but you will be missing the foundation on which that answer is built. This is the main source of confusion with git.
The better way is to learn git from the inside out. You should first learn about what objects are and how they're stored and identified, and how they relate to each other. You should learn what blobs, trees, and commits actually are, and how they relate to each other, and how commits form a linked list from which a graph of all objects can be derived.
Then you should learn how the ref database gives friendly names like "master" and "feature/foobar" to objects, and how the reflog tracks changes to references over time.
THEN, and only then, should you learn how to use the CLI. Then you can learn about using the staging area to add objects to the database and create commits, and how doing this updates the reflog.
Git makes total sense when you approach it from this angle. Supposedly hard tools like git rebase are totally understandable when you view them with the appropriate foundational knowledge.
Git is a tool which you will reach for hundreds of times a day, every day, for your entire career. Maybe it's worth learning about properly.
Reviewing a merge request for phosh by Julian with some initial work on the quick settings: https://source.puri.sm/Librem5/phosh/merge_requests/425 #librem5 #DailyLibrem @purism
Jonathan Carter on the #Librem5 "The #Gnome apps are fast and responsive and just feel natural on this form factor. I’m looking forward again to having a pocket computer that can run Debian." - Random bits from FOSDEM 2020 https://jonathancarter.org/2020/02/07/random-bits-from-fosdem-2020/