[Npoc-discuss] TIOF - Platform proposal for NPOC

[Raoul Plommer]

Hi Jean.

That sounds good, let's not lose the momentum on this :)

-Raoul

On Mon, 17 Oct 2022 at 12:50, Jean F. Quéralt <JFQueralt at theiofoundation.org>
wrote:

>
>
> Tapani's proposal sounds like a good starting point.
> Should I prepare some small slides for the next call?
>
> Cheers.
>
> Jean F. Queralt
> Founder & CEO - The IO Foundation <http://www.TheIOFoundation.org>
> Book a meeting <http://TIOF.Click/BookJFQ> (30 minutes)
>
>
> On Wed, 12 Oct 2022 at 16:50, Raoul Plommer via Npoc-discuss <
> npoc-discuss at icann.org> wrote:
>
>> Yeah, I agree, let's start with the easiest first and then progress from
>> there. :)
>>
>> On Wed, 12 Oct 2022 at 10:02, Tapani Tarvainen via Npoc-discuss <
>> npoc-discuss at icann.org> wrote:
>>
>>> On Oct 11 22:31, Tapani Tarvainen via Npoc-discuss (
>>> npoc-discuss at icann.org) wrote:
>>>
>>> > First thing I'd want is to have a team of people to manage the
>>> > process.
>>>
>>> Let me qualify that a bit: I think that'd be necessary for a
>>> big overhaul of our platform(s).
>>>
>>> But we could also start with something less ambitious.
>>>
>>> Like, pick up something small and mostly standalone you can implement
>>> quickly without messing with existing website or mailing lists and
>>> just offer to the ExCom and membership on a "try this out" -basis.
>>>
>>> Maybe just take the first three lines from your proposed timeline:
>>>
>>> >>- Make sure ICANN has no issues with automated SocMed
>>> >>- Establish possible tagline/disclaimer for posts
>>> >>- VBout >> SocMed
>>>
>>> That should be fairly easy and doable without waiting for progress
>>> on the other things in your plan.
>>>
>>> Of course there's nothing stopping us from proceeding with other
>>> things in parallel, if our EC thinks them worthwhile and can find
>>> people to do them.
>>>
>>> --
>>> Tapani Tarvainen
>>> _______________________________________________
>>> Npoc-discuss mailing list
>>> Npoc-discuss at icann.org
>>> https://mm.icann.org/mailman/listinfo/npoc-discuss
>>> _______________________________________________
>>> By submitting your personal data, you consent to the processing of your
>>> personal data for purposes of subscribing to this mailing list accordance
>>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy)
>>> and the website Terms of Service (https://www.icann.org/privacy/tos).
>>> You can visit the Mailman link above to change your membership status or
>>> configuration, including unsubscribing, setting digest-style delivery or
>>> disabling delivery altogether (e.g., for a vacation), and so on.
>>>
>> _______________________________________________
>> Npoc-discuss mailing list
>> Npoc-discuss at icann.org
>> https://mm.icann.org/mailman/listinfo/npoc-discuss
>> _______________________________________________
>> By submitting your personal data, you consent to the processing of your
>> personal data for purposes of subscribing to this mailing list accordance
>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
>> the website Terms of Service (https://www.icann.org/privacy/tos). You
>> can visit the Mailman link above to change your membership status or
>> configuration, including unsubscribing, setting digest-style delivery or
>> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
> *DISCLAIMER*
> *The content of this message, which may contain personal or sensitive
> data, is confidential. If you have received it by mistake, please inform
> the sender by replying to the email and then permanently delete the
> message, including any attachments. It is forbidden to copy, forward or in
> any way reveal the content of this message to anyone. The integrity and
> security of this email cannot be guaranteed over the Internet and,
> therefore, the sender will not be held liable for any damage caused by the
> message.*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/npoc-discuss/attachments/20221017/e3252248/attachment.html>