Highlighting other platforms for Swift?

Hi all-

Apologies in advance if this has been discussed and I missed it, but I was wondering if there'd be any possibility of including an 'Unsupported/User contributed/Not Endorsed/etc.' section under 'Supported Platforms' to link to projects working to bring Swift to other platforms (e.g. Fedora, Windows, etc.).

Disclosure: I've been working to keep Corinne Krych's original RPM build for Swift up to date at https://github.com/tachoknight/swift-rpm (currently at 4.0, testing 4.0.2).

Ron

Hi Ron,

This is a great question.

We’re actively setting up support to wire in up externally hosted CI bots to our CI infrastructure so that the community can help support the bringup and testing of Swift on other platforms beyond the officially supported platforms. The tentative rollout for that was December. We’ll announce more details once we get closer to rollout.

With that in mind, we’d definitely be interested in highlighting platforms that are being brought up, especially those actively tested in CI, prominently on Swift.org <http://swift.org/>. I’m also interested in highlighting other bring-up efforts as well (say those without CI testing), although possibly with much less emphasis. The nice thing about projects that are being actively tested during development is that it provides a transparent read to the community on how actively maintained that platform actually is.

That said, do you have specific ideas on how such efforts should be highlighted on swift.org <http://swift.org/>, and what should be the optics?

Thanks,
Ted

···

On Nov 15, 2017, at 9:01 AM, Ron Olson via swift-dev <swift-dev@swift.org> wrote:

Hi all-

Apologies in advance if this has been discussed and I missed it, but I was wondering if there'd be any possibility of including an 'Unsupported/User contributed/Not Endorsed/etc.' section under 'Supported Platforms' to link to projects working to bring Swift to other platforms (e.g. Fedora, Windows, etc.).

Disclosure: I've been working to keep Corinne Krych's original RPM build for Swift up to date at https://github.com/tachoknight/swift-rpm (currently at 4.0, testing 4.0.2).

Ron
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

1 Like

Just my one cent, but this could be part of a page summarizing the different ports under work/available with their level of maturity/support.
(For instance build instructions do exist for Windows and Ubuntu14.04 but are not publicly mentioned anywhere).

Nice work for packaging swift for RPM any way.

Guillaume

···

Le 15 nov. 2017 à 18:01, Ron Olson via swift-dev <swift-dev@swift.org> a écrit :

Hi all-

Apologies in advance if this has been discussed and I missed it, but I was wondering if there'd be any possibility of including an 'Unsupported/User contributed/Not Endorsed/etc.' section under 'Supported Platforms' to link to projects working to bring Swift to other platforms (e.g. Fedora, Windows, etc.).

Disclosure: I've been working to keep Corinne Krych's original RPM build for Swift up to date at https://github.com/tachoknight/swift-rpm (currently at 4.0, testing 4.0.2).

Ron
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

I think more prominent links to instructions for building Swift on other platforms would be great to have on the web site. Links to third party binary packages I’d be worried about because of the security implications...

Slava

···

On Nov 15, 2017, at 11:35 AM, Ted Kremenek via swift-dev <swift-dev@swift.org> wrote:

That said, do you have specific ideas on how such efforts should be highlighted on swift.org <http://swift.org/>, and what should be the optics?

Hi Ted-

I mocked up an example of the readme.md file:

https://github.com/tachoknight/swift-readme-example/blob/master/Swift%20Programming%20Language.md

I guessed at the Swift For Windows version based on the last build date; I imagine the protocol for getting a link added to the list would require the version of Swift being provided, regardless of the version of the project; Swift for Windows self-versions 1.6, which doesn't indicate what actual version of Swift they're using.

Presumably those projects that support the CI bots could get the badges; I didn't want to adhere too closely to the original platform table without considering all the ramifications so I didn't include them.

Ron

···

On 15 Nov 2017, at 13:35, Ted Kremenek wrote:

Hi Ron,

This is a great question.

We’re actively setting up support to wire in up externally hosted CI bots to our CI infrastructure so that the community can help support the bringup and testing of Swift on other platforms beyond the officially supported platforms. The tentative rollout for that was December. We’ll announce more details once we get closer to rollout.

