Re: to brand or not to brand?

[Martijn Dashorst]

On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:

Mmm, it's still not completely clear. Is the phrase "However, the
Public Relations Committee MUST review any releases by affiliated
organizations or groups to ensure they comply with these branding
guidelines." referring to press release announcing the podling only,
or to all press releases? Since it seems it's not allowed to issue
press releases announcing the release, I'd think it's for press
releases that reference the podling. And that's what my article will
do, reference the podling.


I think the gist is in the term "Press release". I think a press
release is something other than an article. A press release is
something like "Foo is adopting Apache Ivy in its product line and
providing professional support for it." and send it across the wire,
i.e. an announcement.

This is of course something different than "This is how you manage
your Java project dependencies using Apache Ivy, currently undergoing
incubation at the Apache Incubator." which is published on
theserverside.com and/or infoq.


So I'll follow Niclas advice and submit the article to the PRC, it
doesn't hurt (well, I hope :-))


True, but it might wake up sleeping dogs :)

Martijn

--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Branding Guide clarification (was Re: to brand or not to brand?)

[Xavier Hanin]

On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:


On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> Mmm, it's still not completely clear. Is the phrase "However, the
> Public Relations Committee MUST review any releases by affiliated
> organizations or groups to ensure they comply with these branding
> guidelines." referring to press release announcing the podling only,
> or to all press releases? Since it seems it's not allowed to issue
> press releases announcing the release, I'd think it's for press
> releases that reference the podling. And that's what my article will
> do, reference the podling.

I think the gist is in the term "Press release". I think a press
release is something other than an article. A press release is
something like "Foo is adopting Apache Ivy in its product line and
providing professional support for it." and send it across the wire,
i.e. an announcement.

This is of course something different than "This is how you manage
your Java project dependencies using Apache Ivy, currently undergoing
incubation at the Apache Incubator." which is published on
theserverside.com and/or infoq.



It makes sense, indeed. But I think it would be nice to have something in
the branding guide more clearly understandable.

So, maybe I should ask the question to the PRC, and open a JIRA issue to put
their answers or some examples in the branding guide?

Xavier

Re: Branding Guide clarification (was Re: to brand or not to brand?)

[Martijn Dashorst]

On 5/23/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:

It makes sense, indeed. But I think it would be nice to have something in
the branding guide more clearly understandable.



So, maybe I should ask the question to the PRC, and open a JIRA issue to put
their answers or some examples in the branding guide?


It may be on purpose that the wording is vague and open for debate.
This way you get away with a lot, and when things go wrong, you get to
point and slap people on the wrists :)

Maybe a rewording might make us not so fluent in the English language
(and more specifically: the 'legal' English lingo) more confident and
knowledgable in these policies/rules/guidelines.

I think a JIRA with 'This needs more clarification' would suffice
(pointing at the document and this discussion). This way it won't get
lost in the ongoing discussions.

Martijn

--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (INCUBATOR-65) Branding Guide clarification

[Xavier Hanin (JIRA)]

Branding Guide clarification


 Key: INCUBATOR-65
 URL: https://issues.apache.org/jira/browse/INCUBATOR-65
 Project: Incubator
  Issue Type: Improvement
  Components: site
Reporter: Xavier Hanin


As dicussed on the mailing list recently [1] and [2], I think the branding 
guide would benefit from some clarification and examples. The second link point 
to the message with what need some clarification IMO.

Here is a copy of the message:
On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> > Mmm, it's still not completely clear. Is the phrase "However, the
> > Public Relations Committee MUST review any releases by affiliated
> > organizations or groups to ensure they comply with these branding
> > guidelines." referring to press release announcing the podling only,
> > or to all press releases? Since it seems it's not allowed to issue
> > press releases announcing the release, I'd think it's for press
> > releases that reference the podling. And that's what my article will
> > do, reference the podling.
>
> I think the gist is in the term "Press release". I think a press
> release is something other than an article. A press release is
> something like "Foo is adopting Apache Ivy in its product line and
> providing professional support for it." and send it across the wire,
> i.e. an announcement.
>
> This is of course something different than "This is how you manage
> your Java project dependencies using Apache Ivy, currently undergoing
> incubation at the Apache Incubator." which is published on
> theserverside.com and/or infoq. 

It makes sense, indeed. But I think it would be nice to have something in
the branding guide more clearly understandable.

[1] http://www.nabble.com/to-brand-or-not-to-brand--tf3795172.html
[2] 
http://www.nabble.com/Branding-Guide-clarification-%28was-Re%3A-to-brand-or-not-to-brand-%29-tf3802984.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Branding Guide clarification (was Re: to brand or not to brand?)

[Xavier Hanin]

On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:


