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

Organize this repo somehow #2

Open
praiskup opened this issue Nov 1, 2022 · 2 comments
Open

Organize this repo somehow #2

praiskup opened this issue Nov 1, 2022 · 2 comments

Comments

@praiskup
Copy link
Member

praiskup commented Nov 1, 2022

  • it would be nice to have team ideas/brainstorming dumped somewhere, note there's the abandoned ./doc/brainstorming.rst in main repo
  • organizing research, something like Packit has
  • the bigger features before being implemented, this is how CKI team is doing this
@FrostyX
Copy link
Member

FrostyX commented Nov 1, 2022

organizing research, something like Packit has

Sounds good.
Also, we need to decide whether to push freely into the repository or if we want to do pull requests.

./doc/brainstorming.rst

FTR link here https://docs.pagure.org/copr.copr/brainstorming.html

We need to ditch this. It is a list of RFEs, therefore it collides with our pagure issues and it lacks many features (it's way harder to use, so nobody from the community will use it, there is no comment section, and the page needs to be manually rebuilt after every change). And the same time it is much worse for complicated proposals or RFEs than this repository or pagure issues because it's a single page.

It is from the time when we used cgit and there wasn't a better alternative for research documents.

@nikromen
Copy link
Member

nikromen commented Nov 2, 2022

I personally prefer doing it similarly as packit does it. The other option sounds too complicated (writing some web content to it and maintain it).

Also, we need to decide whether to push freely into the repository or if we want to do pull requests.

PRs sounds like a good idea when we want to discuss something in the research. If the researcher decides that there is no need for discussion he/she can push to the repo directly. So I would leave this decision (whether PR or push directly) to the person doing the research.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants