- Updates

December 15th

2022-12-15T00:00:00+00:00

After many days of hard work and preparation by a team of former Gitea maintainers and enthusiasts from the FOSS community, we are proud to announce that the Forgejo project is now live.

Forgejo (/forˈd͡ʒe.jo/ inspired by forĝejo – the Esperanto word for forge) is a community-driven Free Software project that develops a code forge platform similar to GitHub, and that is a drop-in replacement for Gitea. We started Forgejo in reaction to control of Gitea being taken away from the community by the newly-formed for-profit company Gitea Ltd without prior community consultation, and after an Open Letter</a> to the Gitea project owners remained unanswered. The Forgejo project has two major objectives that drive our development and road map:

The community is in control, and ensures we develop to address community needs.</li>

We will help liberate software development from the shackles of proprietary tools.</li> </ol>
Read more</a>.

December 6th

2022-12-06T00:00:00+00:00

Forgejo launch is planned for December 15th and this is the last daily update. You are kindly invited to follow the project at https://floss.social/@forgejo</a> from now on, or to join us in our Matrix chat room</a>. We welcome suggestions on our issue tracker</a>.

December 5th

2022-12-05T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

December 4th

2022-12-04T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

December 3rd

2022-12-03T00:00:00+00:00

The Forgejo repository and feature branches were rebased on top of the latest Gitea development branch and the v1.18 stable branch. This rebasing happens weekly because Forgejo is a soft fork of Gitea. All CI pipelines are green.

December 2nd

2022-12-02T00:00:00+00:00

The 50,000€ NLnet</a> grant to further forge federation started December 1st and its progress can be followed in the Forgejo feature branches</a> dedicated to them.

December 1st

2022-12-01T00:00:00+00:00

A 50,000€ grant application was sent to NLnet</a> to support the development of federated UI/UX.

Hosting for the website https://forgejo.org is ready.

November 30th

2022-11-30T00:00:00+00:00

Forgejo has a logo</a> and a mascotte</a>.

November 29th

2022-11-29T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 28th

2022-11-28T00:00:00+00:00

The Forgejo launch is scheduled for December 8th, 2022. Updates will then be posted on the Forgejo social account at https://floss.social/@forgejo.

November 27th

2022-11-27T00:00:00+00:00

The first draft of the contributor guide</a> is complete, covering all aspects of the Forgejo project: governance, development workflow, release process, security vulnerability handling, Developer Certificate of Origin and funding.

A Forgejo mascot was sketched and discussed: it could be a steampunk squirrel, a mamal that spends a lot of time caring for its food storage.

November 26th

2022-11-26T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 25th

2022-11-25T00:00:00+00:00

A 50,000€ grant application was sent to NLnet</a> to support the development of Forgejo. The packages</a> and binaries</a> for the Forgejo 1.18.0-rc1 experimental release are published. The first meeting to define the Forgejo governance happened and another will follow in two weeks.

November 24th

2022-11-24T00:00:00+00:00

An interim Forgejo logo</a> is now in use while the definitive logo is designed.

November 23rd

2022-11-23T00:00:00+00:00

A social account was created for Forgejo at https://floss.social/@forgejo. It will not publish updates immediately but everyone is welcome to follow.

November 22nd

2022-11-22T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 21st

2022-11-21T00:00:00+00:00

The link to the Matrix account</a> and Mastodon profile</a> are part of our README in order to get verified links. Our CI process for updating the website was hardened to limit the blast radius in case of a security incidence in the future. We are looking for a tagline</a>. Have an idea? Let us know!

November 20th

2022-11-20T00:00:00+00:00

The proofs were uploaded to keyoxide for security@forgejo.org</a>.

November 19th

2022-11-19T00:00:00+00:00

The GPG signing keys for the release and security teams have been generated and published. The proofs were uploaded to keyoxide for contact@forgejo.org</a> and release@forgejo.org</a>.

November 18th

2022-11-18T00:00:00+00:00

The release process is implemented and documented to publish Forgejo 1.18.0-rc1 as soon as Gitea 1.18.0-rc1 is released.

November 17th

2022-11-17T00:00:00+00:00

Preparations are made to publish Forgejo 1.18.0-rc1 as soon as Gitea 1.18.0-rc1 is released. A security team is discussed to cover both Forgejo and Codeberg. The Forgejo domain name (forgejo.org) is in the name of Codeberg e.V. at the registrar. A grant application is drafted to support Forgejo.

November 16th

2022-11-16T00:00:00+00:00

Forgejo</a> is the name that was picked. Codeberg e.V. explicitly accepted the proposal</a> to host and use Forgejo.

