pylapp

joined 2 years ago
MODERATOR OF
 

Cross-posted from : https://programming.dev/post/34733176

"The Accessibility Nutrition Labels help users learn if an app will be accessible to them before they download, and give developers the opportunity to better inform and educate their users on features that their app supports. The labels appear on the app product page and will help users understand if they can use a feature like VoiceOver or Larger Text to complete common tasks in the app."

 

"The Accessibility Nutrition Labels help users learn if an app will be accessible to them before they download, and give developers the opportunity to better inform and educate their users on features that their app supports. The labels appear on the app product page and will help users understand if they can use a feature like VoiceOver or Larger Text to complete common tasks in the app."

 

A bit old but still interesting

[–] pylapp@programming.dev 2 points 4 days ago

We should support our fediverse admins and instances 💪 Support by sending money (for people who can), moderating content, submitting issues or helping the team and project ✌️

 

With some notes about privacy, security and Google services

 

About the Online Safety Act in the UK and the Digital Services Act in Europe

[–] pylapp@programming.dev 2 points 1 month ago

So abandon open source and move to “post open source” or ethical source might be a (sad) solution.

 

About enshitification of web dev.

 

If companies with commercial uses supported open source project by funding or contributing, things could have been better.

[–] pylapp@programming.dev 5 points 2 months ago* (last edited 2 months ago) (1 children)

Anticipate technical debt and follow what Google recommends. In few words, use Kotlin and Compose.

However you should really have a look on Google guidelines. In more worlds:

  • by default Kotlin and Compose
  • if some logic to share between other projects in other environments: Kotlin Multi Platform (KMP)
  • if shared UI: Flutter (but Google reduced Flutter teams and KMP is being better and better, so we can suppose Flutter will join the Google Graveyard
[–] pylapp@programming.dev 2 points 2 months ago

I do not know if the solutions I listed below are open source ; however as an open source contributor I am used to work with some tools depending to choice of the projects:

About credits, I don’t think these tools exposes in some automated way the contributors identities. However, nothing prevents you to use these web UI tools to find who contributed and list people for example in your CONTRIBUTORS files. Another way could be to edit the automated commits these tools submit to your Git repos by adding credits to the translators (with for example Co-authored-by field).

[–] pylapp@programming.dev 1 points 3 months ago* (last edited 3 months ago)

Yep, it seems it is, but it can manage KDBX files. Just wanted to share 😄

Edit: sorry, didn’t see this thread is in Android community, my comment is not relevant for this platform.

[–] pylapp@programming.dev 0 points 3 months ago* (last edited 3 months ago) (2 children)

You can use also for example Strongbox (https://github.com/strongbox-password-safe)

Edit: sorry, didn’t see this thread is in Android community, my comment is not relevant for this platform. For Android I am used to Keepass2Android (https://github.com/PhilippC/keepass2android). Simple, still maintained, under libre licence GPL 3.0.

[–] pylapp@programming.dev 3 points 6 months ago

Not sure of that, maybe we need some case law or update on existing copyleft licenses. Source code generated with GenAI tool, even if their model have been trained with corpora of copyleft sources, are not (yet) considered as derivative works. What a pitty.

[–] pylapp@programming.dev 3 points 6 months ago

Could be interesting. Non-free and current GenAI tools violate copyright, we may consider some evolutions of copyfarleft licenses to forbid such use of source code in these types of tools.

[–] pylapp@programming.dev 4 points 6 months ago (2 children)

Just wanted to share for the common knowledge and the debate as I already saw here some “post open source” and content about rubbish licenses like SSPL or BSL 😉

[–] pylapp@programming.dev 6 points 7 months ago (1 children)

Be sure also the issues you have in your project have the suitable labels to help future contributors to pick easily some of them, i.e. labels like “help wanted” or “good first issue”.

You can also refer to best practices listed and explained for example in Advent of Open Source so as to have a nice and user-friendly repo: https://adventofopensource.com/

[–] pylapp@programming.dev 7 points 8 months ago (1 children)

Have a look on Organic Maps (https://organicmaps.app) or OSMAnd for example (https://osmand.net/).

view more: next ›