User Details
- User Since
- Jun 10 2021, 06:40 (179 w, 3 d)
- Roles
- Administrator
- Availability
- Available
Apr 30 2022
Sep 22 2021
Agreed. We should aim to follow some specific conservative release. CentOS 7 seems reasonable.
Aug 24 2021
what about egrohp? ("phorge" backwards)?
Aug 7 2021
Jul 26 2021
FWIW I don't object to support or community channels off-instance but I do think we need:
- all decisions should be made on-instance
- we should have a culture of ensuring that any "interesting" discussions get recorded on-instance.
Jul 14 2021
Deleted the reference. All communication should happen on-instance.
FWIW I think the master / stable split happened upstream due to some planned deep rewrites. For our process I'd rather go masteronly and not have a separately stable or release branch.
Jul 2 2021
Jun 26 2021
Jun 25 2021
I am not a fan of adding interaction to the upgrade process but we can use the "setup issues framework" or an approach similar to @deadalnix's comment.
I like the proposal above. Especially with having the core team "sign" a vision statement. The goal is less legalistic and more of ensuring we have a consistent view of the end product.
Jun 21 2021
Jun 20 2021
Jun 19 2021
Jun 15 2021
I also think we should make this an application / extension of phorge and not try to own something different.