[Npoc-discuss] TIOF - Platform proposal for NPOC

[Raoul Plommer]

Thanks for this Jean!

This'll be a great help in achieving our goals for outreach and membership
engagement. If Bolutife could be working with Jean to make this happen,
that'd be excellent. Then Caleb could possibly show them the ropes and keep
them engaged.

Perhaps it would be an idea to make a little summary of what direction and
which software we'll be taking and present it for our next EC meeting in
two weeks time?

-Raoul

On Mon, 10 Oct 2022, 21:07 Jean F. Quéralt via Npoc-discuss, <
npoc-discuss at icann.org> wrote:

> Dear all,
>
> Following today's call please find the following summary of what was
> discussed on Point 1 concerning the possible adoption by NPOC of some
> platforms:
>
>
> Proposal
>
> Following the conversation we had during the NPOC EC Meeting of 10th
> October 2022, it would appear that we have 2 scenarios to consider:
>
> Note: Privacy considerations are taken for granted across this text. The
> platforms hereby discussed at at least GDPR compliant.
>
> Note 2: An assumption is made that NPOC scheduling its own SocMed posts
> does not enter in conflict with existing ICANN policies. Please let me know
> if that is not the case.
>
> Note 3: Please find the description of the platforms at the end of the
> text.
>
>
> A) Already existing members of NPOC
>
> This scenario considers how to better engage with the existing member base.
>
> It would appear that NCSG has a CRM that only its EC has access to.
>
> Potentially usable software
>
>    - *Matomo*: Obtain understanding on the use of NPOC's website
>    - *VBout*: SocMed automation
>    - *Hexowatch*: Monitor changes on relevant websites
>
> (I understand none of this enters in conflict with ICANN's policies and
> procedures)
>
>
> *Questions:*
>
> Are the existing listservers able to provide templating and more visually
> compelling emails?
>
>
> B) New members that NPOC would like to bring in
>
> This scenario considers how to engage with new organizations/individuals
> to expand the existing member base.
>
> Potentially usable software
>
>    - *Corteza*: Keep a database of prospect organizations & individuals
>    for NPOC (essentially Leads) - Once joined NPOC it seems that the way to go
>    would be to delete the Lead from this CRM and use NCGS's and ICANN's
>    listservers
>    - *Matomo*: Obtain understanding on the use of NPOC's website
>    - *VBout*: Both EDM & SocMed automation
>    - *Hexowatch*: Monitor changes on relevant websites
>
> (I understand none of this enters in conflict with ICANN's policies and
> procedures)
>
>
> Proposed Platforms
>
> *CRM*
>
> *Corteza*
>
> https://cortezaproject.org/
>
> On premise (VPS): Yes
>
> Cost: USD 0 - By itself
>
> Usage (simplified): Database of Contacts, grouped by Accounts.
>
> Collects personal data: Potentially - Will depend on the data schema,
> decided use case scenario and data collection policy.
>
> Time to deploy: 1h
>
> Time to configure: Will vary as decided scenario
>
> Learning curve: Fairly easy to get acquainted with the interface and
> features
>
>
> *Website metrics*
>
> *Matomo*
>
> https://matomo.org/
>
> On premise (VPS): Yes
>
> Cost: USD 0 - By itself
>
> Usage (simplified): Obtain intelligence on website use, users' journeys,
> most & least used areas, etc.
>
> Collects personal data: Potentially - Will depend on the data schema,
> decided use case scenario and data collection policy.
>
> Time to deploy: 1 day
>
> Time to configure: Will vary as decided scenario
>
> Learning curve: Requires some decent knowledge on website metrics
>
>
> *EDM & SocMed automation (Marketing automation)*
>
> *VBout*
>
> https://www.vbout.com/
>
> On premise (VPS): No
>
> Cost: USD 0 - TIOF has a license we can use
>
> Usage (simplified): Automated or on-demand email campaigns to NPOC member
> leads, automate Social Media posts
>
> Potentially - Will depend on the data schema, decided use case scenario
> and data collection policy.
>
> Time to deploy: 0 days
>
> Time to configure: Will vary as decided scenario
>
> Learning curve: Requires some decent knowledge on EDM and basic SocMed
> management. Interface is fairly easy to understand.
>
>
> *Alternative*
>
> *Mautic*
>
> https://www.mautic.org/
>
> On premise (VPS): Yes
>
> Note: ONLY EDM for all I know, no SocMed automation
>
> Cost: USD 0 - By itself
>
> Usage (simplified):
>
> Potentially - Will depend on the data schema, decided use case scenario
> and data collection policy.
>
> Time to deploy: Unknown - I have no actual experience with it
>
> Time to configure: Will vary as decided scenario
>
> Learning curve: Requires some decent knowledge on EDM. I wouldn't know how
> to evaluate the interface as I am not familiar with the product.
>
>
> *URL monitoring*
>
> *Hexowatch*
>
> https://hexowatch.com/
>
> On premise (VPS): No
>
> Cost: USD 0 - TIOF has a license we can use
>
> Usage (simplified): Monitoring (several styles) of relevant URLs and
> automatic notification to the corresponding parties.
>
> Collects personal data: No
>
> Time to deploy: 0 days
>
> Time to configure: About 15 minutes per URL
>
> Learning curve: Doesn't require much other than taking action upon the
> notifications of something having changed. Admin of the URLs will have to
> be made by myself (license limitations) although some spreadsheet
> automation is likely possible (I'd look into it).
>
>
> *Other products we could consider*
>
> SEO monitor
>
> shortURL
>
>
> -------------------------------------------
>
> Do let me know if there's any further questions.
>
> Some members may have other ideas on other areas where we could improve
> our tech stack, in which case let's get the conversation going.
>
> Cheers
>
> Jean F. Queralt
> Founder & CEO - The IO Foundation <http://www.TheIOFoundation.org>
> Book a meeting <http://TIOF.Click/BookJFQ> (30 minutes)
>
> *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.*
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/npoc-discuss/attachments/20221010/02cfdf33/attachment.html>