Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Everyone can easily contribute to packit-service #1880

Open
3 tasks
TomasTomecek opened this issue Feb 2, 2023 · 2 comments
Open
3 tasks

Everyone can easily contribute to packit-service #1880

TomasTomecek opened this issue Feb 2, 2023 · 2 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.

Comments

@TomasTomecek
Copy link
Member

TomasTomecek commented Feb 2, 2023

Since all sources of Packit GitHub app are open, let's continue towards open source service concept by making it easier for everyone to contribute.

Old confusing motivation Keeping this paragraph for sake of transparency, thanks Hunor for pointing it out.

All our code, deployment recipes, app metadata, documentation is open. The deployment itself (i.e. the cluster) is not for obvious reasons. Metrics are also not open. Hence we meet the criteria for Packit GitHub app to be a truly open source service.

The goal of this issue is to make packit-service more friendly to receive contributions from the public.

We also want to provide info on what exact code (git hash) it is running for all our git repos. One can then navigate and browse sources of code that is running live: both prod and stg.

TODO:

  • The REST API provides info (commit hash, or git tag) of what exact code it's running
  • Check run descriptions have links how anyone can contribute to Packit GitHub app
  • (optional) create follow-up cards or provide additional ideas or proposals what we can improve
@csomh
Copy link
Contributor

csomh commented Feb 6, 2023

Do you mean: "Hence, we do not meet the criteria..."?

@TomasTomecek
Copy link
Member Author

Thanks for the pointer, I am going to reword the first paragraph, agreed it is confusing. The main problem is that we don't have a precise definition of what "open source service" is, the Stef's blog is just a pitch.

@lachmanfrantisek lachmanfrantisek added kind/feature New feature or a request for enhancement. complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. area/general Related to whole service, not a specific part/integration. gain/low This doesn't bring that much value to users. labels May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.
Projects
Status: backlog
Development

No branches or pull requests

3 participants