On Sun, Aug 28, 2011 at 3:23 PM, Dennis E. Hamilton <[email protected] > wrote:
> Kay, > > QUESTION: Are you, or someone you know here, able to assist in the > preservation of the [email protected] for forwarding and in > preservation of the web site (possibly at a part of the podling site that is > targeted by www.openoffice.org) ? > no --sorry. I have very little admin rights on the existing site. > > DISCUSSION > > It was rbircher who did all of that work to move over the /de part of the > site. > > I have three concerns: > > 1. All of the replacement of copyright and license information that > appears to have been done automatically. We are being heavy-handed with > that and need to step back and get clear on what is both legal (I don't > think these sites are in the Oracle grant, although the domain name is > transferred), responsible, and respectful. > > 2. Subject Matter: Looking at the wide variety of pages in the /de > material, for example, I think a great deal of it, perhaps even most of it, > is not particularly appropriate in terms of an Apache project. There is > considerable material which strikes me as "downstream" relative to what > Apache releases release. > Well I have not taken an in-depth look at the "de" site. My feeling is that this is probably one of the more "developed" ones along with maybe 20ish others. > > 3. I thank Rafael for that effort. It gives us a reality check on all > that is involved and how we need to consider some sort of differentiation > between the openoffice.org face to the world and the kind of face to the > world from a development project that is more appropriate on apache.org. > I think both are critical for openoffice.org. > > 3.1 As we find more and more cross-dependencies, I maintain that there is > good cause to preserve and support openoffice.org as the face to (and > from) the broader community of adopters, evangelists/marketers, and > institutions/businesses that are engaged with openoffice.org. > > 3.2 I think both sites are needed, with distinct identities. (I can even > imagine openoffice.org being spun out but I think that is too disruptive > to consider at this time. The community needs some stable footing before we > adjust too much. Just tying to the Apache podling and then the Apache > Top-Level Project is going to be more than enough.) > > 3.3 I'm not sure how a mapping to the wiki would work, but I think it > should be gradual with retargeting of pages on the web site as appropriate. > (My sense is that MediaWiki is up to the task and there can be locked pages > that are not publicly editable.) > Well I truly truly hope we can do re-directs from something like ar.openoffice.org to something like http://ooo-wiki.apache.org/wiki/ar I don't have any idea what will happen with these projects. I want to preserve their content if at all possible but as a wiki presence where these communities can more easily participate without going through the Apache committer process. Right now even though I KNOW about the html to mediawiki tools I have NO idea how well they'd work on the native-lang sites. > > > I am looking at your wiki material with interest. > well have fun! :) > > Thanks, > > - Dennis > > -----Original Message----- > From: Kay Schenk [mailto:[email protected]] > Sent: Sunday, August 28, 2011 14:24 > To: OOo Apache > Subject: [discuss][www][wiki] Native-lang sites was Web, WIki, and > Participation > > Continuing our discussion from Thurs, if you now go to > > https://cwiki.apache.org/confluence/display/OOOUSERS/Site-PPMC-Plan > > and navigate through this "portal", specifically the survey of existing > OOo services, I tried to reorganize some things, and include the web > pages in this overview. > > and, did address some of the "old" questions (topics) in > > > https://cwiki.apache.org/confluence/display/OOOUSERS/OOo-to-ASF-site-recommendation > > So, maybe that will help. > > Now, getting back to Dave's suggestion of > > >>>> When we are ready to consider each OOo project site for conversion we > >>>> should send an email to ooo-dev to determine which way that site > >>>> should go - CMS or Wiki? We can label the thread with > >>>> "[www][${project}]". We can also ask for someone to step up and lead > >>>> the content conversion process for a project. > > Were you thinking about "accepted and/or incubator" projects only or ???? > > There are about 95 native-lang projects. I can’t remember who moved the > "de" site to our current site (not the current de language project > lead), but aside from this, only 1 other native-lang project lead, Maho > NAKATA (japan native lang), has commit rights. > > I would strongly suggest/urge that when the new wiki becomes viable, we > just decide to move the native-lang web areas to the wiki. There are > utilities for converting html to mediawiki markup which I will happily > explore once that become viable. Once these sites get moved, we would of > course contact the project heads about their new home. I don't have any > suggestions about the new "de" site except to leave it as a web site. > > We could contact these leads to see what they want to do, but, even if > they wanted to keep web sites instead of wiki sites, I don't see that > being viable. > > Thoughts? > > > -- > ------------------------------------------------------------------------ > MzK > > "Music expresses that which cannot be said and > on which it is impossible to be silent." > -- Victor Hugo > > -- --------------------------------------------------------------------------------------- MzK "Music expresses that which cannot be said and on which it is impossible to be silent." -- Victor Hugo
