Remove Raspberry Pi documentation

[quozl]

Anurag Singh and Walter Bender replaced this documentation with https://github.com/sugarlabs/RPi-Docs

@walterbender, @Ovalelephant35, please review.

[Ovalelephant35]

Sir i have gone through this doc completely i was thinking rather than removing it altogether because generally people come to sugardocs only as a first choice is it possible that we can give a link to the same. @quozl sir

[walterbender]

I think the new docs are more comprehensive. But I think they should be referenced here or they will be hard to find.

[Ovalelephant35]

Though you are absolutely correct regarding dual and conflicting info but there aren't any conflicting info rather rpi docs is more in depth with VM hardware etc so if there is any alternative way.

[quozl]

Thanks. Please provide what you think should be in sugar/docs.

[rhl-bthr]

Why is the Raspberry Pi documentation moved to a separate repo and the rest of the distributions kept here?
This looks a little inconsistent?

[Ovalelephant35]

Currently Working on it , will make a proper linking and everything will be in order in sometime sorry for any inconvenience.
@rhl-bthr

[quozl]

Yes, it is unusual and inconsistent, and I've said so already, but we're an open source project, and if a developer wants to do something strange all we can do is wait for them to finish and then tidy up the mess. Bad workmanship is acceptable if it improves the situation marginally.

[Ovalelephant35]

Respected Sir @quozl @walterbender , the only reason its taking me time is because you must be aware about the fact that recently most of the chips have shifted to arm based so it has become very difficult to integrate VM and then run RPi and then sugar , but by investing time and talking around forums etc and running each and every command myself i tried to accumulate as much info as i can , as i dont want to put something which is wrong or ambiguous.
But after going through the docs i think we dont need RPi-docs at all as i have already done enough damage and i dont want it to propogate further as i only code, because it makes me happy and satisfied and i dont want to something which leads to distrust in already well established orgs like sugarlabs and also with my mental peace , so i know i have wasted enough of your time but would ask little bit more to just delete the repo as of now. I see only two forks one done by me and one done by my colleague who was helping me with windows VM and if it is possible to know all the people who have viewed the repo i will apologize to each of them even they are in thousands , also there were several issues raised with QEMU , Vbox , VMWARE and recently with debian if i get any update i will write in element channel.
Again I am reallly sorry from bottom of my heart and hope you will accept my apology as i am just a new developer coding from around 6 months i dont have any industry or professional experience i study in a college as sophomore student only.

[quozl]

Thanks for your thoughts. I've looked again at your work in https://github.com/sugarlabs/RPi-Docs/ and the most valuable steps are how to install Sugar and change the default desktop environment with update-alternatives, which is not a method we had recommended here yet. It is more typing than replacing .xession, but should last longer and is easier to understand. .xsession is frankly obscure.

I don't recommend using a VM or ARM emulator for Raspberry Pi OS; use the Raspberry Pi Desktop build instead, at the end of the page; https://www.raspberrypi.com/software/operating-systems/

Sorry, I don't know what element channel is.

[Ovalelephant35]

Thank you sir @quozl for providing additional insights and recommendations.
The only reason i used update-alternatives to change the default desktop environment is a robust method that ensures the changes persist across system updates and upgrades. It's a more systematic approach compared to directly modifying the .xsession file, which can be prone to issues and might not be as straightforward for some users.
But we have both the method already mentioned one is here in sugar-docs rpi.md we can leave it as it is and the other method as obvious in rpi-docs.
Regarding VM and emulator what i have to come to know is most people try to use VM only nowadays it is in general trend though installation guide is for any user i from my side use VM so that in worst case i can get result.
And element channel - matrix channel i was talking about.
Thankyou.

[Ovalelephant35]

And currently I was working on QEMU specific guide i have accumulated all the commands for any linux as well as MAC m1 , m2 , m3 users. And also working on certain activities specific those will be specific to RPi and have asked , searching for different examples so that RPi packaging can be done with more activities.

Now the major point being i was thinking of linking both the docs after i was done with all the activities and packaging but i think it would be better to remove dual information and just make it a single flowing if any user wants to go into complete RPi he can follow Rpi-docs with activities configuration etc with just some starting point being here rest all the docs in rpi-docs we can do it now otherwise it will create more confusion if anyone else comes and see dual presence of some info.

[quozl]

Okay, I suggest you begin with the branch on this pull request and make changes that appear in a new pull request. Then developers will review.

[Ovalelephant35]

Created Pull Request #982 Kindly suggest the changes if any ,
Though few important things

1. Major idea behind rpi-docs was to include all the activites and there setup and usage that can be modified with rpi sensors and gpio pins etc could be documented and kept at one place under activities section in Rpi-docs.
2. Packging RPi for sugar including relevant apps and creating custom image will also be documented,
   there links have not been provided as it part of the project and as soon as they will be done a seperate pr will be created to link them here

[Ovalelephant35]

Rest all the docs have been verified from my side and there is no conflict in any information as of now and as sugar-docs is first choice it can act as landing page for RPi doc if anyone is interested in that.
Thankyou