SVN whiteboard created...

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

SVN whiteboard created...

Bertrand Delacretaz
at http://svn.apache.org/repos/asf/incubator/flex/whiteboard/

As code speaks louder than words, if a committer wants to create some
prototypes there go ahead - just create subfolders under that one to
keep things more or less organized.

It seems like we have agreement on this from another thread, but if
not it's easy to reorganize later.

If your apache username is listed in the
http://markmail.org/thread/ly6isc4z7f7bp2aw thread you should be able
to commit (using https - http is read-only).

See also http://incubator.apache.org/flex/developer-faqs.html#how_do_i_use_apache_subversion
if you're not familiar with svn.

-Bertrand

Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Alex Harui



On 1/6/12 9:20 AM, "Bertrand Delacretaz" <[hidden email]> wrote:

> at http://svn.apache.org/repos/asf/incubator/flex/whiteboard/
>
> As code speaks louder than words, if a committer wants to create some
> prototypes there go ahead - just create subfolders under that one to
> keep things more or less organized.
>
Bertrand, do folks have to fill out a Software Grant and/or make sure they
have Apache licenses for new files they commit?

Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Bertrand Delacretaz
On Fri, Jan 6, 2012 at 7:00 PM, Alex Harui <[hidden email]> wrote:
> On 1/6/12 9:20 AM, "Bertrand Delacretaz" <[hidden email]> wrote:
>
>> at http://svn.apache.org/repos/asf/incubator/flex/whiteboard/...

> ...Bertrand, do folks have to fill out a Software Grant and/or make sure they
> have Apache licenses for new files they commit?..

To commit their own code people only need to have filed an iCLA [1],
which is required for getting their apache account, so all committers
should be good. See also section 4. of that, "You represent that you
are legally entitled to grant the above license" etc., that's where a
software grant might be needed, but that's not the case for one's own
code.

-Bertrand

[1] http://www.apache.org/licenses/icla.txt

Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Michael Schmalle
>
> To commit their own code people only need to have filed an iCLA [1],
> which is required for getting their apache account, so all committers
> should be good. See also section 4. of that, "You represent that you
> are legally entitled to grant the above license" etc., that's where a
> software grant might be needed, but that's not the case for one's own
> code.
>
> -Bertrand
>
> [1] http://www.apache.org/licenses/icla.txt
>

I'm being numb here but what exactly would we expect to put in the  
white board?

examples, component code? Please excuse me being naive.

And "what" license do we put on the source code, the Apache 2?

Mike


Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Bertrand Delacretaz
On Fri, Jan 6, 2012 at 7:17 PM, Michael Schmalle <[hidden email]> wrote:
> ...I'm being numb here but what exactly would we expect to put in the white
> board?
>
> examples, component code? Please excuse me being naive....

In my view the whiteboard is for experimental stuff - anything that
one or several committer want to work on and make visible to others.

>
> And "what" license do we put on the source code, the Apache 2?
>

Of course.

-Bertrand

Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Greg Reddin
In reply to this post by Michael Schmalle
On Fri, Jan 6, 2012 at 12:17 PM, Michael Schmalle <[hidden email]> wrote:
>>
> I'm being numb here but what exactly would we expect to put in the white
> board?
>
> examples, component code? Please excuse me being naive.

Anything. Yes, examples, components are fine. But heck, you can start
refactoring the whole framework there if you want. Or you can start a
completely new framework from scratch. If the fire catches on it will
eventually be moved to trunk (or rewritten in trunk).

> And "what" license do we put on the source code, the Apache 2?

Yes, anything you contribute will be licensed as Apache 2.

Greg

Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Greg Reddin
In reply to this post by Michael Schmalle
On Fri, Jan 6, 2012 at 12:17 PM, Michael Schmalle <[hidden email]> wrote:
> I'm being numb here but what exactly would we expect to put in the white
> board?
>
> examples, component code? Please excuse me being naive.

Let me give a quick example of how this can work. Apache Tiles used to
be a subproject of the Apache Struts project. Someone decided it was
better as a standalone project so they forked it to the Struts
sandbox. Work continued there by multiple people until Tiles was
completely separated from Struts. So Apache Tiles became a top-level
project (TLP) in its own right. The code from the Struts sandbox
became the trunk of Tiles.

Over time the code stabilized and releases were made. Eventually
commiters started thinking about revolutionary changes to Tiles. They
forked the codebase to the Tiles sandbox and went to work. Eventually
that work became stable enough that we moved it to trunk and it is now
the main development line of the Tiles project. Eventually a Tiles 3
version will be released from it.

If you have the gumption to do it you can see the entire history of
this by looking at Subversion logs. It all happened in the public
Subversion repo.

Greg

Reply | Threaded
Open this post in threaded view
|

Re: SVN whiteboard created...

Michael Schmalle
Quoting Greg Reddin <[hidden email]>:

> On Fri, Jan 6, 2012 at 12:17 PM, Michael Schmalle  
> <[hidden email]> wrote:
>> I'm being numb here but what exactly would we expect to put in the white
>> board?
>>
>> examples, component code? Please excuse me being naive.
>
> Let me give a quick example of how this can work. Apache Tiles used to
> be a subproject of the Apache Struts project. Someone decided it was
> better as a standalone project so they forked it to the Struts
> sandbox. Work continued there by multiple people until Tiles was
> completely separated from Struts. So Apache Tiles became a top-level
> project (TLP) in its own right. The code from the Struts sandbox
> became the trunk of Tiles.
>
> Over time the code stabilized and releases were made. Eventually
> commiters started thinking about revolutionary changes to Tiles. They
> forked the codebase to the Tiles sandbox and went to work. Eventually
> that work became stable enough that we moved it to trunk and it is now
> the main development line of the Tiles project. Eventually a Tiles 3
> version will be released from it.
>
> If you have the gumption to do it you can see the entire history of
> this by looking at Subversion logs. It all happened in the public
> Subversion repo.
>
> Greg
>

OK point clear, you should have named the folder "innovation", that is  
a lot more clear to me. ;-)

Mike