On 7/30/14, Kay Schenk <kay.sch...@gmail.com> wrote: > > > On 07/30/2014 12:02 PM, Alexandro Colorado wrote: >> On 7/30/14, Kay Schenk <kay.sch...@gmail.com> wrote: >>> >>> >>> On 07/30/2014 11:05 AM, Marcus (OOo) wrote: >>>> Am 07/28/2014 09:43 PM, schrieb Marcus (OOo): >>>>> Am 07/28/2014 07:07 PM, schrieb Kay Schenk: >>>>>> >>>>>> >>>>>> On 07/28/2014 01:05 AM, Tal Daniel wrote: >>>>>>> On Mon, Jul 28, 2014 at 2:35 AM, Kay Schenk<kay.sch...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 07/26/2014 10:16 PM, Tal Daniel wrote: >>>>>>>>> Don't you think this page should exist elsewhere, not on the site? >>>>>>>>> maybe >>>>>>>> on >>>>>>>>> openoffice.apache.org> native language section? It's feels as a >>>>>>>>> status >>>>>>>>> page, rather than a page for visitors. >>>>>>>>> >>>>>>>>> Tal >>>>>>>> >>>>>>>> I think it's just where it is for historical purposes, and I see >>>>>>>> your >>>>>>>> point. We can move it. >>>>>>>> >>>>>>>> Anyway, my "new" version is at: >>>>>>>> >>>>>>>> http://ooo-site.staging.apache.org/projects/native-lang-new.html >>>>>>>> >>>>>>>> Even after I suggested it, I'm not sure I'm 100% happy with my >>>>>>>> simpler >>>>>>>> definitions. See the definition for "maintained". The download >>>>>>>> links >>>>>>>> from these pages work, but some are NOT to a localized download due >>>>>>>> to >>>>>>>> editing (by me some weeks ago) to at least get them to some correct >>>>>>>> download area. :/ So, what to do with these gray areas? >>>>>>> >>>>>>> >>>>>>> Nonactive/non-maintained websites will, eventually, be removed from >>>>>>> the >>>>>>> language selection box;a call for volunteers is also appropriate, in >>>>>>> order >>>>>>> to revive such a website (another column?) >>>>>> >>>>>> yes... >>>>> >>>>> choosing the language from the drop-down-box is a fast and cheap way >>>>> to >>>>> come to unmaintained webpages that have the large hint (we have to >>>>> make >>>>> this sure) to help to get it complete again. >>>>> >>>>> So, I think it would not be good to delete it from the selection. >>>>> >>>>>> Ok, I just changed the definitions slightly and corrected some errors >>>>>> I'd made in assessment yesterday as well. This needs another pair of >>>>>> eyes! >>>>>> >>>>>> again, at: >>>>>> http://ooo-site.staging.apache.org/projects/native-lang-new.html >>>>> >>>>> Maybe we should take the content (current or outdated) and the work on >>>>> it (maintained or help wanted) into account? With this we can say, >>>>> e.g., >>>>> "outdated + maintained". This means that the content is old but there >>>>> is >>>>> someone who is working on updates. >>>>> >>>>> Here my further idea: >>>>> >>>>> current The website is OK and needs no help. >>>>> >>>>> outdated The website has old content and needs to be updated. >>>>> >>>>> maintained Someone is already actively working on the website. >>>>> >>>>> help wanted Volunteers are welcome to help updating the website. >>>> >>>> the discussion about formatting is all fine and all good. But without >>>> content is doesn't matter, right? ;-) >>>> >>>> Please can we first finalize the content. Then we can beautifying the >>>> webpage step by step. >>>> >>>> Thanks >>>> >>>> Marcus >>> >>> That would be nice! :) >>> >>> I just put the page with the changes I made recently into production at: >>> >>> http://www.openoffice.org/projects/native-lang-new.html >> >> Not sure how that is necesarry thats why we have a staging site. I >> would publish the current mdtext, and then see the next changes on >> staging. > > Maybe a bit of an explanation. I published the mdtext but it gets > converted to html on publication. The mdtext had been in stating for a > few days. This is still only a "working" document since it is not the > one being linked, and I thought for non-committers, this way might be > easier. Maybe I'm wrong about that.
I am mostly on a KISS (Keep it simple stupid) creating '-new' documents are mostly a bad idea since is not surprise we have a lot of '*-new' documents somewhat polluting the site tree. Non-commiters can always post their version on their hosts (I try to use people.apache.org) but there is always space on google drive, or github to put your version with your tweaks, maybe is a good test case to move to GIT and work with branches. I suggest checking out gitflow for a good workflow system when dealing with git commiters. >> >>> >>> so it should be easy for others to make further changes. >>> >>> As usual, older versions can be had from svn -- >>> >>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/projects/native-lang.mdtext?view=log >>> >>> I'm not sure how long it takes for the latest revision to show up in >>> this list. >>> >>> >>> >>> >>> >>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >>> >>> -- >>> ------------------------------------------------------------------------- >>> MzK >>> >>> "To be trusted is a greater compliment than being loved." >>> -- George MacDonald >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >> >> > > -- > ------------------------------------------------------------------------- > MzK > > "To be trusted is a greater compliment than being loved." > -- George MacDonald > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
