Mailinglist Archive: zypp-devel (43 mails)
| < Previous | Next > |
[zypp-devel] zypp developers status meeting 2007-Apr-25
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Thu, 26 Apr 2007 13:54:02 +0200
- Message-id: <20070426115402.GA10861@xxxxxxxxxxxxx>
zypp developers status meeting 2007-Apr-25
participants: visnov, jsrain, mvidner, jkupec, dmacvicar, ma, kkaempf
topics:
1. Weekly call
2. Status and progress reporting
3. Milestone definition
4. Bits and pieces
1. Weekly call
We will have a weekly phone call to synchronize status and to define
tasks for the next week.
2. Status and progress reporting
Everyone is requested to report status to zypp-devel at least once
a week. This should also be done if no time was spent on zypp.
This mail should esp. include status on the given tasks and
committments.
If applicable, everyone is welcomed to sent status mails more often.
Additionally, we will set up a Wiki page to define milestones ('touch
base' points) and to collect tasks (see 'Bits and pieces' below).
This will be accompanied by a 'timeline' page, tracking tasks, assignments
and accomplishments.
Duncan will set up the initial wiki pages.
Everyone involved is responsible to document his given and done
tasks.
3. Milestone definition
We agreed on three 'big' milestones we want to achieve in the near
future:
i) Have parsers ready to fill the database
ii) Refactor the 'source handling'
iii) Be able to install a single package
Milestone i) is set to Wednesday next week (2nd of May). This includes
- Ability to parse 'susetags' file and fill internal data structures
(abstract syntax tree) with the data. (ma, 27-Mar)
- Write parsed 'susetags' data to cache (database). Initially only
resolvables attributes, UI attributes (like summary and description)
will follow later. (ma, 2-May)
- Ability to parse 'repomd' file and fill internal data structures
(abstract syntax tree) with the data. (jkupec, 27-Mar)
- Write parsed 'repomd' data to cache (database). Initially only
resolvables attributes, UI attributes (like summary and description)
will follow later. (jkupec, 2-May)
Requirements for milestone ii) are not fully known currently. We will
investigate in order to give a reasonable effort estimation until
next week.
Milestone iii) is a 'touch base' point and currently cannot be set
to a specific date.
However, it is important to have this milestone in mind and work
towards it. This means that functionality not needed for it will
be postponed, e.g. handling of translations for 'summary' and
'description'.
4. Bits and pieces
- During the discussions we collected a lot of 'bits and pieces' which
should be documented and assigned to developers eventually.
Duncan volunteered to set up a wiki page to collect such things.
Everyone is asked to fill this page with all the 'small things' he's
doing or he sees need to do.
- To easy the entry level for 'outsiders', Duncan will set up an overview
page to describe the directory layout and namespaces.
The intent of this page is to give direction to someone e.g. wanting
to help with the repomd parser.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
participants: visnov, jsrain, mvidner, jkupec, dmacvicar, ma, kkaempf
topics:
1. Weekly call
2. Status and progress reporting
3. Milestone definition
4. Bits and pieces
1. Weekly call
We will have a weekly phone call to synchronize status and to define
tasks for the next week.
2. Status and progress reporting
Everyone is requested to report status to zypp-devel at least once
a week. This should also be done if no time was spent on zypp.
This mail should esp. include status on the given tasks and
committments.
If applicable, everyone is welcomed to sent status mails more often.
Additionally, we will set up a Wiki page to define milestones ('touch
base' points) and to collect tasks (see 'Bits and pieces' below).
This will be accompanied by a 'timeline' page, tracking tasks, assignments
and accomplishments.
Duncan will set up the initial wiki pages.
Everyone involved is responsible to document his given and done
tasks.
3. Milestone definition
We agreed on three 'big' milestones we want to achieve in the near
future:
i) Have parsers ready to fill the database
ii) Refactor the 'source handling'
iii) Be able to install a single package
Milestone i) is set to Wednesday next week (2nd of May). This includes
- Ability to parse 'susetags' file and fill internal data structures
(abstract syntax tree) with the data. (ma, 27-Mar)
- Write parsed 'susetags' data to cache (database). Initially only
resolvables attributes, UI attributes (like summary and description)
will follow later. (ma, 2-May)
- Ability to parse 'repomd' file and fill internal data structures
(abstract syntax tree) with the data. (jkupec, 27-Mar)
- Write parsed 'repomd' data to cache (database). Initially only
resolvables attributes, UI attributes (like summary and description)
will follow later. (jkupec, 2-May)
Requirements for milestone ii) are not fully known currently. We will
investigate in order to give a reasonable effort estimation until
next week.
Milestone iii) is a 'touch base' point and currently cannot be set
to a specific date.
However, it is important to have this milestone in mind and work
towards it. This means that functionality not needed for it will
be postponed, e.g. handling of translations for 'summary' and
'description'.
4. Bits and pieces
- During the discussions we collected a lot of 'bits and pieces' which
should be documented and assigned to developers eventually.
Duncan volunteered to set up a wiki page to collect such things.
Everyone is asked to fill this page with all the 'small things' he's
doing or he sees need to do.
- To easy the entry level for 'outsiders', Duncan will set up an overview
page to describe the directory layout and namespaces.
The intent of this page is to give direction to someone e.g. wanting
to help with the repomd parser.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |