TIOF - Platform proposal for NPOC
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.*
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@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*
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*
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*
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*
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*
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@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.
On Oct 11 00:42, Jean F. Quéralt via Npoc-discuss (npoc-discuss@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.
Well, yes, although as they are only software, their GDPR compliance would depend on the installation and setup. That is, if we host them ourselves we'd have to take care of GDPR requirements by ourselves. Which is not quite trivial, however well the software supports them. There're also other regulations and directives and also non-EU laws that'd have to be considered.
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.
As long as we don't claim ICANN endorsement we can do pretty much anything we want in social media. In some instances we might need to have an explicit disclaimer somewhere to make it clear, that's it.
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.
Yes. CiviCRM. But there's no technical reason why it could not be used by NPOC as well. It could be configured so that NPOC EC (or whoever NPOC delegates to the task) can only see and handle NPOC members there. In practice, it would obviously need NCSG EC approval (I don't think that'd be a big problem) and some amount of work, possibly a lot, on the technical side (CiviCRM is powerful but also complex, not always easy to configure for unusual situations). But given that it already has all the data about NPOC members, it might be worthwhile to investigate its possibilities.
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)
No conflict *if* we undertake to maintain and manage them ourselves without any support from ICANN staff. Given that we can't even manage our regular mailing lists on our own, they're hosted at ICANN's Mailman (unlike NCUC and NCSG's) and administered by ICANN secretaries, I'm not sure we'd be wise to commit to that. Comparing experiences with NCUC and NCSG (who, as noted, are much more independent from ICANN here) might be a good idea. (I know a fair amount of their IT setup, as it happens.) And maybe start by considering how easy it'd be to take over our own mailing lists, so that we could at least update them ourselves even when ICANN staff is on vacation.
*Questions:*
Are the existing listservers able to provide templating and more visually compelling emails?
CiviCRM certainly is (not saying how easily). Mailman, not so much (especially since current ones we use are Mailman version 2).
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
Yes. It'd be an extra step. It should be possible to automate it to some degree, even if it might not be quite trivial. Of course this is also something CiviCRM could do as well.
- *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)
No, with the caveat about staff support noted above.
Proposed Platforms
I won't comment on these now, just noting one key thing:
Time to configure: Will vary as decided scenario
That variation and consequently the time may be quite significant. Also, we'd need to consider long-term maintenance. I'm pretty sure we won't have enough volunteers within NPOC membership to manage any of these for long. I'd love to be proven wrong there, though. How many people do we have who think they both technically could to do this kind of thing and would be able and willing to commit time to do it for several years to come? Otherwise, we'd have to consider commercial support. We might be able to get funding for that from ICANN, but we'd need a pretty good idea of the availability and cost of such support. Either way, such a project would require considerable amount of time and commitment from NPOC ExCom, too. I would advise against being too ambitious. Start with the low-hanging fruit as it were. Say, Social Media automation - simply some tool to automatically copy postings to a number of platforms would be helpful. -- Tapani Tarvainen
On Oct 11 06:22, Jean F. Quéralt (JFQueralt@theiofoundation.org) wrote:
*Well, yes, although as they are only software, their GDPR compliancewould depend on the installation and setup. That is, if we host themourselves we'd have to take care of GDPR requirements by ourselves.Which is not quite trivial, however well the software supports them.There're also other regulations and directives and also non-EU laws that'd have to be considered.*
Agree. Would you have a list of those so we keep them in mind?
No. But some obvious ones would be the ePrivacy directive (and even more so the regulation when and if they get it done), possibly some of the new D*A directives, CCPA (in California)... But even with just GDPR it wouldn't be trivial.
As long as we don't claim ICANN endorsement we can do pretty much anything we want in social media. In some instances we might need to have an explicit disclaimer somewhere to make it clear, that's it.
Noted and makes sense. Maybe NPOC could have a standard statement for it and determine (and document) when it needs to be used?
I don't know. Curiously, NCUC's website has one that looks like it's been dictated by ICANN Legal, but I don't see one at npoc.org. Anyway, this is what NCUC's looks like: "This website is sponsored and operated by the Noncommercial Users Constituency (NCUC). This is not a website supported or operated by the Internet Corporation for Assigned Names & Numbers (ICANN)." Looks good enough to copy (replacing NCUC with NPOC, of course).
*Yes. CiviCRM. But there's no technical reason why it could not be usedby NPOC as well. It could be configured so that NPOC EC (or whoeverNPOC delegates to the task) can only see and handle NPOC members there.*
If they are open to that then indeed.
"They" is actually us, or at least 40% of them as it were: NCSG EC is comprised of two NCUC and two NPOC representatives (me and Caleb) and the Chair (who presently doesn't belong to either, just NCSG). So I dare they NCSG EC would be open to discussing it at least. But of course it would be a question of who would do what and at what cost. I'm not up to date on the situation with CiviCRM there, but last I heard there was a paid support agreement, and using them to do this kind of thing would obviously cost money which NCSG may have better uses for. So it might not be all that easy regardless of any, er, political will. But an option worth investigating. Perhaps NCUC could see use for similar tools for themselves, too.
I am not acquainted with CiviCRM at admin level so I don't believe I could help on this.
You could learn. :-)
*No conflict *if* we undertake to maintain and manage them ourselves without any support from ICANN staff. Given that we can't even manageour regular mailing lists on our own, they're hosted at ICANN's Mailman (unlike NCUC and NCSG's) and administered by ICANN secretaries, I'm not sure we'd be wise to commit to that.*
The idea would be to have some time of balance between "what ICANN enforces" and "what NPOC needs to do".
ICANN *enforces* very little. They only put conditions on their support. Which admittedly may amount to the same thing, given that NPOC doesn't have much money of its own (as far as I know).
(In other words, NPOC should make sure to remain independent by hosting its own products and under its own licensing control.)
Yeah. NCUC does that, sort of, with their own VPS. They still rely on ICANN staff (Andrea and Brenda, I believe) for managing them. NCSG's situation is more complex, but most of NCSG's mailing stuff, in particular mailing lists are hosted outside ICANN, too.
*And maybe start by considering how easy it'd be to take overour own mailing lists, so that we could at least update themourselves even when ICANN staff is on vacation.*
Is there an ICANN regulation here that would stop NPOC from doing so?
I seem to recall ICANN didn't want to give administration rights to mailing lists it hosts to anybody but their staff. That might be worth confirming, perhaps it could be negotiated. But even if they did, there's the consideration that led NCSG and NCUC avoid ICANN-hosted lists: the threat that ICANN might censor them. There was some discussion about that way back: ICANN implied that they might have to filter some messages that might have legal implications, as ICANN could then be held liable.
Yes, my position is that we need to find ways for NPOC to handle these things.
It would be nice, yes. But perhaps not so easy.
*Also, we'd need to consider long-term maintenance. I'm pretty surewe won't have enough volunteers within NPOC membership to manage any of these for long. I'd love to be proven wrong there, though.*
This is a forever problem that we need to address indeed. For the time being I can take care of the stuff we implement and thus to not over saturate me we would establish an implementation timeline and take it one step at a time.
Depending on any single individual is not really sustainable.
*How many people do we have who think they both technically could todo this kind of thing and would be able and willing to commit timeto do it for several years to come?*
We do need to answer that and maybe that's something members can take care of (to offload EC - and obviously depending on which tasks according to privacy, etc.).
Maybe.
*Otherwise, we'd have to consider commercial support. We might beable to get funding for that from ICANN, but we'd need a pretty good idea of the availability and cost of such support.*
Pay me!!
Paying you won't make it any easier if you're still just one man. If you have a company with several employees doing such support it'd be different.
*Either way, such a project would require considerable amount of time and commitment from NPOC ExCom, too.*
How so?
Mostly all these would be tools for the ExCom to use. They'd have to be involved in their setup and customization, be trained in their use &c. At least you'd need one EC member closely involved in the process.
If we decide to move forward a sensible timeline would something along this lines (with the info I have so far):
While your timeline looked reasonable I cut it off because I think it's a bit too early to do that. First thing I'd want is to have a team of people to manage the process. Including at least one, preferably two from the EC, to oversee it and also to act as a guinea pig as it were, trying things out to see if they'd work for the EC &c, and more than one person actually doing the thing (it should not be just you). Someone should also liaise with NCSG and NCUC. But of course I'm not in a position to decide anything, I'm just commenting from the side. Decisions are up to the EC to make. -- Tapani Tarvainen
On Oct 11 22:31, Tapani Tarvainen via Npoc-discuss (npoc-discuss@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
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@icann.org> wrote:
On Oct 11 22:31, Tapani Tarvainen via Npoc-discuss (npoc-discuss@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@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.
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@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@icann.org> wrote:
On Oct 11 22:31, Tapani Tarvainen via Npoc-discuss ( npoc-discuss@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@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@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.*
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@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@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@icann.org> wrote:
On Oct 11 22:31, Tapani Tarvainen via Npoc-discuss ( npoc-discuss@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@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@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.*
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.
Totally works for me.
-- Tapani Tarvainen _______________________________________________ Npoc-discuss mailing list Npoc-discuss@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.*
Hi Jean, Thanks again for your email and taking the time to share with us on the call yesterday, your suggestions are really insightful and we hope to adopt some of these tools you recommended. In the meantime, I will liaise with the EC and staff to see what restrictions and data regulations we should be mindful of and get back to you afterwards. Best - Bolutife
On 10. Oct 2022, at 20:07, Jean F. Quéralt via Npoc-discuss <npoc-discuss@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
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
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
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
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
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 Book a meeting (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@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.
Excellent. Thx Bolutife. Best, Jean F. Queralt Founder & CEO - The IO Foundation <http://www.TheIOFoundation.org> Book a meeting <http://TIOF.Click/BookJFQ> (30 minutes) On Tue, 11 Oct 2022 at 16:39, Bolutife Adisa <adisabolutifeo@gmail.com> wrote:
Hi Jean,
Thanks again for your email and taking the time to share with us on the call yesterday, your suggestions are really insightful and we hope to adopt some of these tools you recommended.
In the meantime, I will liaise with the EC and staff to see what restrictions and data regulations we should be mindful of and get back to you afterwards.
Best - Bolutife
On 10. Oct 2022, at 20:07, Jean F. Quéralt via Npoc-discuss < npoc-discuss@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*
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*
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*
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*
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*
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@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.*
participants (4)
-
Bolutife Adisa -
Jean F. Quéralt -
Raoul Plommer -
Tapani Tarvainen