On Wed, Feb 2, 2011 at 2:52 PM, Jos Poortvliet <jospoortvliet(a)gmail.com> wrote:
<snip>
>> That reads as if you assume OBS is not successful. I feel the opposite.
>
> Indeed. It is popular but could be more so ;-)
>
> BTW we also need to do more in the area of USING those huge numbers. For
> marketing but also community building purposes. How could we get the tens of
> thousands who use OBS to contribute to openSUSE? After all, they're VERY close
> to openSUSE already - it's just pushing a few buttons to submit their packages
> to factory or request merges with existing packages to fix bugs.
I don't think it is necessarily that simple.
First, I _assume_ lots of those 100+K packages are the same package
just in lots of repos.
For instance each of the main packages is probably in at least a devel
package, factory, 11.3, 11.2, 11.1 discontinued. Admittedly, each of
those may be at a different version level/patch level. But 100+K
packages is a highly misleading number I suspect.
And then for lots of smaller packages, I don't think they are really
built for distro use.
First, many don't have man pages for executables, which I think is
required in the push to factory.
Another example is open2300. I packaged it because I use it, but it
generates a dozen or so executables. All *2300 (open2300, log2300,
etc.). I can't envision putting that in factory that way. The names
really need to be changed to 2300* (2300open, 2300log, etc), but the
upstream project is basically dead, so I don't see it happening there.
I may get it into the distro eventually, but for now I'm happy with it
in a devel project. So OBS for open2300 is giving me exactly what I
want. A way to publish a little known/used app without the more
formal requirements appropriate to a full distro release.
Greg
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On Wednesday 02 February 2011 21:21:59 Bryen M. Yunashko wrote:
> On Wed, 2011-02-02 at 14:46 +1100, Helen wrote:
> > On a related note, I was under the impression that Bretzn was being
> > renamed to 'AppInstaller' though perhaps I've got the "wrong end of
> > the stick" as the saying goes.
>
> Maybe we should come up with something that conforms with our "open"
> identity? Something like openApp or openInstaller or something? I
> dunno, "installer" sounds a bit intimidating to some people, but
> open-something might be the way to go.
Well, the name of the application for installation is "openSUSE Application
Installer", see:
http://news.opensuse.org/wp-content/uploads/2011/02/appstore_details.png
The product you might call 'bretzn' is the plugin for IDE's which ties the
Build Service(s) to application store(s), websites and repositories.
And the name of the whole project developing it is Bretzn. But it's still
vague because - is Bretzn a KDE project? or is it an openSUSE project? The ppl
who started it are KDE and openSUSE people. But they want it to be cross-
desktop and cross-distribution as well as based on open standards (eg
libattica, OCS).
So the bretzn branding is surely unclear in general. I've copied in
Karlitschek who started this whole thing, and vuntz who's been busy on the
cross-distro side (and might get involved with the GNOME application installer
on openSUSE).
I've recently asked Frank to move the Bretzn mailinglist to freedesktop.org -
a cross-desktop, cross-distro project with a mailinglist named "kde-
bretzn(a)kde.org" doesn't make much sense. Still, unless people from other
distros and desktops actually get involved, it's not much of a cross-project.
I think we should get the people who are working on this stuff for KDE, GNOME
and all distro's together on that one new mailinglist...
Meanwhile, we do indeed need to think about the name. How big is the scope of
Bretzn, and IF we decide it's fully cross desktop/distro, is Bretzn the right
name? It has indeed disadvantages, being hard to spell and pronounce for non-
Germans...
> Just thinking out loud here.
>
> Bryen
I personally have mixed feelings about this - the fact that OBS has
openSUSE in its name helps to get the openSUSE name 'out there' as its
use becomes more popular, but I agree that there is a strong
implication for users that it is only for openSUSE. The other reasons
raised by Gumb are also valid ones.
So a change to just 'open' could be positive in many ways.
I'm still relatively new to the project myself, so I don't know the
whole story - I imagine this was probably discussed at length when the
Build Service first became an entity.
On a related note, I was under the impression that Bretzn was being
renamed to 'AppInstaller' though perhaps I've got the "wrong end of
the stick" as the saying goes.
Because we are going to be doing a lot of work in the coming months to
promote both the OBS and Bretzn, it might be a good idea to clarify
naming right away, and also perhaps talk about branding and logos for
both of these projects. Is there anything in progress towards
developing artwork?
Again, apologies if this is old territory being covered again!
cheers,
Helen
On Mon, Jan 31, 2011 at 10:44 AM, gumb <gumb(a)linuxmail.org> wrote:
> Hi. I am forwarding a proposal for the renaming of the openSUSE Build
> Service, in order to try and increase its adoption and recognition. Indeed,
> it seems like certain moves may already have been made in this direction but
> I'm not too clear on that (see below). This is a follow-up to a suggestion
> by Jos Poortvliet which he originally made mention of in a recent blog post,
> here:
> http://nowwhatthe.blogspot.com/2011/01/lca-on-friday.html
>
> Whilst I am merely an end-user, he has suggested in the spirit of openness
> that I contact the project via this list to further the discussion.
> Essentially, such a renaming could be as 'simple' as calling it the 'Open
> Build Service', and I note that the Meego project, for example, already
> seems to use this on some of its webpages, but the main OBS introduction
> page does not, hence my uncertainty. The reasoning behind this subtle change
> is that the project has perhaps not gained the traction that it should have
> done in the wider open source and distro community in consideration of what
> an advanced and useful tool it is. I see there being two key contributory
> factors behind this:
>
> 1) The very name openSUSE Build Service immediately implies something
> related and perhaps specific to the openSUSE distribution. Many developers /
> packagers are simply unaware of its scope.
>
> 2) There are those for whom anything associated with the name openSUSE makes
> them run a mile. Rightfully or wrongfully, all the previous Novell / MS
> associations forever tarnish the image of openSUSE for some. The OBS is
> unfairly tarred with the same brush, and no matter how good a service it
> becomes, this perception is unlikely to change for a long time to come.
>
> Of course, general marketing and other factors may also play a part, but I
> don't think the above two reasons should be easily discounted. Several times
> I have read conversations involving developers / packagers who are
> struggling to make packages available for a variety of distros, and when OBS
> is raised as a potential solution the thread often falls flat or it is
> dismissed, sometimes for some technical reason or sometimes for no good
> reason.
>
> To appease the latter category of OBS avoiders, the openSUSE branding could
> perhaps take a back seat and not be so obviously featured. Let the service
> speak for itself. The website would need some rewording and perhaps more
> generic theming or image elements to reduce all the immediate references to
> openSUSE. I'm basing this broadly on the concept that subtle or subconscious
> persuasion can often triumph over blatant advertising, but I'm no marketing
> expert!
>
> Having openSUSE in the title should bring some prestige and publicity to the
> openSUSE project, but it probably has just as much adverse effect. Far
> better to attract more people to the service in the first instance, and upon
> discovering its qualities a certain kudos might then be attributed before
> the user needs to discover who's behind it.
>
> The rewards and prestige would eventually come from the project generating
> many times as much usage and therefore media recognition, instead of
> shouting about itself and falling upon deaf ears, and ultimately occupying a
> niche.
>
> Not meaning to take anything away from the efforts so far. Having Meego and
> others on board is a great achievement, but I think the points in Jos's post
> are an indicator of the widespread ignorance that may be holding it back
> from reaching out further.
> --
> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
> For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
>
>
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi everybody,
I know we do not have stats on OBS, which is unfortunate, but well...
But maybe somebody with some good access to log files could still try
to draft up something?
As a member of the SuperTuxKart dev and translation team, we're
interested in the number of downloads STK get's from the OBS, of
course also to find out if the distribution channel is the right one,
if we should promote it more/better (hope so) or if the other channels
are to be favored.
Of course this means we should get at least some information on how
many downloads of STK we had in the last 2 months (Last release was on
Dec 21, which makes this period rather interesting).
Would it be possible to draft up something?
Thank you very much for your appreciated help!
Dominique
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I just happened to notice that build30 looks locked up.
Greg
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
dolphin-emu from home:RedDwarf:NonFree, that uses the new tar_scm
source service, has been in "source update running" for more than an
hour.
Also, at least the tar_scm version I have installed from
openSUSE:Tools seems to have a typo that makes --filename not work.
Where it says
FILE="$FILENAME"
VERSION="$MYVERSION"
it should say
FILE="$MYFILENAME"
VERSION="$MYVERSION"
I would create a SR, but not sure what/where is upstream/devel project
for the source services.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I started using the project linking feature (described here:
http://en.opensuse.org/openSUSE:Build_Service_Concept_project_linking
), and on that page it mentions this about listing packages: "Please
note that they get not listed by default, when you list the project
content.". But it does not mention how to override that default, and I
couldn't find that info. Is there a way to get it to list the packages
for a linked project?
Thanks,
Christian.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org