You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by Les Hazlewood <lh...@apache.org> on 2009/01/01 20:33:54 UTC

Fast track out of incubation - exit criteria

It is now finally glaring clear to me the importance of getting out of
incubation.  I feel disheartened by the fact that the 5 originating
developers have no formal voting authority.  Obviously, the best way to
alleviate this is to ensure we get out of incubation and obtain voting
capability as soon as is possible.  Of course there are other benefits to
exiting the incubator (including retaining the great ASF community that has
been building with us), and we'll naturally achieve those as well.

Here is the current status file, which lists what is left to do to exit the
incubator:
http://svn.apache.org/viewvc/incubator/jsecurity/STATUS?view=markup

The "Copyrights & Licensing" section is probably completed - how do we
verify so we can check this off?

The "Distribution Rights' section is probably completed - how do we verify
so we can check this off?

I believe "Infastructure" section is complete.

I think most of the "Collaborative Development" criteria has been met.

Can the Mentors clarify exactly what they feel has been met and what is to
remain?  Once we get this list, we can check them off one by one to ensure
we can exit the incubator asap.

Thanks!

Les

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
We don't distribute the JSecurity site with a release (currently), nor
have we ever in the last 4 years.  Wouldn't it be ok to use the theme
for now if that is the case since we're not distributing any of it?

We had a similar discussion about the use of the google code project
Syntax Highlighter (http://code.google.com/p/syntaxhighlighter/),
which is LGPL.  Because we don't distribute the website, legal said it
was no problem for us to use it.

I'm CC'ing legal to see if they have any objections, as they might be
ok with LGPL but not with GPL - just checking to be sure.

Thanks,

Les

On Sun, Jan 11, 2009 at 2:35 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org> wrote:
>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>> I guess since the site is not really used, I can use it freely for a
>>>> few days while I get the template up and running?
>>>
>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>
>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>> API is, I fail to find any license for the theme). I'm not sure what
>> consequences re-using this theme would have for the JSecurity site at
>> Apache. For example, it's common to redistribute the site with a
>> release, I suspect that might be impossible.
>>
>> Anyone got a clue? Does anyone know what license really apply to the theme?
>
> Any takers? I would like to move forward with this but would like to
> have a clear understanding of if the template would be allowed to be
> used :-)
>
> /niklas
>

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
Thanks Emmanuel :)

On Sun, Jan 11, 2009 at 4:07 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> Les Hazlewood wrote:
>>
>> I personally prefer Directory's - the way it presents information
>> feels closer to the current JSecurity organization.  It has a very
>> clean appearance too.
>>
>> Emmanuel, what do you think - could we use that as a base and change
>> the colors and logo to match the current JSecurity site, and do
>> whatever other customization we would need? Would the Directory team
>> be ok with that?
>>
>
> You do whatever you want ! The site has been designed with ASL 2.0 in mind,
> so it's not 'stealing' to use the Directory template, it's just sparing
> useful resources !
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: Fast track out of incubation - exit criteria

Posted by Emmanuel Lecharny <el...@gmail.com>.
Les Hazlewood wrote:
> I believe that Niklas' plan is to use confluence exporting - as soon
> as he could get the theme cleared.  But if we just start out with a
> Wicket-derived theme, that'd be the easiest I think...
>
> I'm just so thrilled that he has volunteered to help us out that I'd
> like to see _any_ solution at this point, Confluence-based or not :)
>   
we just have to redesign the template for JSecurity in the auto-export 
plugin. We are currently using the default template.

Here is the one we use for Directory (seems to be Velocity script):

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at
 
        http://www.apache.org/licenses/LICENSE-2.0
 
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
-->
##
#set ($images = "http://directory.apache.org/staticresources/images")
#set ($siteroot = "http://directory.apache.org")
#set ($pageContentHeaderEnabled = false)
##
#if ( $page.title.equals("Index") )
    #set ($title = "LDAP and Kerberos, entirely in Java")
#else
    #set ($title = $page.title)
#end
##
#macro (renderPage $title)
    #set($globalHelper = $action.getGlobalHelper())
    #set($renderer = $globalHelper.getWikiStyleRenderer())
 
    ##
    ## FIXME: Must be a more efficent way to find a page...
    ##
 
    #foreach ($child in $page.space.pages)
        #if ( ($child.title.equals($title)) && ( $child.contentStatus.equals("current") ) )
            #set ($content = $renderer.convertWikiToXHtml($child.toPageContext(), $child.content).trim())
 
            ##
            ## HACK: Remove the leading <P> and trailing </P>
            ##
 
            #set ($content = $content.replaceAll("^<[pP]>|</[pP]>$", "") )
            ##set ($content = $content.substring(3, $content.length()))
            ##set ($end = $content.length() - 4)
            ##set ($content = $content.substring(0, $end))
 
            $content
        #end
    #end
#end
##
 <html>
 <head>
<link rel="shortcut icon" href="http://directory.apache.org/staticresources/images/server-icon_16x16.png">
  <link rel="alternate" type="application/rss+xml" title="RSS" href="http://cwiki.apache.org/confluence/createrssfeed.action?types=blogpost&statuses=created&statuses=modified&spaces=DIRxSITE&labelString=&rssType=rss2&maxResults=5&timeSpan=99&publicFeed=true&title=Apache+Directory+News+RSS+Feed">
  <!-- $PAGETITLE -->
        <title>Apache Directory - $title</title>
        <link href="http://directory.apache.org/staticresources/green.css" rel="stylesheet" type="text/css">
        <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-1358462-1";
urchinTracker();
</script>
    </head>
    <body>
        <a name="top"></a>
        <div id="container">
            <div id="header">
                <div id="subProjectsNavBar">
                    <a href="http://directory.apache.org/"><strong>Apache Directory</strong></a>
                    &nbsp;|&nbsp;
                    <a href="http://directory.apache.org/apacheds/1.0/">ApacheDS 1.0</a>
                    &nbsp;|&nbsp;
                    <a href="http://directory.apache.org/apacheds/1.5/">ApacheDS 1.5</a>
                    &nbsp;|&nbsp;
                    <a href="http://directory.apache.org/triplesec/">Triplesec</a>
                    &nbsp;|&nbsp;
                    <a href="http://directory.apache.org/studio/">Studio</a>
                </div><!-- subProjectsNavBar -->
            </div><!-- header -->
            <div id="content">
                <div id="leftColumn">
                    <div id="navigation">
                        #renderPage("Navigation")
                    </div><!-- navigation -->
                    <br />
                    <hr width="75%"/>
                    <br />
                    <!-- div align="center">
                        <a href="http://apachecon.com/2007/EU/" target="_top"><img src="http://www.apache.org/ads/ApacheCon/2007-europe-125x125.png" border="0" width="125" height="125" alt="ApacheCon Europe 2007"></a>
                        <a href="http://people.apache.org/calendar.html#200711" target="_top"><img src="http://www.apache.org/ads/ApacheCon/2007-usa-125x125.png" border="0" width="125" height="125" alt="ApacheCon US 2007"></a>
                    </div -->
                </div><!-- leftColumn -->
                <div id="rightColumn">
                    <div id="editPage"><a href="$confluenceUri/pages/editpage.action?pageId=$page.id" onMouseOver="document.getElementById('editPageImage').src='http://directory.apache.org/staticresources/images/edit_over.png';" onMouseOut="document.getElementById('editPageImage').src='http://directory.apache.org/staticresources/images/edit_out.png';"><img id="editPageImage" src="http://directory.apache.org/staticresources/images/edit_out.png" width="16" height="16" border="0" title="Edit this page" alt="Edit this page"></a></div>
                    $body
                </div><!-- rightColumn -->
                <div id="endContent"></div>
            </div><!-- content -->
            <div id="footer">&copy; 2003-2008, <a href="http://www.apache.org">The Apache Software Foundation</a>&nbsp;-&nbsp;<a href="http://directory.apache.org/privacy-policy.html">Privacy Policy</a></div>
        </div><!-- container -->
    </body>

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: Fast track out of incubation - exit criteria

Posted by Emmanuel Lecharny <el...@gmail.com>.
Les Hazlewood wrote:
> I personally prefer Directory's - the way it presents information
> feels closer to the current JSecurity organization.  It has a very
> clean appearance too.
>
> Emmanuel, what do you think - could we use that as a base and change
> the colors and logo to match the current JSecurity site, and do
> whatever other customization we would need? Would the Directory team
> be ok with that?
>   
You do whatever you want ! The site has been designed with ASL 2.0 in 
mind, so it's not 'stealing' to use the Directory template, it's just 
sparing useful resources !

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
I personally prefer Directory's - the way it presents information
feels closer to the current JSecurity organization.  It has a very
clean appearance too.