The next step is to figure out how to properly communicate about Forgejo</a>.

November 15th

2022-11-15T00:00:00+00:00

The development workflow</a> discussed over the past week</a> was bootstrapped</a>.

November 14th

2022-11-14T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 13th

2022-11-13T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 12th

2022-11-12T00:00:00+00:00

Discussions started today to apply for a 50,000€ grant</a> to further the project. It is still unclear if all the conditions are met for it to succeed.

November 11th

2022-11-11T00:00:00+00:00

There is no high level update today although progress happened.

See here</a>, here</a> and there</a> for the details.

November 10th

2022-11-10T00:00:00+00:00

A Code of Conduct was adopted</a> and immediately applies to all spaces of the fork (chatroom, repositories, etc.). A "well being" and a moderation team were appointed and are ready to help preserve an inclusive environment for everyone.

November 9th

2022-11-09T00:00:00+00:00

People willing to help launch the fork can pick a task</a> and get involved, follow the progress in the dedicated chatroom</a> or discuss in the space where over sixty people got together in the past week</a>.

November 8th

2022-11-08T00:00:00+00:00

The launch date for the fork is set to December 15th, but it could happen earlier if all is ready. The list of tasks</a> that need to be completed before the launch is finalized and work is in progress.

November 7th

2022-11-07T00:00:00+00:00

The process of picking a name for the fork has started and will be completed November 13th. A number of other tasks are being worked on for the launch to happen and can be found in the corresponding milestone</a>.

These updates will stop when the fork launches and will be replaced by blog posts and release notes.

November 6th

2022-11-06T00:00:00+00:00

Early feedback from Codeberg e.V. indicates the proposal to host and use the fork was received positively and a decision can be expected in the following days.

A temporary organization</a> was created at Codeberg to prepare for the launch of the soft fork. It has repositories for non-technical tasks</a>, a temporary repository for the fork</a> and another for the content of the website</a>.

November 5th

2022-11-05T00:00:00+00:00

The process to pick a name has been established and will now be implemented.

Discussions regarding the long term sustainability covered donations campaigns, grant applications and personnel delegation.

The Woodpecker CI</a> was setup for the current Codeberg codebase</a>. If Codeberg agrees to host and use the fork, a similar configuration will be used for the CI.

November 4th

2022-11-04T00:00:00+00:00

Around fifty names were suggested (Smithy, GitLibre, LibreForge etc.).

Preliminary technical work started to use Woodpecker</a> for the CI of the fork, instead of Drone which is proprietary software</a>.

November 3rd

2022-11-03T00:00:00+00:00

An action plan was proposed to Codeberg e.V.</a> to host and use a Gitea soft fork.

When the fork happens, it should be communicated to the general public in a positive way. Work has been done to create communication material that conveys a broad vision of Free Software development, which will hopefully help convey the cooperative state of mind in which the fork is being prepared.

November 2nd

2022-11-02T00:00:00+00:00

The action plans converged into one that is in its final draft stage. A few names were suggested for the fork and registered as a precaution.

November 1st

2022-11-01T00:00:00+00:00

More discussions and drafting of two action plans, with a focus on allowing Gitea developers to find a transparent, democratic and Free Software environment.

October 31th

2022-10-31T00:00:00+00:00

A plan for a hard fork drafted on October 29th is set aside. A new, low profile action plan based on a soft fork is in draft stage. It focuses on allowing Gitea developers to find a transparent, democratic and Free Software environment and continue their work in an existing organization like Codeberg. It could keep the Gitea community united.

Discussions regarding the claims that Gitea Ltd was created to solve a sustainability problem led to the publication of a blog post: The Gitea Ltd Sustainability Smokescreen</a>.

October 30th

2022-10-30T00:00:00+00:00

Ambassador(s) are engaged in discussions with the shareholders of the Gitea Ltd company and the members of the Gitea Community who signed the Gitea Open Letter. In the afternoon, a second blog post is published</a> and signed by Lunny and techknowlogick.

The shareholders of Gitea Ltd do not agree to the demands of the Gitea Open Letter.

October 29th

2022-10-29T00:00:00+00:00

A second blog post is being prepared from the same authors as the original Gitea post.

October 28th

2022-10-28T00:00:00+00:00

The announcement of Gitea Ltd raised concerns from members of the Gitea community, who published the Gitea Open Letter</a>. It was advertised</a> on the fediverse, HN etc. 

October 25th

2022-10-25T00:00:00+00:00

A blog post was written on the Gitea blog</a>, informing about the creation of a company named Gitea Ltd.