On 11/10/22 20:05, Andreas 'Segaja' Schleifer wrote:
On 11/9/22 01:13, Levente Polyak wrote > I have a few questions about the setup:
1. Who can create issues? Anyone or only people registered to the gitlab or only staff?
Everyone, explicitly inviting the community as well. I've made this clear by adding a paragraph [0].
2. I saw that on the first issue [0] you added some labels and I was wondering from which guidelines/rules you derived the size. I'm not saying I object to the sizing, but it could be that the process of assigning a size feels a bit arbitrary.
They are based on t-shirt sizing strategy from agile project management. It's just an idea, the actual duration need to be declared by projects following it. I've picked a couple of ranges to distinguish between ideas that can be implemented in couple of days, around a week, a month or noticeably more. You can see the current sizing by hovering over the labels or in this overview: https://gitlab.archlinux.org/archlinux/ideas/-/labels
3. Is there some kind of timeline between proposing an idea and actual action on the idea (like making a tool out of it, accepting it, drafting an RFC)? I mean maybe there should be at least some kind of minimal time between the creation and any action on it.
There isn't anything strictly defined (yet). More like something that evolves out of the discussions or whenever marked as ready could simply be picked up right away.
4. What if an idea was rejected for some reason by I have an additional thought about it that suddenly would make the idea feasible? The issue template [1] states in the second checkbox that I have checked that the idea wasn't proposed before. In such cases is re-opening allowed?
Good point, I have extended the README.md and documented this case in this commit [1]. Providing new thoughts that could potentially tilt the previous reason for marking it as rejected is better to preserve discussion history instead of opening a new issue
Also one curious question I have when reading the README [2] is that in the last paragraph you defined a license (which is fine), but you posted the link to the license in a code block. Wouldn't it be more convenient to link it directly?
License link fixed as well. Thank you very much for your review! Cheers, Levente [0] https://gitlab.archlinux.org/archlinux/ideas/-/commit/e2fb11b26aecd9633b9875... [1] https://gitlab.archlinux.org/archlinux/ideas/-/commit/d7088e4e65270bcd6d17a4...