Nabble - Apache Incubator - Projects

Kato next steps

2008-11-06T07:15:50Z

Hi Kato committers.

Now that Kato has been accepted for Incubation I'll go kick off the process
to get the ASF infrastructure set up for it. In the meantime you each need
to sign and fax in an Individual Contributor License Agreement to the ASF,
see: http://www.apache.org/licenses/#clas. Additionally, if there is
existing code that you want to seed the project with then you will need to
submit a Software Grant Agreement, see:
http://www.apache.org/licenses/#grants

...ant

Promote your project in the Fast Feather Track at ApacheCon US 08

2008-09-09T00:44:58Z

Committers, friends, fellow revelers!

We've less than two months to go until ApacheCon kicks off with style in
New Orleans! Are you ready?

Hopefully by now, you've already registered, and you've had a chance to
suss out which sessions you're interested in. You've probably signed in
to CrowdVine to make plans to meet with the people working in your
project - or to follow the people who know where to find the best bars ;-)

But apart from New Orleans nightlife, what could possibly be more
exciting than your Next Big Thing? The Fast Feather Track provides space
for the projects that are just too new or fast-moving to fit in to the
normal CFP. So if you've got the skinny on an Apache Incubator project,
or the lowdown on the Labs, this is your chance for fifteen minutes of fame.

The Fast Feather Track is all about the technology - so whether you're a
novice or a natural at public speaking, there's room for you! Anything
new at The Apache Software Foundation belongs here - whether you're
ready for showtime and want the world to know, or you're still finding
your feet, and just fishing for a few new contributors.

We don't expect that the Fast Feather Track will be set up and nailed
down this far out - we'll try and slot your sessions in somewhere, right
up to the last minute. But if you've already got your ticket, and you
know what you want to talk about, please let us know now, so we can make
sure there's space for everyone.

You'll need to send

* a title (you can make it vague, if you're not sure whether that
release will make it out the door in time, or you're still arguing over
the project name!),

* a brief description of what you want to talk about (remember that the
talk is only 15 minutes long - five sentences is probably plenty),

* and a short bio (if you're already speaking at ApacheCon, you can
skip this step).

to the mailto:fastfeather-2008-us@... list.

What do you get out of it? If you send in your details soon, we'll do
our best to make sure they appear in the program - and we'll be able to
make sure that your talk gets printed nicely on the schedule at the
conference. You'll also get bragging rights, kudos and karma - and you
might even pick up a few new groupie^Wcommitters.

ApacheCon New Orleans - are you ready, for just about anything?

Craig & Carsten, your Fast Feather Krewe

(NB Speaking in the Fast Feather Track does not entitle you to the full
range of speaker perks - you'll get a shiny badge, and your bio in the
program, but you won't get your travel, room or registration comped.
Doesn't make it any less fun though, we promise!)
--
Carsten Ziegeler
cziegeler@...

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

Re: PhotArk: getting started

2008-09-05T16:11:23Z

OK, our mailing lists are up, so we should move to using those now. (I'm
sending this here because I figure people haven't had time to subscribe
yet.) I've also changed the commit notifications to go to our commits list,
now that we have one.

I've put up our Incubator Status page:

http://incubator.apache.org/projects/photark.html

and added PhotArk to the Projects list in the right hand column of Incubator
site pages. I admit to getting a little ahead of myself by adding a link
from the status page to our JIRA component, given that the JIRA component
hasn't been created yet, but I figured it wouldn't do any harm given that
people shouldn't be ready to file bugs against PhotArk yet. ;-)

--
Martin Cooper

On Sat, Aug 23, 2008 at 3:39 PM, Martin Cooper <martinc@...> wrote:

> I've created the SVN repo, although commit messages are temporarily set to
> go to cvs@... since we don't have our mailing lists yet. I also
> have our Incubation Status page ready to go, but I'm not going to check it
> in until the mailing lists are created, in case someone tries to subscribe.
> ;-) The JIRA project is also pending mailing list creation, but I don't
> imagine we'll need that right away anyway.
>
> --
> Martin Cooper
>
>
>
> On Sat, Aug 23, 2008 at 1:15 AM, Roland Weber <ossfwot@...> wrote:
>
>> Luciano Resende wrote:
>>
>>> I have create necessary JIRA issue and sub-tasks to start the creation
>>> process for the PhotArk podling
>>>
>>> https://issues.apache.org/jira/browse/INFRA-1713
>>>
>>
>> Thanks! I have now sent the trigger mail to infra@, with cc:
>> to private@. That mail must be sent by an IPMC member.
>>
>> http://www.apache.org/dev/reporting-issues.html#intro
>>
>>
>> cheers,
>> Roland
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: projects-unsubscribe@...
>> For additional commands, e-mail: projects-help@...
>>
>>
>

Re: architecture questions

2008-08-28T09:25:42Z

Hi all,

Luciano Resende wrote:
> Also, I was wondering if I should move the sample code I had started
> in Tuscany to our new photArk svn repo

Nope, we can't use that yet. Infrastructure requires that the
'commits' list has a complete audit trail of all repository commits.
Please don't use the repo until our own commits list is up and
the repo is configured to send there. We don't want to ask
infra to merge individual commit messages from another list.

> On Wed, Aug 27, 2008 at 12:48 PM, Felix Meschberger <fmeschbe@...> wrote:

