« Return to Thread: Project status
Re: Project status
by Vlad Skvortsov
::
Rate this Message:
FWIW, this is a brief list of requirements/expectations that I pose on
such a system. I just want to emphasis that my primary environment is
FreeBSD/MacOS/Linux, so this might be a little bit skewed. As for the
scale, I expect the system to be sufficient for small groups of developers.
My main requirement: the system should be self-contained. If required,
one should be able to update issues as simple as editing text files with
any ASCII text editor and commit the changes / get updates with 'svn'
(with currenly available systems, I find myself uncomfortable working on
a plane since crucial part of the information I need is only accessible
through the web).
Since svn allows 'disconnected' operation, the issue tracking system
(which contents are closely related to the code stored in svn) should
also allow such mode of operation.
There should be no 'single point of control' for the issues database.
Under this I mean that most existing systems (well, the ones I've seen)
pose themselves as the only gateway to access the data. If the web
server with such a gateway (in a form of GUI) goes down, you're screwed
up. We do already have one bottleneck (subversion server) and I don't
see a reason to add another one.
This leads us to the architecture that is built on several
"applications" dealing with their own working copies of the issues
database and a subversion server as a datasource. One application might
be a web frontend to the system (and there might be another backup one,
etc). Another application is a backup system that just makes 'svn up' in
remote location. The third one might be an e-mail integration
application (sending updates to specific addresses and/or updating
issues by attaching arriving mail). Other 'applications' are sets of
scripts on developers' desktops dealing with issues in their working
copies directly.
Here we come to the problem of database consistensy in terms of metadata
and business logic in different points of execution within such
distributed system. This is vague for me yet, but I'd say that the goal
is to make these rules declared, not hardcoded, and stored right with
the issues data so that different implementations of the 'applications'
deal with the data in consistent way.
Still much to think about.
Wherry, Matt wrote:
>BTW:
>
>If the issue of interest here is subversion integration, rather than some of the more esoteric or useful planned features, has anyone had a look at trac?
>
>http://www.edgewall.com/trac/
>http://www.edgewall.com/trac/license.html
>
>The Scipy and numpy guys seem to be using it in conjunction with svn to some success. To see it in action, see http://projects.scipy.org/scipy/scipy.
>
>It looks nice. Simple. Nice.
>
>M
>
>-----Original Message-----
>From: Wherry, Matt
>Sent: 08 May 2006 11:15
>To: dev@...
>Subject: RE: [subissue] Project status
>
>
>I'd also like to contribute, but I've a lot of time commitments ( No work time allocated, and 3 kids at home ), although if there's anything low load, I'd be happy to pitch in.
>
>M
>
>-----Original Message-----
>From: Jean-Louis JUAN [mailto:jean-louis.juan@...]
>Sent: 04 May 2006 12:42
>To: dev@...
>Subject: Re: [subissue] Project status
>
>
>Hello,
>
>As I see, we are all interested by this project and waiting that someone
>to lead it !!
>Can anyone take the "responsability" or do we need to reach the main
>leader ?
>
>Are we enough members to do the job ?
>
>
>Juan Heyns a écrit :
>
>
>>I would also be interested in being involved. I had a lot of hope for
>>this project but are disappointed by the current thread of messages I
>>have in my mailbox.
>>
>>Ciao
>>Juan
>>
>>
>>
>>
>>
>>>>>Cage Jonathan <JCAGE@...> 05/04/06 10:32 am >>>
>>>>>
>>>>>
>>I too have been watching this one and was disappointed to learn of
>>it's demise. If either of you _do_ start something off I would be
>>interested in
>>collaborating as well.
>>
>>Cheers,
>>Jon
>>
>>-----Original Message-----
>>From: drew@... [mailto:drew@...]
>>Sent: 04 May 2006 02:54
>>To: dev@...
>>Subject: Re: [subissue] Project status
>>
>>* Vlad Skvortsov (vss@...) wrote:
>>
>>
>>>Drew Myers wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>I'm new to the list, as I just found this project listed on tigris.
>>>>After looking through the mail archives though, it appears this
>>>>project
>>>>is no longer active. Is that accurate?
>>>>
>>>>
>>>I've been watching this for quite a long time, but it seems there is
>>>no movement. So I've started my own implementation of similar idea.
>>>
>>>
>>Do you want some help? Is it hosted anywhere? This is truly
>>something I think is worth doing, and will probably implement it
>>myself if I can't
>>find another project already in-progress.
>>
>>Thanks,
>>
>>drew
>>
>>
>
>This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
>Danish - Deutsch - English - Español - Français - Italiano - Japanese - Nederlands - Norsk - Portuguese - Svenska: www.cardinalhealth.com/legal/email
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@...
>For additional commands, e-mail: dev-help@...
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@...
>For additional commands, e-mail: dev-help@...
>
>
>
>
--
Vlad Skvortsov, vss@..., vss@...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
such a system. I just want to emphasis that my primary environment is
FreeBSD/MacOS/Linux, so this might be a little bit skewed. As for the
scale, I expect the system to be sufficient for small groups of developers.
My main requirement: the system should be self-contained. If required,
one should be able to update issues as simple as editing text files with
any ASCII text editor and commit the changes / get updates with 'svn'
(with currenly available systems, I find myself uncomfortable working on
a plane since crucial part of the information I need is only accessible
through the web).
Since svn allows 'disconnected' operation, the issue tracking system
(which contents are closely related to the code stored in svn) should
also allow such mode of operation.
There should be no 'single point of control' for the issues database.
Under this I mean that most existing systems (well, the ones I've seen)
pose themselves as the only gateway to access the data. If the web
server with such a gateway (in a form of GUI) goes down, you're screwed
up. We do already have one bottleneck (subversion server) and I don't
see a reason to add another one.
This leads us to the architecture that is built on several
"applications" dealing with their own working copies of the issues
database and a subversion server as a datasource. One application might
be a web frontend to the system (and there might be another backup one,
etc). Another application is a backup system that just makes 'svn up' in
remote location. The third one might be an e-mail integration
application (sending updates to specific addresses and/or updating
issues by attaching arriving mail). Other 'applications' are sets of
scripts on developers' desktops dealing with issues in their working
copies directly.
Here we come to the problem of database consistensy in terms of metadata
and business logic in different points of execution within such
distributed system. This is vague for me yet, but I'd say that the goal
is to make these rules declared, not hardcoded, and stored right with
the issues data so that different implementations of the 'applications'
deal with the data in consistent way.
Still much to think about.
Wherry, Matt wrote:
>BTW:
>
>If the issue of interest here is subversion integration, rather than some of the more esoteric or useful planned features, has anyone had a look at trac?
>
>http://www.edgewall.com/trac/
>http://www.edgewall.com/trac/license.html
>
>The Scipy and numpy guys seem to be using it in conjunction with svn to some success. To see it in action, see http://projects.scipy.org/scipy/scipy.
>
>It looks nice. Simple. Nice.
>
>M
>
>-----Original Message-----
>From: Wherry, Matt
>Sent: 08 May 2006 11:15
>To: dev@...
>Subject: RE: [subissue] Project status
>
>
>I'd also like to contribute, but I've a lot of time commitments ( No work time allocated, and 3 kids at home ), although if there's anything low load, I'd be happy to pitch in.
>
>M
>
>-----Original Message-----
>From: Jean-Louis JUAN [mailto:jean-louis.juan@...]
>Sent: 04 May 2006 12:42
>To: dev@...
>Subject: Re: [subissue] Project status
>
>
>Hello,
>
>As I see, we are all interested by this project and waiting that someone
>to lead it !!
>Can anyone take the "responsability" or do we need to reach the main
>leader ?
>
>Are we enough members to do the job ?
>
>
>Juan Heyns a écrit :
>
>
>>I would also be interested in being involved. I had a lot of hope for
>>this project but are disappointed by the current thread of messages I
>>have in my mailbox.
>>
>>Ciao
>>Juan
>>
>>
>>
>>
>>
>>>>>Cage Jonathan <JCAGE@...> 05/04/06 10:32 am >>>
>>>>>
>>>>>
>>I too have been watching this one and was disappointed to learn of
>>it's demise. If either of you _do_ start something off I would be
>>interested in
>>collaborating as well.
>>
>>Cheers,
>>Jon
>>
>>-----Original Message-----
>>From: drew@... [mailto:drew@...]
>>Sent: 04 May 2006 02:54
>>To: dev@...
>>Subject: Re: [subissue] Project status
>>
>>* Vlad Skvortsov (vss@...) wrote:
>>
>>
>>>Drew Myers wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>I'm new to the list, as I just found this project listed on tigris.
>>>>After looking through the mail archives though, it appears this
>>>>project
>>>>is no longer active. Is that accurate?
>>>>
>>>>
>>>I've been watching this for quite a long time, but it seems there is
>>>no movement. So I've started my own implementation of similar idea.
>>>
>>>
>>Do you want some help? Is it hosted anywhere? This is truly
>>something I think is worth doing, and will probably implement it
>>myself if I can't
>>find another project already in-progress.
>>
>>Thanks,
>>
>>drew
>>
>>
>
>This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
>
>Danish - Deutsch - English - Español - Français - Italiano - Japanese - Nederlands - Norsk - Portuguese - Svenska: www.cardinalhealth.com/legal/email
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@...
>For additional commands, e-mail: dev-help@...
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@...
>For additional commands, e-mail: dev-help@...
>
>
>
>
--
Vlad Skvortsov, vss@..., vss@...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: Project status
| Free embeddable forum powered by Nabble | Forum Help |