Emmanuel, what do you think - could we use that as a base and change
the colors and logo to match the current JSecurity site, and do
whatever other customization we would need? Would the Directory team
be ok with that?

- Les

On Sun, Jan 11, 2009 at 3:38 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Sun, Jan 11, 2009 at 9:34 PM, Les Hazlewood <lh...@apache.org> wrote:
>> Oh?  Interesting.
>>
>> Both Wicket and Directory's sites are quite nice.  I'd be happy using
>> either as a base and customizing it however you wish.  What would you
>> prefer Niklas?
>>
>> If the template is not committed into SVN, I'm assuming it would be ok
>> to use a GPL'd template (assuming legal doesn't object).
>>
>> But would you rather base it off of Wicket and/or Directory?  If you
>> do, it seems like your job might be easier, but I don't know - I'm
>> just making an assumption.
>
> Starting from a Confluence based theme is surely easier. Pick one you
> like, and let's check with that project so they don't feel like we're
> stealing their work.
>
> /niklas
>

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Sun, Jan 11, 2009 at 9:34 PM, Les Hazlewood <lh...@apache.org> wrote:
> Oh?  Interesting.
>
> Both Wicket and Directory's sites are quite nice.  I'd be happy using
> either as a base and customizing it however you wish.  What would you
> prefer Niklas?
>
> If the template is not committed into SVN, I'm assuming it would be ok
> to use a GPL'd template (assuming legal doesn't object).
>
> But would you rather base it off of Wicket and/or Directory?  If you
> do, it seems like your job might be easier, but I don't know - I'm
> just making an assumption.

Starting from a Confluence based theme is surely easier. Pick one you
like, and let's check with that project so they don't feel like we're
stealing their work.

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
Oh?  Interesting.

Both Wicket and Directory's sites are quite nice.  I'd be happy using
either as a base and customizing it however you wish.  What would you
prefer Niklas?

If the template is not committed into SVN, I'm assuming it would be ok
to use a GPL'd template (assuming legal doesn't object).

But would you rather base it off of Wicket and/or Directory?  If you
do, it seems like your job might be easier, but I don't know - I'm
just making an assumption.

On Sun, Jan 11, 2009 at 3:29 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Sun, Jan 11, 2009 at 9:11 PM, Les Hazlewood <lh...@apache.org> wrote:
>> I believe that Niklas' plan is to use confluence exporting - as soon
>> as he could get the theme cleared.  But if we just start out with a
>> Wicket-derived theme, that'd be the easiest I think...
>
> Right, and the theme is stored in Confluence, not in SVN.
>
> /niklas
>

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Sun, Jan 11, 2009 at 9:11 PM, Les Hazlewood <lh...@apache.org> wrote:
> I believe that Niklas' plan is to use confluence exporting - as soon
> as he could get the theme cleared.  But if we just start out with a
> Wicket-derived theme, that'd be the easiest I think...

Right, and the theme is stored in Confluence, not in SVN.

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
I believe that Niklas' plan is to use confluence exporting - as soon
as he could get the theme cleared.  But if we just start out with a
Wicket-derived theme, that'd be the easiest I think...

I'm just so thrilled that he has volunteered to help us out that I'd
like to see _any_ solution at this point, Confluence-based or not :)

On Sun, Jan 11, 2009 at 3:07 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> Les Hazlewood wrote:
>>
>> I'd be quite happy to just take Wicket's page as a base, and change
>> the colors to be blue like our existing site.  Pull in our logo, clean
>> things up a little bit, and it will be a good enough transformation I
>> think...
>>
>
> If we go this way, the best would be to base the site on Confluence, as it
> will be way easier to inject modifications in it.
>
> (I think that Wicket is based on Confluence, from the top of my head)
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: Fast track out of incubation - exit criteria

Posted by Emmanuel Lecharny <el...@gmail.com>.
Les Hazlewood wrote:
> I'd be quite happy to just take Wicket's page as a base, and change
> the colors to be blue like our existing site.  Pull in our logo, clean
> things up a little bit, and it will be a good enough transformation I
> think...
>   
If we go this way, the best would be to base the site on Confluence, as 
it will be way easier to inject modifications in it.

