You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/03/26 19:30:25 UTC
[GitHub] [cloudstack] apurv-1 opened a new pull request #4879: [UPDATE] IRC on Readme.
apurv-1 opened a new pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879
### Description
The readme file had older `irc.freenode.net`, without any link.
<!--- Describe your changes in DETAIL - And how has behaviour functionally changed. -->
<!-- For new features, provide link to FS, dev ML discussion etc. -->
<!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. -->
<!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed when this PR gets merged -->
<!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
<!-- Fixes: # -->
<!--- ********************************************************************************* -->
<!--- NOTE: AUTOMATATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE DOCUMENTATION. -->
<!--- PLEASE PUT AN 'X' in only **ONE** box -->
<!--- ********************************************************************************* -->
### Types of changes
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] Enhancement (improves an existing feature and functionality)
- [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
### Feature/Enhancement Scale or Bug Severity
#### Feature/Enhancement Scale
- [ ] Major
- [x] Minor
#### Bug Severity
- [ ] BLOCKER
- [ ] Critical
- [ ] Major
- [ ] Minor
- [x] Trivial
### Screenshots (if appropriate):
### How Has This Been Tested?
By open `https://webchat.freenode.net/` on the browser.
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- Please read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md) document -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] apurv-1 commented on pull request #4879: [UPDATE] IRC on Readme.
Posted by GitBox <gi...@apache.org>.
apurv-1 commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-808949737
Done @GabrielBrascher
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] DaanHoogland commented on pull request #4879: [REMOVED] IRC references on Readme.
Posted by GitBox <gi...@apache.org>.
DaanHoogland commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-810073668
come to think about it, this should go on as old a branch as possible, should it?
cc @GabrielBrascher @rhtyd @andrijapanicsb @PaulAngus
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] GabrielBrascher commented on pull request #4879: [REMOVED] IRC references on Readme.
Posted by GitBox <gi...@apache.org>.
GabrielBrascher commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-809487810
Ping for review: @PaulAngus @andrijapanicsb @DaanHoogland @rhtyd @svenvogel @wido @kiwiflyer @ustcweizhou @weizhouapache and others.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] andrijapanicsb commented on pull request #4879: [UPDATE] IRC on Readme.
Posted by GitBox <gi...@apache.org>.
andrijapanicsb commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-808872959
+1 on what Paul said.
Remove all IRC info. as it's (at best) misleading, and mention Slack channel together with a way on how to requests joining it (@kiwiflyer had some fancy Google Form sheet or something), but still emphasise " it's ML or nothing"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] PaulAngus commented on pull request #4879: [UPDATE] IRC on Readme.
Posted by GitBox <gi...@apache.org>.
PaulAngus commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-808856539
The discussion was here @GabrielBrascher - https://lists.apache.org/thread.html/296def97c549e0b75bc14d0382ae412245cef6088e576acbcb007cc8%40%3Cdev.cloudstack.apache.org%3E
I think my view remains the same - only promote the mailing lists and if people want to have a synchronous call/chat, they can use whatever platform they like at the time. That may be the Slack channel, whereas the UI SIG used an adhoc Google Meet.
If a subject such as this can be resolved through community discussion, there is no need for a formal vote.
(For the record, irc.freenode.net is the URI for an IRC client, webchat.freenode.net is *a* client, which may or may not stay around)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] GabrielBrascher commented on pull request #4879: [UPDATE] IRC on Readme.
Posted by GitBox <gi...@apache.org>.
GabrielBrascher commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-808939613
@PaulAngus @andrijapanicsb thanks for answering. In order to track such a process, I created issue #4880.
@apurv-1 as you brought this up, could you please change the PR scope from _updating the IRC reference_ to _removing IRC references_ at the README?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] GabrielBrascher commented on pull request #4879: [REMOVED] IRC references on Readme.
Posted by GitBox <gi...@apache.org>.
GabrielBrascher commented on pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879#issuecomment-811588123
Good question, @DaanHoogland.
IMHO I don't see much problem with keeping it on master; I think that users tend to check the README at the master.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rhtyd merged pull request #4879: [REMOVED] IRC references on Readme.
Posted by GitBox <gi...@apache.org>.
rhtyd merged pull request #4879:
URL: https://github.com/apache/cloudstack/pull/4879
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org