On 5/23/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> It makes sense, indeed. But I think it would be nice to have something
in
> the branding guide more clearly understandable.

> So, maybe I should ask the question to the PRC, and open a JIRA issue to
put
> their answers or some examples in the branding guide?

It may be on purpose that the wording is vague and open for debate.
This way you get away with a lot, and when things go wrong, you get to
point and slap people on the wrists :)

Maybe a rewording might make us not so fluent in the English language
(and more specifically: the 'legal' English lingo) more confident and
knowledgable in these policies/rules/guidelines.

I think a JIRA with 'This needs more clarification' would suffice
(pointing at the document and this discussion). This way it won't get
lost in the ongoing discussions.



I've created a JIRA issue:
https://issues.apache.org/jira/browse/INCUBATOR-65

Thanks,

Xavier

Martijn


--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/

Re: [VOTE] second try Change "Mentor" to "Mentors" in Incubator Policy

[Craig L Russell]

On May 22, 2007, at 10:59 AM, Craig L Russell wrote:

I've updated this proposal to explicitly include the possibility of  
a single Mentor. Since this change affects Policy, another vote is  
needed.


Please review the changes in https://issues.apache.org/jira/browse/ 
INCUBATOR-60 and vote to accept them. The JIRA issue has .html  
files to review in addition to the patch.


[X ] +1 Accept the changes
[ ] -1 Don't accept the changes because...

This vote will run until Friday May 25.

Thanks,

Craig




smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] second try Change "Mentor" to "Mentors" in Incubator Policy

[Martijn Dashorst]

[X ] +1 Accept the changes


--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Apache ODE 1.0

[Paul Fremantle]

+1 from me!

Paul

On 5/22/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

+1 from me? (or did i vote before :)

-- dims

On 5/21/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> All the listed issues have been solved for a few days now. Robert mentioned
> being offline this week so could somebody else pick this up? We still need 2
> IPMC votes for this release.
>
> Thanks!
> Matthieu
>
> On 5/17/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> >
> > I've posted a new RC addressing all the issues you've mentioned. The only
> > gotcha is with the SQL files, these come from Quartz (Open Symphony project,
> > Apache 2.0 license). So for these I've just added a short note pointing to
> > the NOTICE, which mentions the license and copyright. Hope this is enough.
> > Otherwise, all missing headers have been added.
> >
> > The new release, 1.0-RC4, can be found here:
> >
> > - The WAR-based distribution
> > 
http://people.apache.org/~mriou/ode-1.0-RC4/org/apache/ode/apache-ode-war/1.0-RC4-incubating/
> >
> > 

> >
> > - The JBI-based distribution
> > 
http://people.apache.org/~mriou/ode-1.0-RC4/org/apache/ode/apache-ode-jbi/1.0-RC4-incubating/
> >
> > 

> >
> > - The source distribution
> > 
http://people.apache.org/~mriou/ode-1.0-RC4/org/apache/ode/apache-ode-sources/1.0-RC4-incubating/
> >
> > 