(I think that Wicket is based on Confluence, from the top of my head)

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
I'd be quite happy to just take Wicket's page as a base, and change
the colors to be blue like our existing site.  Pull in our logo, clean
things up a little bit, and it will be a good enough transformation I
think...

What do you guys think?

On Sun, Jan 11, 2009 at 2:53 PM, Les Hazlewood <lh...@apache.org> wrote:
> Oh?  We have to commit this to SVN?  I wasn't sure how the website
> template stuff was stored - either on a server directly or actually
> checked in to SVN.
>
> If we have to commit it to SVN, I guess we'll have to write our own...
>
> On Sun, Jan 11, 2009 at 2:49 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>> Niklas Gustavsson wrote:
>>>
>>> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com>
>>> wrote:
>>>
>>>>
>>>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org>
>>>> wrote:
>>>>
>>>>>>
>>>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>>>> I guess since the site is not really used, I can use it freely for a
>>>>>> few days while I get the template up and running?
>>>>>>
>>>>>
>>>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>>>>
>>>>
>>>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>>>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>>>> API is, I fail to find any license for the theme). I'm not sure what
>>>> consequences re-using this theme would have for the JSecurity site at
>>>> Apache. For example, it's common to redistribute the site with a
>>>> release, I suspect that might be impossible.
>>>>
>>>> Anyone got a clue? Does anyone know what license really apply to the
>>>> theme?
>>>>
>>>
>>> Any takers? I would like to move forward with this but would like to
>>> have a clear understanding of if the template would be allowed to be
>>> used :-)
>>>
>>
>> Looking at some Legal mail :
>>
>> "On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:
>>
>>> ...
>>> At issue is whether artifacts with unacceptable licenses can appear in
>>> Apache public svn repositories.
>>
>> They can't.  Only open source is allowed in Apache's public svn.
>>
>> ....Roy
>> "
>>
>> It seems that if we are using a Drupal Theme, as it is distributed under a
>> GPL license, then we can't use it, as we will have to inject this theme into
>> svn.
>>
>> wdyt ?
>>
>> --
>> --
>> cordialement, regards,
>> Emmanuel Lécharny
>> www.iktek.com
>> directory.apache.org
>>
>>
>>
>

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
Oh?  We have to commit this to SVN?  I wasn't sure how the website
template stuff was stored - either on a server directly or actually
checked in to SVN.

If we have to commit it to SVN, I guess we'll have to write our own...

On Sun, Jan 11, 2009 at 2:49 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> Niklas Gustavsson wrote:
>>
>> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com>
>> wrote:
>>
>>>
>>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org>
>>> wrote:
>>>
>>>>>
>>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>>> I guess since the site is not really used, I can use it freely for a
>>>>> few days while I get the template up and running?
>>>>>
>>>>
>>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>>>
>>>
>>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>>> API is, I fail to find any license for the theme). I'm not sure what
>>> consequences re-using this theme would have for the JSecurity site at
>>> Apache. For example, it's common to redistribute the site with a
>>> release, I suspect that might be impossible.
>>>
>>> Anyone got a clue? Does anyone know what license really apply to the
>>> theme?
>>>
>>
>> Any takers? I would like to move forward with this but would like to
>> have a clear understanding of if the template would be allowed to be
>> used :-)
>>
>
> Looking at some Legal mail :
>
> "On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:
>
>> ...
>> At issue is whether artifacts with unacceptable licenses can appear in
>> Apache public svn repositories.
>
> They can't.  Only open source is allowed in Apache's public svn.
>
> ....Roy
> "
>
> It seems that if we are using a Drupal Theme, as it is distributed under a
> GPL license, then we can't use it, as we will have to inject this theme into
> svn.
>
> wdyt ?
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
Oh?  We have to commit this to SVN?  I wasn't sure how the website
template stuff was stored - either on a server directly or actually
checked in to SVN.

If we have to commit it to SVN, I guess we'll have to write our own...

