gitea-blog/content/post/a-message-from-lunny-on-gitea-ltd.-and-the-gitea-project.md
HesterG dab0be78b2 docusaurus blog (#266)
# Notes

- date must not have double quotes, e.g., should be like `date: 2022-10-30T18:25:00+09:15`

- Updated header.

  ![Screen Shot 2023-07-11 at 17.27.49](/attachments/d14b0c62-3630-47a9-bcda-25c6459d4e8b)

- Used customized blog plugin to get all tags with reference to [plugins/blog/index.js](https://github.com/questdb/questdb.io/blob/master/plugins/blog/index.js). Filter by tag section, tag list page.

  ![Screen Shot 2023-07-11 at 18.10.28](/attachments/59561940-a2f7-4ab5-b99a-1d5b84fdbcad)

  ![Screen Shot 2023-07-11 at 17.31.20](/attachments/d6d82976-12c0-4c0f-acfe-218e30c7c627)

- Added coverImage to frontmatter to assgin cover image, e.g., `coverImage: "/img/blog-covers/test.jpeg"`
  And on blog page, cover image will appear on top if `coverImage` added to frontmatter, e.g.,

   ![Screen Shot 2023-07-11 at 17.33.09](/attachments/c27e7971-11db-4241-bc53-9e43df235fbc)

  ![Screen Shot 2023-07-11 at 17.33.20](/attachments/552dd9cf-fc55-4547-8014-864aeb0e5050)

- authors are managed by the `authors.yml` file. [reference](https://docusaurus.io/docs/blog#global-authors)
- [ejected](https://docusaurus.io/docs/swizzling#ejecting) `@docusaurus/theme-classic BlogListPage` and `@docusaurus/theme-classic BlogPostPage`, which are marked as `unsafe` by docusaurus, so need to maintain these components. ([original BlogListPage](https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/BlogListPage/index.tsx), [original BlogPostPage](https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/BlogPostPage/index.tsx))
- [referenced repo](https://github.com/questdb/questdb.io)

# How to test

```
npm i
npm run start
```

# Build and serve

```
npm run build
npm run serve
```

# Help Needed

Deploy and preview steps

# More Screenshots

![Screen Shot 2023-07-11 at 17.34.54](/attachments/ee9d46ac-72ac-49de-90df-38e2afc6db02)

Mobile:

![Screen Shot 2023-07-11 at 18.16.54](/attachments/8f1471a3-27cc-459a-a2ce-c0e5bdf604d3)

![Screen Shot 2023-07-10 at 17.53.18](/attachments/992d9f24-e130-41a9-8b55-86744539524c)

![Screen Shot 2023-07-06 at 11.02.21](/attachments/af1632b8-6a61-47f7-b15d-4a6080bebadb)

![Screen Shot 2023-07-11 at 18.17.43](/attachments/af0df617-27a4-46f9-a8a3-037be268e1cd)

![Screen Shot 2023-07-03 at 15.32.45](/attachments/ad2c1217-e82d-434c-81c8-5d4058e18591)

# TODO

- [x] Add Banner to blog page

Reviewed-on: gitea/blog#266
Co-authored-by: HesterG <hestergong@gmail.com>
Co-committed-by: HesterG <hestergong@gmail.com>
2023-07-12 03:25:19 +00:00

5.3 KiB
Raw Permalink Blame History

date authors title tags draft
2022-10-30T18:25:00+09:15 lunny A message from Lunny on Gitea Ltd. and the Gitea project
announcement
false

Thank you everyone for your comments and considerations over the past couple of days regarding our announcement on October 25, 2022. We know the Gitea community is involved and passionate about our shared project and thats why weve been taking the time to listen to your feedback, and I personally would like to address your concerns regarding its future.

Our beginnings

In 2015, I created Gitea along with its domain, gitea.io and acquired gitea.com at the same time. Throughout the life of the project, I have always personally owned both domains. As it continued to grow, I additionally trademarked the name “Gitea” in order to protect the projects brand. (More on the trademark later.)

Over the years, Gitea has matured into a robust community with over a thousand contributors globally. However, as with most open source projects, our maintainers have been mainly unpaid volunteers who have spent countless hours of their personal time to manage and grow Gitea. To support the sustainability of the project, we began creating a more formalized operating model so that Gitea could earn funding through public donations, selling Gitea merchandise, and receiving paid commercial contributions. We also ensured that those funds were then evenly distributed to cover basic overhead costs, while also reinvesting back into our maintainers so they could receive minor compensation for their time and effort. While this model has covered the barebones cost for operating, it is not enough to adequately and fairly compensate our maintainers for their time. As well, many commercial entities have been unable to work with individual Gitea maintainers as they often award contracts to organizations instead.

Our path forward

As we look towards the future of this project, we want to be able to bring in greater opportunities and attract an even broader pool of contributors so Gitea can truly thrive. That includes hiring both part-time and full-time maintainers to be part of the Gitea community so that the project gains dedicated talent and expertise solely focused on further developing Gitea. In order to support this vision, I took the next step to create Gitea Limited.

To keep a transparent governing structure for Gitea, the owners group will continue to vote on decisions about the distribution of funds and the direction of the project. We are working with our current maintainers to ensure that the governance will best support Gitea. I have also transferred both the domains and trademarked name to Gitea Ltd. so that they are no longer personally owned by me and will remain indefinitely with the Gitea project. The logo has always and will continue to be owned by the community.

Our operational plan

As part of building our business, we will introduce and test new methods for generating revenue for the Gitea project. This will include consulting and contracting arrangements, as well as sponsored development. This will enable us to invest the funds into bounties and other developer contributions, further benefiting the Gitea community.

Our goal remains that we will always give back to the Gitea community whenever possible. We have already been able to contribute back code weve made for clients into the codebase, so everyone can access the new developments. We are also currently working on a long-term support (LTS) version in order to provide a stable release for those who need it. As well, we are enhancing Giteas vulnerability disclosure program to ensure that security issues are reported and fixed in a timely manner.

Our continued community engagement

To help ensure the operation and community decision-making of the Gitea project remains transparent and public, were exploring the use of different management models. One of the options we have been considering includes a decentralized autonomous organization (DAO). This method would allow us to have continued voting within our community (including votes from non-code contributors), help keep track of topics being voted upon and provides contributors with greater participation to have more votes. The DAO management model would also not mean the creation of a gitcoin or crypto token. While we continue to deliberate how to best oversee and manage the Gitea project going forward, we will keep listening to your feedback as part of our discussions.

We want to be clear that Gitea will always be a community-built project that is open. This means:

  • the Gitea project source code will remain open sourced, MIT licensed, and available to everyone
  • Gitea Ltd. will be open to building special versions for special clients and will contribute any features back to the main repository when possible
  • Gitea Ltd. will always prefer and recommend contracts that align with that projects mission and values

This is just the start of our new chapter for Gitea and we want to continue engaging with our community members. As our commitment to the community, we will also provide quarterly updates on our progress and will continue to be transparent about our business plan to remain accountable to our contributors. We are always open to your feedback and welcome new ideas to help better the Gitea project.

Sincerely,

Lunny and techknowlogick