[–] [S] 1 point 3 days ago (1 child)

Damn wasn't expecting this to get philosophical lol. Good points, I didn't think of documentation through this lens, I was just thinking of writing basic instructions, which might not be as easy for a beginner to understand.

My initial idea was just to use a blog, but it might not be easy to find for people new to the project and having docs as a repo might also allow the devs to change anything when they want as well.

  • source
  • parent
  • context
  •  

    I've been thinking of contributing to foss projects with more than testing and bug reporting. I want to contribute to mainly open source game engines. There are a few that are mature and underrated, but lack any documentation for a user to get started. This is why I decided to do documentation, but I don't know where or how to start.

    Is there any general rule/guidelines for getting started with this ? I'm looking for anything that can help a beginner documentation writer

    [–] 9 points 1 month ago (2 children)
    1. Kvaesitso
    2. Lawnchair
    3. Murine
    4. Ion Launcher

    I've been testing new launchers, and since most are unfortunately just text based or "minimalist", your options are limited.

    Lawnchair and Kvaesisto just works at least on my phone. Search on lawnchair wasn't great. Murine is the one I'm trying and seems to be one of the better ones in the new set.

    You can try Launcher314, but it's choppy on my phone, almost like the app drawer scrolling is below 60Hz.

    Another one I used was Yagni, but it's in Alpha stage. And the dev kept renaming the project so often it got confusing

  • source
  •  

    I'm not at all an expert with open source licensing, but does the following conflict with open source licensing ?

    I don't mean any ill intent to the developers of the application, but want to inform them if there is something wrong. (Sorry if my question feels dumb, I'm just getting familiar with licensing terms)

    I've been following this app for sometime and it recently had its alpha release. While taking a look at the Terms and Conditions section of the app, I came across the Application Use section which reads:

    1. Application Use

    3.1. License

    Pockaw grants you a personal, non-transferable, non-exclusive license to use the app for personal or small business financial management purposes. 3.2. Prohibited Use

    You agree not to: Reverse engineer, decompile, or modify Pockaw. Use the app for illegal activities. Exploit the app in ways not intended, such as reselling it as your own product.

    view more: next ›