[forge-dev] Migrating Forge to the EPL license- how we can all help

[Lincoln Baxter, III]

Ah, sorry. Stick with /* ... */

On Thu, Aug 9, 2012 at 10:47 PM, jdbjunior at gmail.com <jdbjunior at gmail.com>wrote:

> I do forge-shell.
>
> On Thu, Aug 9, 2012 at 5:36 PM, Jevgeni Zelenkov
> <jevgeni.zelenkov at gmail.com> wrote:
> > The old license is commented using the regular comments /*  */, the
> > new one suggests javadoc style comments /** */
> > Shall we stick with the javadoc ones?
> >
> >
> > On Thu, Aug 9, 2012 at 9:17 PM, Lincoln Baxter, III
> > <lincolnbaxter at gmail.com> wrote:
> >> Hey everyone,
> >>
> >> Thanks for "volunteering" to help with the EPL license effort.
> >>
> >> The first thing we should do to get started migrating the Forge license
> is
> >> each choose module(s) that we'd like to help migrate. Simply reply here
> with
> >> the forge/core module you are taking on, and we will try not to overlap.
> >>
> >> Once you've chosen your module(s), we'll need to take the following
> steps.
> >>
> >> In all of the source file, check the /** License */ header to ensure
> that
> >> the (c) Copyright is owned by JBoss.
> >>
> >> If it is, replace the header with the following License:
> >>
> >> /**
> >>  * Copyright 2012 Red Hat, Inc. and/or its affiliates.
> >>  *
> >>  * Licensed under the Eclipse Public License Version 1.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.eclipse.org/legal/epl-v10.html
> >>  *
> >>  * 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.
> >>  */
> >>
> >> If it is not, then record the name of the file and at the end of your
> >> review, send a list of all such files discovered as a reply to this
> thread
> >> so that we can review the necessary actions to take (most likely no
> action
> >> will be required, and we will simply leave the header in tact.)
> >>
> >> Send your changes as a pull request for review.
> >>
> >> Another committer will review your pull request and merge the changes.
> Note
> >> - please DO NOT merge your own pull requests. We should have at least
> two
> >> sets of eyes reviewing each license change. We don't want to get this
> wrong!
> >>
> >> Drink beer.
> >>
> >> Thanks folks! Let the re-licensing begin!
> >>
> >> --
> >> Lincoln Baxter, III
> >> http://ocpsoft.org
> >> "Simpler is better."
> >>
> >> _______________________________________________
> >> forge-dev mailing list
> >> forge-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/forge-dev
> >>
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120810/aba787e5/attachment-0001.html