### WiP - needs to be reworked

Participants: Michael, Robert, Stephan
Date: Thu, 05.06.2025

# EDP Product Line 'Portal/Frontend/Forgejo'

[Also refer to other page here](../../../product/components/forgejo/index.md) 


## how to proceed

* let's create tickets!
* let's mob!

## terms

Frontend: The part in the platfrom the user accesses. These are CLIs, APIs and Portals. Forgejo is our Portal.

### Agreement

* Forgejo=Portal (of the platform)
* Forgejo has a 'Frontend' - this is the touchpoint for users (like HTML-browsers)
* Forgejo has a backend, which delivers the content to be presented in the frontend

## issues

* Michael into ArchMeeting?! (agreement!)
    * Robert/Stepan: discusion about our mindset - mobbing as avoiding missing detailed planning, in two streams
    * Michael - Michal, Felix sind das 'Portal-Frontend'
        * Tickets in Jira currently
        * TODO creating tickets in forgejo / porting tickets from Jira
        * we create the new forgejo-proect 'Portal-Frontend'
        * zweiter meilenstein: Backend-activities need to be adressed in the future 
* TODO have a look into the old backstage-portal

* TODO Stephna an Julius ... Logo/CICD: We should define Logo/name tenant name, product name, url schemas

### Development lifecycle

* create project in CFor
* create tasks in CFor
* TODO Stephan possible tasks
    * Environments -> let's provide a 'productline-forgejo' env in OTC!
    * Pipelines
    * check all tests!

### Architecture

* Goals:
    * Stay Open Source compatible!
    * stay forgejo-downstreaming compatible!
    * provide ADRs before breaking changes

#### forgejo-Architecture

* analyse, presnt ad discuss forgejo architecture
* Notice [Forgejo-Design guidleine](https://codeberg.org/forgejo/design/)
* Notice/You must read [Developer Doc](https://forgejo.org/docs/next/contributor/)