On Mon, Nov 15, 2010 at 9:44 PM, Michael Glavassevich
<[email protected]> wrote:
> Hi Hiranya,
>
> Hiranya Jayathilaka <[email protected]> wrote on 11/15/2010 01:47:56 AM:
>
>> Hi Michael,
>>
>> This is a very good migration plan. Regarding the mailing lists, I'm
>> usually bit hesitant on merging a mailing list to another. But I believe
>> the traffic level on these lists are not that high. So it should be fine.
>
> I happen to be subscribed to the "new" and merged [email protected] list, so
> am quite aware of how such moves can annoy and chase away some of the
> subscribers, but I think it's the right thing to do with the commits list
> for XML Commons.
>
>> However it would be great if we can somehow tag the
>> commit mails to indicate the project name, so subscribers can easily
>> filter them out.
>
> Should be easy to filter based on the subject line, e.g. grepping for
> "/xerces/java/" vs. "/xerces/c/" vs. "/xerces/xml-commons/".

+1

Thanks,
Hiranya

>
>> Thanks,
>> Hiranya
>>
>> On Sun, Nov 14, 2010 at 11:24 PM, Michael Glavassevich
>> <[email protected]> wrote:
>> > Hi all,
>> >
>> > With the XML project appearing to be slowly shutting down (Xindice is
>> > now
>> > the only project left there) I think it's time we fully moved XML
>> > Commons
>> > over to Xerces. In my opinion these changes are long overdue.
>> >
>> > Here's what I'm proposing:
>> >
>> > ==================================
>> >
>> > 1) Move the website to xerces.apache.org
>> >
>> > Proposing the new site address to be
>> > http://xerces.apache.org/xml-commons
>> > and set up a permanent redirect to it for old links to
>> > http://xml.apache.org/commons
>> >
>> > 2) Move the download area to http://www.apache.org/dist/xerces
>> >
>> > Releases would be located under
>> > http://www.apache.org/dist/xerces/xml-commons with a permanent redirect
>> > set
>> > up for links to the old one http://www.apache.org/dist/xml/commons
>> >
>> > 3) Move the 2 XML Commons mailing lists on to @xerces.apache.org
>> >
>> > [email protected] --> [email protected]
>> > [email protected] --> merge into the existing
>> > [email protected]
>> >
>> > All of Xerces' other sub-projects share the same commits list. Hoping
>> > this
>> > will improve oversight / awareness of activities in XML Commons in the
>> > rest
>> > of the project.
>> >
>> > 4) Migrate XML Commons from Bugzilla to JIRA
>> >
>> > All of Xerces' other sub-projects track their issues in JIRA.
>> > Occasionally
>> > issues are opened against XML Commons which should have really gone to
>> > Xerces-J or Xalan. Right now we return these as invalid and ask the
>> > reporter
>> > to reopen against the correct project in JIRA. With this move we can
>> > transfer the issue to the right JIRA project on their behalf.
>> >
>> > 5) Move XML Commons to Xerces SVN
>> >
>> > Proposing that we move this out from 'xml/commons' to
>> > 'xerces/xml-commons'
>> > (with no change to the committer list).
>> >
>> > ==================================
>> >
>> > I believe that covers everything. If no one objects I'll start the
>> > process
>> > of moving things over.
>> >
>> > Thanks.
>> >
>> > Michael Glavassevich
>> > XML Parser Development
>> > IBM Toronto Lab
>> > E-mail: [email protected]
>> > E-mail: [email protected]
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: [email protected];  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: [email protected]
> E-mail: [email protected]



-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to