On Sun, Jan 11, 2009 at 2:49 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> Niklas Gustavsson wrote:
>>
>> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com>
>> wrote:
>>
>>>
>>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org>
>>> wrote:
>>>
>>>>>
>>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>>> I guess since the site is not really used, I can use it freely for a
>>>>> few days while I get the template up and running?
>>>>>
>>>>
>>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>>>
>>>
>>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>>> API is, I fail to find any license for the theme). I'm not sure what
>>> consequences re-using this theme would have for the JSecurity site at
>>> Apache. For example, it's common to redistribute the site with a
>>> release, I suspect that might be impossible.
>>>
>>> Anyone got a clue? Does anyone know what license really apply to the
>>> theme?
>>>
>>
>> Any takers? I would like to move forward with this but would like to
>> have a clear understanding of if the template would be allowed to be
>> used :-)
>>
>
> Looking at some Legal mail :
>
> "On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:
>
>> ...
>> At issue is whether artifacts with unacceptable licenses can appear in
>> Apache public svn repositories.
>
> They can't.  Only open source is allowed in Apache's public svn.
>
> ....Roy
> "
>
> It seems that if we are using a Drupal Theme, as it is distributed under a
> GPL license, then we can't use it, as we will have to inject this theme into
> svn.
>
> wdyt ?
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: Fast track out of incubation - exit criteria

Posted by Emmanuel Lecharny <el...@gmail.com>.
Niklas Gustavsson wrote:
> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
>   
>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org> wrote:
>>     
>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>> I guess since the site is not really used, I can use it freely for a
>>>> few days while I get the template up and running?
>>>>         
>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>>       
>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>> API is, I fail to find any license for the theme). I'm not sure what
>> consequences re-using this theme would have for the JSecurity site at
>> Apache. For example, it's common to redistribute the site with a
>> release, I suspect that might be impossible.
>>
>> Anyone got a clue? Does anyone know what license really apply to the theme?
>>     
>
> Any takers? I would like to move forward with this but would like to
> have a clear understanding of if the template would be allowed to be
> used :-)
>   
Looking at some Legal mail :

"On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:

> ...
> At issue is whether artifacts with unacceptable licenses can appear in 
> Apache public svn repositories.

They can't.  Only open source is allowed in Apache's public svn.

....Roy
"

It seems that if we are using a Drupal Theme, as it is distributed under 
a GPL license, then we can't use it, as we will have to inject this 
theme into svn.

wdyt ?

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
We don't distribute the JSecurity site with a release (currently), nor
have we ever in the last 4 years.  Wouldn't it be ok to use the theme
for now if that is the case since we're not distributing any of it?

We had a similar discussion about the use of the google code project
Syntax Highlighter (http://code.google.com/p/syntaxhighlighter/),
which is LGPL.  Because we don't distribute the website, legal said it
was no problem for us to use it.

I'm CC'ing legal to see if they have any objections, as they might be
ok with LGPL but not with GPL - just checking to be sure.

Thanks,

Les

On Sun, Jan 11, 2009 at 2:35 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org> wrote:
>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>> I guess since the site is not really used, I can use it freely for a
>>>> few days while I get the template up and running?
>>>
>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>
>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>> API is, I fail to find any license for the theme). I'm not sure what
>> consequences re-using this theme would have for the JSecurity site at
>> Apache. For example, it's common to redistribute the site with a
>> release, I suspect that might be impossible.
>>
>> Anyone got a clue? Does anyone know what license really apply to the theme?
>
> Any takers? I would like to move forward with this but would like to
> have a clear understanding of if the template would be allowed to be
> used :-)
>
> /niklas
>

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org> wrote:
>>> Having it zipped up would be good enough, just email it to me offlist.
>>> I guess since the site is not really used, I can use it freely for a
>>> few days while I get the template up and running?
>>
>> Of course - please feel free.  I'll zip it up and send it over asap.
>
> Looking closer at this, if I'm correct, the current jsecurity.org uses
> the default Drupal skin, which seems to be GPL2 (at least the Drupal
> API is, I fail to find any license for the theme). I'm not sure what
> consequences re-using this theme would have for the JSecurity site at
> Apache. For example, it's common to redistribute the site with a
> release, I suspect that might be impossible.
>
> Anyone got a clue? Does anyone know what license really apply to the theme?

Any takers? I would like to move forward with this but would like to
have a clear understanding of if the template would be allowed to be
used :-)

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <lh...@apache.org> wrote:
>> Having it zipped up would be good enough, just email it to me offlist.
>> I guess since the site is not really used, I can use it freely for a
>> few days while I get the template up and running?
>
> Of course - please feel free.  I'll zip it up and send it over asap.

