Nabble - tigris - subissue

Re: Subissue Status

2008-06-02T16:51:31Z

I do hope Subissue development moves forward. In my company we have started some basic user interface (for Windows unfortunately using .NET) using the standards stated on the Subissue webpage but would love to see a web app for it.
Thanks
Ganesh

On Mon, Jun 2, 2008 at 11:53 AM, Bradley Holt <bradley.holt@...> wrote:

It appears that there hasn't been much work recently on Subissue. Is this true? I might be interested in tackling the web-based interface as a PHP/Zend Framework application. It would be a little while (a few months at least) before I could get started working on it, however. Is this something that would be welcomed or is there more work on this already that I just haven't seen?

Thanks,
Bradley

--
Bradley Holt
bradley.holt@...

--
Ganeshram Iyer
Open Source and CAD: http://ossandcad.blogspot.com
ganeshramiyer@...

From forum: subissue - dev

Subissue Status

2008-06-02T09:53:49Z

It appears that there hasn't been much work recently on Subissue. Is this true? I might be interested in tackling the web-based interface as a PHP/Zend Framework application. It would be a little while (a few months at least) before I could get started working on it, however. Is this something that would be welcomed or is there more work on this already that I just haven't seen?

Thanks,
Bradley

--
Bradley Holt
bradley.holt@...

From forum: subissue - dev

Development cycle

2007-05-28T12:05:50Z

Hi all,

I was working on something kind of similar, so I'd like to throw in some code
if possible. But maybe this is the wrong project, so let me first explain my
idea:

I am a user of Aegis for several years:

http://aegis.sourceforge.net/

What I really like about Aegis is that it establishes a development cycle that
basically consists of:

- definition
- implementation
- review
- integration

as well as an enforcement to write automatic tests. Aegis uses RCS and tries
to enhance it to support features that Subversion has by default like atomic
commits, file rename etc. Basically if you use Subversion, you can have
something similar with much less code, which is what I did. Well on a very
small scale to fit my needs.

The development cycle helps a lot to improve code quality as well as project
overview. In my company, we first define the changes to be done in one line
descriptions and sometimes some short sentences to make it clear. This gives
a cheap overview of what is left to be done. Changes are usually something a
developer can do in 2h to 2 days. The review is done by peers and helped to
improve code quality and spread knowledge about how things work among the
developers. The integration leaves a trace about what has been done and get
rid of these "continued development" commit comments.

Thinking about this, I came up with the usual thing developers do: generalize
(sometimes until unuseablity). Why not have a review after the definition
stage? Why not have an automatic (as in code metrics) and a manual review?

The code I currently have allows to do the definition and the integration
steps. The review is done by commiting to a separate branch which can be
checked out by the peer and reviewed.

Another reason for this code was the need for semi-automated merging of
branches. Aegis makes this very easy by simply locking every file that leaves
the implementation stage until it is integrated into the "trunk". SVN imposes
the hassle to keep track of which changes in the trunk you already merged
into your branch. Well my code does this job for you by introducing a "delta"
file that contains a serial number of commits to the trunk. This does also
yield a nice version number that is unaffected by other commits to the
repository as it is only increased when the trunk changes.

So, as you guys seem to be deeply into this subject, is subissue resp. DITrack
the right place?
--
Greetings

Kurt Huwig (Vorstand)
Telefon 0681/96751-50, Telefax 0681/96751-66
http://www.iku-ag.de/

iKu Systemhaus AG, Am Römerkastell 4, 66121 Saarbrücken
Amtsgericht: Saarbrücken, HRB 13240
Vorstand: Kurt Huwig, Andreas Niederländer
Aufsichtsratsvorsitzender: Jan Bankstahl

GnuPG 1024D/99DD9468 64B1 0C5B 82BC E16E 8940 EB6D 4C32 F908 99DD 9468

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Subissue Status?

2007-04-25T11:50:05Z

ronald@... wrote:
> Is the subissue project still active? What state is it currently in?
>
> Just come across this and looks like a very good idea. Maybe I will
> be able to provide some input as well.
>

It doesn't seem to be moving for quite a while. You might be interested
to check out DITrack: www.ditrack.org.