>> Yes, Sling accesses the repository directly and maps it into its own
>> abstraction called the Resource tree. Each Resource retrieved from the
>> Resource tree by means of the so-called ResourceResolver can be adapted to
>> other objects.
>>
>> For example if a Resource is backed by a JCR node, you can adapt it to the
>> Node interface and get the backing node. If you employ Jackrabbit Object
>> Content Mapping (OCM) you may also adapt to the object classes mapped by the
>> content. This gives you seemless access to the repository data as raw JCR
>> items or as mapped business objects.
>>
>> Hope this helps.

Thanks!

cheers,
Roland

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

Re: architecture questions

2008-08-27T13:32:52Z

I think moving the code is a great idea. Also, I was having problems
getting it to run because I know that my classpath is incorrect. I
just haven't had enough time in one sitting to fix it
completely. Will the correct jars be part of the project or should
we just create a list of which files are needed for the project?

I also like the idea of defining the basic scenarios. That will give
us a perfect start for a Web page describing the product as well.

Angie

At 03:58 PM 8/27/2008, Luciano Resende wrote:

>Would it be better if we define a set of basic scenarios/functionality
>we want to have for PhotArk 0.1, and then we start expanding and
>choosing the best design/technology to use during implementation ? I
>guess this would allow us to have the right questions to allow us to
>properly pick/choose design, technology, etc
>
>Also, I was wondering if I should move the sample code I had started
>in Tuscany to our new photArk svn repo
>
>On Wed, Aug 27, 2008 at 12:48 PM, Felix Meschberger
><fmeschbe@...> wrote:
> > Hi,
> >
> > Roland Weber schrieb:
> >>
> >> Hi Angie,
> >>
> >> happy hacking :-)
> >>
> >> As I understand it, you are currently working from
> >> Luciano's Tuscany-based codebase, hence the ? arrow.
> >> Unless you have way too much time on your hands, I
> >> would stick with that architecture until the layout
> >> of the repository is stabilized.
> >> Regarding the ? box, I also don't see a layer there.
> >> Sling is meant to access JCR directly, if I am not
> >> mistaken. Of course one should have a few helper
> >> interfaces or classes that define the repository
> >> layout, but these are utilities and not an access
> >> layer that separates the front-end from the repository.
> >
> > Yes, Sling accesses the repository directly and maps it into its own
> > abstraction called the Resource tree. Each Resource retrieved from the
> > Resource tree by means of the so-called ResourceResolver can be adapted to
> > other objects.
> >
> > For example if a Resource is backed by a JCR node, you can adapt it to the
> > Node interface and get the backing node. If you employ Jackrabbit Object
> > Content Mapping (OCM) you may also adapt to the object classes
> mapped by the
> > content. This gives you seemless access to the repository data as raw JCR
> > items or as mapped business objects.
> >
> > Hope this helps.
> >
> > Regards
> > Felix
> >
> >
> >>
> >> Maybe you want to put a small "access control" box
> >> into the JCR box?
> >>
> >> cheers,
> >> Roland
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: projects-unsubscribe@...
> >> For additional commands, e-mail: projects-help@...
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: projects-unsubscribe@...
> > For additional commands, e-mail: projects-help@...
> >
> >
>
>
>
>--
>Luciano Resende
>Apache Tuscany Committer
>http://people.apache.org/~lresende
>http://lresende.blogspot.com/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: projects-unsubscribe@...
>For additional commands, e-mail: projects-help@...

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

Re: architecture questions

2008-08-27T12:58:05Z

Would it be better if we define a set of basic scenarios/functionality
we want to have for PhotArk 0.1, and then we start expanding and
choosing the best design/technology to use during implementation ? I
guess this would allow us to have the right questions to allow us to
properly pick/choose design, technology, etc

Also, I was wondering if I should move the sample code I had started
in Tuscany to our new photArk svn repo

On Wed, Aug 27, 2008 at 12:48 PM, Felix Meschberger <fmeschbe@...> wrote:

> Hi,
>
> Roland Weber schrieb:
>>
>> Hi Angie,
>>
>> happy hacking :-)
>>
>> As I understand it, you are currently working from
>> Luciano's Tuscany-based codebase, hence the ? arrow.
>> Unless you have way too much time on your hands, I
>> would stick with that architecture until the layout
>> of the repository is stabilized.
>> Regarding the ? box, I also don't see a layer there.
>> Sling is meant to access JCR directly, if I am not
>> mistaken. Of course one should have a few helper
>> interfaces or classes that define the repository
>> layout, but these are utilities and not an access
>> layer that separates the front-end from the repository.
>
> Yes, Sling accesses the repository directly and maps it into its own
> abstraction called the Resource tree. Each Resource retrieved from the
> Resource tree by means of the so-called ResourceResolver can be adapted to
> other objects.
>
> For example if a Resource is backed by a JCR node, you can adapt it to the
> Node interface and get the backing node. If you employ Jackrabbit Object
> Content Mapping (OCM) you may also adapt to the object classes mapped by the
> content. This gives you seemless access to the repository data as raw JCR
> items or as mapped business objects.
>
> Hope this helps.
>
> Regards
> Felix
>
>
>>
>> Maybe you want to put a small "access control" box
>> into the JCR box?
>>
>> cheers,
>> Roland
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: projects-unsubscribe@...
>> For additional commands, e-mail: projects-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

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

Re: architecture questions

2008-08-27T12:48:13Z

Hi,

Roland Weber schrieb:

