pydicom-dev group

[Darcy Mason]

Hi all,

I have created a new group, pydicom-dev [http://groups.google.com/
group/pydicom-dev], for discussion of developing the pydicom code
itself (in contrast to using it, which will be the focus of this
group). The group will also get automated messages about issue list
updates or repository commits. Please join that group if you are using
the repository code, or are interested in helping develop pydicom
itself, or just want to listen in on those discussions. If you are
only interested in _using_ pydicom, then subscribing to this first
pydicom group should be enough. New packaged versions will still be
announced here.

I will soon start a discussion on pydicom-dev about ideas for
significant code changes. Pydicom originally avoided turning data
elements into separate object types, but a lot of code has built up a
little change at a time, and I think a bit of a refactoring is
justified. This will hopefully lead to a backwards compatible solution
which won't break existing user code. However, the changes could be
substantial, and better position the code to move forward. Just one
example of the kind of discussions I hope we can have on the new
group.


Regards
Darcy

[Sebastian Haase]

Hi Darcy,

Are you sure that there would be enough traffic to require another
list. It might be a disadvantage to split this little amount of
postings even further into two lists.

I would not mind to hear more about pydicom on this list - how do
others feel ? comments ?

- Sebastian Haase

[Darcy Mason]

On Nov 12, 3:47 am, Sebastian Haase <seb.ha...@gmail.com> wrote:

> Are you sure that there would be enough traffic to require another
> list. It might be a disadvantage to split this little amount of
> postings even further into two lists.

It's a very good question. I avoided doing this for so long exactly
for that reason. So a little background explanation is in order:
- lately I've had several extended conversations (one-to-one) through
regular email about development issues, and started to realize that
those conversations might be of interest to some others
- I've avoided using the google code automated messages for issue list
changes and repository updates because those would probably be equal
or greater in number than the posts on this group. With a different
list, this one could stay more relevant to those just wanting to use
the code. And new people coming across the discussions would be able
to see a clearer list of real discussion as opposed to housekeeping
messages
- right now the traffic is not justified, but it may be in the future.
The one discussion I mentioned on changing data element object models
could be quite extended, so I thought it might be a good time to make
the jump now, even though it may well be too early

> I would not mind to hear more about pydicom on this list - how do
> others feel ? comments ?
>

Yes, I'd love to hear also. Hopefully my comments above make it a
little clearer why I made the new group. But if people feel it's not
necessary, I'd be happy to delay it until the traffic warrants it.

-Darcy

> - Sebastian Haase

[Matthew Brett]

Hi,

>> Are you sure that there would be enough traffic to require another
>> list. It might be a disadvantage to split this little amount of
>> postings even further into two lists.
>
> It's a very good question. I avoided doing this for so long exactly
> for that reason. So a little background explanation is in order:

I'd subscribe to both, but maybe it would be worth seeing how the
traffic goes with one list, and then splitting it if it starts
becoming too intimidating?

Best,

Matthew

[Reso Nance]

> I have created a new group, pydicom-dev [http://groups.google.com/
> group/pydicom-dev], for discussion of developing the pydicom code
> itself (in contrast to using it, which will be the focus of this
> group).

At the current stage I do not have a preference and am comfortble with
a single
as well as with two separate groups. I normally like to have things
organized
though, and I am not sure that 2 groups will hurt.

[Darcy Mason]

On Nov 11, 5:24 pm, Darcy Mason <darcyma...@gmail.com> wrote:
>
> I have created a new group, pydicom-dev [http://groups.google.com/
> group/pydicom-dev], for discussion of developing the pydicom code

Hi all,

There hasn't been a strong reaction one way or another on having a
separate pydicom-dev list, and I'd like to settle this -- I have code
to commit and I'd like to start the refactoring discussion.

After thinking it over some more, I still think a separate list is
slightly better because it gives everyone maximum choice of which
types of messages to receive. For me personally, that means I can
commit code, alter issue list items, or discuss internal changes at
length without wondering if there is a subset of people getting
annoyed by all the extra messages.

So I'm going to start using pydicom-dev. It won't be a lot of traffic
initially, and there may be periods of silence, and overlap with this
group at times. But ultimately I hope it will result in a new kind of
discussion.

So if you are interested, please join up. If you're unsure about
joining the new group, you could view online or subscribe for a while,
until you see if the new group is of interest.

Regards,
Darcy