--
Vlad Skvortsov, vss@..., http://vss.73rus.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Subissue Status?

2007-04-25T07:14:32Z

Is the subissue project still active? What state is it currently in?

Just come across this and looks like a very good idea. Maybe I will
be able to provide some input as well.

Ronald

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

[Fwd: DITrack 0.5 is available]

2007-03-06T12:59:48Z

Hi!

Sorry for cross-posting and slight off-topic. We have just released
DITrack 0.5 (www.ditrack.org), which might be of interest to people
subscribed to the Subissue mailing lists.

--
Vlad Skvortsov, vss@..., http://vss.73rus.com

[sorry for double-posting, the previous message has had invalid subject
line]

Hi!

It's my pleasure to announce that DITrack 0.5 is
available at:

http://www.ditrack.org/files/ditrack-0.5.tgz

There were no changes after the previously released beta version.

Below is the changelog:

v.0.5, 06-Mar-2007
==================

* The database format has changed (see the README file for the upgrading
instructions).

* Support for disconnected operations added (new commands: 'commit',
'remove',
'status'; the 'act' and 'new' commands modified accordingly).

* Installation script is now provided in the distributive.

* Categories may now be marked as disabled (and thus won't appear in menus)
(i#73).

* Added the 'resolution' header for closed issues (e.g. 'dropped', 'fixed',
'invalid') (i#75).

* It is now possible to specify user id through the '--user'/'-u'
command line
option or by setting the DITRACK_USER environment variable (i#98).

* The 'act' command will now display titles of the issues worked on (i#74).

* The 'cat' command now accepts arguments of the syntax X.Y, meaning
"display
comment Y of issue X".

* A new command line option for the 'cat' command: '--headers-only'.

* Duplicate user accounts in the configuration are now detected.

* Fixed: dt-createdb doesn't set 'ditrack:format' property (i#72).

* Fixed: unhandled exception if database root specified doesn't exist (i#76)

* Fixed: the usage of filters in 'ls' cause unhandled exception if database
path is invalid (i#81).

* Fixed: referencing nonexistent header from a filter results in a crash
(i#96).

* Fixed: assertion fault on empty 'DT-New-*' header.

* Fixed: 'cat' handles invalid entity ids ungracefully (i#88, i#94).

* The debug output enabled by the DITRACK_DEBUG environment variable.

* Added the test suite (48 testcases).

--
Vlad Skvortsov, vss@..., http://vss.73rus.com

_______________________________________________
Announce mailing list
Announce@...
http://lists.ditrack.org/mailman/listinfo/announce

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

(no subject)

2007-03-06T12:59:48Z

Hi!

Sorry for cross-posting and slight off-topic. We have just released
DITrack 0.5 (www.ditrack.org), which might be of interest to people
subscribed to the Subissue mailing lists.

--
Vlad Skvortsov, vss@..., http://vss.73rus.com

[sorry for double-posting, the previous message has had invalid subject
line]

Hi!

It's my pleasure to announce that DITrack 0.5 is
available at:

http://www.ditrack.org/files/ditrack-0.5.tgz

There were no changes after the previously released beta version.

Below is the changelog:

v.0.5, 06-Mar-2007
==================

* The database format has changed (see the README file for the upgrading
instructions).

* Support for disconnected operations added (new commands: 'commit',
'remove',
'status'; the 'act' and 'new' commands modified accordingly).

* Installation script is now provided in the distributive.

* Categories may now be marked as disabled (and thus won't appear in menus)
(i#73).

* Added the 'resolution' header for closed issues (e.g. 'dropped', 'fixed',
'invalid') (i#75).

* It is now possible to specify user id through the '--user'/'-u'
command line
option or by setting the DITRACK_USER environment variable (i#98).

* The 'act' command will now display titles of the issues worked on (i#74).

* The 'cat' command now accepts arguments of the syntax X.Y, meaning
"display
comment Y of issue X".

* A new command line option for the 'cat' command: '--headers-only'.

* Duplicate user accounts in the configuration are now detected.

* Fixed: dt-createdb doesn't set 'ditrack:format' property (i#72).

* Fixed: unhandled exception if database root specified doesn't exist (i#76)

* Fixed: the usage of filters in 'ls' cause unhandled exception if database
path is invalid (i#81).

* Fixed: referencing nonexistent header from a filter results in a crash
(i#96).

* Fixed: assertion fault on empty 'DT-New-*' header.

* Fixed: 'cat' handles invalid entity ids ungracefully (i#88, i#94).

* The debug output enabled by the DITRACK_DEBUG environment variable.

* Added the test suite (48 testcases).

--
Vlad Skvortsov, vss@..., http://vss.73rus.com

_______________________________________________
Announce mailing list
Announce@...
http://lists.ditrack.org/mailman/listinfo/announce

---------------------------------------------------------------------
To unsubscribe, e-mail: announce-unsubscribe@...
For additional commands, e-mail: announce-help@...

From forum: subissue - announce

Re: Project Status

2006-11-08T09:48:12Z

Peter Davis wrote:
> Hello Colin and everyone else on the list,
>
> It seems the project has stagnated once again. There was a flurry of
> activity a couple months ago but I don't know what happened after
> that. I, myself, never developed it past what you see on the website,
> which is basically just the concept. I'm currently studying abroad in
> India without much email access, but when I return I'll have a few
> spare hours to work on it between my university classes if you want to
> help. Code basically needs to be architected from scratch.
That flurry of activity in May/Jun resulted in me starting an
alternative project, check out http://www.ditrack.org. Any help is
greatly appreciated. :-)

>
> Thanks once again to everyone who's taken an interest and encouraged
> me that this project is a good idea.
>
> -Peter
>
>
> On Wed, 8 Nov 2006, Gourlay, Colin wrote:
>
>> Hello.
>>
>> I just stumbled across this project late last night and am wondering
>> what the status of the project is and how I may get involved.
>>
>> Cheers
>>
>> Colin
>>
>> ---------------------------------------------------------------------
>> 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@..., http://vss.73rus.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

RE: Project Status

2006-11-08T05:06:52Z

I'd love to help out - just let me know how to progress this.

Cheers

Colin

-----Original Message-----
From: Peter Davis [mailto:pediddle@...]
Sent: 08 November 2006 12:58
To: dev@...
Subject: Re: [subissue] Project Status

Hello Colin and everyone else on the list,

It seems the project has stagnated once again. There was a flurry of
activity a couple months ago but I don't know what happened after that.
I, myself, never developed it past what you see on the website, which is
basically just the concept. I'm currently studying abroad in India
without much email access, but when I return I'll have a few spare hours
to work on it between my university classes if you want to help. Code
basically needs to be architected from scratch.

Thanks once again to everyone who's taken an interest and encouraged me
that this project is a good idea.

-Peter

On Wed, 8 Nov 2006, Gourlay, Colin wrote:

> Hello.
>
> I just stumbled across this project late last night and am wondering
> what the status of the project is and how I may get involved.
>
> Cheers
>
> Colin
>
> ---------------------------------------------------------------------
> 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@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project Status

2006-11-08T04:57:48Z

Hello Colin and everyone else on the list,

It seems the project has stagnated once again. There was a flurry of activity a couple months ago but I don't know what happened after that. I, myself, never developed it past what you see on the website, which is basically just the concept. I'm currently studying abroad in India without much email access, but when I return I'll have a few spare hours to work on it between my university classes if you want to help. Code basically needs to be architected from scratch.

Thanks once again to everyone who's taken an interest and encouraged me that this project is a good idea.

-Peter

On Wed, 8 Nov 2006, Gourlay, Colin wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Project Status

2006-11-08T03:31:44Z

Hello.

I just stumbled across this project late last night and am wondering
what the status of the project is and how I may get involved.

Cheers

Colin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Flagged Account

2006-07-10T01:47:13Z

PayPal

July 2006


	Track your expenses using PayPal. It's easy to track your expenses and stay organized when you use PayPal. All your incoming and outgoing payments are tracked on your Account History page. See sample.

Your account has been flagged!
PayPal Security Measures.

Dear PayPal Member,

Your account has been randomly flagged in our system as a part of our routine security measures. This is a must to ensure that only you have access and use of your Paypal account and to ensure a safe PayPal experience. We require all flagged accounts to verify their information on file with us. To verify your information at this time, please visit our secure server webform by clicking the hyperlink below:

Click here to verify your Information

If you choose to ignore our request, you leave us no choice but to temporarily suspend your account.
Thank you for your patience as we work together to protect your account.

Your PayPal Account in Action

			Use PayPal to purchase with cash. When you link your bank account to your PayPal account, you can fund your purchases with the money from your bank account. So get Verified—it's just like spending cash. Learn more.

			Make FREE calls around the world. Reduce your phone bills—with Skype software you can talk to other Skype users all over the world for free. Or make low-cost calls to any landline or cell phone with SkypeOut^TM services you purchase with PayPal. Learn more.

			Pay or get paid back with PayPal. Start off the year with a clean slate. Easily pay your family and friends what you owe them, or request money that they owe you. See how easy it is to send or request money with PayPal.

Special Offers for PayPal Customers


			Save 20% on Dell Inspiron Notebooks when you use PayPal. Enter code at checkout: SFW86WKM?16WSL				Special Offer— Use PayPal and get free Super Saver Shipping on ship- ments of $49 or more.				Save 10% on over 300,000 products. Enter promo code: paysave. Plus Free Shipping, Free Returns, and No Sales Tax.


		Helpful Links: ID Theft Resources \| Help Center \| PayPal Shops \| Password Help

Please do not replay to this e-mail. To modify your notification preferences, log in to your PayPal account, click the Profile sub-tab, then click the Notifications link under Account Information. Changes may take up to 10 days to be reflected in our mailings. PayPal will not sell or rent any of your personally identifiable information to third parties. For more information about the security of your information, read our Privacy Policy at https://www.paypal.com/privacy.

Copyright © 2006 PayPal Inc. All rights reserved. Designated trademarks and brands are the property of their respective owners. PayPal is located at 2211 N. First St., San Jose, CA 95131.

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...

From forum: subissue - dev

DITrack

2006-06-26T19:05:01Z

Hi!

For those who might be interested, our project, which was inspired by
Subissue, is located at:

http://www.ditrack.org

This is a newborn, treat accordingly.

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Continuance?

2006-05-31T13:45:09Z

After a brief flurry of activity, interest seems to have died or has it
moved to IRC?

G.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Subissue web-interface [Was: Subissue status]

2006-05-11T02:07:48Z

> XSLT/XML for me is a good call.
>
> I think this might also help with the reporting capability, as well
> helping support multiple frontends.
>
> Thought about Python for the web frontend? - It's very nice....

No. Time is limited by work and girlfriend so I keep to C++ and Java. I
know you can use C++ and Java via CGI but that is less than standard
(maybe not?). My friend has been badgering me to learn PHP, which is
class based and has ports of struts etc., so that looks like where I
will aim for. Also when I get stuck I will have 24/7 support in it.

Whatever is chosen I think the XML output and have the client use XSLT
to translate it is the right choice in this case. Also the cleanliness
demonstrated by Insurrection gives a good indication of what can be done.

I haven't checked the source but I think Insurrection project (hosted
here at http://insurrection.tigris.org/) could be used as a good
starting point for the web interface. However the code is Perl, which I
have never actually touched so the learning curve (I imagine) will be steep.

If anyone has any ideas of why we should reinvent the wheel and not use
the Insurrection source as a start I would like to hear it.

G.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project status

2006-05-10T10:35:19Z

Drew Myers wrote:

>I agree with Vlad in that whatever solution we develop, it definitely
>should not be dependent upon a single client interface.
>
>Ronny and I have spoken a bit via email about this topic. As an
>example, TortoiseSVN already handles some degree of issue tracking, when
>the issue tracking is done via a set of rules they've set forth. While
>TortoiseSVN is significant, and perhaps one of the most popular clients
>for Subversion, I still think Vlad is right...the issue tracking should
>not be limited to a single interface.
>
>However, I'm not sure that extends to administration of the
>issue-tracking system. If the administrative interface to 'subissue' is
>web-based, but various clients can interact via some issue-tracking API,
>with all the metadata stored within the subversion repository itself,
>then, to my mind, that's a clean solution. You may disagree.
>
>

The 'administration' term usually means access restriction and control
for different groups of users. The only way to control access to data is
to direct it through single gateway that enforces policies established.
The 'administrative interface' in this case is the control interface for
such a gateway.

In my model data is distributed between different consumers (by the
means of svn) thus the only point of control is the repository itself
with its hooks. I believe that administrative settings (ACLs, user
roles, etc) should be kept in a repository as well and be enforced by
hooks dealing with the same repository. So if one needs, any number of
administrative interfaces could be built within the same model: those
will access data in the same repository (provided having enough
permissions, enforced by repository hooks).

So, may be what I thought of doesn't fit into others' mode of operation
regarding the business logic of issue tracking system. My focus is
currently on small groups (because my group needs that) that can just
hack administrative settings with 'vi' and do not need any
administrative interfaces *for now*. This is according to the general
engineering philosophy that I stick with: "Build something small that
works, then try to scale."

Anyway, it seems that the project founder wants to get back to Subissue
some time in the future, so there are too many cooks in the kitchen,
probably...

>If you haven't seen the spec the TSVN guys have laid out, here's a link:
>http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch05s24.html
>
>If nothing else, perhaps this will give us some solid grist for the mill
>:).
>
>
>drew
>
>

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

RE: Subissue status

2006-05-10T05:16:03Z

XSLT/XML for me is a good call.

I think this might also help with the reporting capability, as well
helping support multiple frontends.

Thought about Python for the web frontend? - It's very nice....

M

-----Original Message-----
From: Graham Reeds [mailto:grahamr@...]
Sent: 10 May 2006 11:16
To: dev@...
Subject: [subissue] Subissue status

I spoke with Peter Davis (the founder of the project) on 05/10/05 and he

explained that he started the project with good intentions but he is
doing an undergraduate degree "So it's really a matter of too little
time, what with homework and all.". He goes on to say "Not much code
was ever written, so for the near/medium term I don't expect the project

to go anywhere. I do hope to pick it up again in the future."

I will be willing to lend a hand (UK, so GMT+0).

For the web-based viewing system mentioned in the project outline I
think the back end should produce an XSLT/XML script which can either be

parsed by a client tool or rendered by a browser. I am a "dab-hand" at
HTML, CSS, etc but primarily a Java/C++ person though I could probably
learn the rudiments of PHP fairly quickly if need be.

Graham Reeds

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

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 - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese - Svenska:
www.cardinalhealth.com/legal/email

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Subissue status

2006-05-10T04:15:41Z

I spoke with Peter Davis (the founder of the project) on 05/10/05 and he
explained that he started the project with good intentions but he is
doing an undergraduate degree "So it's really a matter of too little
time, what with homework and all.". He goes on to say "Not much code
was ever written, so for the near/medium term I don't expect the project
to go anywhere. I do hope to pick it up again in the future."

I will be willing to lend a hand (UK, so GMT+0).

For the web-based viewing system mentioned in the project outline I
think the back end should produce an XSLT/XML script which can either be
parsed by a client tool or rendered by a browser. I am a "dab-hand" at
HTML, CSS, etc but primarily a Java/C++ person though I could probably
learn the rudiments of PHP fairly quickly if need be.

Graham Reeds

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project status

2006-05-10T01:39:11Z

Vlad Skvortsov a écrit :
> FWIW, this is a brief list of requirements/expectations that I pose on
> such a system.

It seems that some of yours requirements are already presents in the
initials goals of subissue. But I am completly agree with your point of
view.

As a quality engineer, I expect from subissue to reach a maximum of the
goals defined by the CMMi (process area CM): tracking the bugs and
issues is one of the major requirements.

[jean-louis.juan.vcf]

begin:vcard fn:Jean-Louis Juan n:Juan;Jean-Louis org;quoted-printable;quoted-printable:AtosOrigin Syst=C3=A8me Int=C3=A9gration;Cellule Qualit=C3=A9 adr;quoted-printable;quoted-printable:BP 475;;1, Rue Amp=C3=A8re;Lab=C3=A8ge Cedex;;31315;France email;internet:jean-louis.juan@... title;quoted-printable:Ing=C3=A9nieur Qualit=C3=A9 tel;work:05.61.39.24.30 tel;fax:05.61.19.16.65 note;quoted-printable:=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A= Ce message electronique est confidentiel. Il peut contenir des=0D=0A= informations protegees par le secret professionnel, le secret de=0D=0A= fabrication ou autres regles legales. Si vous recevez ce message par=0D=0A= erreur, il vous est interdit de le reproduire ou de le distribuer en=0D=0A= tout ou en partie, ou de le divulguer de quelque maniere que ce soit a=0D=0A= quelque personne que ce soit. Nous vous prions de bien vouloir en=0D=0A= informer Atos Origin, par telephone ou par retour d'e-mail puis de=0D=0A= detruire le message et toutes copies de votre systeme informatique. Le=0D=0A= contenu de ce message ne reflete pas necessairement ni les opinions=0D=0A= d'Atos Origin ni celle des membres de son groupe. Bien que l'emetteur=0D=0A= de ce message ait fait tout son possible pour maintenir son systeme=0D=0A= informatique sans virus, il ne peut garantir que cette transmission ne=0D=0A= comporte aucun virus et il ne pourra etre tenu pour responsable de=0D=0A= quelque dommage que ce soit resultant de la transmission d'un virus.=0D=0A= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A= This electronic transmission is confidential. It may contain=0D=0A= information that is covered by legal professional privilege, work=0D=0A= product immunity or other legal rules. If you have received this=0D=0A= transmission in error, you must not copy or distribute this message or=0D=0A= any part of it or otherwise disclose its contents to anyone. Please=0D=0A= notify Atos Origin Legal Services by telephone or return E-mail, and=0D=0A= then delete this transmission and any copies of it from your computer=0D=0A= system. The views expressed in this electronic transmission do not=0D=0A= necessarily reflect those of Atos Origin SA or any member of its group.=0D=0A= Although the sender endeavours to maintain a computer virus free=0D=0A= network, the sender does not warrant that this transmission is virus=0D=0A= free and will not be liable for any damages resulting from any virus=0D=0A= transmitted.=0D=0A= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D version:2.1 end:vcard

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project status

2006-05-09T15:07:11Z

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?

Yep, I am using it in a medium scale enterprise. See my email of the 8th.

Regards,
Felix

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project status

2006-05-09T14:13:14Z

I agree with Vlad in that whatever solution we develop, it definitely
should not be dependent upon a single client interface.

Ronny and I have spoken a bit via email about this topic. As an
example, TortoiseSVN already handles some degree of issue tracking, when
the issue tracking is done via a set of rules they've set forth. While
TortoiseSVN is significant, and perhaps one of the most popular clients
for Subversion, I still think Vlad is right...the issue tracking should
not be limited to a single interface.

However, I'm not sure that extends to administration of the
issue-tracking system. If the administrative interface to 'subissue' is
web-based, but various clients can interact via some issue-tracking API,
with all the metadata stored within the subversion repository itself,
then, to my mind, that's a clean solution. You may disagree.

If you haven't seen the spec the TSVN guys have laid out, here's a link:
http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch05s24.html

If nothing else, perhaps this will give us some solid grist for the mill
:).

drew
--

Never offend people with style when you can offend them with substance.
- Sam Brown, Washington Post, 1977

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Project status

2006-05-09T10:32:36Z

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@...

From forum: subissue - dev

RE: Project status

2006-05-09T02:34:01Z

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@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-08T10:52:56Z

So, did you guys have a meeting? Was there any outcome?

Malik, Ajay wrote:

>All,
>
>Lets have a quick meeting to align our expectations on Saturday at the
>time suggested and then we will have a follow up.
>
>Regards
>Ajay
>
>-----Original Message-----
>From: Vlad Skvortsov [mailto:vss@...]
>Sent: Friday, May 05, 2006 10:55 AM
>To: dev@...
>Subject: Re: [subissue] Dev Meeting
>
>Drew Myers wrote:
>
>
>
>>For a meeting time, I suggest Saturday May 6th GMT 1700.
>>
>>
>>
>>
>I won't be in town till Monday. Actually, workdays fit better for me.
>Anyway, I don't want to hold you guys, so go ahead and do this. I would
>like to read the IRC log afterwards.
>
>
>

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

RE: Project status

2006-05-08T04:15:20Z

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@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-07T17:33:22Z

Ronny Hanssen wrote:
>
> BTW: I am currently using Trac for my projects, but liked the idea that

Hi,
I've been watching this list for over a year now. Glad to see some
activity getting going! We are using Trac (projects.edgewall.com/trac)
here very successfully. For those who haven't seen Trac it is a Python,
web based ticketing program with some nice integration to SVN. It
allows browsing of the repo, displaying the SVN changesets as part of a
project timeline and linking from tickets and the wiki to SVN changesets.

There has been a bit of discussion in Trac about using various backends
for the ticket storage. Currently I think it defaults to SQLite but
there is a plugin to use PostGresql. How about the idea of writing a
plugin backend for Trac that uses SVN as the backend? Trac is evolving
very nicely and has recently been refactored to give a nicer plugin
architecture. The advantage of doing subissue as a plugin for trac is
you already get all the features (and plugins) of Trac for free and one
can concentrate on the interesting work (the repo backend) without the
distraction of having to invent all that gui. It is already possible to
radically alter the functionality of Trac with other plugins and patches
so if one does not like the way something works that can be dealt with
as a separate issue.

Looking forward to seeing this progress.

Regards,
Felix

GMT +12
New Zealand

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T18:16:43Z

I guess that the meeting is then on irc://chat.freenode.net/subissue

irc://freenode.net timed out for me, and since the freenode.net website
referred to chat.freenode.net I tried that instead - which worked for
me. The channel is obviously #subissue :)

I hope people will be using nicks that relate to their email address or
their real name.

BTW: I am currently using Trac for my projects, but liked the idea that
installing subversion was all that would be needed in terms of backbone.
A missing feature for all the project/issue tracking systems (at least
the free and/or open sourced ones) are the lack of updating the user
about which issues has been fixed since last update (when updating the
source). I think this is an extremely useful feature, since it tells you
what to expect from the source you are using. Since issues and source
are closely related with subissue implemented I'd love to see a way to
report back the progress... Maybe this is an extension for TortoiseSVN
for svn-servers using the subissue plugin? Maybe the whole
project-tracking GUI could be implemented as an extension to TSVN? Even
configuration perhaps? I am using TSVN or alternatively the Subclipse
extension for Eclipse. I guess that both of these could have a subissue
extension.

Regards,
Ronny

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

RE: Dev Meeting

2006-05-05T13:15:54Z

All,

Lets have a quick meeting to align our expectations on Saturday at the
time suggested and then we will have a follow up.

Regards
Ajay

-----Original Message-----
From: Vlad Skvortsov [mailto:vss@...]
Sent: Friday, May 05, 2006 10:55 AM
To: dev@...
Subject: Re: [subissue] Dev Meeting

Drew Myers wrote:

>For a meeting time, I suggest Saturday May 6th GMT 1700.
>
>
I won't be in town till Monday. Actually, workdays fit better for me.
Anyway, I don't want to hold you guys, so go ahead and do this. I would
like to read the IRC log afterwards.

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

________________________________________________________________________
This email has been scanned for computer viruses.

________________________________________________________________________
This email has been scanned for computer viruses.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T11:56:57Z

hi!

> For a meeting time, I suggest Saturday May 6th GMT 1700.
> (...)
> GMT+1: 1800 (6pm Saturday evening)
sounds good to me.

> I realize this is a little quick, so if we need to push it out, that's
> fine. Given the various timezones, and other personal commitments, I'd
> imagine a weekend will probably be better for everyone. Feel free to
> comment.
i agree. i can't really do this sort of thing easily during the week.

jens

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T11:55:24Z

Drew Myers wrote:

>For a meeting time, I suggest Saturday May 6th GMT 1700.
>
>
I won't be in town till Monday. Actually, workdays fit better for me.
Anyway, I don't want to hold you guys, so go ahead and do this. I would
like to read the IRC log afterwards.

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T11:52:06Z

* Vlad Skvortsov (vss@...) wrote:
> Malik, Ajay wrote:
> >Hi,
> >I am located in California, GMT - 8.
> >
> Me too, Palo Alto / Mountain View.

For a meeting time, I suggest Saturday May 6th GMT 1700.

Given the variety of timezones we have, this breaks down as:

GMT-8: 0900 (9am Saturday morning)
GMT-5: 1200 (12pm Saturday noon)
GMT: 1700 (5pm Saturday afternoon)
GMT+1: 1800 (6pm Saturday evening)

I realize this is a little quick, so if we need to push it out, that's
fine. Given the various timezones, and other personal commitments, I'd
imagine a weekend will probably be better for everyone. Feel free to
comment.

> >Agenda:
> >[0] Overview of the project
> >
> Do you wanna share this with us? If you have any write-ups can you
> please post a link so that we read them prior to the discussion?
> >[1] Current Status of development
> >[2] Establish model/processes of communication and information
> >exchange
> >[3] Next steps

I'm with Vlad here...I'd like to see whatever documentation is available
prior to the meeting, if possible. If it can't be posted anywhere,
perhaps just a tarball of what currently exists emailed to the list?
Dunno if attachments are allowed here.

Thanks,

drew
--

Honest differences are often a healthy sign of progress.
- Mahatma Gandhi (1869 - 1948)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T11:20:46Z

Malik, Ajay wrote:
> Hi,
>
> I am located in California, GMT - 8.
>
Me too, Palo Alto / Mountain View.
> Agenda:
>
> [0] Overview of the project
>
Do you wanna share this with us? If you have any write-ups can you
please post a link so that we read them prior to the discussion?
> [1] Current Status of development
> [2] Establish model/processes of communication and information exchange
> [3] Next steps
>
>

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

RE: Dev Meeting

2006-05-05T10:54:51Z

Hi,

I am located in California, GMT - 8.

Agenda:

[0] Overview of the project
[1] Current Status of development
[2] Establish model/processes of communication and information exchange
[3] Next steps

Regards
Ajay

-----Original Message-----
From: Vlad Skvortsov [mailto:vss@...]
Sent: Friday, May 05, 2006 9:44 AM
To: dev@...
Subject: Re: [subissue] Dev Meeting

I don't mind meeting on IRC (it's actually more preferrable for me than
a WebEx). However for the meeting to be useful for everyone involved I
would still recommend having an agenda.

We could start with requirements for the system. It may be useful to
have put that on Wiki somewhere. However, as a cheapiest solution
everyone could just toss drafts of the requirements into this list.
Then we need another person to fish these drafts from the mailing list
archives, compile a single version of that and go from there. Having a
document to discuss will greatly improve productivity of such a meeting.

Drew Myers wrote:

>Ajay and I discussed this briefly via email, but I'd like to toss the
>idea to the group for consideration.
>
>Ajay mentioned a webex, but I'd also like to suggest perhaps a meeting
>via IRC. IRC would allow us to log all the text, which could then be
>condensed into minutes of the meeting.
>
>What do you guys think? Any suggestions for IRC server/channel?
>
>Thanks,
>
>
>drew
>
>

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

________________________________________________________________________
This email has been scanned for computer viruses.

________________________________________________________________________
This email has been scanned for computer viruses.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T10:44:23Z

I don't mind meeting on IRC (it's actually more preferrable for me than
a WebEx). However for the meeting to be useful for everyone involved I
would still recommend having an agenda.

We could start with requirements for the system. It may be useful to
have put that on Wiki somewhere. However, as a cheapiest solution
everyone could just toss drafts of the requirements into this list.
Then we need another person to fish these drafts from the mailing list
archives, compile a single version of that and go from there. Having a
document to discuss will greatly improve productivity of such a meeting.

Drew Myers wrote:

--
Vlad Skvortsov, vss@..., vss@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev

Re: Dev Meeting

2006-05-05T10:43:12Z

> What do you guys think? Any suggestions for IRC server/channel?
freenode.net? and yes, i'd vastly prefer irc to webex. and my timezone
is gmt+1

jens

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: subissue - dev