> Hi Angie,
>
> happy hacking :-)
>
> As I understand it, you are currently working from
> Luciano's Tuscany-based codebase, hence the ? arrow.
> Unless you have way too much time on your hands, I
> would stick with that architecture until the layout
> of the repository is stabilized.
> Regarding the ? box, I also don't see a layer there.
> Sling is meant to access JCR directly, if I am not
> mistaken. Of course one should have a few helper
> interfaces or classes that define the repository
> layout, but these are utilities and not an access
> layer that separates the front-end from the repository.

Yes, Sling accesses the repository directly and maps it into its own
abstraction called the Resource tree. Each Resource retrieved from the
Resource tree by means of the so-called ResourceResolver can be adapted
to other objects.

For example if a Resource is backed by a JCR node, you can adapt it to
the Node interface and get the backing node. If you employ Jackrabbit
Object Content Mapping (OCM) you may also adapt to the object classes
mapped by the content. This gives you seemless access to the repository
data as raw JCR items or as mapped business objects.

Hope this helps.

Regards
Felix

>
> Maybe you want to put a small "access control" box
> into the JCR box?
>
> cheers,
> Roland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

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

Re: architecture questions

2008-08-26T09:06:41Z

Hi Angie,

happy hacking :-)

As I understand it, you are currently working from
Luciano's Tuscany-based codebase, hence the ? arrow.
Unless you have way too much time on your hands, I
would stick with that architecture until the layout
of the repository is stabilized.
Regarding the ? box, I also don't see a layer there.
Sling is meant to access JCR directly, if I am not
mistaken. Of course one should have a few helper
interfaces or classes that define the repository
layout, but these are utilities and not an access
layer that separates the front-end from the repository.

Maybe you want to put a small "access control" box
into the JCR box?

cheers,
Roland

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

architecture questions

2008-08-25T06:10:32Z

As much fun as setting up resources can be, I was hoping to get my
hands a bit dirty in the next few days. The thought occurred to me
that we have a lot of functionality that we would like to put into
the gallery. As I was thinking about this, I feel like I might be
missing a piece, or else I just need coffee.

There are 2 jpg files at http://www.nechtan.org/caitrin/ The first
is an ultra simple architecture diagram. The second is just a list
right now of the JCR schema. On the architecture diagram there is a
question mark at the one arrow. This arrow is currently the way we
are viewing the repository. Should the arrow stay? The second
question is between the JCR and the interfaces. It doesn't seem to
me like there is anything to put there which is seeming wrong. I
can't explain why I think it is wrong though which leads me to
believe it might be right. It also might be fun and interesting,
although I don't know if it would work and I haven't read nearly
enough yet....would it be possible to read/write xml files from the
sling interface and have tuscany utilize those files? "Why would you
do that?" one might ask. Answer: To take advantage of the different
protocols that WS can run over. Basically, you would be making a
RESTful interface an active interface for the applications it was needed for.

The files for the drawings is also available on the page as an
OpenDocument Drawing so that others can update it as needed.

Angie

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

Re: PhotArk: getting started

2008-08-23T15:39:50Z

I've created the SVN repo, although commit messages are temporarily set to
go to cvs@... since we don't have our mailing lists yet. I also
have our Incubation Status page ready to go, but I'm not going to check it
in until the mailing lists are created, in case someone tries to subscribe.
;-) The JIRA project is also pending mailing list creation, but I don't
imagine we'll need that right away anyway.

--
Martin Cooper

On Sat, Aug 23, 2008 at 1:15 AM, Roland Weber <ossfwot@...> wrote:

> Luciano Resende wrote:
>
>> I have create necessary JIRA issue and sub-tasks to start the creation
>> process for the PhotArk podling
>>
>> https://issues.apache.org/jira/browse/INFRA-1713
>>
>
> Thanks! I have now sent the trigger mail to infra@, with cc:
> to private@. That mail must be sent by an IPMC member.
>
> http://www.apache.org/dev/reporting-issues.html#intro
>
>
> cheers,
> Roland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

Re: PhotArk: getting started

2008-08-23T01:11:55Z

Luciano Resende wrote:
> I have create necessary JIRA issue and sub-tasks to start the creation
> process for the PhotArk podling
>
> https://issues.apache.org/jira/browse/INFRA-1713

Thanks! I have now sent the trigger mail to infra@, with cc:
to private@. That mail must be sent by an IPMC member.

http://www.apache.org/dev/reporting-issues.html#intro

cheers,
Roland

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

Re: PhotArk: getting started

2008-08-21T16:58:46Z

I have create necessary JIRA issue and sub-tasks to start the creation
process for the PhotArk podling

https://issues.apache.org/jira/browse/INFRA-1713

On Thu, Aug 21, 2008 at 1:27 PM, Luciano Resende <luckbr1975@...> wrote:

