<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Remember that in my design for aslov4, it must "support activity bundles uploaded via ssh," </pre> </blockquote> I have seen and read the GSoC guidelines. I have also noticed that aslov4 should support activities uploaded by ssh. But it is almost impractical in my case. I do not own a ssh server so I cannot build / deploy a server / storage where I could publicly give ssh access to developers at sugarlabs. The best I could do is to make use of a free service (in this case, GitHub; but I have also mentioned of the alternatives to GitHub in my first email, (because personally I do not prefer Github too). If in case, I get access to a free ssh server on Google Cloud Platform or something, I will extend this feature. Because, I cannot implement a feature which I cannot test. But this is absolutely possible, because sugarappstore-generator script is modular, I can easily provide the bundle location and it can automaticaly generate the static location. In this case, a custom `list_activities` needs to be defined to find uploaded bundles. <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">and may also "for a specific list of activities, access the source repository and detect any change to a release tag (publish), create a bundle and extract release notes,"</pre> </blockquote> I am not sure if you have noticed, I have added support for all activities to extract the release notes from the current tag. The problem with some repositories is that, they do not use annotated tags, so I cannot extract the Release notes from the tags. But I am able to extract the Release Notes from activity NEWS. I added this feature in the past week, maybe it went unnoticed. To do some special testing / checking / checking out some commit or branch on the activity, the generator gives the option as given below ``` --build-entrypoint BUILD_ENTRYPOINT Specify a path to any Linux compatible script which is intended to be executed on every build --build-override Override `python setup.py dist_xo` with --build-entrypoint argument shell script --build-chdir Changes directory to Activity dir ``` It implies, we could feed a custom build script, instead of using `python setup.py dist_xo` . So I hope that would do! The idea of automatic building was to <ul> <li>increase the quality of activity (I will extend this to testing activities, (make sure it starts) using Continuous Integration) </li> <li>an activity built on your system, should be equally built on another developer's system (i.e should be reproducible)</li> <li>Reduce the time needed by developers to manually fill in the details and, upload binaries etc etc. I have used the exact same principle used by the <a class="moz-txt-link-freetext" href="https://appimage.org">https://appimage.org</a> You can see their pull requests, which automatically tests if the appimage would work on Ubuntu Xenial (the oldest LTS). </li> </ul> Please let me know if there is anything I can do. I will try to get a server (temporarily) to add the ssh feature. <div class="moz-cite-prefix"> </div> <div class="moz-cite-prefix">On 30/06/2020 09:24, James Cameron wrote: </div> <blockquote type="cite" cite="mid:20200630062442.GJ13840@laptop.org"> <pre class="moz-quote-pre" wrap="">On Tue, Jun 30, 2020 at 12:22:41AM +0300, Srevin Saju wrote: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Thanks Yes, there is no single source of Python 3 activity bundles. There was for Python 2 activities; it was activities.sugarlabs.org. I hope aslov4 would solve this issue. I have now uploaded entire successfully built Python3 bundles to <a class="moz-txt-link-freetext" href="https://github.com/srevinsaju/sugar-activity-build/">https://github.com/srevinsaju/sugar-activity-build/</a> releases. You can check them out if you are interested and get some spare time. </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> Thanks. That there is no single source of Python 3 activity bundles doesn't really cause a problem for me. I don't need aslov4 to fix it. There's more to the dependency problems than Python version. That's why I said in the aslov4 idea "(a) ported to Python 3 and released, and (b) tested on Sugar Live Build." </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap=""> Yes, there is no single source of activity sources. Best we have is GitHub sugarlabs org, where directory activity has a file activity.info which has a valid exec key. But also gitorious. By 'no single source', is there any instance of python3 activities on gitorious? </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> You'd have to look. I don't know of any. Ibiam is probably right, but as Gitorious is still open, commits may be pushed, and so there is a possibility that a repository there may contain activity source compatible with Python 3. I don't think you need to concern yourself with it though. </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">I wanted to know if all the python3 activities are either forked or owned as a repository at sugarlabs GitHub organization? or does it still exist at some other places? </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> You'd have to look. There can be activities for Sugar that are not part of the GitHub sugarlabs organisation. We have seen several over the years, and we try to fork them, but there's no guarantee that we have been successful. I don't think you need to concern yourself with it though. Remember that in my design for aslov4, it must "support activity bundles uploaded via ssh," and may also "for a specific list of activities, access the source repository and detect any change to a release tag (publish), create a bundle and extract release notes," I'm looking forward to those two features in particular. Some source repositories are used to make multiple activity bundles; Wikipedia and TamTam are examples. I'm not interested in GitHub integration, because I don't always use GitHub, and some of the use cases for aslov4 are for situation where no internet access is available. </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap=""> Yes, aslov4 as specified in our GSoC project idea could look like it was a smaller than normal project, but if you iterate through each of the requirements it could easily fill the time available for a GSoC student working for 12 weeks of seven hours a weekday. Yes I agree. ASLOv4 is not an easy task. I am not sure when Manish (radii.dev) would be free, I will try to complete the best I can, to my knowledge. </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> Thanks. </pre> </blockquote> <pre class="moz-signature" cols="72">-- V/r Srevin Saju</pre> </body> </html>