Summary:	ASTERISK-30317: Adding CodeSpaces config for the GitHub Mirror
Reporter:	Marcel Wagner (chingucoding)	Labels:
Date Opened:	2022-11-17 12:07:02.000-0600	Date Closed:	2022-11-17 12:07:02.000-0600
Priority:	Trivial	Regression?	No
Status:	Closed/Complete	Components:	Documentation
Versions:	20.0.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I was wondering whether you would accept changes to the Asterisk Gerrit Repository, who would only affect the GitHub mirror of the repository. Namely, would you accept adding a GitHub Codespaces config that would allow people to create a GitHub Codespace for the Asterisk project that is ready to compile the asterisk? Best, Marcel
Comments:	By: Asterisk Team (asteriskteam) 2022-11-17 12:07:02.468-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2022-11-17 12:07:02.863-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-11-17 12:10:35.321-0600 I'd prefer such things occur after we've moved over to Github. By: Marcel Wagner (chingucoding) 2022-11-17 13:42:03.974-0600 Do you happen to know when approximately that would be? By: Joshua C. Colp (jcolp) 2022-11-17 13:47:40.100-0600 We have not yet started but will start doing so shortly. I hope by the end January stuff will be settled. By: Marcel Wagner (chingucoding) 2022-11-17 14:03:00.689-0600 Looking forward to that, especially as an avid GitHub user and contributor (also happy to help with that move if there is any way)! So best now is to wait and get back to this once everything is settled with GitHub? By: Joshua C. Colp (jcolp) 2022-11-17 15:03:51.341-0600 That would be ideal, otherwise it's just piling more stuff onto the queue of stuff to do otherwise, and would likely get ignored until we moved to Github anyway. By: Marcel Wagner (chingucoding) 2022-11-18 06:33:10.401-0600 Alright, waiting for the move to GitHub then. Looking forward to that!