> http://incubator.apache.org/incubation/Incubation_Policy.html#Creation+of+Podling
>
> But it looks like it should be started by the mentor. I'm going to ask
> general@ if I can start helping even tough not a mentor.
>
> On Thu, Aug 21, 2008 at 4:17 AM, Angela Cymbalak <a.cymbalak@...> wrote:
>> Is the documentation for getting the podling started publicly available? I
>> can take a look at it. I can also help moderate the mailing lists.
>>
>> Angie
>>
>> At 01:58 PM 8/19/2008, Roland Weber wrote:
>>>
>>> Hi folks,
>>>
>>> we'll need a few volunteers to moderate the
>>> PhotArk mailing lists. I can do it, but I only
>>> boot my machine two or three times a week. It
>>> would be preferable to have moderators that
>>> are more frequently online.
>>>
>>> When requesting mailing lists from infra, we
>>> should ask them to merge this year's archive
>>> of mails on projects@ into photark-dev@.
>>>
>>> I can look into the documentation about
>>> getting a podling up and running this
>>> week-end. If anybody wants to act sooner,
>>> please do so. Mentoring is quite new to me :-)
>>>
>>> cheers,
>>> Roland
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: projects-unsubscribe@...
>>> For additional commands, e-mail: projects-help@...
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: projects-unsubscribe@...
>> For additional commands, e-mail: projects-help@...
>>
>>
>
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>

Re: PhotArk Podling Creation

2008-08-21T13:40:30Z

Hi Luciano,

On Aug 21, 2008, at 1:32 PM, Luciano Resende wrote:

> The podling creation guide [1] mentions that it's creation should be
> initiated by the mentor.
> Is there any issue on having other podling members (such myself)
> helping on getting the project created ?

Anyone with karma can help set up the podling. The reason it's
documented as being initiated by a mentor is to make sure that
"someone" is responsible.

But as long as you keep folks in the loop, go for it. One really good
way is to start with the mail lists and then use the lists for
communication while everything else is getting set up.

Craig

>
>
> [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Creation+of+Podling
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@...
P.S. A good JDO? O, Gasp!

smime.p7s (3K) Download Attachment

PhotArk Podling Creation

2008-08-21T13:32:20Z

The podling creation guide [1] mentions that it's creation should be
initiated by the mentor.
Is there any issue on having other podling members (such myself)
helping on getting the project created ?

[1] http://incubator.apache.org/incubation/Incubation_Policy.html#Creation+of+Podling

--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

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

Re: PhotArk: getting started

2008-08-21T13:27:51Z

http://incubator.apache.org/incubation/Incubation_Policy.html#Creation+of+Podling

But it looks like it should be started by the mentor. I'm going to ask
general@ if I can start helping even tough not a mentor.

On Thu, Aug 21, 2008 at 4:17 AM, Angela Cymbalak <a.cymbalak@...> wrote:

> Is the documentation for getting the podling started publicly available? I
> can take a look at it. I can also help moderate the mailing lists.
>
> Angie
>
> At 01:58 PM 8/19/2008, Roland Weber wrote:
>>
>> Hi folks,
>>
>> we'll need a few volunteers to moderate the
>> PhotArk mailing lists. I can do it, but I only
>> boot my machine two or three times a week. It
>> would be preferable to have moderators that
>> are more frequently online.
>>
>> When requesting mailing lists from infra, we
>> should ask them to merge this year's archive
>> of mails on projects@ into photark-dev@.
>>
>> I can look into the documentation about
>> getting a podling up and running this
>> week-end. If anybody wants to act sooner,
>> please do so. Mentoring is quite new to me :-)
>>
>> cheers,
>> Roland
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: projects-unsubscribe@...
>> For additional commands, e-mail: projects-help@...
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

Re: PhotArk: getting started

2008-08-21T04:17:31Z

Is the documentation for getting the podling started publicly
available? I can take a look at it. I can also help moderate the
mailing lists.

Angie

At 01:58 PM 8/19/2008, Roland Weber wrote:

>Hi folks,
>
>we'll need a few volunteers to moderate the
>PhotArk mailing lists. I can do it, but I only
>boot my machine two or three times a week. It
>would be preferable to have moderators that
>are more frequently online.
>
>When requesting mailing lists from infra, we
>should ask them to merge this year's archive
>of mails on projects@ into photark-dev@.
>
>I can look into the documentation about
>getting a podling up and running this
>week-end. If anybody wants to act sooner,
>please do so. Mentoring is quite new to me :-)
>
>cheers,
> Roland
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: projects-unsubscribe@...
>For additional commands, e-mail: projects-help@...
>

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

PhotArk: getting started

2008-08-19T10:55:08Z

Hi folks,

we'll need a few volunteers to moderate the
PhotArk mailing lists. I can do it, but I only
boot my machine two or three times a week. It
would be preferable to have moderators that
are more frequently online.

When requesting mailing lists from infra, we
should ask them to merge this year's archive
of mails on projects@ into photark-dev@.

I can look into the documentation about
getting a podling up and running this
week-end. If anybody wants to act sooner,
please do so. Mentoring is quite new to me :-)

cheers,
Roland

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

name change

2008-08-14T15:56:56Z

It seems that PhotArk has not garnered any negative response. It
appears that we have a new name for the project and the vote can be tallied.

Angie

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

Re: looking for a new name

2008-08-12T06:46:10Z

On Mon, Aug 11, 2008 at 10:04 PM, Noel J. Bergman <noel@...> wrote:

> PicaGalley or ...
>
> > MemoPics
> > Imagery
> > Image Barn
> > Image Stable (searching for "image stable software" sucks)
> > PhotoGarten (photogarten.de is not about software)
>
> Photo Corral, but that's also taken.
>
> PhotoZon
>
> PhotArk -- I kinda like this one. A bit of a play on archive / Ark.
>
> I also liked ArkLive, but someone may have that -- not sure.
>
> But I'm also satisfied to stick with PicaGalley, if that's what folks want.
> I just don't believe that there is a collision with Picassa.

