Hi Stefan, On Thu, May 23, 2019 at 06:02:59PM +0000, Brüns, Stefan wrote:

When you hover the "clock" icon on https://build.opensuse.org/project/show/ network:osmocom:latest, you will see it clearly says "not yet published".

Thanks, I was aware that such a message can be seen at some places, but it wasn't clear to me what my expectations should be, and whether "not yet published" means "because of some possible bug" or "because of a long queue due to system load".

Mentioning openSUSE Leap, I find it quite awkward you make good use (or abuse - both Ubuntu 16.10 and 17.10 are EOLed) of the infrastructure provided by SUSE, but only care for Ubuntu and Debian.

Osmocom, like most FOSS projects, live by contribution. It happens that the main developers of Osmocom mostly work with dpkg based distributions and hence provide packaging for what they know, and for what they are able to maintain as they're actually using those packages. Also keep in mind that our prime expertise is in implementing cellular systems as FOSS, and not in distributions or packaging. Also, all of the commercial users that fund some of our Osmocom work via various channels (at least those that I know) all using Debian or Ubuntu in production. As a funny coincidence, I also know some of our professional/commercial users are doing their own (Debian) packaging based on private, company-internal OBS instances ;) Rather than the somewhat bitter tone of your e-mail, I would actually give this a positive spin: The OBS developers have managed to create a tool (and likewise, a public service/instance of it) that people working 100% on Debian-flavor distributions want to use more than the tools that those distributions themselves provide for maintaining feeds/repositories. I honestly don't really care what kind of Distribution people choose to use - just as long as they use Free Software. I used LST from 1.8, SuSE from about 4.1 to 6.3, then some RedHat 6.x/7.x, then Conectiva, and since ~2002 I'm on Debian and didn't really feel like investing time in investigating anything else ever since, but rather focus on writing software. Having said this, Martin Hauke has been contributing OpenSUSE packaging for pretty much all of Osmocom for years now. I've invited him several times to merge his https://build.opensuse.org/project/show/home:mnhauke:osmocom:nightly and https://build.opensuse.org/project/show/home:mnhauke:osmocom:latest with the official "network:osmocom:*" packaging, but unfortunately no related patches have been received yet. I suspect it's the lack of time by a volunteer who also "just" does this in his spare time. We're very open for any contributions in that area. They just have to come from people who actually use and work on those distributions. Should there be some kind of "unwritten rule" that the public OBS instance shall not be used by dpgk-only projects: We can set up our own osmocom OBS instance on our buildhosts, if you'd prefer that. I have just again checked the wiki / website and I couldn't find any "terms of use" or "policy" which would have indicated that. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Hi Henne, On Mon, May 27, 2019 at 12:11:50PM +0200, Henne Vogelsang wrote:

Just to make it clear. We are open for everybody doing anything they need to do for their project on build.opensuse.org. We don't consider only building for non-opensuse distros abuse in any way.

Thanks for your clarification. It might make sense to have some kind of official/formal policy for the service and publish that somewhere? Or maybe I just didn't find it? Just to make up an example: Building FOSS is one thing. But what if, for example, somebody was using build.opensuse.org to build some proprietary software pacakges [for whatever distribution], would that still be considered acceptable? I guess most people wouldn't want to upload proprietary source code to a public build service, sure. But what of e.g. having pre-compiled proprietary binaries in the "source" tarballs and then creating dpkg/rpm packages from it? I have no plans in doing that, I'm just pointing out that it might be useful to have some kind of public disclaimer about what is OK and what not. Sure, it's not the most important thing to consider, but maybe worth a thought. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Montag, 27. Mai 2019, 13:27:38 CEST Harald Welte wrote:

Hi Henne,

On Mon, May 27, 2019 at 12:11:50PM +0200, Henne Vogelsang wrote:

...

Just to make it clear. We are open for everybody doing anything they need to do for their project on build.opensuse.org. We don't consider only building for non-opensuse distros abuse in any way.

Thanks for your clarification. It might make sense to have some kind of official/formal policy for the service and publish that somewhere? Or maybe I just didn't find it?

in short the hosted sources do matter here, not the build results. The need to be OSI compliant. Exceptions are only possible via the openSUSE distribution legal team. The build results do not matter for us at least. However, your users may run into legal problems by installing them (eg. GPL conflict by loading code into a GPL app which is OSI, but GPL incompatibel). But this is out of the scope of our project. So neither the used base distros are. We would not offer non-SUSE builds, if we would have a problem with that :)

Just to make up an example: Building FOSS is one thing. But what if, for example, somebody was using build.opensuse.org to build some proprietary software pacakges [for whatever distribution], would that still be considered acceptable? I guess most people wouldn't want to upload proprietary source code to a public build service, sure. But what of e.g. having pre-compiled proprietary binaries in the "source" tarballs and then creating dpkg/rpm packages from it?

I have no plans in doing that, I'm just pointing out that it might be useful to have some kind of public disclaimer about what is OK and what not.

Yes, there should be a popup on first time OBS usage, it is just no there yet due to some code bug.

Sure, it's not the most important thing to consider, but maybe worth a thought.

it is :) -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org