> >
> > Thanks a lot for your time checking our release!
> >
> > Matthieu
> >
> >
> > On 5/17/07, robert burrell donkin < [EMAIL PROTECTED]> wrote:
> > >
> > > On 5/15/07, Matthieu Riou < [EMAIL PROTECTED]> wrote:
> > > > The ODE community held a vote for its first incubator release. See [1]
> > > for
> > > > the tally of 6 +1s (including one mentor vote) and no 0 or -1s. We're
> > > now
> > > > asking for a vote by the incubator PMC to authorize the publication of
> > > our
> > > > 1.0 release.
> > > >
> > > > The release consists of 3 different artifacts:
> > > >
> > > > - A WAR-based distribution [2]
> > > > - A JBI-based distribution [3]
> > > > - A source distribution [4]
> > > >
> > > > Please cast your votes:
> > > >
> > > > [ ] +1 release is approved
> > > > [ ] -1 veto the release (provide specific comments)
> > >
> > > not sure ATM
> > >
> > > BTW i'm offline next week so hopefully other folks will be able to pick
> > > stuff up
> > >
> > > Issues
> > > =
> > >
> > > RAT:
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/assemble_jdoc.rb
> > >
> > > looks to be a creative work in a format supporting comments. if so
> > > then it should have the standard header
> > >
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/bpel-api/src/main/java/org/apache/ode/bpel/iapi/TwoWayUnreliable.usd
> > > again looks to be in format capable of supporting comments. is it
> > > generated? (if not, then it should have a header)
> > >
> > > ditto
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/bpel-api/src/main/java/org/apache/ode/bpel/iapi/TwoWayReliable.usd
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/bpel-api/src/main/java/org/apache/ode/bpel/iapi/TwoWayWithTransactionPropagation.usd
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/bpel-api/src/main/java/org/apache/ode/bpel/iapi/TwoWayIdempotent.usd
> > >
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/bpel-test/src/test/resources/bpel/2.0/TestXslTransform/HelloXslWorld.xsl
> > >   looks borderline creative to me and looks to be a format capable of
> > > supporting comments. if so (and it isn't generated) then it should
> > > probably have a header
> > >
> > > the follow also worry me (for similar reasons):
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_derby.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_firebird.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_hsql.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_mysql_innodb.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_oracle.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_1.0-RC3-INCUBATING/dao-hibernate-db/src/main/sql/tables_postgres.sql
> > >
> > > 
http://svn.apache.org/repos/asf/incubator/ode/tags/APACHE_ODE_

[STATUS] (incubator) Wed May 23 23:56:47 2007

[Rodent of Unusual Size]

APACHE INCUBATOR PROJECT STATUS:  -*-indented-text-*-
Last modified at [$Date: 2006-02-05 04:40:19 -0500 (Sun, 05 Feb 2006) $]

Web site:  http://Incubator.Apache.Org/
Wiki page: http://wiki.apache.org/incubator/

[note: the Web site is the 'official' documentation; the wiki pages
 are for collaborative development, including stuff destined for the
 Web site.]

Pending Issues
==

o We need to be very very clear about what it takes to be accepted
  into the incubator.  It should be a very low bar to leap, possibly
  not much more than 'no problematic code' and the existence of a
  healthy community (we don't want to become a dumping ground).

o We need to be very very clear about what it takes for a podling
  to graduate from the incubator.  The basic requirements obviously
  include: has a home, either as part of another ASF project or as
  a new top-level project of its own; needs to be a credit to the
  ASF and function well in the ASF framework; ...

See also:

  https://issues.apache.org/jira/browse/INCUBATOR

Resolved Issues
===

o The policy documentation does not need ratification of changes
  if there seems consensus. Accordingly, the draft status of these
  documents can be removed and we will use the lazy "commit first,
  discuss later" mode common across the ASF for documentation
  (http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]&by=thread&from=517190)

o Coming up with a set of bylaws for the project
  (http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]&by=thread&from=517190)

o All projects under incubation must maintain a status Web page that
  contains information the PMC needs about the project.
  (http://incubator.apache.org/guides/website.html)

o Projects under incubation should display appropriate "disclaimers"
  so that it is clear that they are, indeed, under incubation
  (http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]&by=thread&from=504543)

o Clearly and authoritatively document how to edit, generate,
  and update the Web site (three separate functions)
  (http://incubator.apache.org/guides/website.html).

The Incubation Process
==

TODO: this does not belong in the STATUS file and probably was integrated into
other documentation a while ago. That should be double-checked and then this
section should be removed.

This tries to list all the actions items that must be complete for a project
before it can graduate from the incubator. It is probably incomplete.

Identify the project to be incubated:

  -- Make sure that the requested project name does not already exist
 and check www.nameprotect.com to be sure that the name is not
 already trademarked for an existing software product.

  -- If request from an existing Apache project to adopt an external
 package, then ask the Apache project for the cvs module and mail
 address names.

  -- If request from outside Apache to enter an existing Apache project,
 then post a message to that project for them to decide on acceptance.

  -- If request from anywhere to become a stand-alone PMC, then assess
 the fit with the ASF, and create the lists and modules under the
 incubator address/module names if accepted.

Interim responsibility:

  -- Who has been identified as the mentor for the incubation?

  -- Are they tracking progress on the "project status" Web page?

Copyright:

  -- Have the papers that transfer rights to the ASF been received?
 It is only necessary to transfer rights for the package, the
 core code, and any new code produced by the project.

  -- Have the files been updated to reflect the new ASF copyright?

Verify distribution rights:

  -- For all code included with the distribution that is not under the
 Apache license, do we have the right to combine with Apache-licensed
 code and redistribute?

  -- Is all source code distributed by the project covered by one or more
 of the following approved licenses:  Apache, BSD, Artistic, MIT/X,
 MIT/W3C, MPL 1.1, or something with essentially the same terms?

Establish a list of active committers:

  -- Are all active committers listed in the "project status" file?

  -- Do they have accounts on cvs.apache.org?

  -- Have they submitted a contributors agreement?

Infrastructure:

  -- CVS modules created and committers added to avail file?

  -- Mailing lists set up and archived?

  -- Problem tracking system (Bugzilla)?

  -- Has the project migrated to our infrastructure?

Collaborative Development:

  -- Have all of the active long-term volunteers been identified
 and acknowledged as committers on the project?

  -- Are there three or more independent committers?

 [The legal definition of independent is long and boring, but basically
  it means that there is no binding relationship between the individuals,
  s