[opensuse-buildservice] "closed" build service
Hi, what is the reason that the build service is closed, so it is not possible to see sources without logging in? It should look like this instead: https://launchpad.net/zodb/ http://www.archlinux.org/packages/13418/ http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/daemons/apache/?cvsroot=Extra&only_with_tag=CURRENT http://trac.macports.org/projects/macports/browser/trunk/dports/www/apache2/... Opinions? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi,
From: "Dr. Peter Poeml" <poeml@suse.de> To:<opensuse-buildservice@opensuse.org> Date: 3/5/2008 13:12 Subject: [opensuse-buildservice] "closed" build service Hi,
what is the reason that the build service is closed, so it is not possible to see sources without logging in?
I agree, the sources should be accessible.. after all, there is nothing worthy to be kept secret... I would prefer having it open for at least all the published packages / projects. The unpublished could remain closed... I as packager might be busy with some dirty hacks I plan to remove... and for this reason I also chose not to publish it... so no reason to show it 'yet'. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 05 March 2008 12:17:09 wrote Dominique Leuenberger:
Hi,
From: "Dr. Peter Poeml" <poeml@suse.de> To:<opensuse-buildservice@opensuse.org> Date: 3/5/2008 13:12 Subject: [opensuse-buildservice] "closed" build service Hi,
what is the reason that the build service is closed, so it is not possible to see sources without logging in?
This is due to load reasons in first place. However, it would be possible to create read-only mode pages for everything, but it would be bad if plenty people do download lots of source via api.opensuse.org. I have a source.opensuse.org on my feature list, where public source checkouts/downloads can be done (to be able to drop src.rpms from our mirrors ;) As usual, it is just work. If someone wants to work this, please speak up. We have no concept how to implement this yet, so the design phase / requirements collection should come first, but we can help with that. however, it is really easy to get an account, so it is relative wide open already ;) bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 05, 2008 at 12:57:12PM +0100, Adrian Schröter wrote:
what is the reason that the build service is closed, so it is not possible to see sources without logging in?
This is due to load reasons in first place. However, it would be possible to create read-only mode pages for everything, but it would be bad if plenty people do download lots of source via api.opensuse.org.
May I recommend a simple solution: a caching reverse proxy. Can be done e.g. with squid or apache.
however, it is really easy to get an account, so it is relative wide open already ;)
Accounts are nice for developers. Users are not interested in an account like that. Just as I don't make accounts for myself in dozens of other systems, I don't expect the average interested user to create accounts just to look things up. (And I'm even a developer.) I'm talking about transparency here, and visibility. Things that should be natural, IMO. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Le mercredi 05 mars 2008 à 13:13 +0100, Dr. Peter Poeml a écrit :
On Wed, Mar 05, 2008 at 12:57:12PM +0100, Adrian Schröter wrote:
however, it is really easy to get an account, so it is relative wide open already ;)
Accounts are nice for developers. Users are not interested in an account like that.
Also, upstream people may want to look at the patches used in openSUSE and might not want to get yet another account. You can easily get the Debian/Fedora/Gentoo/Mandriva/OpenSolaris/Ubuntu patches, iirc, but not the openSUSE patches. Good to hear that there's a plan for source.opensuse.org, though :-) Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
* Vincent Untz <vuntz@novell.com> [2008-03-05 13:25]:
Le mercredi 05 mars 2008 à 13:13 +0100, Dr. Peter Poeml a écrit :
On Wed, Mar 05, 2008 at 12:57:12PM +0100, Adrian Schröter wrote:
however, it is really easy to get an account, so it is relative wide open already ;)
Accounts are nice for developers. Users are not interested in an account like that.
Also, upstream people may want to look at the patches used in openSUSE and might not want to get yet another account. You can easily get the Debian/Fedora/Gentoo/Mandriva/OpenSolaris/Ubuntu patches, iirc, but not the openSUSE patches.
Well, you can 'unrpm' the src.rpm. But I also think that readonly things should be possible to do without an account. Bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
Just as I don't make accounts for myself in dozens of other systems, I don't expect the average interested user to create accounts just to look things up. (And I'm even a developer.)
If the Build Service would support OpenID logins, it wouldn't be necessary for many people to create another account, they could just use their existing OpenID one. -- Cornelius Schumacher <cschum@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
* Cornelius Schumacher <cschum@suse.de> [2008-03-05 13:26]:
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
Developers in general but users and not developers of openSUSE. Bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 05 March 2008 13:26:41 wrote Cornelius Schumacher:
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
yes, but the point is that it is maybe not for developers how have a relationship with openSUSE at all. But they may want to dig in, because some packager has asked them something. A login does may get refused by them. Therefore, it would be also very helpfull to have the log file at the same place for direct references.
Just as I don't make accounts for myself in dozens of other systems, I don't expect the average interested user to create accounts just to look things up. (And I'm even a developer.)
If the Build Service would support OpenID logins, it wouldn't be necessary for many people to create another account, they could just use their existing OpenID one.
well, it would still not make us GPL compliant (if we drop the source rpms). We need really a public downloadable place without login at all for that. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 05, 2008 at 02:23:35 +0100, Adrian Schröter wrote:
well, it would still not make us GPL compliant (if we drop the source rpms).
We need really a public downloadable place without login at all for that.
Don't consider dropping the source rpms. They can be highly useful for rebuilding packages on architectures that the buildservice doesn't support. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Wed, Mar 05, 2008 at 01:26:41 +0100, Cornelius Schumacher wrote:
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
It is not only about sources. Think about a bug tracker for example. Changelogs. Finding out who's responsible and get in touch. I'm sure you catch my drift. And if you feel it's okay to put up barriers like that for developers, I can say I don't agree with you :-)
Just as I don't make accounts for myself in dozens of other systems, I don't expect the average interested user to create accounts just to look things up. (And I'm even a developer.)
If the Build Service would support OpenID logins, it wouldn't be necessary for many people to create another account, they could just use their existing OpenID one.
I don't know how many people have an openid account. I for one don't have one. So it doesn't make any difference for me. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On 05/03/2008, Dr. Peter Poeml <poeml@suse.de> wrote:
On Wed, Mar 05, 2008 at 01:26:41 +0100, Cornelius Schumacher wrote:
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
It is not only about sources. Think about a bug tracker for example. Changelogs. Finding out who's responsible and get in touch. I'm sure you catch my drift.
And if you feel it's okay to put up barriers like that for developers, I can say I don't agree with you :-)
Just as I don't make accounts for myself in dozens of other systems, I don't expect the average interested user to create accounts just to look things up. (And I'm even a developer.)
If the Build Service would support OpenID logins, it wouldn't be necessary for many people to create another account, they could just use their existing OpenID one.
openID support for users.opensuse.org is on the roadmap so you should be able to use users.opensuse.org as your openid provider, which can continue to use ichain for authentication. With openID anyone can be an identity provider http://openid.net/what/ -- Benjamin Weber --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 05 March 2008 15:25, Dr. Peter Poeml wrote:
On Wed, Mar 05, 2008 at 01:26:41 +0100, Cornelius Schumacher wrote:
On Wednesday 05 March 2008 13:13:12 Dr. Peter Poeml wrote:
Accounts are nice for developers. Users are not interested in an account like that.
Aren't sources something for developers not users?
It is not only about sources. Think about a bug tracker for example. Changelogs. Finding out who's responsible and get in touch. I'm sure you catch my drift.
Ah, you are talking about generally making the build service data available for users not logged in. That's something which certainly would be nice. For most of the data the only reason for logging in should be, if you want to edit it.
And if you feel it's okay to put up barriers like that for developers, I can say I don't agree with you :-)
I thought you said that in "Accounts are nice for developers" ;-). I don't want to put up any barriers (not even for developers). The more open the Build Service is the better.
I don't know how many people have an openid account. I for one don't have one. So it doesn't make any difference for me.
Hundreds of millions of people have OpenID accounts (e.g. all Yahoo or AOL users) and the number is growing. So chances are becoming higher and higher that somebody who wants to log in into the Build Service already has an OpenID account somewhere. -- Cornelius Schumacher <cschum@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2008-03-05 17:36:04 +0100, Cornelius Schumacher wrote:
I don't know how many people have an openid account. I for one don't have one. So it doesn't make any difference for me.
Hundreds of millions of people have OpenID accounts (e.g. all Yahoo or AOL users) and the number is growing. So chances are becoming higher and higher that somebody who wants to log in into the Build Service already has an OpenID account somewhere.
without stopping your enthusiasm. but in the first step we will only allow openid with our own provider as it makes the task easier to map to the usernames. supporting multiple openid accounts for the same username is something for the long term todo. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 05, 2008 at 05:36:04PM +0100, Cornelius Schumacher wrote:
On Wednesday 05 March 2008 15:25, Dr. Peter Poeml wrote:
On Wed, Mar 05, 2008 at 01:26:41 +0100, Cornelius Schumacher wrote:
Aren't sources something for developers not users?
It is not only about sources. Think about a bug tracker for example. Changelogs. Finding out who's responsible and get in touch. I'm sure you catch my drift.
Ah, you are talking about generally making the build service data available for users not logged in. That's something which certainly would be nice. For most of the data the only reason for logging in should be, if you want to edit it.
Yes, indeed -- that's what I meant! It would be the most natural thing, to make as much data available as possible. I mean, people do all kind of things with that information, that we don't necessarily envision. They write scripts which screen-scrape information and make it available otherwise. They write articles and want to look aroud for that. They are developing somewhere else (other distro, upstream) and want to compare. I mean, all the stuff that guys like us did with other applications also ;) Hidden behind some awkward "ichain" authentication, a lot of potential is in vain.
And if you feel it's okay to put up barriers like that for developers, I can say I don't agree with you :-)
I thought you said that in "Accounts are nice for developers" ;-). I don't want to put up any barriers (not even for developers). The more open the Build Service is the better.
Indeed.
I don't know how many people have an openid account. I for one don't have one. So it doesn't make any difference for me.
Hundreds of millions of people have OpenID accounts (e.g. all Yahoo or AOL users) and the number is growing. So chances are becoming higher and higher that somebody who wants to log in into the Build Service already has an OpenID account somewhere.
I didn't know that -- sounds promising. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (8)
-
Adrian Schröter -
Benji Weber -
Bernhard Walle -
Cornelius Schumacher -
Dominique Leuenberger -
Dr. Peter Poeml -
Marcus Rueckert -
Vincent Untz