Looking closer at this, if I'm correct, the current jsecurity.org uses
the default Drupal skin, which seems to be GPL2 (at least the Drupal
API is, I fail to find any license for the theme). I'm not sure what
consequences re-using this theme would have for the JSecurity site at
Apache. For example, it's common to redistribute the site with a
release, I suspect that might be impossible.

Anyone got a clue? Does anyone know what license really apply to the theme?

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
> Having it zipped up would be good enough, just email it to me offlist.
> I guess since the site is not really used, I can use it freely for a
> few days while I get the template up and running?


Of course - please feel free.  I'll zip it up and send it over asap.

Thanks again,

Les

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Jan 1, 2009 at 10:38 PM, Les Hazlewood <lh...@apache.org> wrote:
> Hi Niklas,
>
> Seems like export is up and running:
>> http://incubator.apache.org/jsecurity/.
>
> Oh really?  I thought that was just the confluence wiki.  That's an exported
> page?

Yeah it is. Seems to be running as a cron job.

>> But I guess a nicer template
>> would be in place. How about reusing the existing look and feel from
>> jsecurity.org, should be easy enough to convert into a Confluence
>> template. Let me know if you like any assistance in this area.
>
> I would _greatly_ appreciate any help you could offer with that :)  How
> would you like to go about doing it?  I can give you access to our existing
> server/drupal installation and you can take the theme if you like.  Or I
> could zip it up and give it to you.  Whatever you'd like.  Or, if something
> else would be convenient, please let me know.

Having it zipped up would be good enough, just email it to me offlist.
I guess since the site is not really used, I can use it freely for a
few days while I get the template up and running?

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
Hi Niklas,

Seems like export is up and running:
> http://incubator.apache.org/jsecurity/.


Oh really?  I thought that was just the confluence wiki.  That's an exported
page?


> But I guess a nicer template
> would be in place. How about reusing the existing look and feel from
> jsecurity.org, should be easy enough to convert into a Confluence
> template. Let me know if you like any assistance in this area.


I would _greatly_ appreciate any help you could offer with that :)  How
would you like to go about doing it?  I can give you access to our existing
server/drupal installation and you can take the theme if you like.  Or I
could zip it up and give it to you.  Whatever you'd like.  Or, if something
else would be convenient, please let me know.

Thanks!

- Les

Re: Fast track out of incubation - exit criteria

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Thu, Jan 1, 2009 at 10:00 PM, Les Hazlewood <lh...@apache.org> wrote:
>>  The "Distribution Rights' section is probably completed - how do we verify
>>> so we can check this off?
>>>
>> This has to be done.
>
> How do we do that?

Getting an Apache release out is a good focus. Passing the release
vote will mean scrutiny on licensing and distribution rights.

> The web site has to be up and running too. No web site, no visibility...
>
> Yes, we should get started on that ASAP.  I believe Allan's efforts fell to
> the wayside.  I don't know that he has had time lately to get the Confluence
> export stuff working...

Seems like export is up and running:
http://incubator.apache.org/jsecurity/. But I guess a nicer template
would be in place. How about reusing the existing look and feel from
jsecurity.org, should be easy enough to convert into a Confluence
template. Let me know if you like any assistance in this area.

/niklas

Re: Fast track out of incubation - exit criteria

Posted by Les Hazlewood <lh...@apache.org>.
>
> first, there is nothing such a Fast Track. The project exits the incubator
> when it's ready - or dead -.


I'm aware of that :)  I was making a statement that for us, the "fast track"
would be to focus on the checklist more than anything else (instead of
architecture, code changes) to appeal to people to get focused on that.

The "Copyrights & Licensing" section is probably completed - how do we
>> verify so we can check this off?
>>
>>
> I don't remember that we did any IP clearance so far.


Ok - but how do we do that?

>
>  The "Distribution Rights' section is probably completed - how do we verify
>> so we can check this off?
>>
>>
> This has to be done.


How do we do that?

>
>  I believe "Infastructure" section is complete.
>>
>>
> Nope. The web site is still void.


Ok, cool.  Thanks for clarifying.

At least the 'mailing lists' line item can be checked off now.

Is there anything else aside from the website?


