headers
Davidlohr Bueso | 25 May 14:43
Picon

fdisk project - GSoC weekly report 1

Hi,

This is my first report of what we've been doing regarding the fdisk
redesign project.

1) What's been done in previous weeks, before SoC development officially
started:

- Consolidate and agree on internal fdisk API and data structures with
Petr and mainstream util-linux community.

- Isolate DOS specific label logic. This is important since DOS
partition table context was deeply embedded in the heart of fdisk logic,
making it impossible to implement a new API. Now DOS, like all other
supported labels, has its own file and functions.

- Fixed two nasty bugs that are currently present in most distros.
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=50f6100a960d96471980a9a5354d9ee426b00673
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=44d2fc819840d821db8dc965decf1f490ae9cc95

- Generic code cleanups.

2) What's been done during week 1:

- Implemented and merged in mainstream the initial functions and data
structures of the new internal API.
http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commit;h=823f0fd107415ced8edde12306b9134058aafdc0

- Implement dynamic debug support. By reading environment variables
($FDISK_DEBUG) developers and users can quickly be informed of important
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Klumpp | 19 May 22:46
Gravatar

Announcing AppStream GSoC project

Hello OpenSUSE!

I am Matthias Klumpp and I will work on making the AppStream[1]
project work for OpenSUSE as part of the Google Summer of Code this
year.
A little bit about myself:
I study Molecular Biomedicine in my second semester at University of
Bonn in Germany and I use Linux for years now.

I contribute to KDE (mainly to Apper, the PackageKit-based KDE package
manager) and I am PackageKit upstream developer, as well as the
maintainer of Listaller, a cross-distro application installer, which
has the goal to make installations of 3rd-party apps on multiple
distributions as easy, generic and integrated as possible, by using
just one package. (Yes, 3rd-party repos and native packages have some
issues, just before you ask the obvious question ^^)

I’m not really a typical KDE user, as I also use GNOME from time to
time and contribute to GNOME (but just very unimportant things for
now). Knowing both desktops and both communities is usually an
advantage, and therefore I very much enjoyed the last Desktop Summit
in Berlin.  If you’ve been there, you might have met me there already
;-)

I am Debian Maintainer and maintain all PackageKit and most
PackageKit-related packages there. This means I also use Debian, so
doing a project for OpenSUSE might look strange on the first look.
But’s it’s not strange at all: I’m working on a cross-distro project
so the distribution doesn’t matter that much. Also, SUSE was the first
Linux distribution I've ever tried :-) - so I know OpenSUSE.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pascal Bleser | 19 May 12:54
Favicon
Gravatar

Our progress in taking the list back

Hi all

I'm sure everyone will have noticed that we, collectively, made
substantial progress in taking back our list as our media of
communication.

There have been, and still are, quite a few interesting topics
of discussion over here, and the tone remained civil and even
friendly, quite focused, and productive.

So let's pat ourselves on the back and keep up the good work :)

And if you believe I'm wrong, please let me (or even everyone on
the list) know. To fix issues, we first need to be aware of them
-- people have different sensibilities and goals, there are
difficulties with language, etc..., so if you believe there is
something wrong, please let us know instead of staying in your
corner with it or even going away :)

But let's not keep it there, let's think and discuss about ways
to keep improving it.

Personally, I believe we should look at ways to improve the
productivity of discussions, as the threads are still really
long. That is fine (as long as it doesn't go off-topic or turns
into a fight), but we might want to think of ways of capturing
the results of such discussions as they get swamped easily into
the depths of threads.

1. Better threads
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eun Kyung | 18 May 18:15

Introducing myself and GSoC syslog-ng MongoDB driver project

Greetings, fellow developers.

I recently joined the openSUSE and syslog-ng communities because of
Google Summer of Code, and I thought this would be a good time to
briefly introduce myself. I am studying Information Technology in
Dublin, Ireland, and I got accepted for GSoC 2012 to work on the
MongoDB destination driver project.

