Github repo for main website source?
-
@RayCulp I think it is there https://github.com/ubports/ubports.com
-
@lduboeuf Thanks for that info.
@all Just wondering, the README.md says I should check https://wiki.ubports.com/wiki/Writing-a-Good-Bug-Report for hints on how to write a good bug report, but that site is currently down. Does anyone know if this is temporary?
-
@lduboeuf
Isn't UBports team migrating on gitlab ? -
@Keneda said in Github repo for main website source?:
@lduboeuf
Isn't UBports team migrating on gitlab ?it will yes, but not all repositories yet
-
@RayCulp Short answer, there is not a repo for the main website, but there is acknowledgement it needs to be easier for community contribitions. The Github Issues page is the best place to log issues with the website, though it seems to be checked infrequently.
My suspicion is that wiki.ubports is dead, and is replaced by docs.ubports.com, though there is still the occasional dead link.
https://docs.ubports.com/en/latest/contribute/bugreporting.html is not quite a perfect replacement, but contains some guidelines about halfway down the page.
-
@prophanetes said in Github repo for main website source?:
My suspicion is that wiki.ubports is dead, and is replaced by docs.ubports.com, though there is still the occasional dead link.
https://docs.ubports.com/en/latest/contribute/bugreporting.html is not quite a perfect replacement, but contains some guidelines about halfway down the page.Ok, is there a way we could determine that for sure? Then I could go ahead and edit the readme.md file and have it point to https://docs.ubports.com/en/latest/contribute/bugreporting.html. Who would I need to talk to for access/permission.
-
@RayCulp said in Github repo for main website source?:
Ok, is there a way we could determine that for sure? Then I could go ahead and edit the readme.md file and have it point to https://docs.ubports.com/en/latest/contribute/bugreporting.html. Who would I need to talk to for access/permission.
The Wiki is gone and not coming back. The docs page is the future. The readme is in a GitHub repo, so you don't need special access. Fork the repo to your own account, make the necessary changes in your fork. And then propose the changes back as a PR (Github) or MR (Gitlab) to the main repo. Lastly, bug someone (probably one of the contributors, but preferably not Marius G. Although I'm not sure who else otherwise... ) to review and merge your PR / MR.
-
@arubislander said in Github repo for main website source?:
The readme is in a GitHub repo, so you don't need special access. Fork the repo to your own account, make the necessary changes in your fork. And then propose the changes back as a PR (Github) or MR (Gitlab) to the main repo.
Very true, didn't think of that.
@arubislander said in Github repo for main website source?:
Lastly, bug someone
Yeah... I'm not so sure about that part.
-
Just one more question: The README.md also says "Please make sure that you're in the right place".
That page, which was also part of the wiki, was a list of bug trackers for different purposes. Here is a snapshot of the page:
https://web.archive.org/web/20170622144801/https://wiki.ubports.com/wiki/UBports-Bug-Trackers
I didn't find anything similar in the current documentation, but I think such a list is quite useful. If it does not yet exist, then since the logical place to (re)create it would be the documentation site, and since it would take a while to create it and get it merged, I would suggest creating a short, temporary list directly in the README.md file. If you have time, please have a look at my proposed changes here: https://github.com/RayCulp/ubports.com/tree/master
If it seems like I'm a little unsure of myself, that's because I am.
Up till now I've only ever used Github to host my own private repos. I've never actually created a single pull request. -
@RayCulp said in Github repo for main website source?:
If it seems like I'm a little unsure of myself, that's because I am. Up till now I've only ever used Github to host my own private repos. I've never actually created a single pull request.
That is the beauty of PR's. You propose them, and a discussion develops around them. Suggestions for improvements can be implemented in your fork, and the PR will automatically be updated to reflect the changes.
