In T15048#2214, @20after4 wrote:Does anyone else feel that this is not a good idea? Seems like the consensus here is that it's at least acceptable if not desirable to have.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Apr 30 2022
Apr 30 2022
Sep 22 2021
Sep 22 2021
Agreed. We should aim to follow some specific conservative release. CentOS 7 seems reasonable.
Aug 24 2021
Aug 24 2021
what about egrohp? ("phorge" backwards)?
Aug 7 2021
Aug 7 2021
Jul 26 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
Jul 14 2021
eax closed T15032: [META] "Chat Room" link in sidebar still links to temporary Zulip instance as Resolved.
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
Jul 2 2021
Jun 26 2021
Jun 26 2021
eax added a comment to T15024: Landbot discussion(s), and generally ensuring that what is landed is what was reviewed.
In T15024#716, @avivey wrote:The plan upstream was to (eventually) have arc land trigger T182, and do the whole thing server-side.
Jun 25 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.
In T15008#651, @speck wrote:@jupe yea I figure similar to the Phabricator landing page on https://phacility.com/phabricator/ I think we want a basic static page which showcases the project & features, along with some form of T15010, then points to the other content on this install.
In T15008#619, @deadalnix wrote:In T15008#573, @jupe wrote:should we also start working on the content?
Yes. If there is something that is obviously useful and that you know how to do, then please do it. You'll be adding a ton of value.
Definitely -- I believe the idea that @avivey is aiming for is something extending AphrontSite which would serve up this static page/content, then we can update nginx to point phorge.it to that site leaving we.phorge.it to point here. If you'd like to start putting together the content or learning about extending AphrontSite that would be a great help.
Jun 21 2021
Jun 21 2021
Jun 20 2021
Jun 20 2021
Jun 19 2021
Jun 19 2021
In T15004#425, @speck wrote:Currently rP and rARC only allow Blessed Committers to push - with those herald rules in place should we open that up?
Jun 15 2021
Jun 15 2021
I also think we should make this an application / extension of phorge and not try to own something different.
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0