> I think most of the "Collaborative Development" criteria has been met.
>
>
So far, since the project has been accepted into the incubator, no new
> committer has been added to the project. Community building is one of the
> most important thing, and it's one of the reason the projects stay a long
> time in the incubator. You can have a look at this page :
> http://incubator.apache.org/clutch.html


Very cool tool - thanks for pointing it out.


> The K column is a good indicator. Currently, if you except WSRP4J, UIMA and
> Shindig, all the other projects are still to add new committers. It takes a
> lot of time, and effort.
>
>> Can the Mentors clarify exactly what they feel has been met and what is to
>> remain?  Once we get this list, we can check them off one by one to ensure
>> we can exit the incubator asap.
>>
>>
> I think we can focus on low hanging fruits atm : IP clearance, paperwork.
> This will check some more crosses on the list.


Awesome - that's what I'm hoping for - I want to essentially get us cleared
on all things that can be cleared asap.  Then we can focus on the
longer-term stuff like getting new committers, etc.

The web site has to be up and running too. No web site, no visibility...


Yes, we should get started on that ASAP.  I believe Allan's efforts fell to
the wayside.  I don't know that he has had time lately to get the Confluence
export stuff working...


> Last, not least, the community. The project has still to demonstrate it can
> attract people other than the original contributors.
>
> Hope it helps.


Certainly did - thank you.  But, of the remaining unchecked stuff in the
STATUS file, is there something that we can look at (or that you tell us)
that we can use to know _exactly_ how to go about doing that?  I don't know
how to check for IP clearance, exactly what paperwork is remaining, etc...

Thanks,

Les

Re: Fast track out of incubation - exit criteria

Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi,

first, there is nothing such a Fast Track. The project exits the 
incubator when it's ready - or dead -.

Les Hazlewood wrote:
> It is now finally glaring clear to me the importance of getting out of
> incubation. 
The ASF incubator is meant to be a place where a project stays the 
shortest possible time. When the project is ready to fly the Apache Way, 
then it's time to get out.
>  I feel disheartened by the fact that the 5 originating
> developers have no formal voting authority.
That does not matter a lot. Vote are usually necessary for releases, new 
committers addition (and this is the PMC role, so unless the project is 
out of incubation, the Incubator PMC), and when a consensus can't be 
find, which is not an encouraged solution (ie, it's also a part of the 
Apache Way to get things done through consensus, not though a vote. If a 
vote is needed, that means either there is a split community, or someone 
is trying to push his opinion a bit too far, when others disagree, or 
there is not a clear consensus but no one want to move forward).
>   Obviously, the best way to
> alleviate this is to ensure we get out of incubation and obtain voting
> capability as soon as is possible. 
This will be a consequence, not a goal. Again, limiting votes to 
important decisions is a must.
>  Of course there are other benefits to
> exiting the incubator (including retaining the great ASF community that has
> been building with us), and we'll naturally achieve those as well.
>   
Those are the most important reasons for exiting the incubator, and 
'gaining vote power' is certainly not one of them.
> Here is the current status file, which lists what is left to do to exit the
> incubator:
> http://svn.apache.org/viewvc/incubator/jsecurity/STATUS?view=markup
>
> The "Copyrights & Licensing" section is probably completed - how do we
> verify so we can check this off?
>   
I don't remember that we did any IP clearance so far.
> The "Distribution Rights' section is probably completed - how do we verify
> so we can check this off?
>   
This has to be done.
> I believe "Infastructure" section is complete.
>   
Nope. The web site is still void.
> I think most of the "Collaborative Development" criteria has been met.
>   
So far, since the project has been accepted into the incubator, no new 
committer has been added to the project. Community building is one of 
the most important thing, and it's one of the reason the projects stay a 
long time in the incubator. You can have a look at this page :
http://incubator.apache.org/clutch.html

The K column is a good indicator. Currently, if you except WSRP4J, UIMA 
and Shindig, all the other projects are still to add new committers. It 
takes a lot of time, and effort.
> Can the Mentors clarify exactly what they feel has been met and what is to
> remain?  Once we get this list, we can check them off one by one to ensure
> we can exit the incubator asap.
>   
I think we can focus on low hanging fruits atm : IP clearance, 
paperwork. This will check some more crosses on the list.

The web site has to be up and running too. No web site, no visibility...

Last, not least, the community. The project has still to demonstrate it 
can attract people other than the original contributors.

Hope it helps.

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org