I'd like to get involved in supporting the mailing lists from the
infrastucture point of view...I think that would be fun to learn and get
involved with (...famous last words ;-)....)

I'll sign up for that...Is there a place where I can get some info on
how to get involved?  Any mentors out there?  I don't even know what
software is used, but I am willing to learn!!! 

Please provide some info on getting started...

Thanks!!

-Sal

-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 17, 2005 10:27 AM
To: [email protected]
Subject: Re: migration to-do list

Yes, i am part of it and try to help..Note that i've been asking for
volunteers. No one has signed up yet.

-- dims

On 6/17/05, Ian Springer <[EMAIL PROTECTED]> wrote:
> Issues have been filed in Infrastructure JIRA:
> 
> http://issues.apache.org/jira/browse/INFRA-388
> http://issues.apache.org/jira/browse/INFRA-389
> 
> Unfortunately, I notice dozens of other Infra issues that have been 
> languishing in JIRA for months. Is there anyone in WS that is also 
> part of Infra that is willing to help expedite these two issues?
> 
> Thanks,
> Ian
> 
> Davanum Srinivas wrote:
> 
> >Ian,
> >
> >Let's do this on [EMAIL PROTECTED]
> >
> >thanks,
> >dims
> >
> >Please see below...
> >[INFRA] - Need to create a separate JIRA issue for infrastructure
folks.
> >[ME] - I can do this.
> >[YOU] - Any committer can do this.
> >
> >On 6/16/05, Ian Springer <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Here's a list of the tasks we need to do to migrate the projects out

> >>of the incubator + rename them. Dims, two questions for you are
inline.
> >>Basically, we need to know if you have admin access for SVN and/or 
> >>mailing lists.
> >>
> >>1) WEB SITES:
> >>   a) move from incubator.apache.org to ws.apache.org
> >>      and add redirects from the original URLs to the new URLs
[DONE]
> >>   b) update links and project names throughout project sites
> >>
> >>
> >[YOU]
> >
> >
> >>   c) update links and project names on ws.apache.org and 
> >>ws.apache.org/ws-fx pages
> >>
> >>
> >[YOU]
> >
> >
> >>2) MAILING LISTS:
> >>   a) rename [email protected] to [EMAIL PROTECTED],
> >>      rename [email protected] to
[EMAIL PROTECTED],
> >>      rename [email protected] to [EMAIL PROTECTED]
> >>
> >>
> >[INFRA]
> >
> >
> >>   b) create the following new lists:
> >>      [EMAIL PROTECTED],
> >>      [EMAIL PROTECTED],
> >>      [EMAIL PROTECTED],
> >>      [EMAIL PROTECTED],
> >>      [email protected],
> >>      [EMAIL PROTECTED]
> >>
> >>
> >[INFRA]
> >
> >
> >>   c) register new lists with marc.theaimsgroup.com
> >>
> >>
> >[YOU]
> >
> >
> >>   d) update contact info pages on project web sites to advertise 
> >>the new lists
> >>
> >>
> >[YOU]
> >
> >
> >>*** Dims *** Is a) and b) something you can do, or do we need to ask

> >>Infrastructure?
> >>
> >>3) SVN DIRS:
> >>   a) SVN-move http://svn.apache.org/repos/asf/incubator/apollo/ to 
> >>http://svn.apache.org/repos/asf/webservices/ws-fx/wsrf/
> >>      SVN-move http://svn.apache.org/repos/asf/incubator/hermes/ to 
> >>http://svn.apache.org/repos/asf/webservices/ws-fx/pubscribe/
> >>      SVN-move http://svn.apache.org/repos/asf/incubator/muse/   to
> >>http://svn.apache.org/repos/asf/webservices/ws-fx/muse/
> >>
> >>
> >[INFRA]
> >
> >
> >>   b) configure SVN to send commit notifications to new mailing list

> >>addresses
> >>      ([EMAIL PROTECTED], [EMAIL PROTECTED], and
> >>[EMAIL PROTECTED])
> >>
> >>
> >[INFRA]
> >
> >
> >>   c) update version control pages on project web sites to advertise

> >>new SVN URLs
> >>
> >>
> >[YOU]
> >
> >
> >>*** Dims *** Is a) and b) something you can do, or do we need to ask

> >>Infrastructure?
> >>
> >>4) JIRA PROJECTS:
> >>   a) rename projects  [DONE]
> >>      (Note: it doesn't seem possible in JIRA to rename the project
"keys"
> >>      (i.e. the unique project IDs used to form issue IDs and issue
URLs),
> >>      but I think I can live with keeping APOLLO and HERMES as the
keys
> >>      for the WSRF and Pubscribe projects
> >>
> >>
> >
> >Yep. we can't change that.
> >
> >
> >
> >>   b) change notification schemes to use new dev list addresses once
the
> >>      new dev lists are set up
> >>
> >>
> >[YOU]
> >
> >
> >>5) GUMP DESCRIPTORS:
> >>   a) update to point to new SVN dirs
> >>   b) update to send failure notifications to new mailing list 
> >>addresses
> >>
> >>
> >[YOU]
> >
> >
> >>6) ANNOUNCEMENTS:
> >>   a) Send emails to project announcing exit from incubation, name 
> >>changes, and new project infra info
> >>   b) Send email to [EMAIL PROTECTED] (other Apache lists?) announcing exit

> >>of projects from incubation
> >>
> >>
> >[YOU]
> >
> >
> >>=====
> >>
> >>Please add on to this if there's anything I forgot.
> >>
> >>Thanks,
> >>Ian
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> 
> 
> 
> 


--
Davanum Srinivas -http://blogs.cocoondev.org/dims/

Reply via email to