Recent events have made me realise something. In the early days, when PieFed was tiny (it’s still tiny I guess) me being really engaged with the community was a huge strength. I knew immediately what was going on and could release a fix/change really fast and people loved that. In contrast it made the other […]
yes, but we would go back to having more sources of truth that are heavier on the devs, even because of the repetitions and scattering of the same topics
why do you take single part of my message and answer to them like they are not part of the whole message blaze :(
first i said that single source of truth etc and then i pointed out that the single source has not to be dev oriented, don’t answer to my second point with the issue of the first point
Deactivitating issues there would hide visibility on the work being done and planned
that is not true, there are a lot of kanbans and ticketing software that can be used; to be fair, i should have said deactivating the possibility to open and comment except by mantainers
and in the system i proposed, you could still join and comment issues and features on piefed anyway (if you are not one of the piefed people)
yes, but we would go back to having more sources of truth that are heavier on the devs, even because of the repetitions and scattering of the same topics
why do you take single part of my message and answer to them like they are not part of the whole message blaze :(
first i said that single source of truth etc and then i pointed out that the single source has not to be dev oriented, don’t answer to my second point with the issue of the first point
that is not true, there are a lot of kanbans and ticketing software that can be used; to be fair, i should have said deactivating the possibility to open and comment except by mantainers
and in the system i proposed, you could still join and comment issues and features on piefed anyway (if you are not one of the piefed people)