https://github.com/google/open-location-code/issues/138 - relevant Q/A 
quoted from FAQ.txt should be added to the Wiki FAQ, then this issue be 
closed.

https://github.com/google/open-location-code/issues/161 - four years ago, a 
"Google-internal" discussion was supposedly started to find out where 
expanded functionality should go. If any progress has been made on that 
internal thread, please add the outcome to the issue. If none, the issue 
might as well be closed as "out of scope" for this project.

https://github.com/google/open-location-code/issues/278 - seems as if the 
original question has been answered; unsure if anything needs to be added 
based on the discussion; if not, close this issue - otherwise, let's 
discuss what exactly should be added where.

https://github.com/google/open-location-code/issues/343 - seems as if this 
could be closed, partially because it is out of scope insofar as it 
discusses Google Maps, and on top of that with a reference to the new FAQ 
addition, similar 
to https://github.com/google/open-location-code/issues/497 and other 
recently closed issues.

https://github.com/google/open-location-code/issues/483 - can be closed 
after accepting #502

On Wednesday, October 5, 2022 at 5:10:06 PM UTC+2 Andreas B wrote:

> Hi Roy,
>
> if it is something I can help you with, I'm happy to do that right here on 
> the mailing list. Just open a new conversation with your questions. :)
>
> On Wednesday, October 5, 2022 at 4:27:00 PM UTC+2 shu...@gmail.com wrote:
>
>> I am looking for some guidance on Plus Code implementation. If you can 
>> help please send me an email.
>>
>> Thanks,
>>
>> Roy
>>
>> On Sat, Mar 13, 2021 at 8:36 AM Andreas B <and...@bocops.de> wrote:
>>
>>> Hi everyone, especially Google people,
>>>
>>> is this project still actively maintained? I just replied to someone who 
>>> opened a new issue over on GitHub, and from a short survey it looks as if 
>>> many of the currently open issues are actually resolved (or never were 
>>> proper code issues to begin with) and can be closed.
>>>
>>> Is there any way I could help with that, for example by tagging issues 
>>> as "solved"?
>>>
>>> -- 
>>>
>> Public site: http://www.openlocationcode.com/
>>> Github project: https://github.com/google/open-location-code
>>> Demo site: http://plus.codes/
>>> --- 
>>>
>> You received this message because you are subscribed to the Google Groups 
>>> "Plus Codes Community Forum" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to open-location-c...@googlegroups.com.
>>> To view this discussion on the web, visit 
>>> https://groups.google.com/d/msgid/open-location-code/886cb9ef-afa2-47fc-97db-1172fcbf0657n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/open-location-code/886cb9ef-afa2-47fc-97db-1172fcbf0657n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
Public site: http://www.openlocationcode.com/
Github project: https://github.com/google/open-location-code
Demo site: http://plus.codes/
--- 
You received this message because you are subscribed to the Google Groups "Plus 
Codes Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-location-code+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/open-location-code/a1062369-5e0d-4c27-8a07-7807366f80e3n%40googlegroups.com.

Reply via email to