Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
admin
admin
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • F-Droid
  • adminadmin
  • Issues
  • #200

Closed
Open
Opened Jan 21, 2021 by Izzy@IzzySoftDeveloper

Let's have a Wiki (again)

In my talk today with Hans at our regular "Office Hour" we agreed it would be nice to have a Wiki again. My idea was to use it for documenting our processes, helpful hints for our daily work, etc. It could also serve as a "brain-storming center" for new documentation to be added to f-droid.org/docs – which is why I'd propose using the GitLab wiki of "website" for this.

Some points I'd like to see there (and collected details on during the last months):

  • how often does X run and what triggers it (with X in checkupdates, build, sign)
  • common errors with build runs and possible approaches (e.g. "Unable to strip the following libraries, packaging them as they are: XXX.so, ..." usually meaning the build block needs ndk: r21d or whatever NDK is available then)
  • hints for setting up specific build blocks (eg for Flutter apps: have prebuild: echo "flutter.sdk=$$flutter$$" >> ../local.properties, make sure build: has the $$flutter$$/bin/flutter config --no-analytics step, and more)

All these things are easier "grown" (and found) in a wiki. Sure: as soon they are "grown", most of them probably should be added to /docs, though certainly not all.

While Hans proposed a separate "project" for that, fearing it otherwise would get lost, I think binding it to the repository our docs reside in would to be preferred. It's about documentation, so it somehow belongs. Of course I'm open for alternative ideas, too 😉

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: fdroid/admin#200