Syslog-ng, the leading logging platform for log collection and
management, has been storing logs in MongoDB for over a year, but the
technical documentation on the implementation is rudimentary, which
impedes the improvement of the driver's functionality and speed. The
goal of this project is to enhance the MongoDB destination driver for
syslog-ng, to make it more robust, scalable and performant.

Specific tasks and deliverables will include:
- modifying syslog-ng's internal value pairs subsystem so that it will
be able to emit a tree of values, instead of just a flat name:value
list;
- teaching the mongodb driver to walk the tree, and constructing BSON
objects out of it, and using 'insert' instead of 'upsert';
- adding support for bulk inserts into a MongoDB, instead of inserting
one by one

My GSoC project proposal can be found at
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2012/ekyung/1

This is my first time working on an open source project, and I've
liked a lot so far. My mentor has been tremendously friendly and
helpful.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Per Jessen | 18 May 15:47
Picon

a fully autonomous local repository mirror (was: When is a mirror not a mirror?)

Per Jessen wrote:

> Per Jessen wrote:
> 
>> Togan Muftuoglu wrote:
>> 
>>> On 05/04/2012 02:59 PM, Per Jessen wrote:
>>>> 
>>>> With a couple of custom add-ons, squid will do fine. I've got such
>>>> a proxy setup running since November, you're welcome to try it out.
>>> 
>>> Care to share those custom add-ons
>>> 
>>> Togan
>> 
>> I have actually written most of it up already:
>> 
>> http://wiki.jessen.ch/index/Squid_and_openSUSE
>> 
>> The download links don't work, I'll see if I can also prepare a
>> tarball with all the ingredients.
> 
> Okay, the download links should be working now - be aware, this is not
> exactly a one-click install, i.e. some assembly required.  Feel free
> to contact me off-line if you need help.

I've updated the fetcher206 package and added a step-by-step guide.  

http://wiki.jessen.ch/index/Squid_and_openSUSE
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bryen M Yunashko | 17 May 02:09
Favicon

Freight Train/Bugzilla discussions, etc.

I think the last few days have definitely brought up some good and
interesting discussions regarding the freight train, and particularly
what we should start looking at regarding bugzilla.

However, at the same time, I see the thread becoming longer and longer.
And the "discussers", including myself, are pretty much a few set of
people.  I wonder if we've reached a sufficient point now where we've
identified the people who are genuinely interested in this topic and
should move those into a task force team to focus on this subject matter
directly (and report to the Project at large of its findings and
conclusions periodically.)   In this way, we won't turn off people who
feel the project list has become too bogged down on a subject they may
not be interested in.

Thoughts (at the risk of bogging down with another long thread)?  :-)

Bryen M Yunashko
openSUSE Project

--

-- 
To unsubscribe, e-mail: opensuse-project+unsubscribe@...
To contact the owner, email: opensuse-project+owner@...
Permalink | Reply | 3 comments |
headers
Helen South | 17 May 01:02
Favicon

Re: Improving the bug management lifecycle/process

Forwarding the message I'd accidentally sent off-list. Hopefully it will
stay embedded in the correct thread.

In the light of what Jim says here - and others have said about the process,
too - perhaps it could be worthwhile to look at integrating FATE and
Bugzilla, but only if it doesn't come at the cost of becoming too complex to
manage.

The issue with the vast number of products making Bugzilla almost
unmanageable is an interesting  - and worrying - point, and even from the
user experience of having to navigate the selection options on the front
page, it's daunting.  Would it be possible to have a discrete instance of
Bugzilla purely for openSUSE/SUSE maintained separately to all the other
products?

How did the system cope when we had Bug Squashing Days?

cheers

Helen

---------- Forwarded message ----------
From: Jim Henderson <hendersj@...>
Date: Thu, May 17, 2012 at 1:56 AM
Subject: Re: [opensuse-project] Re: Improving the bug management
lifecycle/process
To: helen.south@...

Not sure if you meant to send this off-list - these are good questions
and probably should be in the ongoing thread. :)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jim Henderson | 17 May 00:35
Picon

