In order to reduce the number of actors, i'd like to propose to statr
with step 3 (voting Sanselan out of incubatgion). Should reduce the
noise for considerable number of people.
On Sun, May 24, 2009 at 9:00 PM, Charles Matthew Chen
wrote:
> Sounds right to me. Thanks Craig.
>
> Matthew
>
>
> O
Sounds right to me. Thanks Craig.
Matthew
On Sat, May 23, 2009 at 8:02 PM, Craig L Russell wrote:
> Here's my take on graduating Sanselan from incubator to commons.
>
> 1. Sanselan has been accepted by Commons.
> 2. The active committers have been granted write access to the repository.
>
> Re
Sounds good.
On Sat, May 23, 2009 at 4:02 PM, Craig L Russell wrote:
> Here's my take on graduating Sanselan from incubator to commons.
>
> 1. Sanselan has been accepted by Commons.
> 2. The active committers have been granted write access to the repository.
>
> Remaining issues:
>
> 1. Deciding
Here's my take on graduating Sanselan from incubator to commons.
1. Sanselan has been accepted by Commons.
2. The active committers have been granted write access to the
repository.
Remaining issues:
1. Deciding on the package name for sanselan at commons.
2. Deciding on the brand name for s
So where are we now with moving/graduating Sanselan?
Regards
Carsten
--
Carsten Ziegeler
cziege...@apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.
On Thu, Apr 30, 2009 at 7:27 AM, Henri Yandell wrote:
> My concern with Sanselan is that it gets us into the trademark game. I
> like that "Apache Commons Logging" is all about the Apache trademark.
That concern is valid, but it should be sufficient to change the name
Sanselan whenever factual t
Both Betwixt and Jelly are on the quiet side of dormant however.
My concern with Sanselan is that it gets us into the trademark game. I
like that "Apache Commons Logging" is all about the Apache trademark.
Still - not enough to cause pain and strife to the users who'll
already be dealing with mav
Hi folks,
changing package names : +1
changing project name : no opinion about - "Commons Sanselan" or
"Commons Image (Sanselan)" is fine for my
Cheers,
Siegfried Goeschl
Charles Matthew Chen wrote:
> +1 To changing package names. It will be an easy update for Sanselan
> and the project's use
I'm against forcing a name change on an existing project without any
other argument other than "functional names". So +1 to what Charles
says.
Niall
On Tue, Apr 28, 2009 at 9:37 PM, Charles Matthew Chen
wrote:
> +1 To changing package names. It will be an easy update for Sanselan
> and the proj
On Apr 28, 2009, at 2:22 PM, Gary Gregory wrote:
I like:
Commons Image
Not as good as any of the following:
Commons Image (Sanselan)
Commons Image "Sanselan"
Commons Image - Sanselan
The idea is that the name is Commons Image + something Sanselan.
I'm fine with any of the above that con
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Tuesday, April 28, 2009 5:08 AM
> To: Commons Developers List
> Subject: Re: [sanselan] Next steps
>
> On 28/04/2009, luc.maison...@free.fr wrote:
> >
> > - "Phil Steitz"
luc.maison...@free.fr wrote:
> -1 to changing names. Names are part of the social link that build
> communities, changing them would appear to me as if we were stealing the
> project from both its promoters and users. All the work done on having a
> brand known would be lost.
>
Yupp, I totally
+1 To changing package names. It will be an easy update for Sanselan
and the project's users.
+1 to keeping the name Sanselan. The name is of no particular
significance, but users have known the project by that name for a few
years.
Charles Matthew Chen
On Tue, Apr 28, 2009 at 8:43 AM, wr
- "sebb" a écrit :
> On 28/04/2009, luc.maison...@free.fr wrote:
> >
> > - "Phil Steitz" a écrit :
> >
> >
> > > We have voted to accept sanselan as a commons component [1].
> > > Welcome!
> > >
> >
> > > We now need to settle the administrative questions raised in [2]:
> > >
> >
On 28/04/2009, luc.maison...@free.fr wrote:
>
> - "Phil Steitz" a écrit :
>
>
> > We have voted to accept sanselan as a commons component [1].
> > Welcome!
> >
>
> > We now need to settle the administrative questions raised in [2]:
> >
> > 2. Most commons components have a "functional"
PM
>>> To: Commons Developers List
>>> Subject: [sanselan] Next steps
>>>
>>> We have voted to accept sanselan as a commons component [1]. Welcome!
>
> Yes, welcome. I have myself some image (resp. imageio) related code sitting
> here and I'
- "Phil Steitz" a écrit :
> We have voted to accept sanselan as a commons component [1].
> Welcome!
>
> We now need to settle the administrative questions raised in [2]:
>
> 2. Most commons components have a "functional" name instead of a "fun"
>
> name. Would Sanselan need to be renamed
Gary Gregory wrote at Dienstag, 28. April 2009 08:10:
>> -Original Message-
>> From: Phil Steitz [mailto:phil.ste...@gmail.com]
>> Sent: Monday, April 27, 2009 6:46 PM
>> To: Commons Developers List
>> Subject: [sanselan] Next steps
>>
>> We
I agree that the package name should be changed to o.a.c.x but I'm not
so happy with changing the name. Sanselan is well-known in the java
image world, so I would rather keep it.
We already have Betwixt and Jelly, so we have two prominent libs not
using a functional name.
Carsten
--
Carsten Zieg
> -Original Message-
> From: Phil Steitz [mailto:phil.ste...@gmail.com]
> Sent: Monday, April 27, 2009 6:46 PM
> To: Commons Developers List
> Subject: [sanselan] Next steps
>
> We have voted to accept sanselan as a commons component [1]. Welcome!
>
>
On Tue, Apr 28, 2009 at 3:45 AM, Phil Steitz wrote:
> 2. Most commons components have a "functional" name instead of a "fun" name.
> Would Sanselan need to be renamed, e.g. Commons Image, or would it be ok to
> have the sub-project called Sanselan, or Commons Sanselan?
What for? It would bring o
On 28/04/2009, Phil Steitz wrote:
> We have voted to accept sanselan as a commons component [1]. Welcome!
>
> We now need to settle the administrative questions raised in [2]:
>
> 2. Most commons components have a "functional" name instead of a "fun"
> name. Would Sanselan need to be renamed, e
We have voted to accept sanselan as a commons component [1]. Welcome!
We now need to settle the administrative questions raised in [2]:
2. Most commons components have a "functional" name instead of a "fun"
name. Would Sanselan need to be renamed, e.g. Commons Image, or would it
be ok to have
23 matches
Mail list logo
