Version 1 vs 3
Version 1 vs 3
Content Changes
Content Changes
=== Meeting notes for {E2}
Attendees:
- @Matthew
- @avivey
- @dcog
- @20after4
1. Action item check-in
- @avivey Set up a table of the Phorge applications, organizing the effort to being rebranding (Completed)
- @speck Update the strategy for how we're going to approach the rebrand so others can contribute (Completed)
- @avivey Communicate our strategy with the upstream (Completed)
- @speck Update meeting notes, organize into Phriction pages (Completed)
- @Matthew Set up new recurring meeting (Completed)
2. High priority task: Rebranding
- {T15077}
- No diffs yet.
- Problem: A ton of work...
- Wikimedia has a translation importer/exporter tool that could perhaps help here. https://phabricator.wikimedia.org/source/phabricator-translations/
- Diviner: Perhaps we can add a banner stating that Phorge is derived from Phabricator to our public-facing documentation. This might buy some time for us to complete the rebrand.
- Dan wants to investigate Rector to see if it will make rebrand easier. Handed as an action item.
3. Spammers
- Automated deployment from our own git repo?
- https://phabricator.wikimedia.org/source/phabricator-ava/ - Useful, potential to migrate into upstream at a future date.
- It's a really good idea to limit users before they're part of #trusted_contributors
- Another useful tool is Askimet: https://github.com/aag/mwakismet - Perhaps we can integrate that into the Phorge code with a configuration option?
- {T15084} might also perhaps help. We should lock down most everything to #trusted_contributors on this install, except perhaps Ponder.
- Better moderation tools also help
- Unbundling of Administrator tools might be useful? WMF does that.
- We could use Projects for that - WMF does that. This gives more granular control but is something we would need to code.
- How do we support open source better? Phabricator is designed closed-source first, but open-source projects have adopted it. Open-Source support is a high priority.
Action Items
- @Matthew Discuss banner on {T15012}
- @Matthew Create task and discussion around integrating Askimet.
- @20after4 - Lock down what we can on this install, make notes on what we can't install.
- @20after4 - Create a banner for the frontpage to show people how to contribute (Link to ponder, info on trusted contributors)
- @dcog Investigate Rector: https://getrector.org/
=== Meeting notes for {E2}
Attendees:
- @Matthew
- @avivey
- @dcog
- @20after4
1. Action item check-in
- @avivey Set up a table of the Phorge applications, organizing the effort to being rebranding (Completed)
- @speck Update the strategy for how we're going to approach the rebrand so others can contribute (Completed)
- @avivey Communicate our strategy with the upstream (Completed)
- @speck Update meeting notes, organize into Phriction pages (Completed)
- @Matthew Set up new recurring meeting (Completed)
2. High priority task: Rebranding
- {T15077}
- No diffs yet.
- Problem: A ton of work...
- Wikimedia has a translation importer/exporter tool that could perhaps help here. https://phabricator.wikimedia.org/source/phabricator-translations/
- Diviner: Perhaps we can add a banner stating that Phorge is derived from Phabricator to our public-facing documentation. This might buy some time for us to complete the rebrand.
- Dan wants to investigate Rector to see if it will make rebrand easier. Handed as an action item.
3. Spammers
- Automated deployment from our own git repo?
- https://phabricator.wikimedia.org/source/phabricator-ava/ - Useful, potential to migrate into upstream at a future date.
- It's a really good idea to limit users before they're part of #trusted_contributors
- Another useful tool is Askimet: https://github.com/aag/mwakismet - Perhaps we can integrate that into the Phorge code with a configuration option?
- {T15084} might also perhaps help. We should lock down most everything to #trusted_contributors on this install, except perhaps Ponder.
- Better moderation tools also help
- Unbundling of Administrator tools might be useful? WMF does that.
- We could use Projects for that - WMF does that. This gives more granular control but is something we would need to code.
- How do we support open source better? Phabricator is designed closed-source first, but open-source projects have adopted it. Open-Source support is a high priority.
Action Items
- @Matthew Discuss banner on {T15012}
- @Matthew Create task and discussion around integrating Askimet.
- @20after4 - Lock down what we can on this install, make notes on what we can't install.
- @20after4 - Create a banner for the frontpage to show people how to contribute (Link to ponder, info on trusted contributors)
- @dcog Investigate Rector: https://getrector.org/
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