I agree - I just don't see the collision. And the way things are going, I'm
beginning to despair that we'll come up with one name that we can settle on
versus half a dozen names each but none we can agree upon. ;-p

--
Martin Cooper

>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

Re: looking for a new name

2008-08-12T05:41:33Z

On Tue, Aug 12, 2008 at 7:58 AM, Angela Cymbalak <a.cymbalak@...> wrote:
> Coming up with untaken names is insane these days. I am starting to realize
> why the projects all get the names that they get.
>
> I am liking PhotArk the more I consider it.
>
> A Google search turns up three references, two of them just being archives
> of photos. None of the references have anything to do with software.
>
> Any dissenters?

Not really, just another thought. I'm not sure why there's a push for
the name to imply what the software does - some of the most successful
[ASF] software doesn't (e.g. Tomcat, Cocoon).

Anyway, I didn't see a take on a photographer's portfolio suggested... so...

- folio(s)
- pholio(s)

--tim

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

Re: looking for a new name

2008-08-12T04:58:34Z

Coming up with untaken names is insane these days. I am starting to
realize why the projects all get the names that they get.

I am liking PhotArk the more I consider it.

A Google search turns up three references, two of them just being
archives of photos. None of the references have anything to do with software.

Any dissenters?

Angie

At 01:36 AM 8/12/2008, Luciano Resende wrote:

>I can't really comment on the infringing/not infringing case for
>PicaGalley, but, as Noel said, I would also be OK if we continue with
>PicaGalley if there is somewhat consensus on it.
>
>As for new names, oh man, I have really thought, but couldn't really
>get something new, that catch the attention, and stick to your mind...
>and it's not take yet :)
>
>On Mon, Aug 11, 2008 at 10:04 PM, Noel J. Bergman <noel@...> wrote:
> > PicaGalley or ...
> >
> >> MemoPics
> >> Imagery
> >> Image Barn
> >> Image Stable (searching for "image stable software" sucks)
> >> PhotoGarten (photogarten.de is not about software)
> >
> > Photo Corral, but that's also taken.
> >
> > PhotoZon
> >
> > PhotArk -- I kinda like this one. A bit of a play on archive / Ark.
> >
> > I also liked ArkLive, but someone may have that -- not sure.
> >
> > But I'm also satisfied to stick with PicaGalley, if that's what folks want.
> > I just don't believe that there is a collision with Picassa.
> >
> > --- Noel
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: projects-unsubscribe@...
> > For additional commands, e-mail: projects-help@...
> >
> >
>
>
>
>--
>Luciano Resende
>Apache Tuscany Committer
>http://people.apache.org/~lresende
>http://lresende.blogspot.com/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: projects-unsubscribe@...
>For additional commands, e-mail: projects-help@...

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

Re: looking for a new name

2008-08-11T22:36:00Z

I can't really comment on the infringing/not infringing case for
PicaGalley, but, as Noel said, I would also be OK if we continue with
PicaGalley if there is somewhat consensus on it.

As for new names, oh man, I have really thought, but couldn't really
get something new, that catch the attention, and stick to your mind...
and it's not take yet :)

On Mon, Aug 11, 2008 at 10:04 PM, Noel J. Bergman <noel@...> wrote:

> PicaGalley or ...
>
>> MemoPics
>> Imagery
>> Image Barn
>> Image Stable (searching for "image stable software" sucks)
>> PhotoGarten (photogarten.de is not about software)
>
> Photo Corral, but that's also taken.
>
> PhotoZon
>
> PhotArk -- I kinda like this one. A bit of a play on archive / Ark.
>
> I also liked ArkLive, but someone may have that -- not sure.
>
> But I'm also satisfied to stick with PicaGalley, if that's what folks want.
> I just don't believe that there is a collision with Picassa.
>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

RE: looking for a new name

2008-08-11T22:04:19Z

PicaGalley or ...

> MemoPics
> Imagery
> Image Barn
> Image Stable (searching for "image stable software" sucks)
> PhotoGarten (photogarten.de is not about software)

Photo Corral, but that's also taken.

PhotoZon

PhotArk -- I kinda like this one. A bit of a play on archive / Ark.

I also liked ArkLive, but someone may have that -- not sure.

But I'm also satisfied to stick with PicaGalley, if that's what folks want.
I just don't believe that there is a collision with Picassa.

--- Noel

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

Re: looking for a new name

2008-08-11T11:37:27Z

Angela Cymbalak wrote:
> It isn't just me, its everyone! It isn't *my* project.

Fair enough. There's you and Luciano on the committers list.
Noel also stated his preference. I'm making suggestions,
but I won't make a decision on the name myself.

> I am good with
> sticking with PicaGalley and for good measure I can send an email to
> Google asking their thoughts. I just have to find the right people to
> talk to there.

I doubt there are the right people for this kind of question.
A trademark lawyer might tell you that you are infringing,
or that (s)he believes you are infringing, or that you might
be infringing, but don't expect a response that you're not
infringing. Unless it's obvious, but then why would you ask?

> We have made a good faith effort but have found no
> reasonable alternative. If those who have concerns would like to help
> find a new name we can reopen the discussion, but for now I would say we
> are in the clear.

OK. I'll give it two or three more days, maybe Luciano
wants to chime in once more. Or somebody else has
another idea. If not, I'll tally the vote later this week.

cheers,
Roland

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

Re: looking for a new name

2008-08-11T10:32:24Z

It isn't just me, its everyone! It isn't *my* project. I am good
with sticking with PicaGalley and for good measure I can send an
email to Google asking their thoughts. I just have to find the right
people to talk to there.

I agree that several people have raised concerns over the name;
however, just ask many people have mentioned that they don't see the
similarity. As well, even more people have not spoken up over the
name concern at all. As well, almost every good alternative we have
come up with has had a conflict. We have made a good faith effort
but have found no reasonable alternative. If those who have concerns
would like to help find a new name we can reopen the discussion, but
for now I would say we are in the clear.

Angie

At 01:03 PM 8/11/2008, Roland Weber wrote:

>Noel J. Bergman wrote:
>>>I would associate "Blur" rather with a painting program.
>>Nor would I call a gallery/archive/storage project "blur".
>
>Good point :-) Rather,...
>
>Reminiscence (but http://reminiscence.en.softonic.com/mac)
>ReminiScene (looks like poor spelling rather than a pun)
>MemoPics
>Imaginary (but http://www.imagescape.com/library/software/)
>Imagery
>Photo Barn (already in use http://www.photobarn.com.au/)
>Picture Barn (still too close to Photo Barn)
>Image Barn
>Image Stable (searching for "image stable software" sucks)
>PhotoGarten (photogarten.de is not about software)
>...[many more already in use]
>
>
>I give up. Angie, if you want to stick with PicaGalley,
>let's just go with that and see how far we get.
>
>cheers,
> Roland
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: projects-unsubscribe@...
>For additional commands, e-mail: projects-help@...
>

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

Re: looking for a new name

2008-08-11T10:00:12Z

Noel J. Bergman wrote:
>> I would associate "Blur" rather with a painting program.
>
> Nor would I call a gallery/archive/storage project "blur".

Good point :-) Rather,...

Reminiscence (but http://reminiscence.en.softonic.com/mac)
ReminiScene (looks like poor spelling rather than a pun)
MemoPics
Imaginary (but http://www.imagescape.com/library/software/)
Imagery
Photo Barn (already in use http://www.photobarn.com.au/)
Picture Barn (still too close to Photo Barn)
Image Barn
Image Stable (searching for "image stable software" sucks)
PhotoGarten (photogarten.de is not about software)
...[many more already in use]

I give up. Angie, if you want to stick with PicaGalley,
let's just go with that and see how far we get.

cheers,
Roland

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

RE: the Apache way to do things

2008-08-10T00:14:04Z

Angela Cymbalak wrote:

> We acknowledge that there is some concern over the name
> PicaGalley.

I don't. :-) I think that it is a totally unwarranted concern.

> Please vote you opinion below. Everyone's vote is
> binding for this vote.

[X] +1 Apache PicaGalley

--- Noel

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

RE: looking for a new name

2008-08-10T00:14:03Z

> I would associate "Blur" rather with a painting program.

Nor would I call a gallery/archive/storage project "blur".

--- Noel

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

Re: looking for a new name

2008-08-08T08:15:31Z

Angela Cymbalak wrote:
> There was a company named Blur Software but they appear to be going out
> of business (www.blursoftware.com). I think that Apache Blur would
> work...other thoughts?

I would associate "Blur" rather with a painting program.
To get an association with "multiple pictures", I thought
about "Collage", but searching for the combination with
software brings up plenty of photo related hits.

My most recent idea, Pinacotheca, is not so original
either... though there's not even a description
of what the project is supposed to offer:
http://developer.berlios.de/projects/pinacotheca/
The project was registered 2007-May-14 and has shown
exactly no activity in over a year. No files, no posts
in the forum, not even a project description. So we
could claim the name as effectively unused. It wouldn't
hurt to try and contact the two people registered as
developers there if you like the name.

cheers,
Roland

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

Re: the Apache way to do things

2008-08-08T08:01:16Z

Hi Angie,

> I have two "Apache way" questions:
>
> 1. It appears that within the community no one objects to Apache Blur.
> Can I put out a [vote] thread on general@ to the effect of:

That is a common misunderstanding, and some projects are or
have been dreaded for their vote-happiness. This is how I
formulated my views when drafting bylaws for a project earlier
this year:

<quote>
Community decisions are consensus driven. The preferred way
to establish consensus is through discussion on the public
mailing lists. To gather additional input from community members,
polls can be run on the same or other mailing lists. Voting on
community decisions should be restricted to cases where it is
necessary or desirable to formally record the consensus
</quote>

The important thing is to find a _consensus_, not to pass
a vote. If there is a consensus, there are only few things
that need a vote. If there is no consensus, passing a vote
doesn't help much...
You pass a vote on a controversial project name now and enter
incubation. On graduation, somebody else will raise the
naming question again when the vote for the TLP proposal
is on. Even if you pass that vote, the TLP proposal is
sent to the board, where yet other people will raise the
question of the project name. And the board certainly won't
care about a vote that passed a year or two earlier. They
will look for a consensus at the time of graduation.

So no, don't even think about calling a vote about the
project name. Send a simple non-vote mail, asking how
people feel about the alternative name. Make sure to
mention that there is a company that has used that name,
and that the respective domain is still online. Personally,
I believe that is a knockout criteria.

(more name suggestions coming up :-)

cheers,
Roland

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

Re: only half working

2008-08-08T00:21:32Z

I have managed to get the gallery working (at least in debug mode)
with your patch...
There was some dependencies issues and couple other small changes that
I made...

On Wed, Aug 6, 2008 at 3:32 AM, Angela Cymbalak <a.cymbalak@...> wrote:

> Not a problem. Should it be part of the Tuscany jira?
>
> Angie
>
> At 10:03 PM 8/5/2008, you wrote:
>>
>> Would you mind providing the code attached in a jira to make sure
>> there is no ip issues when I use these changes in the current Tuscany
>> app.
>>
>> Thanks
>> Luciano
>>
>> On 8/5/08, Angela Cymbalak <a.cymbalak@...> wrote:
>> > OK, I did more reading to confirm what I thought was going on. I put
>> > the new code at http://www.nechtandesign.com/PicaGalley.zip
>> >
>> > It still isn't running correctly. It just appears that the method
>> > marked with @Init is never getting called but that just doesn't make
>> > sense. Is this something that needs addressed in the composite file?
>> >
>> > Angie
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: projects-unsubscribe@...
>> > For additional commands, e-mail: projects-help@...
>> >
>> >
>>
>>
>> --
>> Luciano Resende
>> Apache Tuscany Committer
>> http://people.apache.org/~lresende
>> http://lresende.blogspot.com/
>
>
>

Re: the Apache way to do things

2008-08-07T12:15:17Z

>You can create a new Jackrabbit jira, and link them together...
>And, BTW, sorry for the delay... I'll see if I can get to your patch today.

I will figure out how to link them then after I work on it a little
more. I finished the configuration to be able to debug
Jackrabbit. Don't worry about the delay. I felt like I was pawning
off my problem on you which I'm not trying to do. Jackrabbit appears
to be throwing a not normal (i.e. catchable by a traditional catch
statement) exception that isn't stopping the program but is causing
it to not continue on in the method. The next take is to figure out
where in the constructor this is happening. Hopefully I'll be able
to tell you in an hour or so. This has been fun to try to track
down, in that really weird beat your head against a wall kind of way!

Angie

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

Re: the Apache way to do things

2008-08-07T11:56:42Z

On Thu, Aug 7, 2008 at 11:47 AM, Angela Cymbalak <a.cymbalak@...> wrote:

> I have two "Apache way" questions:
>
> 1. It appears that within the community no one objects to Apache Blur. Can
> I put out a [vote] thread on general@ to the effect of:
>
> We acknowledge that there is some concern over the name PicaGalley. After
> discussions we have decided on the alternative name Apache Blur. Please
> vote you opinion below. Everyone's vote is binding for this vote.
>
> [ ] +1 Apache PicaGalley
> [ ] +1 Apache Blur
> [ ] 0 Don't care
> [ ] -1 I don't like either name
>
> The vote is different from all that I have seen due to having two choices
> and I think that anyone on the general list should have a say in it.
>
> 2. Right now I have opened a bug within JIRA for Tuscany because of an
> issue combining Tuscany and Jackrabbit. I think that I have narrowed down
> that the issue is actually within Jackrabbit.
> 2a. Does JIRA allow you to select 2 distinct products when opening a
> problem? I didn't want to try it and then upset someone because of question
> 2b.
> 2b. If yes to 2a, is it akin to cross posting on the mail lists (very bad
> idea) to select both Jackrabbit and Tuscany as the product in question? At
> the moment I am working the issue but I want to keep JIRA updated correctly.

You can create a new Jackrabbit jira, and link them together...
And, BTW, sorry for the delay... I'll see if I can get to your patch today.

>
> Thanks for the Apache lesson. :-)
>
> Angie
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>

the Apache way to do things

2008-08-07T11:47:14Z

I have two "Apache way" questions:

1. It appears that within the community no one objects to Apache
Blur. Can I put out a [vote] thread on general@ to the effect of:

We acknowledge that there is some concern over the name
PicaGalley. After discussions we have decided on the alternative
name Apache Blur. Please vote you opinion below. Everyone's vote is
binding for this vote.

[ ] +1 Apache PicaGalley
[ ] +1 Apache Blur
[ ] 0 Don't care
[ ] -1 I don't like either name

The vote is different from all that I have seen due to having two
choices and I think that anyone on the general list should have a say in it.

2. Right now I have opened a bug within JIRA for Tuscany because of
an issue combining Tuscany and Jackrabbit. I think that I have
narrowed down that the issue is actually within Jackrabbit.
2a. Does JIRA allow you to select 2 distinct products when opening a
problem? I didn't want to try it and then upset someone because of
question 2b.
2b. If yes to 2a, is it akin to cross posting on the mail lists
(very bad idea) to select both Jackrabbit and Tuscany as the product
in question? At the moment I am working the issue but I want to keep
JIRA updated correctly.

Thanks for the Apache lesson. :-)

Angie

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

Re: looking for a new name

2008-08-06T12:35:08Z

Apache Blur sounds interesting.

As for the Shutter suggestion, that would most likely have the same
naming conflict issue with Shutter Fly.

[1] http://www.shutterfly.com

On Wed, Aug 6, 2008 at 12:17 PM, Angela Cymbalak <a.cymbalak@...> wrote:

> There was a company named Blur Software but they appear to be going out of
> business (www.blursoftware.com). I think that Apache Blur would
> work...other thoughts?
>
> Angie
>
> At 03:07 PM 8/6/2008, Martin Cooper wrote:
>
>
>> On Wed, Aug 6, 2008 at 11:47 AM, Angela Cymbalak
>> <<mailto:a.cymbalak@...>a.cymbalak@...> wrote:
>> I have to go with something Noel mentioned when we first started
>> discussing the name. He said (paraphrase) that it is much easier to settle
>> on a name before setting up all the resources (maillists, jira, etc.)
>> Therefore, I think that we should address the concerns now before the
>> infrastructure for the project is set up.
>> I have no problem with 2A but I do fear that Google may not give the
>> statement. I have a sneaking suspicion that companies only decide that a
>> name is "too close" when the new product starts getting big enough to
>> encroach on "their turf". It may be easier to just avoid the question
>> altogether.
>> There is also option 3, which I think would also be in the Apache way.
>> That would be, call a vote on it and see who thinks the name is too close.
>> But, that could just drag things out.
>> All that being said, I like either Snapshot or Shutter. However, Shutter
>> is taken[1]. SnapShot is also taken[2]. I did appreciate the
>> alliterations on general@ with that one, btw. Neither of these pieces of
>> software is close to what we are doing so does that matter?
>> For what it is worth, Shoebox is the name of a software company[3].
>> Can we do a play on the Louvre? Can we steal Click from that project?
>> My list:
>> Lewva
>> PixPlace
>> Blur
>> PixBlur
>> I'm liking Lewva and Blur myself. I do also like SchuhKarton, the only
>> drawback being the length.
>>
>>
>> Lewva sounds too much like "loofah" to me. I like Blur, though.
>>
>> --
>> Martin Cooper
>>
>>
>>
>> Angie
>>
>> [1]<http://www.cygnet-infotech.com/Screenshot/Shutter-Manufacturing-System-software.htm>http://www.cygnet-infotech.com/Screenshot/Shutter-Manufacturing-System-software.htm
>>
>> [2]<http://www.allworldsoft.com/software/10-171-web-page-snapshot.htm>http://www.allworldsoft.com/software/10-171-web-page-snapshot.htm
>>
>> [3]<http://www.download.com/Shoebox-Software/3260-20_4-6283782.html>http://www.download.com/Shoebox-Software/3260-20_4-6283782.html
>>
>> At 01:54 PM 8/6/2008, Martin Cooper wrote:
>> On Wed, Aug 6, 2008 at 7:46 AM, Roland Weber
>> <<mailto:ossfwot@...>ossfwot@...> wrote:
>> > Hi Angie,
>> >
>> > Should this go to legal discuss to see what the lawyers say?
>> >>
>> >
>> > The lawyers rarely post on legal-discuss. The list is
>> > mostly populated by regular non-lawyer people with an
>> > interest in the legal minefield, like myself. It's not
>> > a place to discuss (non)similarity of names, and I'm
>> > pretty sure that no lawyer would enter the discussion.
>> >
>> > It seems there are a few who are unsure about the name but others who
>> >> don't see a similarity. Plus, as Craig mentioned, Pica is a very
>> >> normal
>> >> word to use in the line of photo galleries.
>> >>
>> >
>> > Well, the options I see are:
>> >
>> > A. enter incubation as PicaGalley and...
>> > A1. try to keep the name and hope that nobody objects
>> > on graduation
>> > A2. seek a statement from Google that they don't
>> > object to our usage of the name
>> > A3. change the name later before graduation
>> > or
>> > B. settle on a new name that doesn't raise any concerns
>> >
>> > If you're _really_ attached to PicaGalley, you could
>> > go for A2. But I doubt that you'll get that kind of
>> > statement from Google. A1 is a poor strategy, and
>> > graduation might even be delayed not because of the
>> > name, but because we didn't address the concerns, at
>> > the time when they were raised, in "The Apache Way".
>> > That is by seeking the broadest possible consensus.
>> >
>> > It's not like we have an existing OSS project with
>> > many users that would have to learn a new name.
>> > We're starting from scratch, and the preliminary
>> > name has only been used for three weeks internally.
>> > (as "internal" as discussions on public mailing
>> > lists can be :-) So my recommendation clearly is B.
>> >
>> >
>> > Additional suggestions on general@ by Martijn were
>> > "Snapshot" and "Shutter". Unfortunately, I don't
>> > know a catchy translation for the german word
>> > "Schuhkarton" (shoe box), which in reality is a
>> > much more common place than an album for keeping
>> > physical photographies :-)
>>
>> Shoebox would be a fine name. :-)
>> --
>> Martin Cooper
>>
>>
>> >
>> > cheers,
>> > Roland
>> >
>> >
>> > Pigalle
>> >>>
>> >>>> Phos Librarius
>> >>>> LibraLux
>> >>>> PhosBiblioteka
>> >>>> BiblioPic
>> >>>> PicAndMix
>> >>>> PhoGal
>> >>>> PhoGa
>> >>>> Foga
>> >>>> SnapLib
>> >>>> SnapStore
>> >>>> PicStore
>> >>>> SnapShow
>> >>>> PicShow
>> >>>> PicLib
>> >>>>
>> >>>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> > <mailto:projects-unsubscribe@...>projects-unsubscribe@...
>> > For additional commands, e-mail:
>> > <mailto:projects-help@...>projects-help@...
>> >
>> >
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> <mailto:projects-unsubscribe@...>projects-unsubscribe@...
>> For additional commands, e-mail:
>> <mailto:projects-help@...>projects-help@...
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: projects-unsubscribe@...
> For additional commands, e-mail: projects-help@...
>
>