Hi Andrus,
On Mar 9, 2006, at 6:21 AM, Andrus Adamchik wrote:
> Thanks Bill! This looks good to me (except that "WADI Wiki" should
> read "Cayenne Wiki").
No prob!
Done, dooh! I hate copy and paste errors :-)
>
> But isn't the Incubator PMC required to vote for us to go ahead
> with the actual code migration?
>
Well as I understand it only special circumstances are required for
an Incubator PMC vote, at least that is what I read here;
http://incubator.apache.org/incubation/
Incubation_Policy.html#Acceptance+of+Proposal+by+Sponsor
Once the DB PMC posted that they accepted us the Incubator acceptance
is automatic.
So now all we really need is for someone to be actively pushing
things forward. I'm happy to do that.
> Other things...
>
> 1. Wiki - we should follow up with Geronimo and Infrastructure
> regarding Confluence install..pache (Geronimo pushed for
> Confluence install, but AFAIK there was no resolution yet).
> Switching to MoinMoin is a downgrade that is not acceptable
> considering that we decided to use Confluence as a main doc system.
>
Yes I think we should bring that up with them after we get moved into
the incubator. If G is pushing for it and we push for it to perhaps
we can get it. We can always leave everything in our current
Confluence for now.
Not that I want to open a can of worms or anything but if the
decision to go with Confluence for all docs was because the docs are
easy to edit and write then you can get basically the same ease with
the APT format from maven.
http://maven.apache.org/guides/mini/guide-apt-format.html
Difference is that editing the docs requires a patch and site install
instead of just editing the docs real time, pluses and minuses to
this approach are certainly there as with any approach. So anyway
this is not a proposal to change anything just a bit of info for
everyone to chew on.
> 2. Jira. We should migrate it too. I can provide the infra with an
> export from our instance. I know there are cross-version issues,
> but let's work on that.
>
Ah great! I did not realize it was that easy, it will be great to get
JIRA moved over. As soon as infra gets a JIRA set up we can post our
export for them to import.
> 3. Repository. CVS history is unimportant - once we change the
> package names the history becomes meaningless. And the old tags
> will be accessible on SourceForge anyways. There is another issue
> though. We discussed CVS vs. SVN in the past (and I was -1 back
> then). Now my vote is +0 to switch to Subversion. Since the whole
> move is already a disruption, we might as well combine it with
> other disruptive things that we considered in the past. But I'd
> like to hear what others say on that.
>
My take is, move to SVN with existing package names and history. Then
use SVN & Eclipse to do the refactoring. This will keep your history
in tact (but it confuses Eclipse so its not easy to see the history
in Eclipse). So you get the best of both, history and new package
names. There are several different ways to do this and I'd be happy
to help out with this we'd just have to have a freeze while we
repackage everything then have everyone help out with getting the
build to work again.
BTW Apache does not support CVS anymore, all projects are now on SVN.
> 4. Mailing list subscriptions - we don't want everyone to re-
> subscribe. I can provide the infra with all current addresses.
>
From what I remember it was more or less painless to get mailing
lists transfered over to apache, the infra folks can take a list of
subscriptions in the initial request to make the list and add all the
users at once (the use elhzm sp? so if we can provide a file
compatible to import it would be best).
> 5. Site. Let's start with a placeholder to objectstyle.org... We'll
> figure it out later.
>
>
> Andrus
>
>
>
> On Mar 9, 2006, at 3:53 PM, Bill Dudney wrote:
>
>> Hi All,
>>
>> I've put together an initial status page here;
>>
>> http://incubator.apache.org/projects/cayenne.html
>>
>> Please take a moment to browse over it and make sure I've not left
>> anyone out or misrepresented anything.
>>
>> This is the next step in moving to the incubator just prior to
>> filing requests for us to get user accounts, JIRA instance, SVN
>> repo etc.
>>
>> As we continue to get ready to make the move we need to decided
>> what we are going to migrate. Here are my initial thoughts;
>>
>> 1) CVS code history in its entirety
>> 2) All docs
>>
>> I'd like for us to be able to move the JIRA and Wiki but that
>> seems to be very difficult from what I can tell by watching other
>> projects make the move.
>>
>> We also need to start at least looking at removing any
>> dependencies we have on any licensed under a non ASF friendly
>> license (GPL, LGPL etc).
>>
>> TTFN,
>>
>> Bill Dudney
>> MyFaces - myfaces.apache.org
>
This archive was generated by hypermail 2.0.0 : Thu Mar 09 2006 - 08:43:43 EST