With that in mind, we’d definitely be interested in highlighting platforms that are being brought up, especially those actively tested in CI, prominently on Swift.org <http://swift.org/>. I’m also interested in highlighting other bring-up efforts as well (say those without CI testing), although possibly with much less emphasis. The nice thing about projects that are being actively tested during development is that it provides a transparent read to the community on how actively maintained that platform actually is.

That said, do you have specific ideas on how such efforts should be highlighted on swift.org <http://swift.org/>, and what should be the optics?

Thanks,
Ted

On Nov 15, 2017, at 9:01 AM, Ron Olson via swift-dev >> <swift-dev@swift.org> wrote:

Hi all-

Apologies in advance if this has been discussed and I missed it, but I was wondering if there'd be any possibility of including an 'Unsupported/User contributed/Not Endorsed/etc.' section under 'Supported Platforms' to link to projects working to bring Swift to other platforms (e.g. Fedora, Windows, etc.).

Disclosure: I've been working to keep Corinne Krych's original RPM build for Swift up to date at https://github.com/tachoknight/swift-rpm (currently at 4.0, testing 4.0.2).

Ron
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

We’re actively setting up support to wire in up externally hosted CI bots to our CI infrastructure so that the community can help support the bringup and testing of Swift on other platforms beyond the officially supported platforms. The tentative rollout for that was December. We’ll announce more details once we get closer to rollout.

This sounds great. IBM has ported Swift to platforms including IBM
System z (mainframe) and it would be good to get CI integration so
that we can run "@swift-ci please test s390" when wanted.

Linking to releases and nightly builds from swift.org would also be
good, where they are available.

That said, do you have specific ideas on how such efforts should be highlighted on swift.org, and what should be the optics?

Python has a main https://www.python.org/downloads/ page and a
separate https://www.python.org/download/other/ page to point users at
non-official ports. That model could work well for Swift too.

···

On 15 November 2017 at 19:35, Ted Kremenek via swift-dev <swift-dev@swift.org> wrote:

--
Ian Partridge

Oh, I was presuming just to have a link to the port's GitHub page, not to any binaries. Were you thinking to include the build instructions/scripts directly in the Swift repo? I personally am okay with that but didn't want to presume anything.

Ron

···

On 15 Nov 2017, at 15:05, Slava Pestov wrote:

> On Nov 15, 2017, at 11:35 AM, Ted Kremenek via swift-dev > <swift-dev@swift.org> wrote:

That said, do you have specific ideas on how such efforts should be highlighted on swift.org <http://swift.org/>, and what should be the optics?

I think more prominent links to instructions for building Swift on other platforms would be great to have on the web site. Links to third party binary packages I’d be worried about because of the security implications...

Slava

For what it's worth, the build instructions for Android, as well as several
build and test scripts, exist within the apple/swift repository. For
example: https://github.com/apple/swift/blob/master/docs/Android.md

I'm very much looking forward to the rollout of externally hosted CI bots!
Last I tried, the majority of Swift's tests passed on Android, but not all
of them. A CI bot would help get that number to 100%, and to identify which
tests are unsupported. Not to mention the fact that a CI bot is a really
great form of documentation -- a repeating build is just about the most
formal set of build instructions you can get!

- Brian Gesiak

···

On Wed, Nov 15, 2017 at 4:15 PM, Ron Olson via swift-dev < swift-dev@swift.org> wrote:

Oh, I was presuming just to have a link to the port's GitHub page, not to
any binaries. Were you thinking to include the build instructions/scripts
directly in the Swift repo? I personally am okay with that but didn't want
to presume anything.

Ron

On 15 Nov 2017, at 15:05, Slava Pestov wrote:

On Nov 15, 2017, at 11:35 AM, Ted Kremenek via swift-dev < > swift-dev@swift.org> wrote:

That said, do you have specific ideas on how such efforts should be
highlighted on swift.org, and what should be the optics?

I think more prominent links to instructions for building Swift on other
platforms would be great to have on the web site. Links to third party
binary packages I’d be worried about because of the security implications...

Slava

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Has there been any movement wrt this topic? I personally would love to see (and host, if necessary) an Arch Linux CI bot, which would be great for catching incompatibilities with new dependency versions early (Arch being a rolling distro means everything is mostly available in the newest released version). Folks working on/using Windows, ARM/Linux and Android would surely love to see this as well.