OK have finished uploading cosmin1's missing photos to the git now. Alongside the schematic.Again there is no editable .sch, because well: nobody listens to me. But this is supposed to be an open source project. So letting others edit your .sch is actually something that matters. To get people to map their circuits and share that.
Heres what you posted for my cosmin1, sorry it's rather late.
Images file size had to be reduced from 45mb. Because: git.
https://github.com/dreamcat4/t12-t245-controllers-docs/tree/master/controllers/stm32-t12-oled/v3.0-and-v3.1/r0@Dreamcat4, for changes like this, how can I set the git to allow 3rd party contributions?
Have left an extensive guidelines about that aspe
ct, in a comment on your PR #1.
In short: The right way takes a certain amount time, work, effort to setup. You create a new organization on github. Then you add collaborators to it. And give them with whatever permissions you wish. To work together with you on the shared organisation repo...
Very important bit: This then has the added benefit meaning your own repo can have unstable code in it. Then when you are ready push / publish to the org repo.
However others can still see what you are doing, for the unstable work.
Discussion of that here:
https://github.com/deividAlfa/stm32_soldering_iron_controller/pull/1#issuecomment-735274759Also, I'd apreciate some help in the documentation side, as I already saw you are good at it.
I'd like to have all the files like boards, schemtatics, well organized.
OK so the big thing to realize here is that:
For the way that git works, we absolutely cannot put all that stuff into the same git repo as the code. Because the size of all the PDF files and images. And other documentation assets. Its hundreds of megabytes.
Git is accumulative, so nothing gets deleted in there. Already tried some work arounds to avoid that (git LFS, etc). Unfortunately it just doesn't work on github. Not without paying money for storage etc. And this is an open source project. So that is not possible like that.
Anyhow, so this is why the seperate docs repo exists to begin with. I'm very happy to move that repo into a new github organisation, should you decide to create one. For where to put your source code as 'published' and 'stable'. Then multiple people can work on it easily. And improve / upload. Add further assets. Re-organize it. And the docs is just another repo allongside the source code repo.
In fact can have multiple docs repos. If the existing docs repo is too big. For something not the whole kitchen sink. Then just create a brand new docs repo. That is more slim. And easier to follow. While my docs repo is more like a collection of reference materials. To keep them safe.
I'm not going to be responsible for that myself. For time reasons. I have other priorities. Instead everybody should contribute to documenting stuff. It's a community effort. I do my part, so others should too. Which also includes everybody these forums, very helpful!
Just be sure not to stuff the docs in the code repo. It will hurt the repo size too much. To mix them together.
BTW sorry I have not received any new notifications of activity here. But it turns out the forum stops notifying me of stuff, unless I come back to visit the forum again.
So the main thing I missed was you renamed your branch to 'master'. Great. OK so now that you have one clear branch. Then I have now updated the landing page on the docs repo. To point to your master branch. Hopefully it helps for others to find.
Actually theres pages in that docs repo it needs updating. Like where i put: stuff not tested, etc. Well it's getting tested right now! Just even doing that i don't have the time for. But at least the README.md (landing page) is updated.
https://github.com/dreamcat4/t12-t245-controllers-docsAnd also the README page for the controllers themselves
https://github.com/dreamcat4/t12-t245-controllers-docs/tree/master/controllers/stm32-t12-oledAnd that's all the time I have for this project today! (And tomorrow, next week). Until I can try cracking the read protection again. To try to dump the OFW again. With those new set of security hacks.
Home
Help
Search
Login
Register
Topic: CFW for KSGER/Quicko STM32 Soldering Stations (Read 677408 times)