Improve cross-platform setup documentation (Windows, WSL, Linux)

[VanshikaTygi]

While testing the Speak activity locally on both Windows and Ubuntu, I encountered some platform-specific setup issues that may be helpful to document for new contributors.

In particular:

• Running python activity.py outside the Sugar desktop/runtime environment results in ModuleNotFoundError: dbus.
• This behavior is expected since activity.py depends on the Sugar runtime and system-level dbus integration.
• On Windows (without Sugar installed), the full activity cannot run outside the Sugar runtime.
• Core modules such as TTS and LLM components can still be tested independently.

It may be helpful to add a short section in the README clarifying:

1. The difference between testing core AI modules directly.
2. Testing the full Sugar activity (via Sugar desktop or Sugar Live build).
3. Any notes regarding Windows, WSL, or macOS environments.

This could reduce confusion for new contributors attempting to run the activity directly outside the Sugar environment.

I’d be happy to help draft a “Common Setup Issues” section if this sounds useful.

[aditii23]

Hii, @mebinthattil and @chimosky
I’m interested in working on this issue.
I have reviewed the codebase and have a good understanding of what needs to be done. I’m confident I can implement a proper solution.
Could you please assign this issue to me? I’ll start working on it right away.
Looking forward to contributing!!

[VanshikaTygi]

Hi @aditii23,
Thanks for your interest in this issue!

I’ve already submitted a PR addressing this (#36 ), which is currently under review.

Feel free to take a look, and if there are any improvements or related enhancements you’d like to contribute, that would be great! 🙂

[mebinthattil]

@VanshikaTygi Please don't create an issue if you plan on working on the issue yourself. That just creates unnecessary noise for us maintainers. Raise an issue only if you don't intend on working on it.

If you find an issue and you want to fix it you can just raise a PR with the fix instead.

@aditii23 you don't need to be assigned an issue to work on it. You are free to work on any issues, if you decide to do so, raise a PR and reference this issue in the PR description.

[VanshikaTygi]

Hi @mebintthatti,

Thanks for the clarification, I understand your point.

I created the issue to document the problem I encountered while testing, but I see how it can add unnecessary noise if I’m already working on it.

Going forward, I’ll directly raise a PR with the fix and reference it instead of creating a separate issue.

Thanks for the guidance!