On Fri, Apr 1, 2016 at 3:14 PM, Adam Samalik <asamalik@redhat.com> wrote:

On Thu, Mar 31, 2016 at 7:21 PM, Sinny Kumari <ksinny@gmail.com> wrote:

On Thu, Mar 31, 2016 at 8:55 PM, Adam Samalik <asamalik@redhat.com> wrote:
Thank you for the link!

I think that this content would be very useful to Fedora packagers. Do you think it would be useful to our target audience as well?
Yes, it will be useful for target audience who are looking to run their application on architectures like s390, PowerPC using Fedora. For example: Foo is a  developer who is writing his application on Intel laptop (x86_64 easily accessible) but interested in running his application on other architectures (say s390) too. For testing his application he can't go and buy a new s390 box (costly and will have to  set-up running environment). But, by reading this page he can build his application on s390 arch using infrastructure provided available in Fedora. If needed he can run and test by getting access to available Fedora s390 box.
Can anyone, without being a Fedora packager, do that?

It is not necessary that person must be a Fedora packager but little knowledge of  RPM packaging will be required to modify RPM package to test with updated source code. The advantage is that even without direct access to machine architecture like s390, he can test his app by just submitting a job to s390 koji. For an unpackaged application, developer portal does explain how to do
RPM Packaging[1]

Assuming that the person reading the portal is going to develop on Fedora, the app will end up being distributed as a RPM. From what I understand, that is the purpose of having RPM Packaging and Copr Build service[2] on developer portal as well.

[1] https://developer.fedoraproject.org/deployment/rpm/about.html
[2] https://developer.fedoraproject.org/deployment/copr/about.html