Hey, glad you decided to move over ! As long as its in your lab i don't mind the name "pyo" but will really think about it again over the weekend.. Also, if its a tool mostly about osgi then consider to put it into the pax familiy (package wise). There we mostly go for "practical" names or associative names (runner,construct, web,url, exam).
Can you also highlight the current (implemented+shortly planned) features/usecases here on the mailinglist? Maybe this inspires peope as well. But in the end, its your baby. Welcome to ops4j ! Toni On Fri, Apr 3, 2009 at 9:31 AM, Filippo Diotalevi < [email protected]> wrote: > Hi, > as discussed a couple of weeks ago, I'm starting porting proveasyo > http://code.google.com/p/proveasyo/ to ops4j > > Before committing, I want to rename the packages and add the correct > license headers. > > - for package names, I propose org.ops4j.pax.pyo > > - for the license is it ok to use (like in some examples of pax-runner) > /* > * Copyright 2009 the original author or authors. > * > * Licensed under the Apache License, Version 2.0 ..... etc etc > */ > using the @author tags to list all the authors ? > > - as for the SVN repo, should I use my personal folder inside the > laboratory? > something like i.e. > https://scm.ops4j.org/repos/ops4j/laboratory/users/fdiotalevi/pyo ? > > -- > Filippo Diotalevi > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Toni Menzel Software Developer Professional Profile: http://www.osgify.com [email protected] http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