Does the project have a publicly accessible project management tool?

General question to those more closely involved in oS project management 
- is there a tool we have access to that can help track tasks and 
progress on projects within the oS project?

I'm thinking something like a Kablink (or Vibe OnPrem) task list.  I've 
got Vibe installed at home with a limited number of users, but I'd rather 
track the bugzilla/bug process project in a more visible way than on a 
private server in my house. :)

If we don't, I can set something on on the Kablink site so those who are 
interested can follow along and help document the tasks that need to be 
completed and their progress.

Thanks,

Jim

-- 
 Jim Henderson
 Please keep on-topic replies on the list so everyone benefits

--

-- 
To unsubscribe, e-mail: opensuse-project+unsubscribe@...
To contact the owner, email: opensuse-project+owner@...
Permalink | Reply | 35 comments |
headers
Felix Miata | 16 May 18:41
Picon
Favicon

Re: bugzilla resolution "OBSOLETE"

On 2012/05/16 16:09 (GMT) Jim Henderson composed:

> On Wed, 16 May 2012 14:11:26 +0200, Vincent Untz wrote:

>>  In GNOME Bugzilla, we do have a OBSOLETE resolution. I think that would
>>  help in such cases.

> I like this idea in concept.

I don't...

> I think the use of an OBSOLETE resolution is something that would be
> useful, but we have to be careful in actually using it - obviously there
> are some fixes (security in particular) where backporting a fix is
> generally considered a good idea.  So we need to be extremely clear that
> the reason it's flagged obsolete is because (a) it's been resolved in a
> later release, and (b) a decision has been made (and that decision should
> at least be explained in the comments, IMHO) to not backport because of
> the effort/impact/whatever.

Instead of OBSOLETE, do like mozilla.org -> EXPIRED or INCOMPLETE, neither of 
which judge what has been done, and leave for consideration possible 
propriety to reopen with updated information.

Don't forget too that one justification for INVALID can be obsolescence.

Looking briefly through bugzilla.mozilla.org re the Bugzilla software 
product, the word obsolete seems to have a special meaning reserved for use 
with attachments.
(Continue reading)

Permalink | Reply | 14 comments |
headers
Per Jessen | 16 May 08:19
Picon

Who do I contact about bugzilla?

$SUBJ - I would like to have the "Scheduled Reports (Daily, Weekly,
Hourly, etc.) by Email" feature activated. 

thanks

-- 
Per Jessen, Zürich (7.1°C)

--

-- 
To unsubscribe, e-mail: opensuse-project+unsubscribe@...
To contact the owner, email: opensuse-project+owner@...
Permalink | Reply | 4 comments |
headers
Jim Henderson | 16 May 06:32
Picon

Re: bugs that are against 11.1

On Wed, 16 May 2012 14:25:11 +1000, Helen South wrote:

> I'm a little out of the loop on this stuff - is there an existing thread
> on bugzilla and how it works, flaws, issues etc?
> I've only ever filed the one bug I think, so you'll have to excuse my
> ignorance about it.

I don't recall seeing one - this kinda grew out of the "Freight Train" 
thread.

But I've been involved on a number of discussions (mostly with forum 
users) about bug submissions, and usually (but not always) the person, if 
not technical, is intimidated by the process because it's not explained 
at a 'lay-person' level.

> How much flexibility do we have to adapt the way it works? Is there
> possibilities to flag 'power users' whose bugs usually deserve closer
> attention, or to flag 'more information available/needed' and so on?

In terms of the process, I think we have a lot of flexibility.  In terms 
of the specifics in the system itself, that may depend.  The 
implementation at bugzilla.novell.com is stretched /extremely/ thin (last 
I heard, which was a little over a year ago, just before the layoff that 
affected - among others - me).  The number of products and group 
management is one of the more extreme implementations from what I've 
heard.

> However I fear I'm asking old questions. I'd like to get more 'up to
> speed'; it'd be interesting to contribute in this area, it seems
> valuable.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane