[Systems] developer.sugarlabs.org

[James Cameron]

Thanks for looking at this.

Needs more work; some of the actual documentation is missing.  For
example, compare
https://developer.sugarlabs.org/sugar3/sugar3.activity.activity.html
against
https://dev.sl.srevinsaju.me/sugar3/sugar3.activity.activity.html

Collapse the patches into one.

Otherwise, I don't see why it can't be merged into
https://github.com/sugarlabs/sugar-toolkit-gtk3

On Wed, Jan 06, 2021 at 12:30:19AM +0300, Srevin Saju wrote:
> I happened to see this thread late,
> 
> I would like to propose movinghttps://developer.sugarlabs.org/sugar3
> <https://developer.sugarlabs.org/sugar3> to
> https://github.com/sugarlabs/sugar-toolkit-gtk3
> <https://github.com/sugarlabs/sugar-toolkit-gtk3>'s GitHub pages. A live
> example of that would be here: https://dev.sl.srevinsaju.me/sugar3
> <https://dev.sl.srevinsaju.me/sugar3> built using GitHub Actions
> <https://github.com/features/actions> from
> https://github.com/srevinsaju/sugar-toolkit-gtk3.
> 
> *Procedure*
> 
> * The documentation is built on every commit to master, and deployed to
> `gh-pages` or a branch of choice
> * We host the static HTML version of the documentation using GitHub Actions,
> hence we can decommission developer.sugarlabs.org, which means, one less
> service we need to maintain. No more play with queues or docker builds,
> safer.
> * Update CNAME on Sugar Labs's nameservers to make developer.sugarlabs.org
> as an alias of sugarlabs.github.io
> * Update custom domain settings on
> https://github.com/sugarlabs/sugar-toolkit-gtk3 to point to
> developers.sugarlabs.org
> 
> Hence, we do not need to change any old links, as the links will still work,
> even if we discontinue the service on Freedom.
> 
> In my example / fork, I have added the script to sugar-toolkit-gtk3, and
> deployed the static docs to `gh-pages` branch. But, it is also possible to
> create a fresh GitHub repository: "developers.sugarlabs.org" and then add
> same script there, only that: the builds will now run on a cron job, instead
> of every commit to sugar-toolkit-gtk3. I suppose thats fine too, if we do
> not want to mess up with sugar-toolkit-gtk3 repository or keep it separate.
> In that case, we can make the repository at
> https://github.com/sugarlabs-infra. If the demo looks fine, let me know, and
> I will create a Pull Request to the preferred repository.
> 
> Let me know of suggestions, criticisms, pros and cons, or the need of any
> further information :)
> 
> 
> -- 
> Srevin Saju
> https://srevinsaju.me
> 

pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) <srevinsaju at sugarlabs.org>
> sub   RSA 4096/14479587 2020-05-19
> 




-- 
James Cameron
https://quozl.linux.org.au/