It looks like we did not have a resolution to this issue yet, shall we vote on this?
On Fri, Jul 27, 2018 at 1:55 AM, Cameron Shorter <[email protected]> wrote: > When it comes to giving credit, I think there are a number of factors to > consider: > * What is the cost to us in maintaining a current list of supporters long > term? The supporter list is only valuable if it is known to be kept up to > date. > * What value do we gain by recognising the supporters? Eg: Saying that > hundreds of people have contributed to OSGeoLive is a level of endorsement > which has marketing value. > * What value do we provide to the supporters we mention? Mentioning an > individual developer or a small geospatial company would provide marketing > value whereas mentioning Google Translate would likely have much less > proportional value. Lets not waste our time maintaining a supporter list if > the supporters don't appreciate the service we provide. > * What contribution is worthy of mention? If we make everyone special, > then no one is special. We run the risk of weakening the value of our > endorsement by endorsing everyone who asks for it. (Same goes for which > projects we accept into OSGeoLive). The hardest part is working out how to > say "No" nicely. It is best to have clear criteria which can be referenced. > > At the moment, I don't think Leopark fits into the criteria we have > applied to existing OSGeoLive sponsors. (Roughly, organisations which have > are providing developer time and/or resources for core OSGeoLive > activities). We haven't written this criteria down or talked about it much. > > We might want to create a criteria for "Supporters", as Jeff suggests. But > I see this a long term activity as it will take some discussion, and then > inviting groups to be included, then adding then .... > > > > On 27 July 2018 at 03:22, Vicky Vergara <[email protected]> wrote: > >> Hi Cameron: >> >> >> I think, >> if a company, no matter which company, lets us use some of the >> resources, in this case their Azure account, lets give them credit for >> doing so. >> >> I added you to the Spanish translation group >> Please evaluate: >> https://www.transifex.com/osgeo/osgeolive/translate/#es/quic >> kstart--ideditor_quickstart/124084168 >> >> >> Up to this line the decision should be made. >> >> I would like to say *trust* on what OSGeoLive PSC members ask. >> >> Regards >> Vicky >> >> >> >> >> >> >> >> >> On Thu, Jul 26, 2018 at 5:30 AM, Cameron Shorter < >> [email protected]> wrote: >> >>> Hi Vicky, I would like some background information before forming my >>> opinion on this proposal. >>> If we are to give leopark special mention, how does it stand out when >>> compared to other projects. Eg: If someone uses Google Translate, should we >>> also mention Google Translate? >>> What does Leopark gain by being mentioned? Have they requested to be >>> mentioned? >>> >>> On 25 July 2018 at 01:45, Nicolas Roelandt <[email protected]> >>> wrote: >>> >>>> Hi thanks Vicky, >>>> >>>> I do use it too when no pre-existing translation is not available and I >>>> don't know the project. >>>> >>>> Cheers, >>>> >>>> Nicolas >>>> >>>> >>>> Le lun. 23 juil. 2018 à 23:31, Vicky Vergara <[email protected]> a >>>> écrit : >>>> >>>>> >>>>> Hi all, >>>>> Since osgeolive has been in transifex, leopark let us use the >>>>> "translation code" to do machine translations, I would like to add it as >>>>> sponsor (could be a sponsor on the translations section of sponsors). >>>>> >>>>> Who does not use it: >>>>> English speaking only people, don't use it. because there is no need >>>>> to translate. >>>>> Languages that maybe were mostly translated, and every time the file >>>>> changed, they retranslated, and just copied/pasted old translation, might >>>>> have not used it. >>>>> >>>>> From who I know that use it (for spanish): >>>>> The students from the ENAH (archeology students) use it (so says >>>>> MarPetra <https://www.transifex.com/user/profile/MarPetra/>) >>>>> specially because they don't know the terminology used on the software. >>>>> I do use it, (as Spanish translation was incomplete, and not up to >>>>> date). >>>>> >>>>> Please comment >>>>> >>>>> Vicky >>>>> >>>>> >>>>> -- >>>>> >>>>> Georepublic UG (haftungsbeschränkt) >>>>> Salzmannstraße 44, >>>>> 81739 München, Germany >>>>> >>>>> Vicky Vergara >>>>> Operations Research >>>>> >>>>> eMail: [email protected] >>>>> Web: https://georepublic.info >>>>> >>>>> Tel: +49 (089) 4161 7698-1 >>>>> Fax: +49 (089) 4161 7698-9 >>>>> >>>>> Commercial register: Amtsgericht München, HRB 181428 >>>>> CEO: Daniel Kastl >>>>> >>>>> >>>>> _______________________________________________ >>>>> osgeolive mailing list >>>>> [email protected] >>>>> https://lists.osgeo.org/mailman/listinfo/osgeolive >>>>> >>>> >>>> _______________________________________________ >>>> osgeolive mailing list >>>> [email protected] >>>> https://lists.osgeo.org/mailman/listinfo/osgeolive >>>> >>>> >>> >>> >>> -- >>> Cameron Shorter >>> Technology Demystifier >>> Open Technologies and Geospatial Consultant >>> >>> M +61 (0) 419 142 254 >>> >>> >>> >>> >>> _______________________________________________ >>> osgeolive mailing list >>> [email protected] >>> https://lists.osgeo.org/mailman/listinfo/osgeolive >>> >>> >> >> >> -- >> >> Georepublic UG (haftungsbeschränkt) >> Salzmannstraße 44, >> 81739 München, Germany >> >> Vicky Vergara >> Operations Research >> >> eMail: [email protected] >> Web: https://georepublic.info >> >> Tel: +49 (089) 4161 7698-1 >> Fax: +49 (089) 4161 7698-9 >> >> Commercial register: Amtsgericht München, HRB 181428 >> CEO: Daniel Kastl >> >> >> > > > -- > Cameron Shorter > Technology Demystifier > Open Technologies and Geospatial Consultant > > M +61 (0) 419 142 254 > > > > > _______________________________________________ > osgeolive mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/osgeolive > > -- Angelos Tzotsos, PhD OSGeo Charter Member http://users.ntua.gr/tzotsos
_______________________________________________ osgeolive mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/osgeolive
